Zebroo Technical Docs
Zebroo builds a focused toolchain for Odoo development, integration, testing and operations. Each tool covers one phase of the Odoo lifecycle — from setting up a local workspace, through integrating external systems, to testing and deploying — and they are designed to work together.
Our Key Products
| Product | What you'll find |
|---|---|
| zSYNC | Our low-code/no-code integration platform: pipelines, worker types, mappers, examples and developer guides |
| zCICD | Our CI/CD platform for Odoo: branches as testable instances, test runs, approvals and releases |
| zodoo | Our Docker-based Odoo development framework: installation, configuration, DB backups and restores, settings and troubleshooting |
| Gimera | Multi-repository management: assembling and pinning an Odoo source tree from many repos |
| zCloud | Our Odoo hosting platform: create a project and get a provisioned, hardened server running Odoo |
What each one is for
Gimera — assembling the source tree
Gimera is the foundation. An Odoo project is rarely one repository: it pulls in
the Odoo core, possibly Enterprise, several OCA addon repositories and your own
modules. Gimera describes that whole landscape in one gimera.yml, pins each
repository to a known commit, and applies local patches without forking
upstream — so every developer, every CI run and every production system builds
from an identical source tree.
zodoo — running Odoo locally and everywhere else
zodoo (formerly wodoo) wraps Docker Compose and the Odoo server into a single
settings-driven CLI called odoo. It manages the full container stack, generates
docker-compose.yml from a settings file, and handles backup and restore, module
updates, registry push and pull, and debugging.
The point is reproducibility: the same commands work on macOS, on Windows via WSL2, on Linux and in CI, so a developer's machine behaves like the server.
zSYNC — connecting Odoo to everything else
zSYNC is a low-code/no-code integration tool built as a collection of Odoo modules. It connects Odoo to external interfaces and APIs, letting you build automated workflows without extensive programming.
Its core is the pipeline: a chain of workers that grab data from a source, transform and map it, and dump it to a destination. Pipelines keep information consistent across platforms while staying traceable and observable, which cuts manual effort and the data inconsistencies that come with it.
zCloud — hosting it
zCloud is the hosting layer. You sign in with GitHub, create a project, and a real server is provisioned with Odoo running on it — hardened from first boot, with TLS, backups, staging and a browser console for the day-to-day.
It is where the other three end up: Gimera assembles the source, zodoo runs it, zCICD tests it, and zCloud is where it lives for the customer.
zCICD — testing and shipping
zCICD turns every branch in your Git repository into a running, testable Odoo instance, automatically. It builds and starts the instance, seeds its database, runs the tests a change can actually affect, and moves finished work through review and approval into a release.
It is built for Odoo specifically: multi-repository addon landscapes, Docker execution, controlled module installation and updates, and a structured Git workflow.
How they fit together
Gimera assembles the source. zodoo runs it. zSYNC connects it to the systems
around it. zCICD tests and ships it, and zCloud hosts it — using the same gimera.yml and the same
odoo commands you use locally, so what passes in CI matches what you built.