Your Odoo infrastructure. Your cloud. Your control.
OdooTube is Odoo cloud hosting with the deployment machinery a production ERP needs: dedicated infrastructure, production and staging environments, automated releases, backups, monitoring, and rollback — for Community and Enterprise, on the Odoo version you run.
Managed infrastructure, without giving up control of it
Generic Odoo hosting optimises for one thing: getting a database online. That is enough until you need a staging copy of real data, a release you can reverse, a database your compliance team will accept, or a version that is not the newest one. OdooTube is built for the deployment after the first one.
- Dedicated infrastructure
- Isolated infrastructure per customer with reserved compute and its own domain — a single dedicated instance on Launch and Business, a multi-node application tier on Scale and Regulated.
- Community and Enterprise
- Both editions are supported. Enterprise runs against your own Odoo subscription and entitlement.
- Multiple Odoo versions
- Stay on the version your business is standardised on, and move when your testing says you are ready.
- Production and staging
- Staging environments cloned from production data, for upgrade rehearsals and module testing.
- Automated deployments
- Releases come from your repository through a repeatable pipeline, not from someone editing a live server.
- Application rollback
- Roll back the application release to the previous known-good version. Pre-deployment database backups are retained for recovery when an incompatible schema or data migration requires database restoration.
- Monitoring
- Health checks, resource metrics, and log access per environment, with alerting on failure signals.
- Infrastructure control
- Cloud provider, region, database location, and access paths are decisions you make, not defaults you inherit.
What actually runs where
Every OdooTube environment is an isolated stack, and the control plane orchestrates it without sitting in the request path of your Odoo. The shape of the runtime layer is what changes between plans — compare the four below.
Each customer environment runs on isolated dedicated infrastructure. Depending on the plan, that is either a single dedicated compute instance or a multi-node application tier backed by managed PostgreSQL.
Cloud infrastructure options
Deploy on OdooNex-operated cloud capacity, or into a cloud account and region you nominate when residency or procurement requires it.
No shared application tier
Environments never share an Odoo process, a filestore, or a database instance with another customer, whether the plan runs one node or several.
Exit is a supported operation
Your database, filestore, and addon repositories are yours, in standard formats, whenever you ask for them.
One path to production, every time
A release is a pipeline run, not a manual procedure. The same path applies to a one-line fix and a version upgrade.
Deploy from your repository
Point an environment at a branch or tag in your own Git repository. The build is reproducible from that reference.
Tests before promotion
Run Odoo's test runner and your own suites against a staging environment holding production-shaped data.
Health-gated releases
A release that fails its post-deploy checks is a rollback candidate immediately, not a support ticket tomorrow.
Readable release history
Every environment keeps what was deployed, from which commit, by whom, and when — with the previous release still reachable.
CI integration
Trigger builds and deployments from your existing CI system so OdooTube fits the pipeline you already run.
Upgrade rehearsals
Version upgrades run as a normal release against a staging clone first, so the cutover is a repeat of something that already worked.
Staging that resembles production closely enough to trust
A staging environment is only useful if it holds the data and configuration that break things. OdooTube clones production into staging, so the rehearsal reflects the real system.
Create, stop, rebuild, and restore staging environments as needed. There is no per-environment charge and no expiry timer, and the resources available to you depend on your hosting plan.
Where your data lives, and how you get it back
Scheduled, off-instance backups
Database and filestore are backed up on a schedule and stored away from the instance that produced them, so losing the VM does not mean losing the data.
Restore into production or staging
Restore a backup over production when that is what the incident calls for, or into a fresh staging environment when you want to inspect it first.
Retention you set
Backup frequency and retention are configured per environment against your own recovery objectives and audit requirements.
Managed PostgreSQL
Let OdooNex run PostgreSQL for the environment, with tuning, monitoring, and patching handled as part of the service.
External or self-managed PostgreSQL
Point the environment at Amazon RDS, Google Cloud SQL, or a PostgreSQL server in your own data centre when the database has to stay under your control.
Switch later
Moving between managed and external PostgreSQL is a migration we run for you, not a reason to rebuild the environment.
Controls that hold up under review
- Environment isolation
- Each customer environment runs on isolated dedicated infrastructure. Depending on the plan, that is either a single dedicated compute instance or a multi-node application tier backed by managed PostgreSQL.
- Encrypted access paths
- TLS for site traffic; administrative access over an encrypted tunnel rather than exposed management ports.
- Least-privilege administration
- Named administrative accounts with scoped permissions, and no standing shared credentials.
- Patching
- Operating system and platform components patched on a maintained schedule, with Odoo updates run as releases.
- Change control
- Production changes arrive through the release pipeline with an approval and a recorded history.
- Data residency
- Cloud region and database location are chosen per environment, including US-only deployments.
OdooTube is designed to support controlled and compliance-sensitive Odoo environments. OdooNex does not hold or issue ITAR, CMMC, or DCAA certifications; see OdooTube Regulated for what we do and do not claim.
Community or Enterprise, on the version you run
Hosting and licensing are separate concerns. OdooTube provides the infrastructure and operations; an Enterprise subscription, if you want one, stays your contract with Odoo.
| Capability | Odoo Community | Odoo Enterprise |
|---|---|---|
| Dedicated infrastructure | Yes | Yes |
| Production + staging environments | Yes | Yes |
| Automated deployment & rollback | Yes | Yes |
| Backups, monitoring, alerting | Yes | Yes |
| Managed or external PostgreSQL | Yes | Yes |
| Odoo Enterprise apps & official support | Not included in the Odoo edition | Through your Odoo subscription |
| Custom addons from your repository | Yes | Yes |
Supported Odoo versions track the releases Odoo currently maintains, plus older versions we already operate for customers. Ask about a specific version and we will tell you plainly whether we run it.
From plan to running environment
Online checkout is being finished, so every plan currently starts with a short onboarding conversation. The published price does not change; we confirm the configuration, build the environment, and hand it over.
Choose a plan
Pick the tier whose architecture fits the workload. Storage extends up to 10 TB as you grow.
Confirm the configuration
Odoo version and edition, database placement, region, and backup retention.
Billing
Monthly, quarterly, or annually. The billing period is changeable later.
Environment provisioned
We build the environment and send access details once it is up and health-checked.
Four levels of infrastructure, from $59/month
Plans differ by architecture rather than by user count: where PostgreSQL runs, how many Odoo nodes serve traffic, and whether there is a load balancer in front of them. There are no per-user hosting fees.
Questions technical buyers actually ask
Can I keep my database on my own infrastructure?
Yes. An environment can run against managed PostgreSQL that we operate, or against an external PostgreSQL server you control — Amazon RDS, Google Cloud SQL, or a server in your own data centre. You can move between the two later without rebuilding the environment.
Which Odoo versions and editions do you support?
Community and Enterprise, on the versions Odoo currently maintains as well as older versions we already operate for existing customers. Enterprise runs against your own Odoo subscription. If you need a specific version, ask — we will tell you whether we run it rather than promising and finding out later.
How many staging environments do I get?
Create, stop, rebuild, and restore staging environments as needed. There is no per-environment charge and no expiry timer, but each one runs on real compute, so how many you can hold at once depends on the capacity of your hosting plan. We tell you when a plan needs to grow rather than letting an environment quietly fail.
Does a rollback restore the database too?
No, and it is worth being precise about this. A rollback returns the application to the previous known-good release — for container deployments, the previous image and release revision. It does not rewind your database, because reverting data that users have legitimately entered since the deploy is almost never what you want.
Restoring a database is a separate, authorised action — used when a deployment performed an incompatible migration, when data was corrupted, or when a recovery procedure has been agreed. It never happens automatically because an application health check failed.
Can you migrate our existing Odoo onto OdooTube?
Yes, including from Odoo Online, Odoo.sh, another host, or self-managed servers. Migrations are rehearsed on a staging environment built from a copy of your data, and the cutover repeats a run that already succeeded. This is service work — talk to us about scope.
Do you support US-only data residency?
Yes. Cloud region and database location are set per environment, and administrative access can be restricted accordingly. See OdooTube Regulated for the controls this involves and the certification claims we deliberately do not make.
Can we leave and take our data with us?
Yes. The database, filestore, and your addon repositories are yours in standard formats, available on request. No part of the platform depends on holding your data hostage.
See OdooTube running your Odoo
A 30-minute technical session on your current environment, the migration path, and the infrastructure decisions worth making before you move.