# Mimeo documentation Documentation for Mimeo — how to run your email operation from the web UI, and how your coding agent drives it through the API. Mimeo is email automation you own: self-hosted, single-tenant software. One install, one customer — yours. These docs cover both halves of how you run it: the web UI you click through, and the API your coding agent talks to. A note on names: when these docs say **Mimeo**, they mean *your* Mimeo — your own instance of the app, holding only your data. It runs on your own server, on the domain you choose. New here? Start with [Getting started](https://mimeohq.com/docs/usage/getting-started) — download the software, set up sending, and prepare your first audience. Then [How it fits together](https://mimeohq.com/docs/how-it-fits/) is the five-minute map of the pieces, and the [glossary](https://mimeohq.com/docs/glossary/) has every term. Prices, what the license includes and what you need to run it are on the [Pricing page](https://mimeohq.com/pricing). What changed in each release is in the [changelog](https://mimeohq.com/changelog/) and the [release notes](https://mimeohq.com/release-notes). ## Browse the docs - [Getting started](https://mimeohq.com/docs/usage/getting-started): Download Mimeo and Mimeo Manager from your account, connect sending and media, and test your setup. - [Deploy Mimeo](https://mimeohq.com/docs/usage/deploy): Run the Rails app on your server with Hatchbox and DigitalOcean, or use another Rails host. - [Migrating from another email platform](https://mimeohq.com/docs/usage/migrating): Preserve suppressions, move engaged cohorts first, and transition over three newsletters without duplicate sends. - [Usage](https://mimeohq.com/docs/usage/): Working in the app: people, CSV import, authoring emails, and connecting a sending provider. - [API](https://mimeohq.com/docs/api/): The HTTP interface your agent and your app use: events, people, flows, emails, sequences, broadcasts and the manager repo's definition files. - [MCP server](https://mimeohq.com/docs/mcp/): A native tool surface for coding agents, running on your Mimeo. Add it to Claude Code with one command. - [Let an AI agent run your email without accidental sends](https://mimeohq.com/guides/agent-safe-email): Prompts for your agent, rehearsals, guards and test sends, with real screens from a local install. - [Move from Mailchimp or Kit without emailing people who opted out](https://mimeohq.com/guides/migrate-from-mailchimp-or-kit): Import your opt-outs first, then your list, with nothing triggered, tested on a local install. - [Manager repo](https://mimeohq.com/docs/manager-repo/): Your whole operation as files in a git repo you own — pulled, edited and pushed back by the bundled CLI, never by git. ## How Mimeo is put together Your Mimeo instance owns the data and the logic — people, custom fields, tags, events, money history, emails, templates, tracking, and the send log all live in your own database. A pluggable **sending provider** handles delivery to the inbox. The **Sending & domains** section starts with [Set up sending](https://mimeohq.com/docs/providers/setup): connect [Resend](https://mimeohq.com/docs/providers/resend), the simplest starting point, or [Postmark](https://mimeohq.com/docs/providers/postmark), then put the links inside every message on your own [connected sending domain](https://mimeohq.com/docs/usage/domains-and-senders). Everything that enters Mimeo from outside — a signup, a purchase, a renewal, an opt-in — arrives as an [event](https://mimeohq.com/docs/api/events). That one endpoint upserts the person, records first-touch attribution, appends to their timeline, and writes the money tables. If you learn one thing about the API, learn the event contract. ## What Mimeo includes {#whats-here-today} Mimeo includes people management and GDPR tooling, CSV import, custom fields and tags, the email library and editor with templates and previews, open and click tracking, the event API, and the subscription-management API — plus the whole automation engine: [sequences](https://mimeohq.com/docs/usage/sequences), [flows](https://mimeohq.com/docs/usage/flows) with dry runs and versions, the [scheduled queue](https://mimeohq.com/docs/usage/queue), [guards](https://mimeohq.com/docs/usage/guards), send windows, and the [flow API](https://mimeohq.com/docs/api/flows). And the daily-driver console: [segments](https://mimeohq.com/docs/usage/segments) with watchdogs, [broadcasts](https://mimeohq.com/docs/usage/broadcasts), [reporting](https://mimeohq.com/docs/usage/reporting) across emails, sequences, flows and broadcasts, [the activity feed and event registry](https://mimeohq.com/docs/usage/events), [the dashboard](https://mimeohq.com/docs/usage/dashboard), and [keyboard-first navigation](https://mimeohq.com/docs/usage/keyboard). **The agent surface** is here too: [the CLI](https://mimeohq.com/docs/cli/) and a manager repo for anything you want reviewed as a diff, [the MCP server](https://mimeohq.com/docs/mcp/) for questions and one-off changes, [the manager repo](https://mimeohq.com/docs/manager-repo/) that carries both, and [the reference section](https://mimeohq.com/docs/reference/) — the flow schema, the event contract, the repo layout and how to write your own sending adapter — written so an agent can operate a Mimeo from the docs alone.