MariaDB
The community MySQL fork, as a single self-hosted node - drop-in compatible, on a flat plan.
One-click deploy, from $7/mo on a Miget plan.
MariaDB is the community-developed fork of MySQL, drop-in compatible for the vast majority of applications and a popular default across CMSes, frameworks, and self-hosted apps. This template is a single MariaDB 11.8 node configured through the official image`s environment variables, with data on a volume.
It runs internal-only on Miget - apps connect at mariadb:3306, and an app database and user are created on first boot. Miget offers managed MySQL for hands-off operation; run this when you specifically want MariaDB or full control of the configuration.
MariaDB has a rich HA story, and the catalogue covers all of it: this standalone node, mariadb-replication (asynchronous primary/replica), and mariadb-galera (synchronous multi-primary cluster).
Upstream project: MariaDB
#what you get
- MariaDB 11.8, the community MySQL fork
- Drop-in compatible with MySQL for most apps
- Configured entirely by environment variables
- App database + user created on first boot
- Internal-only - reached at mariadb:3306
- GPLv2
#topology
| Service | Role | Public |
|---|---|---|
| mariadb | relational database (:3306) | no (internal) |
#miget sizing
// this stack needs
1 GiB RAM · 10 GB disk · 1 service
1 GiB suits typical workloads; raise for larger buffer pools. A single node is not HA - see mariadb-replication or mariadb-galera.
Hobby - recommended fit
$7/mo
1 vCPU · 1 GiB · 25 GiB disk
Headroom for your own apps: 2 GiB at $13/mo
Professional - production
$22/mo
1 vCPU · 2 GiB · 10 GiB disk
Dedicated resources, production SLOs - plan details
One Miget plan is a fixed pool of compute - the whole stack (managed databases included) deploys inside it, and anything left over runs your other apps. No per-service or per-seat math.
#vs. the managed service
What the hosted equivalents charge, against the flat Miget plan this stack fits on. Prices as of June 2026, sources linked.
| Service | Plan | Monthly | What you get |
|---|---|---|---|
| MariaDB on Miget ★ | 1 GiB plan | $7 | this whole stack, flat - no usage meters, and room left for your own apps |
| AWS RDS for MariaDB | db.t4g.micro | ~$15 | smallest single-AZ instance/mo + storage |
| Aiven for MySQL | Startup | ~$31 | smallest managed plan/mo |
Managed MariaDB/MySQL bills per instance; self-hosted is one flat plan.
#vs. other PaaS
Estimated monthly cost of running this exact stack (1 GiB RAM, 10 GB disk, 1 container) elsewhere, from published June 2026 rates.
| Platform | Est. monthly | Notes |
|---|---|---|
| Miget ★ | $7 flat | compose stacks first-class: one deploy, dedicated vCPU, managed Postgres/Valkey, volumes and TLS all included in the plan |
| Heroku | ~$50 | no volumes; nothing between 1 GB ($50) and 2.5 GB ($250) dynos - 2 GB containers cost far more than shown |
| DO App Platform | ~$17 | no persistent volumes - stateful containers need managed DBs/Spaces (base $5 Spaces included here) |
| Render | ~$15 | per-service instances (0.5 GB $7, 2 GB $25) - every container is its own paid service |
| Railway | ~$12 | usage-based ($10/GB RAM-mo); vCPU billed separately at $20/vCPU-mo on top |
| Fly.io | ~$7 | cheapest sticker price - but burstable shared CPUs (1/16 core; dedicated vCPUs cost ~2-3×), no compose deploys (one app per container, manual wiring), managed DBs billed extra |
Estimates assume RAM fully allocated at published on-demand rates - and sticker price isn't the whole comparison: the cheaper rows buy burstable shared CPUs, per-service wiring instead of a compose deploy, and managed databases billed separately. Heroku and DO App Platform have no persistent volumes at all - stateful stacks like this one need workarounds there.
#deploy it
On Miget
- Create a Compose Stack in app.miget.com pointing at the templates repository
- Set the stack path to
mariadb -
Set the required variables:
MARIADB_ROOT_PASSWORD, root passwordMARIADB_PASSWORD, password for the app user
- Deploy. Miget layers
compose.miget.yaml(RAM, privacy, volumes, managed services) automatically
Locally first?
Every template is portable, vanilla Docker Compose - the Miget overrides are ignored locally:
git clone https://github.com/deployable-sh/stacks
cd miget-compose-templates/mariadb
docker compose up -dSame files, same behavior. The template README covers connection strings and scaling notes.
#faq
Is MariaDB compatible with MySQL?
For the large majority of applications, yes - same SQL, same wire protocol, same clients. There are version-specific differences in newer features, but typical CMS/app workloads run unchanged on either.
What HA options does the catalogue offer?
Three modes: this standalone node, mariadb-replication (asynchronous primary/replica for read-scaling and hot standby), and mariadb-galera (synchronous multi-primary cluster where any node accepts writes).
Managed MySQL or this?
Managed MySQL is simpler to operate. Choose this MariaDB template when you specifically want MariaDB, a particular version, or custom server configuration.
Ship MariaDB today
One compose stack, 1 GiB of RAM, from $7/month flat, and it runs on your laptop with the same files.