Most small companies keep self-hosted Odoo nowhere near their radar: they rent their ERP as SaaS and rent their operations from a partner on retainer. Two invoices every month, and your data and your workflows live on someone else's terms. It works, right up until the day you want to move and discover you can't. This is the case for owning both the software and the ops that keep it running - and why that used to be impractical for anyone outside the partner club.
Rent the software, rent the ops
The default arrangement for an SMB running Odoo looks reasonable on paper. A subscription covers the application. A partner covers the maintenance. But bundle those together and you have rented your entire system of record. Your customer list, your invoices, your inventory, your bespoke workflows - all sitting on infrastructure you don't control, shaped by contracts you didn't write. The convenience is real. So is the quiet dependency it creates.
The alternative is self-hosted Odoo: the same application, running on a server you own or rent directly, with the PostgreSQL database and the filestore under your name. Community edition is open-source and LGPL-licensed, so the software itself is free. Enterprise is available too, on your own subscription. Either way, the deployment belongs to you. That is the difference between renting a system and owning one.
What self-hosting actually costs
Here is the honest part that most guides skip: the licence was never the hard part. You can stand up Community on a $10-a-month VPS. The real cost of running your own ERP is the operations - the installs, the migrations, the version upgrades, the backups, the monitoring, the security patches. That work never appears on an invoice when you rent, because it is baked into the subscription. It doesn't go away. It just becomes invisible, and you pay for it forever.
For years, that ops burden is exactly what made self-hosting impractical unless you had someone on staff who knew Odoo well. A single wrong pg_dump during a migration, a version upgrade that silently breaks a custom module, a backup nobody ever tested - these are the reasons founders decide it isn't worth the risk. The gap between partners and everyone else is precisely this operational knowledge, and it's a real wall.
So the ops go to an agent
The bet behind Zoxron is simple: that operational work is structured, repeatable, and mostly boring - which makes it a good fit for an AI agent to carry out, under supervision. Instead of hiring an ops person or renting a partner, you point your AI assistant at a server you own, and it provisions, installs, migrates and upgrades Odoo for you.
The mechanism is a set of tools the agent can call - over 80 operations covering the full lifecycle. Provision the box. Install a fresh instance. Move an existing one between servers. Step through a version upgrade. Configure backups and monitoring. These aren't chat responses about how to do the work; they are the work, exposed as clean actions.
Crucially, every risky step is preview-first. The agent shows you exactly what it intends to do - the plan, the commands, what gets touched - and nothing runs until you confirm. That show-before-you-run design is what makes handing over infrastructure power sane rather than reckless. The agent proposes; you approve.
Own the system, skip the headcount
The outcome is the part that changes the math. You get data ownership - the database, the filestore, the right to pack up and leave - without having to hire the ops role that ownership traditionally demanded. The boring, high-stakes plumbing stops being your problem, and it stops being a reason not to own your own system.
This isn't theoretical for us. Zoxron runs its own company this way: this website and the ERP behind it are self-hosted on hardware we control, deployed and maintained by the same tooling clients use. It keeps the product honest, because we live with the same trade-offs we set up for everyone else. When a migration or an upgrade is clumsy, we feel it first.
Who self-hosting is (and isn't) for
Self-hosting isn't automatically the right call for everyone. If you have five users, no customisation, and no interest in where the data physically lives, managed hosting is fine. Self-hosting starts to pay off when any of these become true: you have custom modules or third-party addons that a managed plan restricts; you care about data sovereignty for legal or contractual reasons; your subscription cost per user has crept past what a server would cost; or you simply want the freedom to move providers without a project attached to it. If you want a hand weighing it up, the services page lays out how the deployment works.
FAQ
What does self-hosting Odoo actually cost?
The software can be free - Community is LGPL-licensed - and a capable VPS runs from roughly $10–50 a month depending on users and modules. The real cost is operational: installs, migrations, upgrades, backups and monitoring. Handing that work to an agent is how self-hosted Odoo stays cheap in practice, not just on the invoice.
Can I self-host Odoo without a partner?
Yes. Community is open-source and Enterprise runs on your own subscription and licensed .deb. You don't need partner status to run either. What you do need is a reliable way to handle the ops, which is the whole reason an agent-driven approach exists.
Do I really own my data when I self-host?
You own the PostgreSQL database and the filestore outright, on hardware you control. That means you can back it up, move it, or leave for another provider whenever you choose - no export request, no lock-in, no waiting on someone else's schedule.