Odoo hosting and upgrades, with backups we know will restore.
We host your Odoo on a server in the European Union that we set up and look after, or take care of it on Odoo.sh or Odoo Online. We keep backups and test that they restore, monitor the system, and move it to the new release when it pays off, after testing it on a copy with your add-ons.
YOUR ODOO, TODAY
Example Company S.A. · server in the European Union · 18 users
- BackupTonight 02:00 · also in a second locationOK
- Restore testSaturday · restored elsewhere, totals matchOK
- MonitoringServer, database, disk, HTTPS certificateOK
- Access18 users with one-time codesOK
- Security updatesApplied on TuesdayOK
NEW ODOO RELEASE
- Copywith every add-on
- 2Testing with your teamweek 2 of 3
- 3Live systemover a weekend
Only what has been tested on a copy reaches the live system.
WHO LOOKS AFTER YOUR ODOO TODAY?
An Odoo that works every day is easy to forget until the day something is needed. In a group it is often the Greek or Cypriot company's Odoo that nobody at head office really owns. These are the points worth checking in your Odoo hosting.
A backup list where the restore was never tested A backup nobody ever restored
The server keeps backups, but nobody has tried to restore one. On the day you need it, you find the attachments were missing, or that the backups quietly stopped months ago.
We back up every night, to a second location, and regularly test that it opens.
An Odoo report still loading while the warehouse waits Slow when everyone is in
At month end, with the whole team logged in, reports crawl and the warehouse waits to print delivery notes. Usually it's a server that didn't grow with the business.
We see what's slow, and grow the server when your work calls for it.
Three calendar sheets with upgrade dates that were postponed The upgrade that keeps slipping
Your Odoo is two releases behind because nobody knows what will happen to the add-ons. The longer it waits, the bigger the jump, and at some point Odoo stops shipping security updates for your release.
We tell you what changes for you, and test the upgrade on a copy.
An upgrade, step by stepThree access fields: everyone knows the password, the old partner still gets in Passwords too many people know
A former contractor can still log in, the admin password is shared around the office, and the server accepts connections from anywhere. Nobody has looked, because everything works.
Every user signs in with a one-time code on their phone, and the server admits only who it should.
WHAT ODOO HOSTING AND UPGRADES INCLUDE
Hosting in the EU
We set Odoo up on a server in the European Union, sized for your workload, and grow it as the business grows. If Odoo.sh suits you better, we work there.
Backups and restore tests
A copy of the database and attachments every night, plus one more in a second location. We regularly restore a backup on another server and check that everything is there.
Monitoring and speed
We watch the server, the database, disk space and certificates, and usually spot what's slowing down before your team does. We tune the database and scheduled jobs so reports don't keep people waiting.
Security and access
HTTPS, security updates, one-time codes from an authenticator app for every user, and server access only for those who need it. When someone leaves the team, their access goes with them.
Upgrades to the new release
When a new release comes out, we tell you what it changes for your work. If it's worth it, we test it on a copy with your add-ons and the Greek suite, and switch over a weekend.
Support for your team
Your team writes to us, in English or Greek, when something doesn't work: an invoice that didn't go out, a user who got locked out, a report that needs changing. The answer comes from someone who knows your Odoo.
WHERE YOUR ODOO CAN RUN
Odoo runs in one of three places. The choice decides what you can install, who keeps the backups and when upgrades happen. We work in all three.
Scroll sideways to see all columns
| What changes | Odoo Online | Odoo.sh | EU server, run by us |
|---|---|---|---|
| Who looks after the server | Odoo | Odoo | We do |
| Odoo edition | Enterprise | Enterprise, on the Custom plan | Community or Enterprise (Custom) |
| Your own add-ons and the Greek suite | No | Yes | Yes |
| Backups | Daily, by Odoo; you can download them at any time | Daily for the production system, by Odoo | Every night and in a second location, with restore tests |
| Test copy | A test duplicate that expires after 15 days | Staging environments | As many as you need, for as long as you need |
| New release | Mandatory: Odoo gives notice weeks ahead and upgrades on the date it sets | When you decide, tested on staging | When you decide, tested on a copy |
| Where the data lives | In the region you choose; Odoo's backups in Europe and Canada | In the region chosen at setup, e.g. Europe | On a server in the European Union |
| What we do | Setup, configuration, training, a check before every upgrade | Setup, add-ons, testing, upgrades, support | Everything: server, backups, monitoring, security, upgrades, support |
Odoo Online doesn't accept your own add-ons or add-ons from the Odoo Apps Store, so neither the Greek suite nor the e-invoicing connection through eInvoice Link. Editions and plans are explained in our guide Odoo Community or Enterprise.
AN UPGRADE, STEP BY STEP
This is how an Odoo moves to the new release, from the day it comes out to the Monday your team works in it. The switch shows what happens when an add-on isn't ready.
- Your Odoo
- Copy
- Testing
- New release
- The new Odoo release comes out. We try it on our own systems first, then write to you about what it changes for your work and whether to move now or later.
- We take a copy of the live system and move it to the new release, with your own add-ons and the Greek suite. The copy sends no emails, invoices or payments.
- We check that the totals stay the same (balances, stock, open documents) and run a normal day's work: an order, an invoice, a delivery note.
- An add-on written for you years ago doesn't load on the new release. The upgrade stops there, and nobody touches the live system.
- We adapt the add-on to the new release and run the upgrade of the copy again from the start.
- The check runs again: every add-on loads and the totals still match.
- For a week your team tries its daily work on the copy, and your accountant checks test invoices. Whatever they find, we fix before the switch.
- Saturday: a backup first, then the same upgrade we rehearsed, on the live system. On Monday your team works on the new release.
- A backup of the previous release stays on file, and we stay close to the team for the first days.
WHY HOST YOUR ODOO WITH US?
The same infrastructure that hosts your Odoo also runs our own platforms. If anything goes wrong, we're the first to feel it.
- Infrastructure
Backups in separate storage, for every Odoo
Every Odoo we host runs on Kubernetes, with the same tested setup, and backups are kept in separate storage. If the worst happens, your data is somewhere else, and safe.
- Upgrades
Odoo upgrades that don't stop your work
Before an Odoo starts on the new release, an automatic check confirms that its database matches the code. If something doesn't match, it waits, and you keep working as normal.
- Odoo add-ons
The Greek suite, always on the new release
We port the ten add-ons of the Greek suite to every new Odoo release ourselves, so new rules never catch you unprepared. The open-source add-ons we publish with the OCA community move along with them.
- E-invoicing
Your invoices don't get lost on the way
eInvoice Link, our platform that sends invoices from Odoo to the e-invoicing provider, runs on the same infrastructure and is monitored at every step. Every kind of failure has a written runbook, so the fix comes fast.
Want us to look at where your Odoo runs today? Tell us and we'll say what would change.
HOW WE MOVE YOUR ODOO TO NEW HOSTING
Roughly, for an Odoo that already runs somewhere else:
A check of your Odoo
Week 1. We look at where it runs, which add-ons it has, how it keeps backups, who has access and how far it is from the new release. You get the findings in writing.
Proposal
Week 1. We propose where it will run, what we will look after and when the next upgrade is worth doing, at a fixed price.
The move
Week 2. We move Odoo to its new home as a trial first, then for real over a weekend, with a backup beforehand and a check that everything opened.
From then on
Backups, monitoring, security updates and support for your team, in English or Greek. Once a year we talk about the new release.
QUESTIONS
Where will our Odoo be hosted?
Wherever suits you: on a server in the European Union that we set up and look after, on Odoo.sh, or on Odoo Online. The differences are in the table of the three options. Wherever it runs, the data and the passwords are yours, and you get a full copy whenever you ask.
Odoo.sh or a server run by you?
Odoo.sh is Odoo's own platform for companies that need their own add-ons: Odoo looks after the server, it needs Enterprise on the Custom plan, and hosting is billed separately, by resources. Our servers also run Community, and there we look after everything. Tell us how you work and we'll tell you which fits your case.
Can the Greek suite run on Odoo Online?
No. Odoo Online doesn't accept your own add-ons or add-ons from the Odoo Apps Store, so neither the suite nor the e-invoicing connection through eInvoice Link. If you need them, Odoo has to run on Odoo.sh or on your own server or ours. You can leave Odoo Online whenever you like: you download a backup of your database and we restore it on the new host.
How often should we upgrade?
Odoo brings out a new major release every year, and each release gets security updates for three years from its launch. We usually suggest moving when the new release brings something you need, and always before security updates stop for yours. On Odoo Online it isn't your choice: Odoo gives notice weeks ahead and upgrades on the date it sets.
What happens to our add-ons on the new release?
We adapt them. Odoo upgrades its own apps, but any other add-on has to be adapted by whoever maintains it. We port the Greek suite to every new release ourselves, and the add-ons written for you we adapt and test on a copy. If a third-party add-on isn't available for the new release yet, you know before you decide.
Can Odoo Community be upgraded too?
Yes. On Enterprise, the database is upgraded with Odoo's upgrade service, which is part of the subscription. For Community, Odoo offers no such service, and the move is done with OpenUpgrade, the OCA community's open-source tool. Either way, we rehearse it on a copy first.
What if the server goes down?
Monitoring alerts us, and we bring Odoo back on the same server or, if needed, on another one from the latest backup. Because we test restores regularly, we know they work before you ever need one.
Can you take over an Odoo someone else set up?
Yes, including the Odoo of a group's Greek or Cypriot company. We start with a check: where it runs, which add-ons it has and who maintains them, how it keeps backups and how far it is from the new release. Then we write down what's needed and at what fixed price. If you don't run Odoo yet, start with Odoo in Greece or moving to Odoo.
RELATED
Odoo Greece
Odoo set up for companies in Greece, with myDATA, delivery notes, ERGANI and payroll.
Moving to Odoo
From the business software you run today to Odoo, without stopping the business.
Greek suite for Odoo
Ten add-ons for what Greek law asks of a company, ported by us to every new release.
Odoo Cyprus
Odoo for companies in Cyprus, with the Cyprus chart of accounts and VAT report, and one Odoo for groups with a Greek company.
Guide: Odoo Community or Enterprise
What each edition has, how Odoo charges and where it can run.
Guide: Odoo first setup in Greece
Company details, VAT, numbering, warehouses, users and tests with your accountant.
TELL US WHERE YOUR ODOO RUNS TODAY.
And how it keeps backups and how far it is from the new release. Then we write down what we'd change in the hosting, when we'd do it and at what fixed price.