Where is your Odoo hosted?

Two hosting options

There is no one-size-fits-all solution. The right hosting option depends on your company’s setup, existing infrastructure, and in-house IT capabilities.

If you decide to switch from one hosting option to the other later, it requires a migration rather than rebuilding your Odoo solution. Your Odoo environment, database, and custom developments remain unchanged.

Which Hosting Option Is Right for You?

On Your Infrastructure

We install Odoo on your Linux servers and configure the environment so that your IT team can manage it independently going forward.

Odoo runs as systemd services that restart automatically after a server reboot or process failure. We define service dependencies and resource limits and configure logging so that Odoo logs can be managed and archived alongside other server services. There is no need to start Odoo services manually, and an issue with a single process does not affect the entire server.

We also configure PostgreSQL based on the system workload, as well as a Caddy reverse proxy with automatically issued and renewed TLS certificates. Web and cron processes run as separate services, while the filestore and backups follow a clear and documented structure.

The test environment is built according to the same principles as the production environment. This allows version upgrades and other changes to be tested under conditions that closely match the production setup before they are deployed.

At handover, you receive the complete server configuration together with management documentation. From there, your own IT team can take over the day-to-day management, or Avalah can continue to provide updates and monitoring under an SLA.

On Our Infrastructure: NixOS

Our hosting environment is built on NixOS. We chose it for a practical reason: it gives us precise control over how an Odoo server is configured and allows us to reliably recreate the same environment whenever needed.

A conventional server setup typically evolves over time through many small changes. Software packages and dependencies are added, configurations are adjusted, and quick fixes are made. Unless every change is accurately recorded, recreating the same environment later can be difficult. As a result, test and production environments can gradually drift apart, meaning that an upgrade that worked in testing may behave differently in production.

With NixOS, the entire server configuration is defined and version-controlled. This includes the operating system, PostgreSQL database, Python environment, Odoo version, and any custom developments created for the customer. Instead of configuring servers individually by hand, environments are built from the same configuration. This keeps them consistent and prevents unnoticed differences from accumulating over time.

In practice, this provides two key benefits. First, test and production environments are built from the same configuration, allowing version upgrades to be tested in an environment that matches the production system as closely as possible. Second, deployments can be rolled back to the previous working version. If an upgrade fails, it can be reversed quickly instead of leaving the system unavailable while the cause of the issue is being investigated.

Every change made to the environment is also traceable. Version control provides a clear record of what was changed, when the change was made, and who made it.

Backups, Updates and Recovery

A backup only proves its value when it can actually be restored. That is why regular recovery testing is part of our hosting service.

We configure automated backups of both the database and filestore and store them separately from the server running Odoo. This ensures that backups remain available even if the Odoo server itself is affected. Recovery is tested at a frequency agreed with each customer.

Version upgrades are first carried out in a test environment using a copy of your actual data. An upgrade is deployed to the production system only after testing and within an agreed maintenance window. The Odoo version upgrade itself is covered by our upgrade service, while the role of hosting is to provide a controlled and recoverable environment for the process.

Backup retention periods, backup frequency, and the target recovery time are agreed individually with each customer and documented in the contract.

The Right Solution Starts with Understanding Your Current Setup

We begin by reviewing your current environment: your existing infrastructure, Odoo version, custom developments, and integrations, as well as the impact on your business if Odoo becomes unavailable.

Based on this assessment, you receive a written recommendation comparing both hosting options. We also consider factors that can easily be overlooked: who responds when an issue occurs and how quickly, how long it would take to restore the system, and when updates can be carried out.

If your current setup works well and there is no clear reason to change it, we will tell you that too. Changing your hosting setup only makes sense when it helps address a specific risk.