Your Odoo, actually doing the work.
Diana works across your Odoo — drafts the quote, chases the overdue, reconciles the bill — and you approve every move. It doesn't just tell you. It does it.
A page headline, at scale.
One or two sentences that set the promise for this page — what Odient does here, and what stays in your hands. Every move is audit-logged.
It reads, it drafts, it does — you say go.
One question crosses your whole Odoo, comes back as real work ready to run, and nothing happens until you approve it.
On every Odoo screen, and in the chat your team already uses.
Ask from the record you’re on with the Odient panel, or mention Diana in Discuss. It answers from live data and prepares the next step, in place.


The thing that’s drifting, handled before it costs you.
Overdue accounts, stock about to run dry, a deal going cold — Odient flags it, prepares the fix, and waits for your go.
Stop assembling. Start approving.
The Monday overdue-chase, the “where’s that order” hunt, the month-end reconcile — Odient does the assembling. Your team does the deciding, and gets its week back.
Before: a request in chat. After: a quote out the door.
One flow, three beats — and the only human minute in it is the one where you approve.
You can let it act, because every move is auditable.
Who asked, what ran, whether policy allowed it, exactly when. One trail across every assistant — the reason a lean team can hand real work to AI.
tell you no.
An assistant that can do real work is only safe if it can be refused. Ask Odient to touch a record you are not allowed to see, and it stops — and the refusal is logged too.
Every write is decided before it happens.
Reading is scoped to the person. Writing is held to a gate you set — each of these is a control Odient checks before a single record changes. Built and tested this way, not bolted on.
- ✓Allow / deny / confirmPer model, per action. Each write is matched to a rule before anything runs — some go, some stop, some wait.
- ✓Value capsA reminder over a set amount, a change past a threshold — held for a person, not sent on the assistant's say-so.
- ✓Rate limitsHow many writes an assistant can make in a window is bounded, so nothing runs away in a loop.
- ✓Dry-runThe write is computed and shown first, so the exact change is on screen before it ever lands.
- ✓Human-confirmAnything above policy waits for a person to approve. Drafts stay drafts until you say go.
- ✓PII redactionSensitive fields are stripped at egress, before anything leaves your Odoo on its way to a model.
- ✓One audit record per writeAllowed, blocked or approved — every decision writes exactly one row, tied to the person who made the request. Not a sample. Every write.
A day, in the audit trail.
This is what a shop day looks like when the assistant keeps the ledger. Four moments, time-stamped — asked, flagged, held, filed. Every one logged the moment it happens.
Before the doors open, you already know where you stand.
Ask how yesterday closed and whether today is set up clean. Diana reads the registers and the day’s stock position and answers in the panel you already have open — no report to build, no export to wait on.
A fast seller dips — and the flag arrives in time.
Mid-morning, the bar stool that has been moving all week slips below its comfort level. Odient watches stock against how fast things are actually selling, not just a fixed minimum, so you hear about it while the shelf still has something on it.
| Product | On hand | Selling | Status |
|---|---|---|---|
BBar Stool (Oak, Swivel) front floor |
low | fast | running dry |
LLadder Bookshelf (Oak, 72") stockroom |
low | steady | reorder soon |
The reorder is written. And then it stops.
By mid-afternoon the draft already exists — the flagged items, your usual supplier, your usual terms. Odient holds it there. Ordering stock is your call, so nothing leaves the building until you look it over and say go.
The till closes. The day reads back as a ledger.
What was asked, what was flagged, what was held for your decision — the whole day in one trail, each entry tied to who asked and what ran. Tomorrow starts from a record, not from memory.
the rail above shows how it reads and files your own shop’s records.
One line, from delivered to paid.
Every project walks the same four stations. Odient keeps the line moving — and nothing advances without you.
A real ledger, mid-chase: Posted + Overdue, and Diana already drafting the reminder for the $276,570.00 balance.
One engine. Different keys.
Give one AI the keys to your whole ERP and you have built a liability. Scope a team instead: each assistant sees only its own world, acts only where you allow, and lands every move in the audit trail.
Start free today. Cloud and on‑prem come next.
The beta is live and free. Cloud is the planned default once we launch, and on-prem with Odient LM is still in development. We’d rather tell you the roadmap straight than dress it up as a price grid.
Beta
For early Odoo teams. Run the full assistant on your own Odoo, with hands-on onboarding from the people building it.
- ✓Diana in Discuss
- ✓Odient panel on every screen
- ✓MCP endpoint for any MCP client
- ✓Governed actions + per-user audit trail
- ✓Hands-on onboarding from our team
Cloud
The planned default once we launch — Odient managed and hosted by Zehntech, so your team just connects Odoo and gets to work.
- ✓Everything in Beta
- ✓Managed and hosted by Zehntech
- ✓Updates and upkeep handled for you
- ✓Straightforward per-team pricing
On-prem
Odient on your own infrastructure with the on-prem Odient LM model, so everyday questions never leave your network. Still being built — tell us if this is where you need to land.
- ✓Everything in Cloud
- ✓Runs on your own infrastructure
- ✓On-prem Odient LM for everyday questions
- ✓Your data stays inside your network
when beta ends, existing teams hear about pricing well before anything changes.