Every Odoo you run, with its version and region, in one list.
Click a screen to enlarge it
Odoo 16 to 20
Every current version
Your servers
Any VPS, your data
GitHub
Your modules, deployed
AI built in
In the console and in your Odoo
Supported versionsv20v19v18v17v16
The problem
Running Odoo is more than installing it.
The work starts after the first install, when there are several clients, several versions and nobody watching the servers.
01
Every server by hand
Database, proxy, certificates and workers, set up again for every client and slightly differently each time.
02
You find out last
A backup that stopped weeks ago, a disk at 100%, production down. The first warning is the client calling.
03
Deploying is a risk
Modules copied over SSH, no staging to try them and logs scattered in files nobody can find.
Features
What an infrastructure team does, without having one.
Everything you need to keep an Odoo running, on the same screen.
A server, ready in minutes
Hetzner, DigitalOcean or Vultr
Regions in Latin America
You only pick where
Use the machine you have
A VPS, the office PC or Windows
Connected with one line
WSL set up for you on Windows
Instant environments
Production or staging in minutes
Database, configuration and networking included
Bring the Odoo you have
Upload the .zip backup Odoo exports
From Odoo.sh, another host or your own server
Restore it on any environment in one click
GitHub integration
Deploy by push; submodules all at once or one by one
The deploy key installs itself
Commit and author of every deployment, with a way back
Custom domains
Your domain on any environment
Automatic SSL, no config files
Your office Odoo, on the internet
Publish an environment on your local network
With your domain and HTTPS
No router settings
Updates without surprises
Automatic, in your maintenance window
In your time zone
Automated backups
Daily backups on your server
On a paid plan, off it too, plus a weekly immutable one
Restore in one click
Clone production to test
From its current state or from any full backup
Neutralized: no emails, scheduled jobs or integrations
Without production access: a copy that deletes itself after 24 h
Production console, under control
Admins, always
Developers, if you allow it
An automatic backup before anything changes
A team with permissions
Owner, admin, developer or viewer
Each person, only in their projects
Alerts that reach you
Server down, backup failed, disk full or production stopped
Notice when it happens and when it clears
Each person picks what they get, outside addresses too
Live logs
Live logs from the panel
No SSH, no hunting for files
Database health
The heaviest tables and orphaned attachments
Message history and stuck jobs
Growth over time
Each environment day by day
Know when the disk will fill up
Real capacity
How many workers fit on your machine
And why, no sizing by eye
Into Odoo in one click
New
From the panel, as the administrator
With a secure link that works only once
On production, only the project admins
A public status page
New
90 days of uptime and incidents per server
Never shows its IP, projects or versions
A clear page while an Odoo cannot answer
The assistant in your Odoo
New
Your users ask and request views from Discuss
Your consultant builds, reviews and approves
Servers
Choose where your Odoo runs. We get it ready.
Create the server with us, or use one you already have. Either way it ends up set up and ready for new environments.
You pick, we create it
Hetzner, DigitalOcean or Vultr. We hand the machine over set up and ready for Odoo.
Close to your users
São Paulo, Santiago and Mexico City, besides Europe and the United States.
It stays under your control
The machine is yours from minute one, and so is everything running on it.
Pick the provider and the region.
One line on your server and that is it.
Your own machine
Already have a server? Connect it in one line.
A VPS, the office PC or a Windows machine. Copy the line, run it and it shows up in the panel in under a minute.
Linux or Windows
Ubuntu 22.04 or 24.04, and Windows 11, where we set up WSL for you.
Also on your local network
An office machine works too: its environments answer inside that network, with valid certificates.
And you can publish it
Open that Odoo to the internet with your domain and HTTPS. No router settings to touch.
AI in the console
Claude Code and OpenCode, inside every environment.
Open a console from the panel and work with AI on the real environment. It knows your Odoo version (models, fields, settings and views), configures for you and, when code is needed, proposes it before writing it. Nothing to install on your computer.
Terminal, Claude Code or OpenCode in the same tab
Shortcuts to update, install and test modules
Changes data only through Odoo, never with direct SQL
With your own account or AI provider
Publishes the code as a pull request to your repository
On production, asks for your confirmation before each change
app.dooservice.sh/projects/apiservicesac
Claude Code on the real environment, from the browser.
Assistant in your Odoo
Your users ask in Odoo. Your team builds the answer.
Dooservice Assistant is a chat in Odoo's Discuss. It explains how the company works, from the processes its consultants reviewed, and turns what someone wants to see into a request your team builds, reviews and deploys.
Ask how the company works
Who approves a discount, when an invoice goes out. The answer comes only from reviewed processes and says which steps it stands on. The AI sees no record.
Request in their own words
A list, a board or a report. Before sending, they see what was understood and on about how many records.
Built, reviewed, deployed
It is built on a development copy, as a pull request in your repository. You approve it in the panel and it arrives with the next deploy.
The project brain
Writes down how this company uses its Odoo from counts and settings, proposes improvements every week and turns what was made by hand into code.
Your AI account, your limit
Anthropic, OpenAI or a compatible service. Every call with its cost, and a monthly limit (100 US$ by default) that warns you at 80%.
Requests need a GitHub repository connected to the project.
Discuss Dooservice
Ariana · Sales
Who approves a discount above 10%?
Dooservice
The sales manager. The salesperson sends the quotation for approval, and it cannot be confirmed until the manager approves it.
From the reviewed process “Discounted sales”, steps 2 and 3
Claude Haiku 5.5 · organization account
Ariana · Sales
I want a board of this month's sales by salesperson
Dooservice
Request
Sales by salesperson, this month
A board · about 1,240 orders
Sent
Built
In review
Deployed
Production
Work on production without fear of breaking it.
The production console backs up the database as it opens and lets nobody write until it is done. You decide who gets in.
A backup before every session
Until the backup finishes, the console only reads. If something goes wrong, you restore in one click.
You decide who gets in
Owners and admins always; each developer only if you allow it, and only in their projects.
The AI asks first
Claude Code and OpenCode read freely, but change data only through Odoo and after your confirmation.
The console on production, with its backup ready.Access to the production console, set per member.
How it works
Your first Odoo running today.
Connect a server with one command. The rest is the panel.
01
Connect your server
Create one with us on Hetzner, DigitalOcean or Vultr, or connect the one you have with a single line. Linux or Windows.
One command
02
Create a project
Pick the server and give it a name. That's your client's workspace.
A name
03
Bring up an environment
Choose the Odoo version and the environment type. Database and networking come solved.
Odoo 16–20
04
Go to production
Your own domain, GitHub, backups and alerts. All from the same panel.
Live
app.dooservice.sh/servers/dooservice-agent-1
Each server reports its memory, disk, uptime and last backup.
Open source
What runs on your server, in the open.
The images your servers run, the modules in your Odoo and the skills of the AI are public on GitHub. Read them, audit them, use them or improve them.
Businesses elsewhere: enter your VAT number at checkout
All three plans include
AI in the console and the assistant in your Odoo, with your account or provider
Production console with an automatic backup first
A restore test every week
Email alerts, for whoever you choose
Servers and staging without limit
Deploy by push, and back again
GitHub with submodules
Domains and certificates
Clone environments from any backup
A team with roles and per-project access
Private networks and VPN
Odoo 16 to 20
How your backups are kept
Free
Daily backups on your server: 7 daily, 4 weekly and 3 monthly are kept.
Restore or clone an environment from any backup, in one click.
A restore test every week.
Paid plans
Everything in the free plan and, besides, off your server:
The same backups at another provider: if you lose the server, you do not lose your data.
A weekly immutable backup, locked for 14 days and kept for 35: nobody can delete it, by mistake or on purpose.
Restore from your server, from the off-site location or from the immutable one.
Grow a paid plan
When a plan falls short in one thing, add just that. It is billed with the plan, monthly or yearly.
Extra project
$4 a month
Extra 50 GB of backups
$7.50 a month
Second off-site location
$8 a month
Third off-site location
$15 a month
Work out your fee
Extra projects
Extra backups
Extra locations
Total
$39a monthplus taxes
10 projects · 50 GB off-site · 1 location
FAQ
Common questions.
Do the servers stay mine?
Yes. You install the agent on your own VPS, wherever you rent it. The machine, the databases and the backups stay yours.
Which Odoo versions does it support?
Odoo 16, 17, 18, 19 and 20. Each environment picks its version, so a server can run several at once.
Do I need to know Docker or Linux?
No. The panel sets up the database, the configuration, the networking and the certificates. You pick a version and a name.
Can I deploy my own modules?
Yes. Connect a GitHub repository, with deploy keys and submodules, and deploy it to any environment.
What happens if a backup fails?
You get an email the same day, and another when it works again. Backups are scheduled and restored from the panel, and every week we check that one really restores. On a paid plan they are also kept off your server, at another provider, with a weekly one nobody can delete: the one that saves the day somebody deletes something they needed.
Is the AI in the console safe?
The AI reads freely, but changes data only through Odoo and, on production, asks for your confirmation before each change. Sessions close after 30 minutes idle; on production, after 10 idle and at most 30 minutes. Without a connected repository, it configures Odoo but does not create or change modules.
Can I use a machine on my own network?
Yes. A VPS, an office PC or Windows, where we set up WSL for you. And if you want that Odoo to answer from outside, you publish it with a switch: your machine reaches out to us, so there are no router settings to touch, and the traffic stays encrypted all the way to your server.
Who pays for the AI?
You, directly to your provider. The AI account belongs to your organization or to one project (Anthropic, OpenAI or a compatible service), never to Dooservice. The panel records each call with its estimated cost, and a monthly limit, 100 US$ by default, warns by email at 80% and stops the calls when it is reached.
Your next Odoo can be running today.
Connect a server, create a project and run everything from one panel.
Supported versions v20v19v18v17v16 
