Enterprise edition

The same platform, on your company's terms.

Your people are already using AI. Enterprise makes it governed, attributable and private — without taking it away from them. Everything in Standard, plus total control of AI across the organisation.

Question one

"What are we spending on AI?" — Every request priced and attributed to a person, per tenant.

Question two

"What are people sending to these tools?" — Out-of-policy requests refused before they reach any model.

Question three

"Can I stop it if I need to?" — Budgets, permitted use and models, set centrally and enforced at the server.

What Enterprise adds

Five capabilities Standard doesn't have.

Everything in the Standard edition, plus the layer that makes AI safe to hand an entire organisation.

01

Private and local AI

Your models, on your infrastructure. Run everything locally and no prompt, document or record value ever leaves your building — and even on a hosted model, prompt text is never stored.

  • Local models via Ollama or any endpoint you control
  • Local embeddings — document text stays on your machines
  • Prompt text never stored — a hash and two lengths only
  • Never indexed, never embedded — pinned off, not defaulted
  • Record values stay local — the audit stream carries field names
  • Data residency as a contract, not a config setting
02

Total control and full observabilityVajraGrid

The control plane for every AI user in your organisation. The company sets the model, the budget and the permitted use — enforced at the server, where an app cannot argue with it.

  • The company picks the model — a user's choice is replaced server-side
  • Spend caps per tenant and per person, with a humane stop
  • Permitted use enforced — refused before a model is called
  • Every request priced and attributed to a named person
  • One correlation ID across conversation, document and ERP write
  • Refusals recorded too — what was stopped, and why
03

Document intelligence beyond OdooIntelliVault

Your ERP holds the records. Your documents hold the context. Enterprise makes both answerable in a single question — and never passes off half an answer as a whole one.

  • One question, two sources — Odoo records and your documents
  • Per-tenant isolation — separate database and separate index
  • Embedded on your machines — text never leaves the deployment
  • Per-document visibility — public, internal, private, by group
  • Fails loudly — a degraded search raises, never under-answers
  • Fed by your own pipeline — OCR'd, classified, entity-resolved
04

A more powerful desktop agent, customised per business function

Not one assistant with a job title. A signed, branded desktop colleague built for each function — HR, sales, finance, operations — each carrying the skills, tools and playbooks of its trade.

  • Per-function agents from a library of 418 skills
  • Signed and branded — with a checksum you can verify yourself
  • Immutable releases — channels, rollback, no surprise updates
  • Works beyond Odoo — decks, reports, email drafts, routines
  • WhatsApp Business API — a public number with tappable approvals
  • Governed identically — same risk tiers, same approvals
05

Role-based access control, end to end

Every person — and every AI acting for them — sees exactly what their role allows. Not filtered in the interface: enforced at the server, and at your ERP's own permission layer.

  • Your identity provider — real SSO, forged tokens refused
  • Everyone acts as themselves in Odoo — never a shared login
  • Odoo's own ACLs stay in force — no privilege escalation on AI paths
  • Unregistered users refused by name, before Odoo is contacted
  • Workspace isolation enforced server-side, not by hidden buttons
  • Partner isolation — run competing clients, neither learns of the other

The details

What a security review will ask — answered up front.

What do you store from our prompts?

A one-way hash, the request length and the response length — no column holds the text. Prompts are not indexed and not embedded. If your own content policy blocks a request, the text is kept for your administrator to review, then erased after 30 days; the record that it was blocked, by which rule, is kept.

How does "fully private AI" actually work?

Optionally, everything local: your models via Ollama or any endpoint you control, and document embeddings served by a local model so text never leaves your deployment. We treat the embedding route as a contractual setting, not an operational one — because repointing it would silently change the answer.

How does per-person Odoo identity work?

The identity hub proves who is calling; the bridge maps that identity to a credential it already holds. Someone with no Odoo login registered is refused by name, before Odoo is ever contacted — and the shared service credential is unreachable either way. One honest cost: an administrator registers each person's Odoo login once.

How far does role-based access actually go?

Three layers, and they compose:

  • At your ERP — every AI action runs as that person's own Odoo user, so Odoo's record rules and ACLs already scope the answer. There is no privilege escalation on any AI write path.
  • At the platform — workspace isolation and the customer/implementation-team split are enforced at the server, not by hiding buttons. Calling the API directly is refused the same way.
  • At the documents — visibility levels and per-group permissions on the document estate.

One honest note: the ERP and platform layers are verified end to end; document-level permissions are built and we'll configure and prove them on your tenant before you rely on them.

What happens when the budget runs out?

The AI step halts and the person sees: "Your organisation's AI budget for this period has been used up… your administrator can raise the limit." No error codes. The admin sees exactly which team spent it.

What if we turn Enterprise off?

The platform behaves byte-for-byte like the Standard edition. That's the acceptance criterion, and proving it is itself a test case. Upgrading — and downgrading — is a decision, not a migration.

Partner isolation, precisely
  • A foreign customer id tells you nothing — real and imaginary ids return the identical answer.
  • Templates carry how you work — never who your last client is; personal data is stripped.
  • Every action names the person, partner and role — "the partner changed it" is not an audit trail.
What we will not claim

No penetration test or compliance certification (SOC 2, ISO) has been performed yet. Claims about what is stored are verifiable from the schema and made above; claims about what is secure we don't make. We'll hand your security tester the code — and show you the enforcement points that exist today.

Every plan includes

Try it free for three months. Keep the support for a year.

No obligation, no card, no lock-in. And what comes with your plan isn't a discount — it's what it takes to make an ERP actually land.

Start free →
Weeks

Start in weeks

Not months. Your implementation is underway in your first week.

1 year

Free support

A full year included with every plan — not a paid add-on.

On-site

Training included

We come to you and train your team in the room, on your data.

100 hrs

Customisation

A hundred hours of our engineering, built into every plan.

No card to start  ·  No obligation  ·  Cancel any time in the three months  ·  Your data stays yours

Questions

Questions before an enterprise rollout.

What Enterprise adds

What is the difference between Standard and Enterprise?
Enterprise runs on infrastructure you control with local models by default, and adds the two remaining products — MCP, the governed door for outside AI tools, and RAG, which turns your document archive into answers with citations. It also adds the WhatsApp Business API channel and the full governance control set.
What does 'private and local by default' mean?
That the default posture is models running inside your own infrastructure, with no dependency on external AI providers. Cloud models remain available as an option — it is your choice, not a requirement built into the product.
Why would we want AI over WhatsApp?
Because the people who most need to ask your ERP a question — sales in the field, operations on site — are not sitting at a desk. The same permissions, previews and audit trail apply there as anywhere else.
Is this the same platform or a different one?
The same one. Moving from Standard does not migrate anything; it switches products on and moves the deployment inside your walls.

The technical and security detail

Can it run with no internet dependency at all?
Yes. Models, embeddings and retrieval can all run locally inside your own infrastructure.
How many model providers can we choose from?
Ten, plus local models. Routing is policy-driven, so which workload uses which model is a setting rather than a rebuild.
What proves what the AI did?
One correlation ID per business event, tying together the person, the request, the retrieval, the model, the cost and the resulting Odoo change.
Does it modify Odoo core?
No — installable addons and services alongside your database. Removing them leaves a working, ordinary Odoo.

Getting started

How does an Enterprise engagement begin?
With a demo on your own documents and a security conversation early rather than late — most of what a review will ask is answered on this page precisely so it isn't a surprise in week six.
Can we trial Enterprise?
Yes. The free three-month trial applies, so the security team can watch it work before anyone signs.

Bring your CFO's three questions.
Leave with the answers running.

A governance assessment walks your own tenant through model control, budget stops and per-person identity — live, on your terms.

Book a demo

See it running on your own documents.

Thirty minutes, your paperwork, your questions. We will show you what it does — and, just as importantly, what it refuses to do.

Book a demo →