Incumbent ledgers

ERPNext

A free, GPL-3.0 open-source ERP with a full double-entry ledger that you can run on your own server or on Frappe Cloud.

erpnext.com · founded 2008 (Frappe Technologies, then Web Notes, incorporated; ERPNext 1.0 released June 2010) · Mumbai, India · researched 2026-10-10

Scope: ERPNext covers accounting (general ledger, invoicing, payments, bank reconciliation, budgeting, multi-company consolidation), plus stock, manufacturing, CRM, projects and, through the separate Frappe HRMS app, payroll. It is one system of record you operate, not an aggregator: it does not pull in and reconcile other accounting systems, and its bank feed options are narrow (statement import, a Plaid integration). It has no first-party AI or agent features.
Backing: Frappe Technologies Pvt. Ltd., privately held and founder-led (Rushabh Mehta). Ran for about 12 years without outside funding; Rainmatter (Zerodha) invested $1.35M (Rs 10 crore) on 24 November 2020, described as the first round. No later round confirmed.
Serves: smb, mid-market, developers
Covers: ledger, bank, payments, invoicing, payroll, reporting, commerce, documents
To ownpurse: Source. ERPNext is a ledger ownpurse could read from, with a clean, uniform API and, when self-hosted, no daily call cap. It is also the clearest case that owner-controlled books already exist: it gives you the server, not a portable, provable record across several systems.

What it is

ERPNext is a free, open-source ERP made by Frappe Technologies, a founder-led company in Mumbai. It is licensed GPL-3.0-only and built on the Frappe framework (Python, JavaScript, MariaDB). The accounting module is a full double-entry ledger with invoicing, payments, bank reconciliation, budgeting and, since version 16, formula-driven financial report templates and a consolidated trial balance. Around it sit stock, manufacturing, CRM, projects and, through Frappe HRMS, payroll. Frappe says 30,000+ companies have adopted ERPNext.

It does one thing ownpurse does not try to do: be the books. It does not gather what other ledgers, banks and wallets report and reconcile them; you run your business inside it.

How it works

You either self-host (free; the pricing page recommends it for companies with a tech team) or rent Frappe Cloud, priced by compute rather than by user: sites from $5 a month, servers from $20 or $40 a month (two Frappe pages disagree), enterprise by quote. A network of 200+ partners does implementations at unpublished prices.

Documents move through draft, submitted and cancelled states. Submitted ledger rows are not edited: the immutable ledger keeps the original rows on cancellation and posts opposite rows, and an amendment is a new document linked by an amended-from reference. A Version log records document changes. That is closer to an append-only log than most incumbents, though master records are still overwritten and there is no as-of query.

Data and access

The REST API is the one the web UI uses. /api/resource/:doctype gives CRUD over every document type, custom ones included, and /api/method/... calls whitelisted server methods. Auth is an API key and secret, a session, or OAuth; every call runs with the roles of its user. Self-hosted, there is no vendor quota. On Frappe Cloud, a plan’s daily CPU-time allowance for web requests is the limit, and past it the site answers HTTP 429. You can export everything: a full database dump and files from backups, or per-doctype CSV and Excel.

Agents

Frappe ships no first-party AI or agent features; neither the v16 release page nor the product page mentions any. The community has filled the gap. Frappe Assistant Core is an MCP server on the Frappe Cloud marketplace, maintained by an individual, AGPL-3.0. The Casys.ai server (MIT, February 2026) is read-write: an agent can create, submit and move documents. None of these describes a confirmation step. The real gate is ERPNext itself: give an agent’s user a role that can create drafts but not submit them, and a person does the submitting.

Customers

Users are mostly small and mid-sized firms, many in manufacturing and distribution, with a strong base in India, Africa and the Middle East. Capterra shows 4.5/5 from 137 reviews (March 2026); G2 shows about 4.2 from around 48. Reviewers praise the cost, the breadth and the customisation. They complain about setup that needs a developer, a less polished UI, weak bank and logistics integrations, slowness on large databases, and support, which is the lowest-rated area on both sites.

History

Rushabh Mehta started the company in 2008. ERPNext 1.0 shipped in June 2010, and version 4 (2014) split it into apps on the Frappe framework. Frappe ran for twelve years without outside money before Rainmatter, Zerodha’s fund, invested $1.35M in November 2020. Zerodha had already built its back office on Frappe without ever contacting the company. Versions 14 (2022), 15 (2023) and 16 (late 2025 or January 2026) followed.

For ownpurse

ERPNext shows that owner-controlled, open-source books work at scale. It also shows the cost: you have to run an ERP. Its custody comes from operating a server stack, not from holding a file, and it keeps one system’s books, not a provable record across several. That gap is ownpurse’s: you keep your ERPNext, Xero or QuickBooks, and ownpurse holds the portable, hash-chained record across all of them. As a source, ERPNext is a good connector target: a uniform API, documented auth and no daily call cap when self-hosted. Two ideas are worth borrowing. Draft and submit, enforced by the ledger, is the incumbent version of a sealed, approved package. A correction posted as reversal rows keeps the history readable.

Data and access

Public API: Yes. REST (/api/resource/:doctype CRUD) plus RPC (/api/method/<dotted.path> for whitelisted Python methods), JSON; webhooks; metadata-driven so every doctype, including custom ones, is exposed the same way.
Auth: API key and secret per user (Authorization: token key:secret), session login, or OAuth 2 bearer tokens. Calls run with the roles of the user who owns the key.
Limits: Self-hosted: no vendor quota, only what your server and any rate_limit settings allow. Frappe Cloud: site plans carry a daily CPU-time allowance for web requests; past it the site answers HTTP 429 until the cycle resets. Default page length is 20 records, paged with limit_start and limit_page_length.
What access costs: No API fee. Self-hosting costs your server; on Frappe Cloud the API draws on the plan's CPU-time allowance.
Export: Full database dump plus public and private files via backups (bench backup self-hosted; downloadable backups on Frappe Cloud); per-doctype CSV/Excel through Data Export and reports; the whole system can be restored on another server.
Notes: The API is the same one the web UI uses, so anything a user can do an API client can do, within role permissions. This is the opposite of Xero's rationed per-organisation daily call cap.

Price

Model: Software free (GPL-3.0); pay for hosting (Frappe Cloud, compute-based per site or per server, not per user) and optionally for partner implementation, product warranty or priority SLA.
Entry: $0 self-hosted; Frappe Cloud sites from $5/month (Rs 410/month), 14-day free trial.
Top: Frappe Cloud dedicated servers from $20 or $40/month depending on page (the two Frappe pages disagree), $125/month for the higher server tier; enterprise by quote.
Notes: Partner implementation, Starter Packs, warranty and SLA prices are not published. Per-plan CPU allowances are not stated in USD on the current pricing page; an AWS Rs 410 plan listed 0.5 h CPU and 250 MB database. Discounts for education and non-profits on request.

Agents

MCP: community
AI features: None first-party: the v16 release page and the ERPNext product page mention no AI or agent features. Community apps fill the gap: Frappe Assistant Core (AGPL-3.0, listed on the Frappe Cloud marketplace, maintained by an individual), the Casys.ai MCP server (MIT, 97 to 120 tools, Feb 2026), erpnext-agent on PyPI, and others.
Agent writes: Yes, through the same REST and RPC API: an agent can create, update, submit and cancel documents within the roles of its API user. The community MCP servers expose create, submit and update tools.
Approval: No agent-specific approval gate. ERPNext's own draft/submit model (docstatus 0 draft, 1 submitted, 2 cancelled) and its configurable Workflow states let a team give an agent a role that can create drafts but not submit them, so a person submits. The community MCP servers describe no confirmation step of their own.
Notes: The draft-then-submit lifecycle is the nearest thing in an incumbent ledger to ownpurse's sealed, approved packages, and it is enforced by the ledger rather than by the agent tool.

Integration and customers

Connects to: Product page names 20 integrations: Plaid (banking); Stripe, PayPal, Razorpay, GoCardless, Braintree, M-Pesa, Paytm (payments); Shopify, WooCommerce, Amazon, Unicommerce, Zenoti (commerce); LDAP; Dropbox, Google Drive, S3 backups; Twilio, Exotel. Plus a marketplace of Frappe apps and 200+ implementation partners.
Notes: Reviewers ask for more bank and logistics integrations. Connectors are Frappe apps installed per site, so they run inside the instance rather than in a hosted hub.
Scale: Frappe claims 30,000+ companies have adopted ERPNext (product page, read 2026-10-10) and, in its customer guide, 20,000+ customers on Frappe Cloud with an estimated 3 to 5 times as many self-hosting (figure seen in a search snippet; page could not be loaded). Caplight reported 151 to 197 employees as of February 2025. GitHub: about 40k stars, 13.1k forks (2026-10-10).
Ratings: Capterra 4.5/5 from 137 reviews (updated 13 March 2026; UAE page 4.6 from 139, value for money 4.7, support 4.1). G2 4.2 to 4.3/5 from roughly 47 to 50 reviews, support the lowest-rated area. No Trustpilot or Reddit figures gathered.
What customers say: Praised for cost (no licence fee), breadth of modules in one system, flexibility and customisation, detailed documentation and an active forum. Complaints: setup takes skill and often a dedicated developer, the UI feels less polished than premium ERPs, reporting quirks, weak bank and logistics integrations, local-compliance work, slow performance on large databases, and weak vendor support.

Timeline

2008
Rushabh Mehta incorporates the company (then Web Notes) and starts ERPNext.
2010-06
ERPNext 1.0 released; source published on Google Code.
2014-02
Version 4 introduces the app architecture on the Frappe framework.
2020
Frappe Cloud managed hosting priced publicly (2020 pricing post).
2020-11-24
Rainmatter (Zerodha) invests $1.35M, the first outside funding after 12 years.
2022-08-01
Version 14 released.
2023-09-10
Version 15 released.
2025-12 to 2026-01
Version 16 released (forum dates moved from 6 December 2025 to 12 January 2026): financial report templates, consolidated trial balance, automatic closing stock posting.
2026-02-28
Casys.ai posts a community MCP server for ERPNext on the Frappe forum.
2026-08-18
v16.32.3 is the latest stable build listed.

Borrow and avoid

Borrow: The draft/submit/cancel/amend lifecycle as an approval gate enforced by the ledger; cancellation as reversal rows rather than deletion; metadata-driven doctypes that expose every type, custom ones included, through one API; compute-based hosting pricing instead of per-seat fees.
Avoid: Becoming an ERP you must operate: the bench, MariaDB, Redis and upgrade stack is the friction reviewers complain about. Also avoid history that is only partly kept (masters overwritten, version log prunable) and agent access with no agent-specific approval step.

Sources

Not confirmed against a primary source

Frappe Cloud server entry price: the ERPNext pricing page says $20/month and the Frappe Cloud pricing page says $40/month (both read 2026-10-10).
Exact v16 release date: the forum moved it from 6 December 2025 to 12 January 2026; Wikipedia lists 10 December 2025 for both v16 and v17, which looks wrong.
20,000+ Frappe Cloud customers and the 3 to 5 times self-hosted estimate come from a search snippet of Frappe's customer guide; the page returned 404 when fetched.
Headcount of 151 to 197 (Caplight, February 2025) is third-party; revenue is not disclosed (third-party estimates of about $2.3M for FY2023 were not relied on).
The immutable ledger arriving in version 13 comes from a search summary; the official page names no version.
The Plaid integration's current maintenance status was not checked.
Rate limits on self-hosted instances (Frappe's rate_limit settings) and any REST v2 API details were not confirmed because the search budget ran out.
No Trustpilot or Reddit sentiment was gathered; sentiment comes from Capterra, G2 and SoftwareConnect.
The geographic concentration of users (India, Africa, Middle East) is from general knowledge, not a cited source.

On the spectrum

0 to 4. The grey tick is ownpurse.

Custody: 3
Where it runs: 2
History: 2
Openness: 4
Breadth: 3
Autonomy: 1
Agent-ready: 3
Easy to connect: 3
Market: 2

See it on the map

Also in incumbent ledgers

ownpurse is not affiliated with ERPNext or any company named here. Names are their owners' trademarks. Figures come from the company's own pages and the press, as linked, as of 2026-10-10; scores are our reading of them against the definitions in the landscape. This is not legal or financial advice.