Prototype your app on a free web service. Run MongoDB as a paid private service with a persistent disk, or connect to MongoDB Atlas.
Each instance has a fixed monthly price, prorated by the second. Disk storage is billed separately.
Capability | Render | |||
|---|---|---|---|---|
How MongoDB runs | Self-hosted Docker private service | Self-hosted MongoDB container with a volume | Third-party add-on (ObjectRocket) | Self-run MongoDB 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 MongoDB as a private service with a persistent disk. Define it alongside your apps in one render.yaml Blueprint.
Connect applications to MongoDB in the same workspace and region. The private service does not expose a public HTTP endpoint.
Attach a disk at /data/db for the documented image. Keep all required database files within persistent storage.
Configure MongoDB authentication and application users. Private networking complements database authentication.
Create backups with the appropriate MongoDB tools and retain copies separately. Test the recovery process before it is needed.
The documented example runs one database instance. Replica sets, transactions, and failover require their own architecture and configuration.
Use MongoDB client libraries from your application service. An externally managed MongoDB deployment is also an option when you want database operations handled elsewhere.
Create a Docker private service from the Render MongoDB example. Pin and review an image version for your application.
Attach the disk at /data/db. Set up database authentication, user access, and the required runtime configuration.
Connect your application using the private hostname and MongoDB port. Test writes and a database-aware backup and restore.