Set up your publication in a free Hobby workspace. A live Ghost site runs on paid compute with MySQL and persistent content storage.
Each instance has a fixed monthly price, prorated by the second. Ghost, MySQL, and their disks are billed separately.
Capability | Render | |||
|---|---|---|---|---|
How Ghost runs | Docker web service plus self-hosted MySQL | Long-running containers | Long-running dynos | Docker image on Fly Machines with a volume |
Free tier | Ghost needs paid compute and disks | $5 trial for 30 days, then $1/month credit | None. Eco: $5/month for 1,000 hours | 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) | $250/month (Performance-M, 2.5 GB dedicated) | $13.39/month shared CPU, $33 dedicated |
MySQL 8 database | Self-run MySQL private service with a disk | MySQL template | Third-party add-ons (JawsDB, Stackhero) | Self-run MySQL on a volume |
Backups | Daily file snapshots. Back up MySQL separately | Daily, weekly, and monthly volume backups | Set by the MySQL add-on | Daily snapshots, 5 days by default |
Persistent disks | SSDs that grow with no downtime (single instance) | Volumes (no replicas) | None. Files reset when dynos restart | Volumes, one per Machine, not replicated |
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 are compute only. Fly.io prices are for US East.
Define Ghost, MySQL, and their disks in one render.yaml Blueprint. You maintain Ghost, the database, and backups.
Run MySQL within the same workspace and region as Ghost. You maintain the database version and database-level backups.
Mount a paid disk at Ghost’s content directory for themes and uploads. Keep database files on MySQL’s separate disk.
Connect your custom domain with managed TLS, then set Ghost’s public URL to match the primary domain.
Configure transactional email and newsletter delivery with the provider Ghost supports for that function. Delivery charges are separate.
Keep database and mail credentials in service configuration. Review access to the publication and the Render workspace.
Test Ghost and MySQL updates before changing production images. Disk-backed services have a few seconds of deploy downtime, so plan maintenance accordingly.
Fork the Ghost example and review its Ghost and MySQL image versions. Update and test versions before using the project for a live publication.
Create a Blueprint, review the paid resource plans, and deploy both services with their content and database disks.
Set Ghost’s public URL and custom domain, complete admin setup, and configure email delivery. Test publishing, media uploads, and backups.