Product terms

Execution Layer for Odoo.

Last updated: 19 September 2026

Plain terms for buying and running the Execution Layer for Odoo. They supplement our site-wide Terms of Service, which also apply; where the two differ for this product, these terms win. By purchasing, installing, or using the module, you agree to them. If you are agreeing for a company, you confirm you may bind it.

1. What you are buying

The Execution Layer for Odoo is an installable Odoo module: an MCP server with verified writes, governance, approvals, evidence, and a semantic registry, for Odoo 19, Community and Enterprise, self-hosted or Odoo.sh. The license fee is USD 499, paid once, per Odoo major version, as published on the product page. It includes updates within that Odoo major and standard support. When a new Odoo major version arrives, existing customers can buy the new major's license at half the then-current price. The optional Context Layer add-on is the only subscription; the module itself is bought once.

2. License

Your purchase gives your company a non-exclusive, non-transferable right to install and run the module for its own business, on the Odoo major version it was bought for. The modules are provided source-available so you can read what you run; that visibility is not a right to copy, resell, redistribute, or build a competing product from the code. Components under an open-source license keep the freedoms that license grants.

3. Delivery and activation

We sell direct: after purchase we deliver the module archive and the invoice by email. You install it like any Odoo addon. It installs read-only and starts recording; writes stay off until one of your administrators turns them on. The Context Layer, if you choose it, is a separate cloud subscription activated inside the module with a key; if that subscription ends, the module itself keeps working.

4. Your responsibilities

The module is tested before every release, and everything it does is logged and auditable inside your own Odoo. It is also a powerful tool: it can let AI write to your production database, under rules that you configure. So the following are your side of the deal:

  • Test on a staging database first. Install, configure, and run the included failure suite against a staging copy of your Odoo before production, and after every Odoo or module update. Every Odoo is configured differently.
  • Keep current backups. Maintain your own working backups of your Odoo database and files at all times.
  • Own your configuration. Which users may connect, which bundles they get, which actions need approval, which rules are enforced: these are your decisions, made in your Odoo, and the consequences of a permissive configuration are yours. The module ships with safe defaults; loosening them is a choice.
  • Use it as intended. The module governs AI access to your own Odoo. Do not use it to circumvent the permissions of your own users, to process data you have no right to process, or in violation of law.
  • Ask before guessing. If you are unsure whether a configuration or an upgrade is safe, write to hello@nanti.ai before trying it in production. That mail costs nothing; a bad production write can cost a lot.

5. What the module does and does not guarantee

The Execution Layer verifies persistence and permissions: that what was written is what persisted, that the actor was allowed, and that evidence was kept. It never verifies the AI's judgment. An action that is authorized under your configuration but commercially wrong will still execute, and the receipt will prove exactly what it did; the rules you write are what stop it. We do not guarantee that the software is error-free or uninterrupted, and audit evidence is tamper-evident, not indestructible: a database administrator with raw SQL access is outside any module's control.

6. No warranty

Except as expressly stated on the product page, the module is provided "as is" and "as available", without warranties of any kind, express or implied, including merchantability, fitness for a particular purpose, and non-infringement. Statements on the product page describe verified behaviour of the released software at the date of publication, not a promise about your specific environment, customizations, or third-party modules.

7. Limitation of liability

To the maximum extent permitted by law, our total aggregate liability for all claims arising out of or relating to the module or these terms, whether in contract, tort (including negligence), or any other theory, is limited to the amount you paid us for the module license in question, and where you have paid us nothing, to USD 100. This is one combined cap across all claims, not per claim.

We are not liable for any indirect, incidental, special, consequential, or punitive damages, or for lost profits, revenue, sales, data, or goodwill, or for the wider extent of any loss, even if we were advised such loss was possible. In particular, we are not liable for damage that results from your configuration choices, from use on a production database without prior staging tests, from missing backups, from modified module code, from third-party modules or AI clients, or from using the module in a way it is not intended to be used. Nothing here limits liability that cannot be limited by law.

8. Third parties and trademarks

The module runs inside Odoo and talks to the AI clients you choose; your use of Odoo, your hosting, and your AI providers is subject to their terms, and we are not responsible for their acts or outages. Odoo is a trademark of Odoo S.A.

9. Changes, governing law, contact

We may update these terms as the product and the law evolve; this page changes first, with a new date at the top. These terms are governed by the laws of India, and the courts of India have jurisdiction, without limiting any mandatory rights you have where you live. Questions, before or after buying, go to hello@nanti.ai.