mesahub replaces your local Docker volume with a managed cloud SQLite database. One connection string change — zero volume management, zero backups to configure, accessible from anywhere.
Local Docker volumes are fragile — one docker compose down -v and your templates,
API keys, and logs are gone. mesahub gives your EmailFlare data a permanent home.
Local volumes disappear when containers are recreated. mesahub persists your database in the cloud — restart, redeploy, or migrate servers without losing anything.
mesahub handles backups automatically. You don't need to configure cron jobs, S3 bucket policies, or volume snapshot schedules. Your data is safe by default.
Switch from local to cloud storage by updating a single environment variable. No schema changes, no data migration tools — just update DATABASE_URL in your .env.local.
With a local volume, your EmailFlare database is locked to one machine. mesahub lets you read your data from any environment — staging, production, CI pipelines.
Running multiple EmailFlare instances behind a load balancer? A shared mesahub database means consistent templates, keys, and domain state across all your containers.
Platform restarts on Railway and Fly ephemeral storage make local volumes impractical. mesahub is the natural persistent storage layer for these PaaS deployments.
Both options work with EmailFlare. Choose embedded for local development and simple single-server deploys; choose mesahub for everything else.
SQLite file lives on disk, mounted as a Docker volume. Simple for development and single-server setups.
Managed SQLite in the cloud. One connection string replaces your local volume with persistent cloud storage.
Switch from a local Docker volume to mesahub cloud storage in minutes. Your data, templates, and API keys migrate automatically.
Sign up at mesahub.app. Create a new database — call it emailflare or anything you like.
After creating the database, mesahub shows you a connection string in the format below. Copy it — you'll use it in the next step.
Replace the local database path with your mesahub connection string. Stop your existing EmailFlare container first so the migration can run cleanly on the next start.
Bring the container back up. EmailFlare will run database migrations against your mesahub database automatically on startup.
Open the admin UI — your templates, domains, and keys should be intact if you migrated an existing deployment, or ready to configure if starting fresh.