Prototype your app on a free web service. Run MySQL as a paid private service with a persistent disk on the same private network.
Each instance has a fixed monthly price, prorated by the second. Disk storage is billed separately.
Capability | Render | |||
|---|---|---|---|---|
How MySQL runs | Self-hosted Docker private service | Self-hosted MySQL container with a volume | Third-party add-ons (JawsDB, Stackhero) | Self-run MySQL container on a volume |
Free tier | Not available for private services | $5 trial for 30 days, then $1/month credit | Depends on the database add-on | No free tier. Personal bills under $5 waived |
Always-on, 2 GB | $25/month (1 CPU) | Up to $40/month at full use (1 vCPU) | Add-on pricing varies | $13.39/month shared CPU, $33 dedicated |
Persistent storage | SSD, $0.25/GB/month. Grows with no downtime | Volume, $0.15/GB/month. 5 GB default on Hobby | Included in the add-on plan | Volume, $0.15/GB/month |
Private networking | Private network per workspace and region | Private network per environment | Depends on the add-on provider | Private network (6PN) by default |
Stack as code | One render.yaml, auto-synced on push | Project file, applied with CLI or CI | app.json per app, read only at creation | fly.toml per app. No database definitions |
Competitor details as of November 2026. Instance prices exclude storage. Fly.io prices are for US East.
Run MySQL as a private service with a persistent disk. Define it alongside your apps in one render.yaml Blueprint.
Run MySQL as a private service and connect applications in the same workspace and region. It does not need a public database endpoint.
Mount the database disk at /var/lib/mysql for the documented image. Only data beneath the mount path survives instance replacement.
Select and maintain a compatible MySQL image. Tune connection limits, memory, and application users for your workload.
Create consistent backups with MySQL tools and store copies separately. Disk snapshots are not a substitute for database-aware recovery.
Describe the service, disk, and environment in render.yaml. Review the selected instance size before applying the Blueprint.
Test version changes and restoration before production use. A disk-backed service has one instance and a few seconds of deploy downtime.
Fork the Render MySQL repository and review its image version and instance plan. Create a Docker private service from your fork.
Set a strong root password and application credentials. Attach a disk at /var/lib/mysql for the documented image.
Deploy, then connect from an application in the same workspace and region. Test writes, backups, and recovery before adding production data.