Community Discussion: The Limits & Possibilities of Frappe (Scale, Integrations, and Unique Architec

ERPNext
, , ,
1

Hi everyone,

​I’ve been working with Frappe/ERPNext for a while now and I am amazed by the development speed. However, I often find myself wondering about the ceiling of the framework.

​I wanted to start a thread to compile “Extreme Use Cases” to help newer developers (like myself) understand the full scope of what is possible. I’m specifically looking for insights on:

  1. ​Enterprise Scale: Has anyone successfully deployed a single site instance for 5000+ concurrent users? What kind of server tuning or database sharding strategies did you use?

  2. ​Headless/Frontend: Who is running Frappe strictly as a backend for complex frontends (Next.js, Flutter, dedicated Vue apps)? How is the developer experience compared to using Desk?

  3. ​Unconventional Domains: We see a lot of Manufacturing/Retail use cases. Is anyone using Frappe for things like IoT fleet management, high-frequency trading, or social networking backends?

​If you have a project that “breaks the mold” or pushes the framework to its limits, I’d love to hear about the architecture and the challenges you faced.

​Thanks!

1 Like
2

In 2015 I worked in a Project for a Telco in Central Americas, that was replacing SAP by ERPNext!

Major focus, issue 100K invoices from data of 250 webservices in less than 8 hours!

At that time, ERPNext wasn’t so performatic as it’s today! Major challenge we faced, inserts are crazy slow, we started with 32 hours to process all those invoices.

Major source of latency: Disk I/O

We had a pretty decent server, with 64Gb of memory, 16 cores, and performance was a nightmare! SAP was doing the same job at 11 hours!

We decided to monkey patch the Sales Invoice document, and instead of insert the data into the database, we simplify save it to a redis queue, associated with a batch number (month-year + inv issuer), and use background jobs to fetch small batches of invoices 50 each batch from the queue, and insert it on the database!

12 workers, and bingo 2 hours! Where we was processing invoices in 1 1/2 hour, and 20 minutes to insert it into the database!

Another special case, was the replacement of Microsoft Dynamics Nav, in an Correctional Industry! 40k users (if you understand), doing daily timesheets.

The server was modest 16Gb of memory, 4 cores, and did the job very well!

Major challenge again? I/O and Nginx

We implemented 3 physical disks on that server

1 for files only

1 for database only

1 for os

The files and database was high performance SSD’s, and man, this little boy was delivering!

At pick times, it was dealing around 8k requests every shift interval!

Regarding nginx, we had to increase the number of processes available for the backend, and change the nginx config for it works as a load balancer!

Ugly, yeah, but works like a champ :trophy:

Those are the situations I had to deal, pushing a little the limits of Frappe and ERPNext

10 Likes
3

Sound scary but epic, Thanks for sharing, i have to learn a lot.

4

EAS LMS 10k user (all levels)

Scale
Managing an LMS + EA system for 10,000 students with 20 years of archived data (10 TB) is not just a technical challenge it’s a demonstration of ERP frameworks stretched to enterprise-level capacity. The fact that the system continues to serve thousands of concurrent users highlights the importance of modular clustering and cloud-native deployment. By distributing workloads across Google Cloud clusters per module, the architecture ensures stability and responsiveness even under heavy demand.

Integrations
The integration strategy is particularly noteworthy. Instead of forcing legacy archives into the core framework, the team built an API-driven bridge between the EAS and LMS. This allows archived transcripts to remain outside the ERP core while still being accessible in real time. It’s a pragmatic approach: respecting the limitations of the framework while ensuring seamless user experience. Integrations also extended to localized payroll compliance, admissions, billing, and reporting modules that often resist one-size-fits-all solutions.

Unique Architecture
What sets this project apart is the customization at the core level. Most ERP deployments avoid deep framework changes due to upgrade risks, but here, customization was unavoidable. Billing, Admissions, Staff Control, Budgeting, Payroll, Accounting, and the Student Portal were all re-engineered to fit institutional workflows. Combined with the cluster-per-module design, the result is a hybrid architecture: part ERPNext core, part custom-built extensions, and part external archive system. This unique layering balances compliance, scalability, and long-term maintainability.

ERPNext can scale beyond its default limits when paired with:

  • Cloud-native clustering for performance

  • API-driven integrations for legacy data

  • Core-level customization for institutional fit

2 Likes