Everything available
Your own server or private cloud
Your team or your Odoo partner runs Enterprise on infrastructure you control.
Both options, including fully private and air-gapped deployment.
For customers on Odoo Enterprise
You already pay for Odoo Enterprise. We build on it, not around it.
Agnidoot works with Odoo Enterprise on versions 16 through 19 — no migration, no licence change, and no rebuilding the apps you already own.
The one question that matters
Your edition is fine. It is your hosting that decides the setup.
Everyone on Enterprise gets the assistant that works alongside Odoo. Whether we can also put AI buttons inside your Odoo screens depends on where your database lives.
Everything, one extra step
Odoo.sh
Odoo hosts you, but you keep your own code repository and staging branches.
Both options. In-Odoo features arrive through your repository and staging, like any other change.
Alongside Odoo only
Odoo Online (odoo.com)
Odoo hosts and manages everything for you at yourcompany.odoo.com.
Odoo Online does not allow outside apps to be installed, so the in-Odoo buttons are not possible there. Your plan also needs to permit an external connection — we check that for you.
On Odoo Online and you want the in-Odoo features?
There are two honest answers: move to Odoo.sh, which keeps Odoo as your host and allows app installation, or stay where you are and use the assistant alongside Odoo. We will not invent a workaround that does not exist. Many customers run happily on the second option alone.
What your team actually gets
Four problems it removes in the first month.
Paperwork stops being typing
A supplier quote or a vendor invoice arrives as a PDF and comes back as a draft order or bill in Odoo, with the line items filled in. Someone still checks it and presses save.
Ask the ERP instead of asking for a report
"Which customers are overdue past 60 days?" gets an answer with the actual records behind it — without waiting on someone to build a view or export a spreadsheet.
AI that has to ask before it changes anything
It drafts the change, shows what it intends to do, and waits for an authorised person. If nobody approves, nothing is written. Every read, change and refusal stays on the record.
Nothing leaves the building, if that is your rule
Run it hosted, or entirely on your own infrastructure with a local model — including with no outbound internet at all, where data residency demands it.
The detail, if you want it
Everything else, one click away.
The four points above are the pitch. Below is the material your IT, finance and audit people will ask for.
Your Enterprise apps are the starting point, not a workaroundScope
On Odoo Community, several apps simply do not exist — Quality, Approvals, Documents, Sign, Helpdesk and Field Service are Enterprise features. For Community customers we have to build equivalents so they are not left without the capability.
You already own those apps. During setup we agree which of your licensed apps are in scope, so the assistant works with the real thing and nothing is duplicated in your database. In practice that means inspections, approvals, document workflows and service jobs become things it can help with, rather than gaps it has to route around.
What we need from you before we can startSetup
- Your Odoo address and database name
- Your server address or yourcompany.odoo.com, and which database to use.
- A dedicated Odoo user with an API key
- Created by your administrator. Never your admin account — we will advise on the right permission level.
- Which parts of the business are in scope
- Sales, purchasing, accounting, inventory, manufacturing, and which Enterprise apps to include.
- A decision on reading versus writing
- Most customers start read-only for a few weeks, then enable drafting area by area.
- Who approves changes
- One or more named people who can approve what the assistant proposes.
How your permissions, data and AI keys are handledSecurity
- It signs in as a user you create. Whatever that Odoo user cannot see or do, the assistant cannot see or do. Your existing access rules stay the ceiling.
- Writing is off by default and switched on deliberately, for the specific areas you choose.
- Higher-risk changes wait for a person. No approval, no write.
- Every action is on the record — who asked, which records were touched, and whether it was approved, refused or completed. Refusals are kept too.
- Bring your own AI account, or run a local model on your own hardware. We never write our keys into your system.
Odoo 19 already includes AI. Where do you fit?Comparison
Odoo 19's built-in AI is genuinely useful and it is included with your Enterprise subscription. This is not a replacement argument — several customers run both.
The short version: Odoo's AI is strongest inside the Odoo interface. Agnidoot adds approval before a governed change, a per-user activity trail, private and air-gapped operation, support for Odoo 16 through 19 so you do not need to migrate first, and work that continues after the Odoo answer.
How a pilot usually runsTimeline
- 1 · Connection check
- We connect read-only and confirm your version, hosting, plan and licensed apps. You get a short written summary of what is actually possible on your instance — before any commitment.
- 2 · Pick your setup
- Alongside Odoo, inside your Odoo screens, or both — based on what the check found rather than on a brochure.
- 3 · Pilot with one team
- Usually read-only for two to four weeks with a single department, then enable drafting where it has proved itself.
Find out what your Odoo actually allows.
Thirty minutes, read-only, on your own instance. You get a written summary of what is possible — including anything that is not.