OEC.sh alternative: CICDoo vs OEC.sh, compared honestly

OEC.sh and CICDoo in one minute

OEC.sh is a deployment and management platform for self-hosted Odoo, built by OpenEduCat. You connect your own cloud account (AWS, Google Cloud, Azure, DigitalOcean, Hetzner, Vultr, Linode, OVH) or any Linux server, link a GitHub, GitLab or Bitbucket repository, and OEC.sh handles deployment, SSL, backups and monitoring. Its homepage also offers its own managed infrastructure as an alternative to bringing a cloud account. OEC.sh describes itself as a platform rather than a hosting provider: you own the servers, it runs the automation.

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

On paper the two overlap a lot. Some third-party comparisons describe CICDoo from outdated information; this page and the CICDoo docs are the current reference.

Where they differ

Buying model. OEC.sh publishes flat monthly plans on its pricing page, from an entry plan with no platform fee up to a SaaS reseller plan, with self-serve sign-up, upgrades and downgrades. CICDoo does not sell self-serve plans: paid access is quoted per project through sales, with nothing feature-gated by plan. Both keep your cloud bill separate and add no compute markup. If you want to sign up and deploy tonight without talking to anyone, OEC.sh is built for that. If you want a scoped agreement that can include engineers running operations, CICDoo is built for that.

Git and stages. Both deploy from Git branches to environments. OEC.sh supports Bitbucket in addition to GitHub and GitLab and documents branch-to-environment mapping, unlimited staging and production clones with automatic PII scrubbing. CICDoo supports GitHub, GitLab.com and self-hosted GitLab, maps every branch to an instance and lets you merge between branches from the console.

Alerts. OEC.sh sends alerts by email, Slack, Discord or webhooks. CICDoo sends them by email, Telegram and SMS. Pick the one that matches where your on-call people actually look.

Permissions. OEC.sh lists RBAC, 2FA, SSO and audit logs. CICDoo grants access per resource (project, instance, server) and per action inside a workspace, so a contractor can work on one staging instance without access to production (workspace permissions).

Operations and AI. OEC.sh positions itself as automation, not people: its FAQ says the platform automates the infrastructure work that normally requires a DevOps engineer. CICDoo offers the same automation plus an optional managed service where CICDoo engineers run your servers, and ticketed human support. On AI, OEC.sh ships an MCP server for Odoo data and, on its Pro plan, an AI dev sidecar with Claude Code, Cursor, Gemini CLI and Codex terminals. CICDoo has agent tasks that work on your repository and Claudoo, an assistant that does real Odoo work (confirm orders, post invoices, validate pickings) as the user through Odoo's own business logic, with an audit trail.

Choose OEC.sh if...

• You want published, self-serve pricing and to start without a sales conversation.
• Your code is on Bitbucket, or you want to spread projects across several cloud providers from one account.
• You need a public REST API, a webhook engine and automation rules to script your hosting.
• You want staging clones with automatic PII masking and a browser SSH terminal on every plan.
• You plan to resell Odoo Community as your own SaaS: their SaaS plan ships storefront, client portal and Stripe billing modules.
• You prefer Slack or Discord for alerts.

Choose CICDoo if...

• You want the option of CICDoo engineers operating your servers, not only software doing it.
• You host code on self-hosted GitLab.
• You need Odoo versions older than 14.0 (CICDoo covers 11.0 to the latest release, plus master).
• You want alerts on Telegram or SMS.
• You run an agency and need per-resource, per-action permissions, white-label workspaces and a partner program.
• You want an assistant that does business work inside Odoo (Claudoo), alongside coding agents.

There are no per-user fees and no compute markup on CICDoo; you pay your provider for servers. Talk to us for a quote.

Moving from OEC.sh to CICDoo

1. Keep or add a server. Because OEC.sh already runs on your cloud account, you can reuse the same provider. Add a server that CICDoo can reach over SSH as root or a sudo user (add a server). A fresh server avoids two platforms managing the same machine.
2. Connect the repository. Link the GitHub or GitLab repository and create the project. If your code is on Bitbucket, mirror it to GitHub or GitLab first.
3. Export from OEC.sh. Download a backup with the full database and filestore. OEC.sh states each backup includes both, stored in your own bucket or SFTP.
4. Restore on staging. With an S3-compatible bucket configured, upload the backup 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. Check scheduled actions, mail servers, payment and shipping connectors, and that the Odoo version matches.
6. Cut over. Lower DNS TTL a day ahead, freeze writes on OEC.sh, take a final backup, restore it on the CICDoo production instance and point the A record at the new server. SSL is issued automatically once DNS resolves.