We make Odoo easy.
Odizy manages the whole lifecycle of your Odoo servers: remote development, a test server for every branch, staging on real data, and a production that fails over to a standby. Where your current hosting hits its limits, large volumes and custom development included.
Mathon: 400 GB+ in production · Actiwork
Odizy, peace of mind: four kinds of server, one recipe.
Everything starts from an App Definition linked to your git repository (GitLab, GitHub, Azure DevOps, Forgejo). Odizy subscribes to its webhooks: a push is all it takes to create or update a server.
A remote development server
You work in a Linux server identical to production, from your browser, VS Code or JetBrains. The only comfortable way to work on large databases.
A test server per branch
Each commit on a feature branch creates or updates a test server, destroyed when the branch is deleted.
Upgrades rehearsed on real data
The default branch runs on a copy of the production database, sized like production for load testing.
A manual, controlled deployment
Going to production is triggered by hand. In high availability, Odizy deploys to every server in the set.
Growth & volume
Your custom Odoo solutions, development environments included, with replication and performance guaranteed even at large volumes.
Security & sovereignty
Odoo on our cloud in France or on your own infrastructure, with monitoring, failover and backups. Pass your audits with confidence.
Multi-site companies
All your Odoo instances from a single platform: planned switchover between sites, centralised monitoring, controlled costs.
It’s not Odoo calling an AI. It’s your AI driving your Odoo.
Plug in your AI
Connect Claude, ChatGPT or a European model to your Odoo data. The assistant reads and writes under your access rules, without rewriting your ERP.
Available · foundationThe AI proposes, you approve
Every sensitive action triggers a one-click human approval, with an audit trail for every operation.
AvailableAn operations co-pilot
Your Odoo monitoring explained in plain language: performance, database locks, replication, backups.
Coming soonDeployment in plain language
From provisioning to go-live through your assistant: modules, configuration, error recovery, under your supervision.
Demonstrated- Odoo calls an AI service
- Your data goes to a third party
- Model imposed on you
- Your AI drives your Odoo, through MCP
- Data under your control
- Choice of model: Claude, ChatGPT, European
- Human approval and audit log
- With Muppy Enterprise, data never leaves your premises
Auto DevOps: five automatic checks on every commit.
Don’t reinvent the wheel. No pipelines to write for weeks, no runners to maintain: every deployment is traced, tied to a commit, and its reports flow back into GitLab for your audits.
Code quality
Code ClimateComplexity, duplication and technical debt detected on every commit.
SAST
Semgrep · BanditSecurity flaws in Python/Odoo code: SQL injection, XSS, misconfigurations.
Secret detection
GitLab SecretsAPI keys, tokens and passwords committed by mistake, across the whole history.
Dependencies
GemnasiumPython libraries with known CVEs and incompatible licences.
Containers
TrivyCVEs, secrets and misconfigurations in Docker images.
Traceability & compliance
Logs for every check, exportable reports, traceable rollback to any commit.
Dev → Debug → Deploy → Scale. No more “it works on my machine”.
Each server can ship Code-Server, VS Code in the browser, published and protected by Muppy. You enable it per environment in the App Definition, then server by server.
- Direct access: SSH, repository, application URL and IDE, from the server’s record.
- Real databases: restore a production backup onto staging in a few clicks.
- Safe upgrades: a backup before every update by default, or a database copy for very large volumes.
- Reproducible builds: a versioned recipe (
buildit.jsonc) describes Odoo, your modules, OCA and Enterprise;ikb installrebuilds everything identically.
| CI/CD setting | Default |
|---|---|
| Trigger | every push, or a tag in the commit message |
| Delete the server with the branch | enabled |
| Backup before update | enabled |
| Stop the server before backup | enabled |
| Starting database for a test server | empty, demo data or latest dump |
| Ignored branches | regular expression of your choice |
The production server is the one whose database is primary.
A standby runs the same code on a read-only copy, fed continuously by PostgreSQL replication. Promoting its cluster is all it takes to put it into production, by hand (“Set as Primary”) or automatically.
Detection
Health checks find that the primary no longer responds; the replication state of the standbys is checked.
Choosing the standby
pglookout picks the best-placed standby after a configurable delay, with no risk of double writes.
Promotion
The standby becomes primary. The load balancer, which polls /inouk_health_check, now sends traffic to it.
Back to normal
The restored node rejoins the set; replication and filestore synchronisation resume.
Point In Time Recovery
WAL files ship to S3 every minute: after a human error, the database goes back to the moment you choose. Target: a few minutes of loss at most.
Real high availability, even with a 400 GB+ filestore.
PostgreSQL replication only copies the database. Odizy keeps the filestore in step in three ways, depending on its size.
| Mode | When | What you gain |
|---|---|---|
| In the database | up to about 50 GB | backup and replication included |
| In an S3 bucket | Odoo 18 and later, scaling, Kubernetes | no node owns the files |
| On disk + rsync | very large filestores (400 GB+ at Mathon) | sync every minute, 7 Prometheus metrics, alert if it stops |
Much more than an Odoo host.
- Odoo Community and Enterprise
- Built for large databases and filestores
- Automated CI/CD deployment and remote development
- Isolated dev, test, staging and production environments
- Performance, scaling and freedom of hosting
- High availability and Zero Trust access with Sunray
Who it’s for:
Odoo integrator or software vendor? Odizy for partners →
Multi-cloud & on-premise
Choose your infrastructure freely.
Built-in security
Backups, replication, high availability, Sunray.
Performance
Optimised, fast environments.
Sovereignty
Your data and your choices stay under your control.
Your Odoo hosted in France. Odizy Flex in beta.
Odizy Flex is turnkey Odoo: a server sized for your users, hosted in France, with Sunray Zero Trust included. Pick your plan, we handle the rest. Change plans whenever you like.
- Odoo 18 or 19, Community or Enterprise, preconfigured
- odizy.cloud address included, your own domain via CNAME
- Sunray Zero Trust (WebAuthn passkeys) at no extra cost
- Automatic nightly backups
- Continuous monitoring and alerts
- Security patches applied automatically
Your platform belongs to you.
At your request, oursbl.eu transfers to you the hosting contract for your platform, virtual machine or physical server. You become the sole master of your Odoo and your hardware, with no dependency on us.
More users, high availability or hosting on your premises: let’s discuss your case.
Beta: limited number of places.
Professional and Enterprise: hosted for you, or on your premises.
Beyond Odizy Flex: Odizy Professional on public hosting, Odizy Enterprise on your private infrastructure, with the high availability, remote development and CI/CD described above.
Odizy Professional
with 1024 GB of RAM
For teams that want to industrialise their Odoo.From 6 Odoo.sh workers, Odizy Professional is a sovereign, competitive alternative.
- 2 production servers, reference architecture
- Remote Development included
- Backup and database lock monitoring
- Alerts and notifications
- One restore test per year
- Optional, billed on time spent:
- High availability (monitoring and failover included once enabled)
- Test and staging environments
- CI/CD
- Switchover and DR tests
- Priority support
Odizy Enterprise
For complex Odoo estates and the most demanding requirements.
- Everything in Professional, plus:
- Custom architecture
- Multi-cloud and hybrid
- Contractual SLA
- Dedicated support
- Training
- Security audit
Prices exclude installation and migration; implementing options is billed on a time-spent basis; Enterprise is quoted according to your architecture. Every service in detail. For hosting on your premises, see also Muppy Enterprise.
Before you trust us with your Odoo
How is this different from Odoo 19’s native AI?
With Odoo 19, Odoo calls an AI service: your data goes to a third party. Odizy does the opposite: your assistant drives your Odoo through an MCP gateway you control, with the model of your choice.
Is it safe to let an AI write to my ERP?
The AI acts under Odoo’s native access rules, every sensitive action triggers human approval and every operation is timestamped. You can also start read-only.
Which Odoo versions?
Community and Enterprise. The ready-made templates cover Odoo 18 and 19, and every server is built from a versioned recipe that pins the version. For an older version, let’s talk about your case.
What if my filestore is huge?
There are three modes: in the database (up to about 50 GB, replicated with it), in an S3 bucket (Odoo 18 and later), or on disk, replicated by rsync every minute and monitored. That last mode is what handles 400 GB+ at Mathon.
Can we host Odoo on our own infrastructure?
Yes, with Muppy Enterprise: the whole platform runs on your premises, with the same monitoring, replication and central management tools.
They already run Odoo with Odizy: see the customer references
Your Odoo deserves better than a makeshift server.
Tell us about your current setup: versions, volumes, availability constraints. In 30 minutes, we’ll show you what Odizy would change.
You describe your project
Four fields, no phone number required.
We talk it through for 30 minutes
Architecture, hosting constraints, security, taking over what you already run.
Prefer to try first? Join the Odizy Flex beta
Manganese Complete App Servers, any stack
Manganese DevFleet Agentic remote dev for large organisations