Odoo Community & Enterprise · git push → live Odoo
Deploy Odoo like Vercel — Community or Enterprise.
ERPForge is the Odoo-native platform for teams without a DevOps department. Host Odoo Community or Enterprise, push to Git, and your instance builds, validates and deploys itself — with live logs, verified backups and real isolation.
- editions: Community + Enterprise
- 2editions: Community + Enterprise
- to first instance
- < 2 minto first instance
- DevOps engineers
- 0DevOps engineers
Built and run by Scriptonix, an Odoo implementation partner — the same platform we use to ship our own clients' Odoo.
- Community + Enterprise
- both editions
- Container-per-instance
- full isolation
- Self-host or cloud
- your choice
Community, not just Enterprise
The Odoo.sh alternative that hosts Community edition
Odoo.sh only runs Odoo Enterprise. If you build on Odoo Community, you've been stuck hand-rolling Docker, CI and backups. ERPForge gives Community the same git-push workflow, staging, live logs and verified backups — and it runs Enterprise too, so mixed fleets live in one place.
Odoo Community
Fully supported — hosting, CI/CD, staging and backups.
Odoo Enterprise
Bring your licence; run Community and Enterprise side by side.
Self-hosted
One bootstrap script stands the whole platform up on your own server.
Everything included
The whole Odoo lifecycle, in one place
Provisioning, deploys, logs, databases, backups and monitoring — built specifically for how Odoo actually behaves.
Git push → live Odoo
Connect GitHub once. Every push to a mapped branch clones your modules, validates them and reloads Odoo automatically.
Builds that fail safely
A syntax or indentation error fails the build with the exact file and line — your running instance keeps serving the last good code.
Typed instances
Spin up production, staging or development instances straight from a project. Each gets its own Odoo, Postgres, filestore and network.
Live Odoo logs
A real-time tail of your Odoo server logs with level filters, full-text search and highlighting. Find the error without scrolling.
Browser workspace
A Monaco editor, a real terminal, a database explorer with a SQL runner and an Odoo shell console — all inside the instance.
Verified backups
Scheduled backups of database and filestore, with restore paths that are actually tested — not just written down.
Monitoring & scaling
Health checks, CPU/RAM/worker metrics and one-click scaling. PDF-safe worker defaults so reports never break.
Secure by default
Read-only deploy keys, secrets kept out of the database, server-side RBAC, and automatic HTTPS on every control plane.
How it works
Three steps. Then just push.
No Dockerfiles, no addons-path debugging, no restart scripts.
- 01
Connect your Git account
Add a GitHub connection to your organization. ERPForge verifies it and lists your repositories.
- 02
Create a project and instance
Pick an Odoo version and an instance type — production, staging or development. A real repository and a running Odoo appear in minutes.
- 03
Push. That's the deploy.
git push. ERPForge builds your modules, promotes them only if they compile, restarts Odoo and shows you the result.
$ git add my_module
$ git commit -m "feat: invoicing report"
$ git push origin main
✓ webhook received · build queued
✓ 3 modules compiled · Odoo reloaded
→ live at your instance URLBuilt-in workspace
Debug without leaving the browser
Everything you'd normally SSH for — safely scoped to the instance you're looking at.
Code editor
Monaco, editing files inside the running container.
Real terminal
A PTY into the instance, plus an Odoo shell with the ORM.
Database explorer
Browse tables and run read-only SQL against the live DB.
Log search
Filter by level, search across the tail, highlight matches.
Why ERPForge
A generic PaaS doesn't know what Odoo is
Odoo has opinions about workers, addons paths, cron, mail and databases. So does ERPForge.
Odoo-native, not a generic PaaS
Addons paths, module compilation, the Odoo shell, database neutralization on staging, worker/PDF quirks — handled, because this platform only does Odoo.
Your Odoo never depends on us
Control plane and data plane are separate. If the ERPForge dashboard goes down, your customers' Odoo instances keep serving traffic.
Real isolation per instance
Container-per-customer by default: a dedicated Odoo container, Postgres, filestore volume and private network. No noisy neighbours.
Bring your own cloud
One command stands the whole platform up on any Linux host you own — with automatic HTTPS and a GitHub Actions pipeline that redeploys on push.
FAQ
Questions teams ask before moving
- Does my Odoo traffic go through ERPForge?
- No. ERPForge is the control plane — it provisions and manages your Odoo instances. Customer traffic goes straight to your Odoo containers. If our dashboard is down, your Odoo keeps running.
- Does it support Odoo Community and Enterprise?
- Yes. Pick the edition per project, and the Odoo version per instance. Supported versions are kept current with upstream releases.
- What happens if I push code that doesn't compile?
- The build fails before anything is promoted. You get the exact file and line number in the build log, and the running instance keeps serving the last known-good code.
- Can I self-host ERPForge on my own server?
- Yes. A single bootstrap script installs Docker, generates secrets, builds the stack and brings it up behind automatic HTTPS on any Ubuntu/Debian host.
- How do staging environments stay safe?
- Moving an environment to staging neutralizes it — outgoing mail, scheduled jobs and payment providers are disabled on the real database, not just flagged.
Your next Odoo deploy is a git push.
Connect a repository, pick a version, and watch the first instance come up. Self-host it on your own server, or run it here.