Skysize alternative: CICDoo vs Skysize, compared honestly

Skysize and CICDoo in one minute

Skysize is an Odoo hosting company built by former Odoo engineers, offering three models on one platform: fully managed hosting on Skysize's cloud, bring your own server (you install a lightweight agent on any Linux server and Skysize orchestrates Odoo on it), and an on-premise edition that runs entirely inside your network and is air-gap compatible. Each Git branch maps to a production, staging or development environment, staging copies have mail and scheduled actions switched off before they start, and every update is preceded by a database copy with automatic rollback. Skysize states its platform is ISO 27001 certified.

CICDoo is a Git-driven Odoo DevOps platform. You connect Linux servers you own over SSH, link a GitHub or GitLab repository (GitLab.com or self-hosted GitLab), and CICDoo deploys an Odoo instance per branch in its own Docker container, with PostgreSQL alongside, nginx and automatic SSL. Branches map to development, staging and production. CICDoo also offers fully managed operations by its engineers on your servers.

These are two of the closest products in this market. The differences are in details that matter to specific teams.

Where they differ

How the server is connected. Skysize installs an agent that runs as an unprivileged user and connects outbound only, so you open no inbound port for Skysize, and its on-premise edition works without internet access. CICDoo connects to your server over SSH with a key or password you provide (adding a server) and then gives your team per-user SSH access to instances. If your security policy forbids inbound management access, or the network is air-gapped, Skysize has the more suitable architecture.

Odoo versions. Skysize supports every stable version from 16 to 19. CICDoo supports 11.0 to the latest release, plus master. If you still run Odoo 12 to 15 in production, CICDoo can host them while you plan the upgrade.

Monitoring and alerts. Skysize's Health tab reads the production log and container and turns known Odoo problems into signals (failing scheduled actions, worker memory limits, default admin password, missing attachments), with a suggested fix and 30-second uptime checks. Their pages describe signals in the dashboard; we could not find the notification channels published. CICDoo runs uptime checks and resource metrics and sends alerts by email, Telegram and SMS (alert notifications).

Roles. Skysize has three roles per project (User reads, Developer works on test branches only, Admin runs the project), groups, expiring invitations and an audit log that records every Log in as user action. CICDoo permissions are per resource and per action inside a workspace (workspace permissions), which gives finer control when an agency hands different clients or contractors different slices.

AI. Skysize's MCP access is deliberately read-only: an assistant can read build logs, the Odoo log, slow queries and metrics, and cannot change anything. CICDoo goes the other way, with agent tasks that work on your repository and Claudoo, which does real Odoo work (confirm orders, post invoices, validate pickings) as the user with an audit trail.

Choose Skysize if...

• You need Odoo on-premise or air-gapped, or you cannot open inbound management access to your servers.
• You want published per-project prices and the choice to move a project between your server, Skysize's cloud and on-premise.
• You value the safety defaults: neutralised staging, a database copy before every update and automatic rollback.
• You want an ISO 27001 certified provider and a contractual uptime SLA on the managed tier.
• You are an Odoo partner who wants recurring commission on hosting and white-label options across all three models.
• You want an AI assistant that can only read, never write.

Choose CICDoo if...

• You run Odoo versions older than 16.0, or you need master for testing.
• You host code on self-hosted GitLab.
• You want alerts delivered to Telegram or SMS.
• You need per-resource, per-action permissions across many projects, instances and servers.
• You want AI that performs Odoo business tasks as the user, plus coding agents on your repository.
• You want plain SSH access to instances for your developers.

CICDoo paid access is quoted per project, with no per-user fees and no compute markup. Talk to us.

Moving from Skysize to CICDoo

1. Prepare a server. Provision a Linux server CICDoo can reach over SSH as root or a sudo user and add it to CICDoo. Use a fresh server rather than one that still runs the Skysize agent.
2. Connect the repository. Link your GitHub or GitLab repository and create the project. Bitbucket users should mirror to GitHub or GitLab first.
3. Export from Skysize. Download an exact copy of the production backup as a standard Odoo zip with database and files. Skysize's backup page confirms downloads work anywhere Odoo runs.
4. Restore on staging. With an S3-compatible bucket configured, upload the zip in the CICDoo instance's Backups tab and restore it on a staging branch (backups and restore). Enable Enterprise if you use it.
5. Test. List anything you configured in the Skysize dashboard rather than in Odoo (environment variables, extra domains), since that is not part of the Odoo backup, then check scheduled actions, mail and integrations.
6. Cut over. Lower DNS TTL in advance, freeze writes, take a final backup, restore it on production and point the A record at the new server. CICDoo issues SSL once DNS resolves.