What products does it have?

Consider how software accumulates in a growing company. Accounting starts in one system. Then sales needs a CRM, so a second is bought. HR and payroll need their own tool, so a third arrives. Customer support adopts a ticketing system. The leadership team wants dashboards, so a reporting tool is layered on top. Somewhere along the way, files live in one place, internal discussions in another, and the company website in a third.

Each of these decisions was reasonable on its own. But the cumulative result, for most growing businesses, is a landscape of disconnected systems - each with its own login, its own data, its own vendor, its own contract, and its own renewal cycle.

The cost of this sprawl is rarely the licence fees alone. It is the friction between the systems:

• The same data lives in several places - a customer record in the CRM, the accounting system, and the support tool - and the versions drift out of sync.
• Work falls into the gaps between systems. An order closed in the CRM has to be re-entered into the ERP; an employee added in HR has to be set up again elsewhere.
• Integrations become a permanent project. Connecting these systems requires middleware, custom code, and synchronisation jobs that someone has to build and then maintain forever.
• No one has a single view. Answering a question that spans functions - true cost-to-serve, end-to-end fulfilment, real profitability - means manually stitching together exports from multiple tools.
• Every system is a separate lock-in. Each vendor holds a piece of your operation, prices it on its own terms, and is difficult to leave.

This is the problem business software is supposed to solve, and too often makes worse.

What a business actually needs

Step back from the individual tools, and the underlying need is consistent. A business needs software that:

• covers the breadth of the business - finance, operations, sales, people, support, and insight - rather than one function well and the rest not at all;
• shares data natively, so that a customer, an employee, or an order is one record understood the same way everywhere;
• presents one consistent experience - a single login, a single permission model, one way of working - rather than a dozen interfaces to learn and administer;
• adapts to how the business actually operates, rather than forcing the business to bend to the software; and
• does not trap the organisation in a web of separate vendors and contracts.

In short: breadth and coherence. Most software markets force a choice between the two - a broad suite that is rigid and proprietary, or best-of-breed tools that are flexible but disconnected. Frappe's portfolio is built to avoid that trade-off.

How Frappe answers it

Frappe is not a single product, and it is not a set of separate products acquired and stitched together. It is a portfolio of applications built on one shared foundation - the Frappe Framework - running on one platform, sharing one data model, one login, and one permission system.

The products, grouped by the business need they address:

Running the core of the business

• ERPNext - the flagship ERP: accounting, inventory, manufacturing, sales, procurement, and operations. For most customers, this is the centre of gravity that the rest connects to.
• Frappe HR - human resources and payroll: employees, attendance, leave, and statutory payroll.
• Lending - loan origination, repayment, and borrower account management, for organisations in lending.

Serving customers and growing revenue

• CRM - leads, contacts, deals, and customer interactions for sales teams.
• Helpdesk - customer support through tickets and structured workflows.

Understanding the business

• Insights - data analysis, dashboards, and interactive reporting across your Frappe data.

Enabling people

• Frappe Learning - creating, managing, and delivering structured online courses.
• Gameplan - team planning, updates, and progress tracking.
• Drive - document storage, sharing, and collaboration.

Building and extending

• Frappe Framework - the full-stack web framework (Python and JavaScript) everything is built on; a database layer, authentication, and a REST API out of the box.
• Frappe UI - a Vue-based UI library for building modern interfaces on the framework.
• Builder - a visual, no-code tool for creating websites and pages.

Running it all

• Frappe Cloud - managed hosting and infrastructure for Frappe applications, where most customers run their systems. See Frappe's business model.

Why the shared foundation is the whole point

Return to the business that began this page, with its disconnected systems. The decisive difference with Frappe is not that it offers an ERP and a CRM and an HR system. Plenty of vendors do. It is that these are not separate products at all - they are built on the same framework, run on the same platform, and share the same database, login, and permission model.

For you, this turns what is normally an integration project into something that simply works:

• A customer is one record, recognised by sales, finance, and support alike - not three records that have to be kept in sync.
• An order closed in CRM flows into ERP without re-entry or a middleware job to maintain.
• An employee set up in HR is the same identity everywhere, under one permission model.
• A question that spans functions can be answered from one source of truth, not reconstructed from exports.

The integration cost between Frappe products is, in effect, near zero - because there is nothing to integrate. This is the single most consequential fact about the portfolio.