Skip to main content

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 receive a default skysize.io address, but new default addresses are rate-limited per account. The recommended setup is to attach your own domain to the project once: one wildcard DNS record, then every branch gets a hostname under it with certificates issued on your server. See Your domain on BYOS. The rest of this section covers adding a single domain to one branch.

Adding your domain​

  1. Open the branch's Domains section and add your domain (for example erp.mycompany.com), leaving SSL enabled.
  2. At your DNS provider, create an A record pointing the domain at your server's public IPv4 address (shown on the server's detail page in the dashboard).
  3. Wait for DNS to propagate, then open the domain in a browser.
note

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, in the server's firewall and in your cloud provider's security group (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 read the Odoo Enterprise source code with your own access, from your own Odoo Enterprise subscription. Skysize's enterprise credentials are never used on customer hardware.

Configure it on your server's detail page, under Odoo Enterprise source. There are two options.

Deploy key (recommended)​

Keep your own copy of the Enterprise source in a private repository you control, on any git host: GitHub, GitLab, Bitbucket or a self-hosted server. It needs one branch per Odoo version, named after the version (for example 19.0). If Odoo gave you access to odoo/enterprise, create your copy as a mirror: a new, empty private repository with the same content, not a GitHub fork. A fork of Odoo's private repository stays attached to Odoo's repository, and GitHub can refuse to let Skysize install the deploy key on it automatically even when you are an admin. Without access to odoo/enterprise, push the source archive downloaded from odoo.com instead.

git clone --bare git@github.com:odoo/enterprise.git
cd enterprise.git
git push --mirror git@github.com:your-company/enterprise.git
  1. Enter the repository URL (SSH or HTTPS form) and click Generate deploy key.
  2. Skysize generates a read-only key for that repository only. When one of your connected Git accounts is an admin of the repository, the key is installed on it automatically.
  3. Otherwise, copy the public key and add it to the repository's deploy keys, with read access only. Install automatically tries again after you connect the right Git account.

A deploy key never gives access to anything but that one repository, and removing it on the server also removes it from the repository when Skysize installed it. Keep the repository up to date when Odoo publishes fixes; a monthly refresh is a good habit. For a mirror, run git fetch origin '+refs/heads/*:refs/heads/*' --prune in the bare clone, then git push --mirror again.

Deploy keys need agent 1.4.4 or later on the server.

Docker image with Enterprise​

The server can run a Docker image that already contains Enterprise; nothing is downloaded then.

You can set up either one while creating an Enterprise project: when the target server has no Enterprise source yet, the dashboard asks for one, with the deploy key as the default choice.

Why not Odoo's official repository?​

Pointing your server at odoo/enterprise directly would make every deploy pull whatever Odoo pushed that day. A change that expects newer Community code than your image carries can break the instance, with no way to go back. With your own copy you decide when to update, and you can revert a bad update. This is why the dashboard offers deploy keys on your own repository, not Odoo's.

caution

Without a deploy key or an Enterprise image, Enterprise builds on that server fail because the enterprise code cannot be found. Community projects are unaffected.


Workers and memory​

Your server, your sizing: on BYOS the deployment's worker count is not sold by the plan, you choose it. Open the project's Settings and go to Workers and memory. These settings size the production deployment only; staging and development deployments always run as a single Odoo process on fixed resources.

  • Workers: the number of Odoo HTTP worker processes. Leave it at 0 for a single process that serves HTTP and scheduled actions together, which is the right choice for a small instance or a modest server. Set 2 or more to run Odoo in multiprocess mode, where each worker handles requests in parallel.
  • Cron workers: how many processes run scheduled actions. Only used in multiprocess mode; Odoo's default is 2.
  • Memory per worker: the hard memory ceiling of each Odoo process, in MB. The minimum is 512 MB and the default is 1024 MB. A process that exceeds it is restarted by Odoo, so raise it if your workload handles large imports or reports.

When you change any of these, the dashboard shows the maximum RAM the deployment may use before you apply: every process at its memory ceiling, plus 512 MB of headroom for the container. Check that your server has that much memory available, on top of Postgres and anything else it runs.

Apply and restart saves the sizing and restarts the production deployment, so expect a short interruption.

note

The Request timeout and Cron worker timeout settings live in the same section and behave exactly as on managed hosting. See Time Limits.


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​

BYOS projects back up to your own storage: Skysize's platform storage is not offered as a target, so both the live data (on your server) and the backups stay on infrastructure you control. Until you configure a target, no backups are made, and the project shows a red banner saying so.

  1. Open the project's Settings and go to Backup Target.
  2. Under Your backup targets, click Add Target and create a target (see the fields for each type below). Use Test to verify the connection: it runs on the server of the production branch, so deploy that branch first.
  3. The first target you add is selected as the project's Storage target automatically. If you add more later, pick the one to use under Storage target and save.

Fields for each type​

Each target has a Name and a Type. The other fields depend on the type. Credentials are stored encrypted and are not shown again after saving: leave a secret blank when editing to keep it. Prefix is always optional and places the archives in a folder, which is useful when several projects share one bucket.

AWS S3​

FieldValue
BucketThe bucket's name. It must already exist.
RegionThe bucket's Region. Defaults to us-east-1.
AuthenticationIAM role if your server is an EC2 instance, so no secret is stored. Access keys otherwise, with the Access key ID and Secret access key of an IAM user.

The role or user needs the permissions listed in the form. Copy policy JSON gives you a policy ready to paste in AWS.

S3-compatible (Wasabi, R2, MinIO...)​

For other providers with an S3 API, such as Wasabi, Backblaze B2, Cloudflare R2, MinIO, OVH, Scaleway, Hetzner and DigitalOcean Spaces.

FieldValue
BucketThe bucket's name. It must already exist.
EndpointYour provider's S3 URL.
RegionYour provider's region, or any value if it has none.
Access key ID and Secret access keyThe key your provider gave you.
Path-style URLsTurn on only if your provider requires it.

Google Cloud Storage​

FieldValue
BucketThe bucket's name. It must already exist.
CredentialsServer default if your server runs on Google Cloud with access to the bucket, so no key is stored. Service account key otherwise: paste the contents of the key file.

The service account needs the Storage Object Admin role on the bucket. With Server default, download links are signed by Google on the server's behalf, so the VM also needs the cloud-platform access scope, and its service account the Service Account Token Creator role on itself. A service account key needs neither.

Azure Blob Storage​

FieldValue
Storage accountThe account name, not its URL.
ContainerThe container's name.
AuthenticationManaged identity if your server runs on Azure, so no secret is stored. Access key otherwise: key1 or key2 from the storage account's Access keys.
Managed identity client IDOptional. Only when the server has several user-assigned identities.

A managed identity needs the Storage Blob Data Contributor and Storage Blob Delegator roles on the account.

Filesystem​

Writes archives to a Directory on the server that runs the project.

caution

Filesystem backups live on the same machine as your databases. They protect against bad data (accidental deletions, failed upgrades) but not against losing the server itself. For disaster recovery, use one of the storage types above, or copy the backup directory off the server yourself.

tip

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.

Storing files once (deduplication)​

Most files in an Odoo filestore (attachments, images, documents) do not change from one backup to the next, yet a regular backup stores all of them again every day. Turn on Store shared files once (deduplication) in the target's form to store each file only once per project: every backup still has its full database dump, and it points to the files it needs. On a large filestore this makes backup storage much smaller, and the backup storage shown for the project is what is really stored.

  • It applies to new backups only. Backups taken before stay as they are and keep working. Turning it off again also applies to new backups only.
  • Restores, off-site copies and downloads work as usual: Skysize rebuilds a standard Odoo .zip with the filestore.
  • On a bucket target, the first download of a backup takes a few minutes to prepare. The button shows Preparing… for everyone on the project, and the download starts by itself if you keep the page open. Once ready, the backup downloads in one click for about a day, and the button shows the time left. If your domain points straight at your server, the download starts at once.
  • The archives in your bucket are no longer complete Odoo backups on their own: they have no filestore, and the files sit under a blobs/ folder. Restore and download them through Skysize, not straight from the bucket.
  • A daily cleanup deletes the files that no backup uses anymore. Files less than a day old are always kept.

It needs the Skysize agent 1.4.23 or later on your server (agents update themselves).


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.
caution

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.io domains. 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.