1. Scope and acceptance
These terms apply to everyone who creates an account and to everyone who uses an environment provided through it. Creating an account, or using one created for you, means accepting them.
If you bought your environment from an integrator using this platform rather than from us, your contract is with that integrator. These terms describe how the platform behaves; your commercial terms are theirs.
2. What the service is
The platform provisions and operates Odoo Community environments: it builds images from a Git repository, deploys them, holds a database and filestore for each, takes backups, and exposes logs and metrics.
It is infrastructure and tooling. It is not Odoo consulting, it does not write your modules, and it does not make your business processes work — those remain yours.
3. Your account
Keep your details accurate — the billing country determines your currency and the taxes applied, and correcting it later does not re-issue past invoices.
You are responsible for your credentials and for the people you invite. A team member you grant a role can act with it, including actions that cost money or destroy data.
4. Acceptable use
You may not use the platform to:
- Host or distribute unlawful content, or content you have no right to host.
- Mine cryptocurrency, or run workloads whose purpose is to consume compute rather than to run your business.
- Attack, probe or overload the platform or another customer, or attempt to reach an environment that is not yours. Testing your own environment is allowed and encouraged; the security page says how.
- Send unsolicited bulk email from an environment.
- Redistribute third-party modules in breach of their licences.
5. Odoo and third-party licences
Odoo is a registered trademark of Odoo S.A. The platform deploys both the Odoo Community edition (LGPLv3) and Odoo Enterprise, and is not affiliated with, endorsed by or a partner of Odoo S.A. The edition is chosen from the catalogue, environment by environment.
You are responsible for the licences of everything you install: your own modules, modules from the marketplace and modules from third parties. The Odoo Enterprise licence is contracted directly with Odoo S.A. and is not included here: deploying an Enterprise environment assumes you hold a valid licence.
6. Your data and your code
Your database, your files and your modules remain yours. Nothing here transfers ownership.
You grant us only what running the service requires: storing, copying, backing up and transmitting your content in order to operate your environments, and nothing beyond that.
7. Pricing and invoicing
An environment is priced by its plan and the number of replicas it runs. Invoices are issued monthly per team and currency. Beyond the published plans, an environment can be sized to order -- CPU, memory, storage and replicas -- after a workload study and on an accepted quote; it is then billed at the quoted price, under the same periodicity and proration rules.
Your currency follows your team country, and prices may differ by country where a regional price list exists. Applicable taxes are calculated at invoicing and recorded on the invoice itself, so a later tax change does not alter an invoice already issued.
An environment created or resized mid-month is prorated to the days it was live. A suspended environment continues to be billed while its data is retained.
8. Credit balance
The platform runs on a prepaid balance. Money you pay in does not expire. Bonus credits granted with a top-up tier or a coupon do expire, and are consumed before the money you paid.
Creating or resizing an environment is refused when the balance would not cover the run rate that would follow, including the addition. Top up first, then create.
9. Payment and renewal
Mobile money does not permit off-session debits. A renewal on that rail is an amount that becomes payable and that you pay; it is not a charge we can push to your handset without you.
Concretely: nothing is taken automatically on those rails. If a payment is due and not made, the account moves into the process in the next section.
10. What happens when an invoice is not paid
A ladder, with a warning at every rung and no silent deletion:
- You are warned before the balance runs out, based on the run rate of what you have running.
- Unpaid past the grace period, the team is suspended: environments stop, and creating, starting, resizing and deploying are frozen. Your data is retained.
- Longer still, the debt is written off for accounting purposes. The team stays suspended and the data stays.
- Final deletion of a suspended team is a manual administrative action, taken deliberately. It is irreversible and it destroys backups too.
11. Availability
We aim for continuous availability and do not commit to an uptime figure outside a separate signed support agreement. Where no such agreement exists, no service level is owed.
Maintenance can interrupt service. Where an interruption is planned and significant, we give notice; a fix for an active security issue may be applied immediately.
12. Backups and restores
Backups are taken according to your plan and can be restored into a new environment.
Two properties worth knowing before you rely on them. A restore only moves forward across PostgreSQL major versions — a backup cannot be restored into an older server. And a backup you have never restored is a belief, not a guarantee: test one before the day you need it.
For data whose loss would harm your business, keep an independent copy. Our liability for data loss is limited as set out below.
13. Reselling to your own clients
If you use the platform to sell environments to your own clients, you contract with them. You set your prices, you issue their invoices, you answer their support, and you are responsible for the commitments you make to them.
We bill you for what runs on your account, whoever is using it. Your clients are not our customers, and nothing you agree with them binds us.
14. AI features
The code, configuration and text produced by the AI features is generated output. It is not reviewed by us and it is not guaranteed to be correct, complete or safe to deploy.
Review it before you approve it. Once you deploy it, it is your code and the responsibility for what it does is yours.
Using these features sends your prompts and the repository files the agent reads to a third-party model provider. The privacy notice sets out what that means.
15. Suspension and closing an account
We can suspend or close an account for serious or repeated breach of these terms, or for non-payment as described above. Where circumstances allow, we tell you first and give you a chance to fix it.
You can close your account at any time. Export your data and take your backups before you do: closure starts deletion, and after that we cannot recover it for you.
16. Liability
The service is provided as it is. We do not warrant that it will be uninterrupted or free of defects.
To the extent the law permits, our total liability arising from the service is limited to the amounts you paid for it in the twelve months before the event. We are not liable for indirect loss, lost profit, lost business or lost data beyond restoring the most recent usable backup.
Nothing here limits liability that cannot lawfully be limited, and where you contract as a consumer your statutory rights are unaffected.
17. Changes to these terms
We can change these terms. Substantive changes are notified to account holders before they take effect, and the date at the top moves.
If a change is unacceptable to you, closing your account before it takes effect is the remedy.
18. Governing law
The operator is RollBackk Technologies SARL, SARL au capital de 990 000 XAF, registered under number CM-DLA-02-2026-B12-00811, with its registered office at Bonamoussadi, Douala, Cameroon. These terms are governed by the laws of Cameroon, and disputes are heard by the competent courts of Douala. The full legal notice is on the about page.