What is Maiilo?

Maiilo is an email template management platform: a CMS for your email templates. You build templates in Maiilo, publish them as fixed versions, and then serve those versions to your application through the API or push them to your email service provider (ESP). What you publish is exactly what ships, until you publish again.

The problem it solves

Email templates tend to drift. The copy in your ESP no longer matches the file in your repo, a shared footer gets edited in one place and not another, and nobody can say which version a customer actually received. Maiilo keeps one source of truth for every template and records every version you ship.

How Maiilo works

1. Build. Design a template in the drag-and-drop builder, or bring your own HTML. Your work is saved automatically as a draft.
2. Publish. Publishing freezes the draft into a numbered, immutable version (v1, v2, v3…). Editing the draft afterwards does not change the published version.
3. Serve or push. Your application fetches the published version from the Maiilo API, or you push it to SendGrid. Both always receive the frozen published version, never the draft you are working on.

What makes it different from an email builder

A builder stops once you export the HTML. Maiilo keeps managing the template after that:

• Versioned publishing. Every publish creates an immutable version. The API and your ESP serve that exact version, byte for byte. See Publishing and versions.
• Version history and rollback. See who published each version and when, and restore any earlier version into your draft. See History and rollback.
• Shared blocks that sync deliberately. Edit a shared footer once, and Maiilo lists every template that needs re-publishing. Published output never changes silently. See Shared blocks.
• ESP push with drift detection. Push a published version to SendGrid, and Maiilo tells you when SendGrid falls behind your latest publish. See SendGrid.
• An API for your application. Fetch the published HTML, subject and variables of any template. See the API reference.

Who it is for

• Developers who send transactional email (receipts, password resets, welcome emails) from their own code and want templates they can edit without a deploy.
• Teams where a designer or marketer edits templates and a developer fetches them via API.
• Anyone maintaining the same templates across products or ESPs who needs to know which version is live where.

What Maiilo does not do

Maiilo does not send email and does not store contacts. Sending stays with your application or your ESP. Maiilo manages the templates you send.

Next steps

• Quickstart: build, publish, and fetch your first template.
• Plans: what Free and Pro include.