Plan your Odoo stack in a free Hobby workspace. A live deployment runs on paid compute with Postgres and a persistent filestore.
Each instance has a fixed monthly price, prorated by the second. Odoo, Postgres, and filestore storage are billed separately.
Capability | Render | |||
|---|---|---|---|---|
How Odoo runs | Custom Docker deployment with Postgres and filestore | Custom container deployment with database and volume | Container dynos. Local filestore isn't kept | Docker image on Fly Machines with a volume |
Free tier | Odoo needs paid compute and a disk | $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 Odoo data | 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.
Run Odoo in Docker with Postgres and a persistent filestore. Define the stack in one render.yaml Blueprint.
Build the Odoo image with your add-ons and required system dependencies. Version the application and modules together.
Place compatible app and database services in the same workspace and region. Configure Odoo database access and privileges deliberately.
Mount paid persistent storage at the configured Odoo data directory. Database backups alone do not preserve file attachments.
Configure the external URL and reverse-proxy behavior for your deployment. Route websocket traffic as required by the selected Odoo worker mode.
Back up Postgres and the filestore as one recoverable application state. Test restores before relying on the deployment for business data.
Describe services, disks, and environment settings in a Blueprint. Disk-backed Odoo services have one instance and a few seconds of deploy downtime.
Choose an Odoo version and include compatible add-ons. Create a Render web service using your Dockerfile or a reviewed image.
Configure Postgres credentials and a paid filestore disk. Set the data directory, external URL, and proxy settings for your deployment.
Test login, attachments, reports, mail, scheduled actions, and any live-chat routing. Verify a complete database-and-filestore restore before launch.