Security
Security built into the foundation
Your data is separated from every other business at the database level, protected by role permissions, and backed up in encrypted copies.
Your data stays yours
Isolation is enforced by the database itself, not only by the application.
- Each business (tenant) is isolated by PostgreSQL row-level security. The database itself refuses to return another business's rows.
- The application runs with a database role that cannot bypass these rules.
- Groups of companies consolidate their statements without ever reading each other's books directly.
The right access for every person
Each person sees and does only what their role allows.
- Ten default roles (owner, manager, accountant, cashier, sales and more) and close to 300 permissions per action.
- Floor staff sign in quickly with a personal PIN; managers and admins with password.
- Sensitive actions such as voids, refunds, discounts and opening the cash drawer without a sale ask for a reason and are logged.
- API keys act as the person who made them, never with more rights, and can be limited to chosen modules or read-only.
Financial integrity
The books cannot be quietly changed.
- Posted financial documents cannot be edited or deleted; corrections are reversals.
- Database rules hold the key financial invariants, so even direct data access cannot unbalance the books.
- Closed accounting periods are locked; only the owner can reopen them.
- Receipts and refunds are written into a hash-chained, gapless fiscal journal that shows any missing or altered entry.
Protected secrets and backups
Keys are encrypted and backups are kept in more than one place.
- Passwords and provider keys (payment, SMS, mail, social) are stored encrypted (AES-GCM) and never shown again after saving.
- Automatic database backups, with encrypted copies sent to off-site storage at two separate providers; backups can be checked and restored.
- Platform administrators sign in with a password plus a one-time code (two-factor authentication).
Secure by process
Security checks are part of every release.
- Every code change runs more than 1,000 automated tests plus dependency, secret and code security scans before release.
- Outgoing connections from customer-configured integrations (such as mail servers) are restricted to the public internet.
- Full audit log of changes for every record.
Run it where your policy requires
If your data must stay on your premises or in your country, install ERP PRO on your own server.
Security questions or a questionnaire to complete? Write to info@erp-pro.biz.
Run your whole organisation on one platform
Tell us how you work. We will set up a trial with the modules you need and help you bring your data in.