Set up your Strapi project in a free Hobby workspace. Strapi needs 2 GB of memory, so run the CMS on a $25/month instance.
Each instance has a fixed monthly price, prorated by the second.
Capability | Render | |||
|---|---|---|---|---|
How Strapi runs | Long-running Node.js CMS or Docker service | Long-running containers | Long-running dynos | Fly Machine built from a Dockerfile |
Free tier | Free instances are below Strapi's 2 GB minimum | $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 |
Postgres for content | Render Postgres from $6/month, with PITR | Maintained Postgres template | Heroku Postgres. No rollback on Essential | Managed Postgres from $38/month, HA included |
Backups | Postgres PITR plus daily file snapshots | Volume backups. Opt-in PITR for Postgres | Postgres backups. Rollback from Standard | Postgres backups. Volume snapshots, 5 days 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 the CMS and its database in one render.yaml Blueprint. You maintain content models, plugins, and upgrades.
Keep structured content outside the application instance. Connect over the private network in the same workspace and region.
Use a compatible object-storage provider for a stateless CMS, or choose a paid disk for a single instance.
Add a custom domain with managed TLS. Configure Strapi’s public URL and proxy settings for your application.
Run the production admin build as part of deployment. Keep content-model changes in your development workflow.
Stateless web services support zero-downtime deploys with readiness checks. Attaching a disk means a few seconds of deploy downtime and one instance.
Choose memory for Strapi, plugins, and API load. Separate database capacity and upload-provider costs from service compute.
Use your maintained Strapi repository and a compatible supported Node.js version. Create a Web Service from that repository.


Set database credentials, application keys, and production build/start commands. Choose an upload provider or attach a paid disk.
Deploy the service, confirm its health endpoint, and create the first admin account. Test a media upload and an API request before using the CMS live.