{feature.title}
+{feature.body}
+Architecture
++ The API layer receives mail requests, auth validates tokens, templates render branded HTML, + and the queue worker ships through SMTP. +
+Workflow
++ Mailify keeps the request path boring: exchange an API key for a JWT, send a template id, + let the queue handle the actual SMTP work. +
+{snippet}
+ Why Mailify
+{feature.body}
+Self-hosted. Theme-aware. Rust-fast.
++ Self-hosted transactional mail with your colors, your templates, and your SMTP provider. + One Docker image. Zero vendor lock-in. +
+ + + +Theme system
++ Mailify’s default templates read from a theme object at render time, so brand changes stay + in config instead of leaking into every mail template. +
+ +primaryaccentsuccess+ Swap colors and logo once, then keep shipping the same templates across environments and + tenants. +
+ Open dashboard + +404
++ This URL didn't match any page on mailify.donilite.me. Maybe it's been renamed, + maybe it never existed. +
+ +Pricing
++ Mailify is MIT-licensed and lives entirely in your infrastructure. There is no + Mailify-Cloud tier, no usage cap, no per-seat fee. The only costs you pay are the + ones you would pay anyway: an SMTP provider and a small server. +
+Always
+What you actually pay for
++ Most teams run it for under $20/month all-in. A 0.25 vCPU container plus a + managed Postgres is enough for thousands of sends per minute. +
++ Star the repo. File a great bug report. Open a PR. Tell a friend. + Sponsorship channels are coming soon. +
+ +