Multiple databases & instances
Put one safe, unified API in front of many Odoo databases and instances, without wiring your app to each one.
The situation
Your Odoo footprint is spread across multiple databases — often on multiple instances and hosts. Pointing your application at each one directly means credential sprawl, a wide-open method surface per database, and bespoke plumbing every time you add another.
How ODXProxy fits
One endpoint, many backends
Each request names both the Odoo instance and the database it targets, so a single proxy deployment routes to every backend. Adding a database or instance is a data change, not new infrastructure.
Per-target identity, enforced by Odoo
Each request carries its own Odoo credentials for the named database, so access rights and record rules are enforced where the data lives — one database can never reach another's records.
A safe, uniform surface
Callers are limited to a curated allowlist of nine actions across every database and instance, shrinking the blast radius of a leaked key while still allowing real business methods through call_method.