EmailFlare ships with embedded SQLite that persists through a Docker volume. It works — but volumes require backup discipline and tie your data to the container's host. mesahub gives you durable, cloud-hosted SQLite with a one-line config change.
Embedded SQLite is excellent for getting started. mesahub cloud storage is what you want when deployment reliability and data portability start to matter.
No Docker volumes to configure, mount, snapshot, or restore. Your data lives in mesahub — independent of any container lifecycle.
Redeploy, restart, or migrate your EmailFlare container without any data loss. The URL stays the same — just point the new container at it.
Switch from embedded to cloud by updating a single environment variable. No schema changes, no data migration commands, no downtime.
Your EmailFlare data is accessible to any container or environment that has your mesahub URL. Move between Railway, Fly, Docker, wherever.
mesahub handles persistence, replication, and backups on its side. You stop worrying about "did the volume survive that deploy?"
mesahub uses SQLite under the hood — the same engine EmailFlare is built around. No query compatibility surprises, no ORM rewrites.
SQLite stored inside the container, persisted via a Docker volume.
SQLite hosted and managed by mesahub. Accessible over HTTP from any container.
The entire migration is a single environment variable update. No schema changes, no data exports.
Visit mesahub.app and sign up for an account. mesahub is built by the same team behind EmailFlare.
From your mesahub dashboard, create a new database. Give it a recognisable name —
something like emailflare-production or emailflare-staging.
Copy the database slug shown after creation.
In your mesahub account settings, generate a new API key.
The key will start with shs_. Copy it now — it is shown once.
Replace the embedded URL in your .env.local (or platform environment settings)
with the mesahub connection URL:
Redeploy your EmailFlare container. On first boot, EmailFlare will bootstrap the
schema in the mesahub database automatically — the same CREATE TABLE IF NOT EXISTS
process as with the embedded path. No migration commands needed.