ERPNext pricing for five users: hosting and operating costs

You have found free ERP software, but someone still needs to run it, load supplier records, and make receiving work for the warehouse. ERPNext pricing starts with that distinction: the software license and the cost of operating a usable installation are separate decisions.

Evaluate managed Frappe Cloud hosting when your team wants to avoid maintaining the hosting environment. Consider self-hosting when you have an accountable technical owner and a budget for maintenance. Keep your current ERP if it handles purchasing and receipts and a scoped configuration fix resolves the remaining problem. A low hosting price alone does not justify moving open orders.

Kartik Deshpande prepared this article from official sources checked October 20, 2026. The examples are budget calculations and proposed workflow tests, not firsthand results. Permute publishes this article and sells connected business data and custom applications.

Separate the software from the people running it

Frappe’s ERPNext pricing page identifies ERPNext as free and open-source and separates hosting from implementation. You can start with the default setup or hire a partner to configure it. Frappe Cloud pricing is not per user, so five employees on one site do not mean five hosting subscriptions.

Assign ownership for supplier and item cleanup, opening inventory, roles, training, and the receiving process. Those tasks exist even when someone on your team performs them without an outside invoice. Record the internal time commitment beside any partner quote so the budget does not assume the work disappears.

Self-hosting adds infrastructure and operational responsibilities to that list. Ask who restores a failed installation, tests upgrades, and maintains custom code. The Odoo vs ERPNext comparison covers that broader edition-and-maintenance decision if both products remain on your shortlist.

Price one site for five users over twelve months

Use one company, one site, five internal users, one warehouse, and standard purchasing and inventory. The Frappe Cloud site page lists USD monthly plans starting at $5, with $25 and $50 options among the published tiers. The following figures annualize those monthly prices; they are not advertised annual invoices or a performance guarantee for this workload.

Do not multiply those totals by five. The users share the site, although their activity contributes to resource use. Taxes, exchange rates, additional sites, and separately purchased services are excluded. Confirm the chosen provider, region, plan, and billing terms at checkout; another environment used for development or testing needs its own scope.

For a worked budget, selecting the $50 site gives a $600 annualized hosting line. Add the implementation proposal, any custom-maintenance agreement, and your internal rollout budget to that amount. Those additions remain unknown until scoped. Calling the deployment a $600 ERP would omit the work needed to make it usable.

Check resource limits with representative activity

The published AWS site examples list $25/month with two CPU hours per day, a 1 GB database, and 25 GB storage; $50/month lists four CPU hours, a 2 GB database, and 50 GB storage. These are plan resource allowances, not a count of employees who can log in or the hours they can work.

Load a representative item list and purchasing history, then run the reports and imports your team expects to use. Inspect resource consumption before approving the plan. A quiet demonstration with a few records does not show how a month-end report or a large attachment archive will behave.

Custom applications can also change the hosting choice. Frappe’s private-bench migration documentation requires a site plan of at least $25/month for private-bench support. Have the implementer identify any custom app and deployment requirement before selecting the cheapest shared setup.

Product Warranty is not an implementation contract

Frappe’s Product Warranty documentation covers verified defects in supported, unmodified products. Site plans starting at $50/month qualify for coverage. Its exclusions include custom code, third-party integrations, functional consulting, training, data corrections, and migration. Obtain a separate agreement for the help your team needs in those areas.

Ask a partner to name the person responsible for configuration questions and custom defects after launch. Define response expectations, supported versions, and what happens when a problem crosses between standard software and a custom app. A hosting support ticket should not be your only plan for an incorrect supplier mapping.

Run a partial purchase receipt before approving the rollout

Use a hypothetical supplier S-01 and stock item P-01 measured in individual units. Start with zero stock in warehouse W-01 and order 100 units at $12 each. The order value is $1,200 before tax or other charges. Receive 60 units first, leaving 40 outstanding; the first received quantity has a $720 value on this simplified basis.

Create the supplier, item, warehouse, and purchase order in an evaluation site. ERPNext’s receipt instructions describe creating a Purchase Receipt from the order, setting the accepted warehouse, entering quantities, and submitting it. For this fixture, enter 60 rather than accepting the full order quantity. Record the order and receipt identifiers.

Check that stock reflects the submitted 60 units and that the remaining order quantity stays visible. Save a second receipt for the remaining 40 as a draft and inspect whether the report distinguishes it from submitted stock. Then submit it and reconcile the total to 100. These are proposed acceptance checks, not results from an installation tested for this article.

If receiving and billing are separate roles, continue through a bill for the first 60 units. The Purchase Invoice documentation describes creating an invoice from the receipt and preserving its references. Test that the team does not receive the same goods again through another stock-updating document. Keep payment as a separate step.

Repeat the test with the warehouse role instead of an administrator. Record which fields and actions that person can access, then have the purchasing owner review the outstanding quantity. Use the same fixture after an upgrade or customization so an accepted workflow can be checked again.

Budget for the records that do not import cleanly

Before loading production data, map supplier IDs, item codes, units, warehouses, and open purchase-order lines. Separate quantities already received from quantities still expected. Keep the old references so a receipt can be traced after cutover. The inventory reconciliation process provides a separate check on opening quantities and unresolved differences.

Ask the implementation proposal to identify excluded attachments, historical transactions, custom reports, and integrations. Agree which system accepts new receipts during the transition. For the wider inventory requirements, see the ERP inventory management comparison. Do not expand the first rollout to every available module before the receiving workflow passes.

Where Permute fits around inventory reporting

Permute sells connected business data and custom applications. We can scope reporting across permitted ERP records and warehouse spreadsheets, matching item and location identifiers while preserving the original references. Unresolved matches stay visible for review instead of becoming assumed stock.

Declare which receipt states count toward available or received quantity, and reuse that definition in an operations report or application. A buyer reviewing an open order can inspect the receipts behind the number and the freshness of the inputs. The same rule should survive the next scheduled refresh.

Keep ERP transaction ownership explicit

Permute is a separate product with its own implementation scope and cost. This article promises no native ERPNext connector, automatic migration, or replacement for purchasing and accounting controls. Verify the access method and supported operations before relying on a combined report.

The five-user budget starts with one site and the work required to run it. Choose hosting from the measured workload and required support, then add implementation and maintenance. Keep the current ERP if a smaller fix meets the need. Approve the move when the partial-receipt test and the complete operating budget both support it.

Questions about budgeting an ERPNext deployment