Running a proper mail server used to mean stitching together half a dozen daemons; maddy folds the whole stack into one binary with one configuration file. It receives mail as your MX, sends as your MTA, stores messages for IMAP clients, and signs and verifies with DKIM, SPF, DMARC, DANE, and MTA-STS so other servers actually trust what you send. The design is composable: checks, modifiers, tables, and delivery targets snap together in the config, so spam scoring, address rewriting, and routing rules read like a pipeline instead of a pile of interlocking config files. Outbound mail queues with retries and backoff, inbound delivery lands in IMAP storage backed by SQLite or PostgreSQL, and a built-in ACME client keeps TLS certificates renewed, including DNS-01 providers. Milter support lets existing filters join the pipeline, authentication spans SASL mechanisms and Dovecot delegation, and Prometheus metrics watch queue length and delivery health from your usual dashboards. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. GPL-3.0 licensed.