Why ODXProxy
Odoo as the brain, not the interface.
ODXProxy exists to decouple two things that are usually tangled together: the presentation layer people touch, and the logical layer that runs the business.
The tangle
Odoo is a capable engine — but its screens aren’t the experience every team or customer should have to live in. So you build apps around it, and each one ends up wired directly to Odoo’s raw XML-RPC / JSON-RPC execute_kw. Business logic leaks into clients, credentials sprawl, and the method surface is wide open. Presentation and logic become fused, and changing one risks the other.
The shift: one clean seam
Put a single, safe seam between the two layers. Odoo becomes the business-function engine and gatekeeper — rules, permissions, and the system of record — and it is never exposed directly. Everything people touch lives on a separate presentation layer that speaks one unified JSON-RPC protocol through ODXProxy.
Because the seam is uniform and authenticated, you can route to many Odoo instances, keep the callable surface to a safe allowlist, and still invoke real business methods when a workflow needs them.
Presentation layer
ODXProxy
one safe JSON-RPC seam
Odoo
business logic · permissions · system of record
the engine & gatekeeper — never exposed directly
What that gets you
Business logic belongs in Odoo
Pricing rules, approvals, accounting, inventory — the hard-won logic and the source of truth stay in the ERP. You don't reimplement it in every app.
Odoo is also the gatekeeper
Access rights and record rules are enforced where the data lives. Each request carries its own Odoo identity, so permissions are never an afterthought in the UI.
Interfaces belong to the people using them
Sales, ops, and customers each need a different surface. Build the right one for each — without coupling it to Odoo's screens or its raw RPC.
Adoption happens when work feels natural
When contributing to the ERP is just “using the app,” data quality and participation go up — because nobody has to learn the ERP to feed it.
The payoff
The ERP gets fed by the work people already do — a form, a mobile app, a portal, a bot. They contribute to the business and its data through workflows that feel natural, often without ever realizing they are “using the ERP.” The business logic stays consistent and governed; the experience stays yours to design.