ERPNext is as secure as the way you deploy and configure it. The software gives you a layered permission system, two-factor authentication, document change history, encrypted backups and, because it is open source and self-hostable, real ownership of your data. The weak link is almost never the code; it is skipped configuration.
Short answer
Yes, ERPNext is secure enough for serious business use. It has role, record and field-level permissions, two-factor authentication, version history on tracked documents, an audit trail for submitted and amended documents, and encryptable backups. Self-hosting keeps the data on infrastructure you choose. Security depends on correct setup, patching and backup discipline, not on the platform alone.
I lead ERPNext and Frappe programmes at MithTech, a team of Frappe specialists in Bengaluru. Security is the first question most executives ask before signing off on an ERP, and it deserves a factual answer rather than a sales one. I have seen far more data lost to a missing backup than to any attacker, so most of "is ERPNext secure" is really "did someone configure it properly".
How does the ERPNext security model work?
Access control runs through stacked layers rather than one switch. Roles decide which document types a user can touch and what they can do (read, write, create, delete, submit, cancel, amend). User Permissions narrow that to specific records: a company, a branch, a warehouse. Permission Levels lock individual fields so only chosen roles see sensitive numbers.
Real businesses need that nuance. A sales executive can create invoices but must not see purchase cost. An accountant sees everything financial but nothing in HR salaries. A warehouse operator sees only their own warehouse's stock.
| Layer | Controls | Typical use |
|---|---|---|
| Role permissions | Which document types and which actions | "Sales User can submit invoices" |
| User Permissions | Which specific records | "This user sees only the Pune branch" |
| Permission Level | Which fields within a document | "Hide cost price from sales roles" |
| Workflow states | Who can move a document forward | "Only a manager can approve above a limit" |
User permissions have edge cases in reports and linked documents; our post on strict user permissions covers the ones that catch teams out.
Does ERPNext support two-factor authentication?
Yes, it is built in. In System Settings an administrator turns it on and picks the method: a code from an authenticator app (the TOTP standard used by Google Authenticator, Authy and similar apps), or a code sent by SMS or email. It can be required for selected roles or for every user. Once active, a user enters their password and then the time-limited code.
For an ERP reachable from the internet, I treat required 2FA as non-negotiable. A leaked password alone should never be enough to reach your ledgers.
Is there an audit trail in ERPNext?
Yes. Document types with change tracking turned on keep a version log of what changed, who changed it and when, visible on each document's timeline. Submitted transactions cannot be edited away: they must be cancelled and amended, which leaves its own record, and the Audit Trail report compares a document with its amended versions. Logins and logouts are recorded in the activity log.
For most businesses that history answers an internal auditor's basic question: show me who touched this invoice and when.
Version history
Field-level record of changes on tracked documents, visible from each document's timeline.
Submit, cancel, amend
Financial documents follow a submit, cancel and amend flow, so corrections are logged, not silent.
User activity
Login and logout events are recorded, so you can review who was active and when.
How does self-hosting affect security and data ownership?
Self-hosting puts the business data on infrastructure you choose: your own server, your cloud account, your jurisdiction. Nobody else holds your database. You set the operating-system hardening, firewall rules, encryption and backup schedule. That control is the main security difference between open-source ERPNext and closed SaaS suites.
Ownership cuts both ways. Patching, monitoring and restore tests become yours, or your hosting provider's, to run. Choose deliberately.
| Self-hosted ERPNext | ||
|---|---|---|
| Where data lives | Infrastructure you own | The provider's infrastructure |
| Control over hardening | Full | Limited to the provider's settings |
| Patching responsibility | You or your implementer | Shared or provider-managed |
| Data portability | Records as CSV or Excel by document type; a full copy with bench backup --with-files on your server | Depends on the provider's export |
| Best for | Control-focused, compliance-sensitive teams | Teams that want hands-off operations |
Managed hosting sits between the two: the system runs on infrastructure in your name while someone else patches, monitors and tests restores. The open-source ERP guide for India covers licensing, lock-in and cost more broadly.
How do ERPNext backups work, and can you get your data out?
ERPNext, on the Frappe Framework, can back up the database and the attached files. bench setup backups writes a cron job that backs up every site every six hours, database only; uploaded files need --with-files. Encrypt Backups is off by default. When it is on, the database and file archives are encrypted with gpg, using a backup_encryption_key that Frappe creates in site_config.json. The copy of site_config.json inside each backup is not encrypted, so keep it out of the off-site copy. A backup is portable: a database dump plus the files archive restores onto any Frappe bench, so you are not locked to one host. You can take a complete backup yourself at any time with bench backup --with-files and stand it up elsewhere.
0 of 4 steps done
Tick a step’s number when it is done; the ticks stay on this device.
Schedule automatic backups
Set daily automatic backups of both the database and the files. Attachments live outside the database, so a database-only backup is incomplete.
Encrypt the backup
Turn on backup encryption so the dump is protected at rest. Keep the encryption key somewhere separate and safe; losing it means losing access to the backup.
Move copies off the server
Keep at least one recent copy off the production machine, in a separate bucket or location, so one server failure never takes your data with it.
Test a restore
A backup you have never restored is a hope, not a backup. Restore to a staging bench at least once a quarter to prove the whole chain works.
Is open-source ERP less secure because the code is public?
Open source does not mean insecure; it means inspectable. ERPNext's code is public under GPLv3, so security researchers, implementers and your own team can read exactly how authentication, permissions and data handling work.
Public code gets more eyes on it, and fixes ship in the open. What decides your security in practice is how quickly you patch, how the server is hardened and how access is managed, the same factors that decide the safety of any proprietary system. Secrecy of source is not what keeps data safe; disciplined operation is.
If you connect ERPNext to AI assistants, treat those integrations with the same care. The access and token model is covered in connecting ERPNext to ChatGPT and Claude via MCP.
Frequently asked questions
Is ERPNext secure enough for a growing business in India?
Yes. ERPNext provides role-based and record-level permissions, field-level access control, two-factor authentication, document version history and encryptable backups. For most Indian businesses that is more than they had before. The deciding factor is correct configuration and disciplined backups, which a competent implementer sets up at go-live.
Who owns the data in a self-hosted ERPNext deployment?
You do. In a self-hosted deployment the database and files sit on infrastructure you control, and you can take a full, portable backup at any time with bench backup --with-files. No vendor holds your records.
Does ERPNext encrypt data?
Backup encryption is off by default. Turn on Encrypt Backups in System Settings and the archives are encrypted with gpg, using a backup_encryption_key that Frappe creates in site_config.json. ERPNext also hashes passwords and encrypts password-type fields such as API secrets. Encryption of the live database and of data in transit depends on how you deploy: TLS for connections and disk encryption on the server are the usual setup.
Can I limit what each employee sees in ERPNext?
Yes. Roles decide which document types a user can act on, User Permissions restrict them to specific records such as a branch or warehouse, and Permission Levels hide individual fields such as cost price from chosen roles.
How often should ERPNext be backed up?
Daily and automatically at minimum, and more often for high-volume businesses. Backups should cover the database and the attached files, be encrypted, and have at least one copy off the production server. Restore one to a staging environment regularly to confirm it works.
Is open-source ERPNext safe compared to paid ERP software?
Open source is inspectable, not exposed. ERPNext's code is public under GPLv3, so anyone can check its security mechanisms, and fixes ship openly. Safety in any ERP, open or proprietary, comes from timely patching, a hardened deployment, strong authentication and tested backups.
To see how we run the platform end to end, see ERPNext at MithTech.
To go through your own site, one check at a time, use the ERPNext hardening checklist.
Comments & ratings
No comments yet. Start a new discussion.
Manoj · Published on 20 July 2026
Worked with us? Leave a Google review