Is it like Odoo Studio?¶
A frequent question when evaluating the plugin. Short, self-contained answers.
Is it like Odoo Studio?¶
Partly, yes. The plugin makes low-code, Studio-style changes (add a field, tweak a view, automate a simple action) directly in the instance/database, on Community or Enterprise, without the Studio app (which is Enterprise-only). The parity is real for the common low-code cases, which is exactly what most "just add this for me" requests are.
Does it write code to a repository or to the database?¶
To the database. Just like Studio, the customizations are saved as Odoo records in the instance, not as module code in a repository. They survive updates as manual customizations.
Does it work on Community?¶
Yes. Studio is Enterprise-only, but the records it produces (fields, views,
automations) are ordinary. This plugin creates them over RPC, so you get the same
results in Community without the license. Note: on Enterprise, what is created
here does not appear inside the Studio editor (it is not tagged as
web_studio), but it behaves the same at runtime.
Where does each type of change live?¶
| Odoo Studio | This plugin (RPC) | Module development | |
|---|---|---|---|
| Edition | Enterprise only | Community and Enterprise | Any |
| Storage | Records in the instance/DB | Records in the instance/DB | Code files in a repo/module |
| Field | Visual editor | odoo_add_field (manual x_ field) |
Python field on the model |
| View | Visual editor | odoo_create on ir.ui.view (inherited xpath) |
XML in the module |
| Automation | Visual editor | odoo_add_automation (safe_eval server action) |
ir.actions.server / real code |
| Later editable in the Studio UI | Yes | No (runs the same, just without the Studio tag) | No |
Does it replace module development?¶
No. For small, low-code things it avoids the work of a full module; but it does not replace serious development: packaged addons, migrations, automated tests, complex business logic or anything that must live in version control. For that, build a module. This plugin is for the small, fast stuff.
What about safe_eval on Odoo online/SaaS?¶
Automations run server-side under Odoo's safe_eval: no import, def, class,
return, with, and no underscore or dunder access. On Odoo online/SaaS this
is enforced strictly. odoo_add_automation validates your Python before sending
it and rejects the forbidden constructs with a clear remediation. Detail and recipes
in Low-code customization.