Bundled platforms
Fixed worker pricing, limited root, and “our cloud only” economics. Fine until you need multi-client isolation or real operator control.
Control plane · not just hosting
Run your Odoo fleet
like an operator,
not a ticket queue.
odoobot is the control plane for Odoo across your own Linux servers. Enroll hosts with a one-line bootstrap, deploy isolated Docker instances, manage Postgres clusters, schedule backups, and watch health in one console — while you keep root, data, and margins.
- Bring-your-own
- Any cloud or bare metal
- Isolation
- One Linux user per instance
- Agent-first
- Live heartbeats from every host
The gap
Odoo partners and operators shouldn’t choose between opaque SaaS hosting and homegrown scripts.
DIY server sprawl
SSH, docker-compose, nginx, cron backups, and a spreadsheet of passwords. Works for one client — falls apart at twenty.
What you actually need
A control plane: enroll any server, ship isolated Odoo, manage databases and backups, and see drift before customers do.
Capabilities
Everything an Odoo fleet operator needs in one plane.
Built from real production layouts: Dockerized Odoo, per-instance users, nginx front doors, Postgres clusters, and agent heartbeats — not a slideshow of hosting promises.
Multi-server control plane
Register Linux hosts across Hetzner, GCP, DigitalOcean, or bare metal. One console for the fleet — not one tab per SSH session.
One-line host enrollment
Mint a token, run a bootstrap script, get Docker, the odoobot-agent, and a registered host. Hands-off from bare VM to managed node.
Hard-isolated instances
Each Odoo runs as its own Linux user with a dedicated Docker container and reverse-proxied domain. Blast radius stays local.
Database cluster management
First-class Postgres clusters with a dedicated database agent — create databases and users, track health, and run backups.
Scheduled backup & restore
Policy-driven schedules for filestore and databases. Restore paths that operators can actually run when something breaks at 2am.
Live health via agents
Lightweight Go agents report heartbeats, capabilities, and host metrics over a persistent channel.
Modules as code
Git-pinned addon sources, version tracking, and install/upgrade flows that match how production Odoo fleets ship custom modules.
Drift detection
Config and state drift surfaces in the console so “works on this server” doesn’t become a multi-client mystery.
Multi-tenant for agencies
Scope hosts and instances to tenants with role-based access. Built for partners hosting many clients.
AI-ready Odoo (MCP)
Enable a per-instance MCP sidecar so agents and tools can work with Odoo safely from the control plane.
Operator surface
What you operate from the plane.
The control plane is organized the way fleets actually run — hosts and agents first, then instances, databases, backups, and drift. No captive panel chrome.
Hosts
Enrolled Linux machines with capability-gated agents and live heartbeats.
Instances
Isolated Docker Odoo stacks — provision, adopt, start/stop, modules.
Databases
Postgres clusters as first-class objects, not a black box sidecar.
Backups
Scheduled filestore + DB backups with restore paths operators can run.
Drift
Config that diverged from the control-plane baseline, surfaced early.
Activity
Operator and system events across the fleet in one feed.
Operating model
From empty server to managed Odoo in three moves.
- 01
Enroll a host
Generate a bootstrap token in the control plane. On the target server, pipe the setup script. Docker, the agent user, and enrollment complete in one pass.
curl -sSL "https://api.odoobot.net/api/bootstrap/setup?token=…" | bash - 02
Deploy an instance
Pick a host, Odoo version, and domain. odoobot creates the Linux user, container, database, and nginx front door — isolated from every other tenant on that machine.
- 03
Operate the fleet
Watch agent heartbeats, schedule backups, inspect drift, manage modules, and open activity history — one plane for production and every client environment you host.
Positioning
Built for operators who want automation and ownership.
Partners want automated Odoo hosting on infrastructure they control. odoobot goes further — a multi-host control plane with agent-reported state, Postgres as a first-class citizen, and isolation patterns taken from production. Migrating an existing fleet?
| Capability | Typical SaaS hosting | Scripted DIY | odoobot |
|---|---|---|---|
| Your servers / any cloud | Sometimes | Yes | Yes — enroll what you own |
| Multi-host fleet view | Limited | No | Native control plane |
| Per-instance isolation | Varies | If you built it | User + container + proxy |
| Postgres lifecycle | Bundled black box | Manual | Cluster agent + API |
| Live agent heartbeats | Opaque health | DIY monitoring | Go agents, capability-gated |
| Backups you control | Plan-dependent | Cron + hope | Scheduled, restorable |
| Drift visibility | Rare | None | First-class console signal |
| Root / data ownership | Often restricted | Full | Full — your infra |
| External instance migration | — | Manual | Dump → provision → adopt |
“Your data. Your servers. Our automation.” is the right instinct. odoobot adds the missing piece: an operator-grade plane that treats hosts, databases, backups, and drift as first-class objects.
Audience
Who runs odoobot.
Odoo partners & agencies
Host many client instances across shared or dedicated servers. Keep margins, standardize ops, and stop reinventing bootstrap scripts.
In-house ERP operators
Run production and staging fleets with real isolation, backup policy, and health visibility — without a single-vendor cloud SKU.
Infrastructure-minded teams
Prefer agents, SSH roots, and explicit Postgres clusters over opaque “managed Odoo.” Bring your Hetzner, GCP, or colo iron.
Teams leaving hosting panels
Migrate instances onto infrastructure you control — from panels or hand-rolled hosts — via dump, provision, restore, and adopt.
Early access
Put your Odoo fleet on a real control plane.
odoobot is the operator console for multi-server Odoo: bootstrap, deploy, back up, and monitor — on infrastructure you already own.
No spam. We'll reply with setup options for partners and operators.