Every question we hear from buyers before they sign up, and a straight answer to each. Grouped into four categories: security, setup, pricing, AI.
Yes. Per-customer Kubernetes namespace, encrypted at rest and in transit, GDPR-ready, hosted in EU and MENA regions.
Why Each customer instance runs in its own isolated namespace with no cross-tenant data access. The same isolation backs every plan, from Starter on up.
Yes. The Odoo runs on standard PostgreSQL plus filestore (we'll export both on request), and your customizations are in a GitHub repo you own from day one.
Why Lock-in is a trust-killer. We are betting on monthly value, not switching costs.
Every ready instance gets a full database + filestore zip nightly. Backups are encrypted in object storage, retained for 90 days, and downloadable yourself from the /dashboard/backups page. The output is the canonical Odoo restore format, so you can drop it into any Odoo via /web/database/restore. A pre-deploy backup is also taken automatically before every customization deploy.
Why Backups are useless if you cannot use them. Plemo gives you the same zip format Odoo itself uses, so you are never locked into our restore tooling.
On managed Kubernetes, with regions in Europe and the Middle East. You choose at signup based on data-residency needs.
Why GDPR-compliant by default with European data sovereignty guarantees. MENA-hosted customers stay regionally compliant.
Days, not months. The wizard captures configuration choices, AI implements the modules, you verify. Most go live in under two weeks.
Why We have automated the 80% of Odoo setup that consultants used to do by hand.
That's exactly what we're built for. Customizations live in your dedicated GitHub repo, and our agents validate and patch them in the sandbox before any Odoo upgrade touches production.
Why Most partners hand you the code and walk away. We own the upgrade path because that is where ERP investments usually die.
Yes. We import your master data (customers, products, chart of accounts, employees, opening balances) during the wizard, and a Plementus consultant validates the migration before you go live.
Why Migrations are the riskiest part of any Odoo project. They get human review on every Plemo onboarding, regardless of plan tier.
One credit covers about 10,000 tokens of AI work: input, output, and code-reading combined. The customization cost depends on what you're asking for.
Voice queries and generated reports are much lighter (around 1 credit per five voice queries, or per generated report). A 2,500-credit plan typically covers 200+ simple changes, or 50 to 100 medium ones, or roughly 25 complex builds, plus the day-to-day voice queries and reports.
Why Per-seat pricing punishes small ops teams who use AI a lot. Per-credit means you pay for the AI work that actually happened, and you can plan the month against concrete numbers.
Starter is self-serve for single-team Odoo. Professional adds advanced customization, voice reporting, and a sandbox refreshed daily. Enterprise covers multi-company setups with dedicated environments and priority support.
Why Plans are calibrated against real Plementus customer workloads. Starter fits a 1-admin-user pilot; Professional is the SMB envelope; Enterprise is for high-volume or multi-region operations.
The /dashboard/usage page shows your live credit balance, per-resource bars (AI customizations, voice queries, reports), the monthly refill date, and a one-click Buy Credits button if you want to top up before the next cycle. Every spend is itemised in the credit ledger; there are no hidden line items.
Why Customers asked for the same kind of transparency they expect from cloud bills. Per-resource bars and a ledger make over-spend impossible to hide.
It can't. Every change runs in your sandbox first; production only updates after you click deploy.
Why BA agent drafts the spec, dev agent ships to sandbox, you approve. No auto-deploy without your sign-off.
A second Odoo instance where every customization is tested before it touches production. Comes with every plan, refreshes from prod on demand.
Why Most Odoo partners debug in production. We won't.
An open-source ERP covering sales, accounting, inventory, HR, and 30+ other modules.
Why Plemo is built on Odoo because it is the only ERP whose code we can customize at the depth our AI needs.
You do. The BA agent writes the spec in plain language; you read and approve it before the dev agent writes a single line of code.
Why The spec is intentionally readable by an ops lead, not just a developer. If it does not make sense to you, the AI rewrites until it does.
Nightly proactive health-check scans across your Odoo. They look for misconfigured fields, stuck workflows, permission drift, and other quiet breakage you have not noticed yet. Findings surface in your next conversation with Plemo, so the agent can offer to fix what it noticed before you ever filed a ticket.
Why Most ERP breakage is silent for days before someone reports it. The agents are already inspecting your Odoo every day; we made the findings visible to you.
If your answer isn't here, talk to sales. We reply within one business day.
Talk to sales