Bring Your Own Server
Bring Your Own Server (BYOS) lets you run your Odoo projects on your own hardware while keeping the full Skysize experience: the same dashboard, the same Git-driven build pipeline, the same backups and monitoring. You provide a Linux server; Skysize deploys and manages your Odoo instances on it.
With BYOS, your Odoo databases and files live on infrastructure you control, in your data center, on your preferred cloud provider, or on a VPS you already rent. This makes BYOS a good fit when you have data-residency requirements, existing hardware, or simply want full control of the machine your ERP runs on.
BYOS requires an active Bring Your Own Server subscription. See pricing for plans, and the setup guide for how to get started.
How it works
You install a small service, the Skysize agent, on your server. The agent connects out to the Skysize cloud and waits for instructions: build this branch, start this container, take this backup. Your projects then deploy onto your server instead of Skysize's managed infrastructure.
Everything else stays the same. You push to your Git repository, Skysize builds the deployment, and the dashboard shows logs, metrics, and backups, exactly as with managed hosting. The only difference is where the containers run.
In the dashboard, your connected servers are managed on the Agents page.
Managed hosting vs BYOS
| Managed cloud hosting | Bring Your Own Server | |
|---|---|---|
| Hardware | Provided by Skysize | Provided by you |
| Odoo deployment, updates, builds | Skysize | Skysize |
| Backup scheduling and restore | Skysize | Skysize (stored where you choose) |
| Operating system and server security | Skysize | You |
| Server capacity and disk space | Skysize | You |
Default *.skysize.io domains | Yes | No, you use your own domain |
| Region selection | Yes | Not applicable (your server is the location) |
| Free tier | Available | Not available, subscription required |
What Skysize keeps managing
- Building and deploying your branches from Git.
- Odoo container lifecycle: start, stop, update, rollback-safe upgrades.
- Backup scheduling, restores, and backup retention.
- The dashboard: logs, metrics, domains, access management.
- Agent software updates.
What you own
- The server itself: provisioning, OS updates, security hardening, and physical or cloud-level access.
- Capacity planning: CPU, RAM, and disk for the Odoo instances you host.
- A domain for each deployment you want to reach over the web, with DNS pointed at your server.
- Your Odoo Enterprise credentials, if you deploy Enterprise (see Operating on BYOS).
Server requirements
| Requirement | Minimum |
|---|---|
| Operating system | Ubuntu 22.04+ or Debian 12+ |
| Architecture | x86_64 or ARM64 |
| CPU | 2 vCPU, plus what your Odoo instances need |
| RAM | 4 GB, plus roughly 1-2 GB per running Odoo instance |
| Disk | 50 GB free, for databases, files, Docker images, and backups |
| Network | Outbound internet access; a public IPv4 address |
The installer sets up everything the agent needs (Docker, PostgreSQL, a web server, and the agent itself), so a fresh, empty server is the ideal starting point.
Your server must be able to reach the internet outbound: the Skysize cloud, the Docker registry (to pull Odoo images), and your Git provider (to clone your repositories). To serve your Odoo sites over HTTPS, ports 80 and 443 must be reachable from the internet; this is also required for SSL certificate issuance.
Size the server for the number of environments it will host, not just production. Staging and development branches each run their own Odoo container and database.
Security model
BYOS is designed so that connecting a server to Skysize does not open your network up:
- Outbound-only connection. The agent dials out to the Skysize cloud over an encrypted, certificate-authenticated channel. You do not need to open any inbound port for Skysize to manage the server; inbound ports 80/443 are only used to serve your own Odoo sites.
- One-time enrollment. The server joins with a single-use join token issued from the dashboard. After enrollment, the agent holds its own certificate, which renews automatically.
- Your projects only. Servers you connect are pinned to your account. Only your own projects ever deploy to your server; no other customer's workload can be placed there.
- No platform secrets. Skysize's own credentials and platform certificates are never sent to customer servers. SSL certificates for your deployments are issued directly on your server via Let's Encrypt, and Odoo Enterprise code is fetched with your own credentials, never Skysize's.
- Your data stays with you. Databases and file attachments live on your server. Backups are written to the storage target you configure, which can be your own bucket (see Operating on BYOS).
Next steps
- Set up your first server: subscription, installation, and first project.
- Operating on BYOS: domains and SSL, Odoo Enterprise, backups, and subscription behavior.