Operating on BYOS
Once your server is connected, day-to-day work looks just like managed hosting. This page covers the areas where running on your own server behaves differently: domains and SSL, Odoo Enterprise, backups, and subscription behavior.
Domains and SSL
Deployments on your own server do not receive automatic *.skysize.io addresses; those are reserved for managed cloud hosting. To reach a BYOS deployment over the web, you bring your own domain.
Without a domain
A deployment without a domain is still reachable for testing at http://<your-server>:<port>, using the server's address and the port assigned to the branch. The dashboard shows the exact URL on the deployment. This is plain HTTP and best kept for internal verification, not end users.
Adding your domain
- Open the branch's Domains section and add your domain (for example
erp.mycompany.com), leaving SSL enabled. - At your DNS provider, create an A record pointing the domain at your server's public IP (shown on the server's detail page in the dashboard).
- Wait for DNS to propagate, then open the domain in a browser.
On managed hosting you point a CNAME at your *.skysize.io hostname. On BYOS there is no such hostname, so you point an A record directly at your server's IP instead. The rest of the custom domain guide applies unchanged.
SSL certificates
HTTPS certificates for BYOS deployments are issued on your server via Let's Encrypt, and renewed there automatically. Skysize's own platform certificates are never installed on customer hardware.
For issuance to succeed:
- The domain's DNS must already resolve to your server.
- Ports 80 and 443 on the server must be reachable from the internet (Let's Encrypt validates the domain over HTTP).
Until the certificate is issued, the site may briefly be reachable over HTTP only.
Odoo Enterprise on your own server
Enterprise deployments on your server download the Odoo Enterprise source code using your own GitHub credentials, from your own Odoo Enterprise subscription. Skysize's enterprise credentials are never used on customer hardware.
To configure it, open your server's detail page and find the Odoo Enterprise source settings:
- GitHub token: a personal access token of a GitHub account linked to your Odoo Enterprise subscription. It is stored encrypted and never shown again after saving.
- Repository URL: leave empty to use the official
odoo/enterpriserepository, or set your own mirror (must start withhttps://).
You can also provide the token while creating an Enterprise project; the dashboard asks for it only when the target server has none configured yet.
Without a valid token, Enterprise builds on that server fail because the enterprise code cannot be downloaded. Community projects are unaffected.
Backups
The full backup system works on BYOS: automatic daily backups of production, manual backups, restores, downloads, and imports. Backup jobs run on your server, then upload the archive to the project's configured storage target.
Choosing where backups are stored
By default, backups go to the Platform default storage. To keep backups entirely under your control, give the project its own target:
- Open the project's Settings and go to Backup Target.
- Under Your backup targets, click Add Target and create a target of type AWS S3 or Google Cloud Storage with your bucket's credentials. Use Test to verify the connection.
- Select your new target as the project's Storage target and save.
From then on, backups of this project land in your own bucket, so both the live data (on your server) and the backups (in your storage) stay on infrastructure you control.
Backups are created on the server before upload, so keep enough free disk space for a compressed copy of your largest database plus its filestore.
If your subscription lapses
If your Bring Your Own Server subscription expires or is cancelled, Skysize never reaches into your server to shut anything down:
- Running deployments keep running. Your Odoo instances and their data stay up on your hardware.
- New work is blocked. Builds, deployments, and backups for BYOS projects are refused until the subscription is active again, and new servers or BYOS projects cannot be added. The affected projects show a banner in the dashboard.
- Renewing restores everything. Renew or repurchase the subscription from the Agents page and builds and backups resume; no reinstallation is needed.
If the account remains without any active Bring Your Own Server subscription for an extended period (about 30 days), connected servers that are not hosting deployments of active projects are removed from the dashboard. You would need to register and enroll them again after resubscribing. Servers still hosting your running deployments are not removed.
Limits and differences vs cloud hosting
- No
*.skysize.iodomains. Every deployment you want to reach over the web needs your own domain, with an A record pointed at your server. - No Cloudflare proxy toggle. Traffic goes straight to your server. If you want a CDN or DDoS protection in front of it, configure that at your own DNS or proxy provider.
- No region selection. Your server's location is the region. Latency and data residency are determined by where you host it.
- No free tier. BYOS projects always require an active Bring Your Own Server subscription, one per project.
- Capacity is yours to manage. CPU, RAM, and disk are limited by your hardware. Watch the server's metrics in the dashboard and add resources, or connect additional servers, before they run out. With multiple servers, production runs on the server you selected and other branches balance across all of them.
- Server maintenance is yours. Operating system updates, security patching, and firewall configuration of the machine are your responsibility. Skysize keeps the agent and your Odoo deployments up to date.
Everything else, including branch workflows, build logs, access management, and restores, behaves exactly as on managed hosting.