Databases 1 service 1 GiB RAM 10 GB disk

Percona Server

A drop-in MySQL replacement with deeper instrumentation and performance tuning, single node.

Deploy to Miget View template source

One-click deploy, from $7/mo on a Miget plan.

Percona Server for MySQL is a free, fully MySQL-compatible drop-in with extra instrumentation (expanded INFORMATION_SCHEMA and PERFORMANCE_SCHEMA tables), better diagnostics, and performance enhancements - the same SQL and clients as MySQL, with more visibility into what the server is doing.

This template is a single node configured with the same MYSQL_* environment variables as the MySQL template, internal-only on Miget (apps connect at percona:3306), with an app database and user created on first boot.

Choose Percona Server when you want its instrumentation and tuning for a single database; for synchronous multi-primary high availability, the catalogue has percona-xtradb-cluster.

Upstream project: Percona Server for MySQL

#what you get

  • Fully MySQL-compatible - same SQL, protocol, and clients
  • Expanded instrumentation and diagnostics
  • Performance and operational enhancements
  • Same MYSQL_* env vars as the MySQL template
  • Internal-only - reached at percona:3306
  • GPLv2

#topology

ServiceRolePublic
perconarelational 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 percona-xtradb-cluster.

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.

ServicePlanMonthlyWhat you get
Percona Server on Miget ★1 GiB plan$7this whole stack, flat - no usage meters, and room left for your own apps
AWS RDSdb.t4g.micro~$15smallest single-AZ MySQL instance/mo + storage

No managed cloud offers Percona Server instrumentation on a small flat plan; self-hosting does.

#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.

PlatformEst. monthlyNotes
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

  1. Create a Compose Stack in app.miget.com pointing at the templates repository
  2. Set the stack path to percona-server
  3. Set the required variables:
    • MYSQL_ROOT_PASSWORD, root password
    • MYSQL_PASSWORD, password for the app user
  4. 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/percona-server
docker compose up -d

Same files, same behavior. The template README covers connection strings and scaling notes.

#faq

How is it different from plain MySQL?

It is a drop-in replacement: same SQL, protocol, and clients, but with additional instrumentation, diagnostics, and performance features. Apps do not need any changes to run against it.

Does it use the same configuration as MySQL?

Yes - this template uses the same MYSQL_ROOT_PASSWORD / MYSQL_DATABASE / MYSQL_USER / MYSQL_PASSWORD variables, so switching between the mysql and percona-server templates is straightforward.

How do I run it highly available?

Use percona-xtradb-cluster, which is synchronous multi-primary HA (Galera-based) built on Percona Server. This standalone template is a single node.

Ship Percona Server today

One compose stack, 1 GiB of RAM, from $7/month flat, and it runs on your laptop with the same files.

Deploy on Miget Browse the catalogue