How projects, branches, and hosting actually work on HostOdooSH. For account-specific questions, see the FAQ or contact us.
Connect any Linux box you already control — a cloud VM, bare metal, anything reachable over SSH as root. We use the root/sudo password once, to install our own SSH key, and never store it. Everything afterward (deploys, backups, resizing) happens over that key. It's your hardware the whole time; we only run the platform on top of it.
A project is one Odoo installation, backed by a Git repository, deployed onto one of your connected servers. Every project has a production branch (your live site) and any number of staging/development branches, each provisioned as its own isolated Odoo instance with its own database, reachable directly at your server's own address (custom domains aren't wired up yet).
Every push runs a real build (module install/update, dependency resolution) before traffic switches over. A build that fails leaves the previous version running untouched — nothing goes live half-migrated.
Upload your own purchased Odoo Enterprise apps as a zip straight into a project's addons folder — at creation time or any time after from its Settings tab. Already keep your custom addons in their own git repo? Point at it as a submodule instead, and it's cloned in automatically on every build from then on.
Create a real backup on demand from the Backups tab, download it, or restore it back — either onto the same project or a different one. Migrating an existing server over? Load an existing backup straight in when you first connect it, before you've even created a project.
In-place Odoo version upgrades run against a real OpenUpgrade-backed migration, with each step tracked individually. If a step fails, the upgrade pauses rather than silently rolling back — you can inspect the live migration log, fix the underlying issue, and resume from exactly where it stopped, or roll back cleanly if you'd rather start over.
Since it's your own server, there's no fixed tier to upgrade — go to a project's Resources section and set new CPU/RAM/disk values yourself, any time, for free. The only real limit is your server's own actual capacity: whatever you've allocated across all your projects on that box has to add up to no more than what it actually has.
Solo ($5/mo) is a fixed quota of one project at a time. Multi ($10/mo) lets you pick your own quota when you buy it — anywhere from 1 up to the current cap — same price regardless of which number you choose. A plan is bought as a code tied to one specific server, then redeemed the moment you create your first project on it. Connect several servers and each one carries its own separate plan, billed separately. Deleting a project frees its slot immediately for a new one.