Platforms · Frappe Framework
Define the record once. Frappe builds the rest. Frappe Framework development by Frappe specialists
Frappe is the open-source framework under ERPNext. Describe a record your team keeps, and it gives you the screens, rules and API around it.
Every guided demo on this site runs on FlowMentor, a Frappe app we wrote.
The DocType
Job Card
Four fields described. Six pieces nobody coded. What we build is what only your business does.
What you get free, and what still gets built
Free with every record you define
- A form with validation, and list, kanban, calendar and report views
- Roles and permissions, down to a single field
- Workflows with approvals and email alerts
- A REST API for every record, with logins and API keys
- Print formats and PDFs
- Real-time updates across open screens
- A change log on any record you choose to track
- Many sites from one install, each with its own database
Defaults of the framework itself, before any app is installed. Source: frappe.io/framework.
Built for you
- The records that describe your work, and how they link
- The rules only your business has, in Python
- Screens outside the admin desk: a portal, a mobile view, a customer page
- Connections to payments, WhatsApp, telephony, your store
- Moving your data in from what you run today
Where Frappe is the wrong tool
One framework, many apps
Every app shares the same users, permissions, database and upgrade.
Frappe, Django or a low-code tool?
Each is right for someone. Here is how we'd choose.
Frappe, Django and a low-code tool, side by side
| Question | Frappe | Django | A low-code tool |
|---|---|---|---|
| On day one | Forms, lists, permissions, workflows, API and reports for every record | A web framework and an admin; the rest is written | Forms and simple flows, made by clicking |
| Business apps beside it | ERPNext, HR, CRM and more on the same site | None; each is built | The vendor's own, if any |
| Custom rules | Python, inside the framework | Python, anywhere | The tool's own rules; limits appear as needs grow |
| Best if | Your app lives next to your ERP, or is an ERP-like system of records and approvals | The product is the screen: a consumer app, a marketplace, an unusual data model | A small team needs a simple internal app quickly |
| Wrong fit if | You want a fully custom front end with little back office | You want accounting, stock or HR without building them | The app grows into your core system |
| Who owns it | You: open source, your Git, your server | You: open source, your Git, your server | The vendor hosts it; leaving means rebuilding |
| Licence model | Open source, MIT; no per-user fee | Open source, BSD; no per-user fee | A monthly fee per user or per app |
Licence models in words, not prices. Low-code tools differ; the column describes the usual hosted model.
What we do on Frappe
Versions, dated
v14
Support ended. Sites on it should move to v15 or v16.
v15
Supported until the end of 2027 (planned).
v16
Released 12 January 2026. Supported until the end of 2029 (planned).
Frappe supports two major versions at a time. Source: Frappe's Supported Versions page, checked 13 October 2026.
We build every custom app as its own app, never as edits to Frappe's code, so upgrades keep working.
Two of our developers hold Frappe School's Frappe Developer Certification.
For developers: the Frappe and ERPNext architecture guide explains DocTypes, hooks, permissions and the scheduler from the source code, at named releases.