Budibase pricing for a five-person approval app

The purchase-approval pilot has five users, but its automation usage keeps growing. Each request runs several steps, and a retry can repeat some of them. Budibase pricing needs a workload estimate as well as a user count. A small team can still create a busy application.

Evaluate cloud when you want Budibase to operate the hosting and can match the application to a paid action allowance. Evaluate self-hosting when deployment control matters and someone will own maintenance. Keep an existing working app if its permissions, usage allowance, and support fit the job. This assessment uses official documentation checked October 22, 2026; the acceptance exercise is proposed, not tested firsthand.

Price one creator and four end users

Use five people total: one creator maintains the app, while four end users submit or approve requests. Assume 500 workflow runs each month, no AI calls, and the same workload for twelve months. Exclude tax, outside services, and migration labor. Separate the subscription estimate from the question of whether its selected usage tier is sufficient.

The current rate card displays cloud Pro at $19, Premium at $49, and Business at $299 per month on yearly pricing. End users add $5 each; monthly billing adds 20%. Pro and Premium include one creator, Business three. The following calculations use the displayed base tiers, not a confirmed quote for this workload.

Confirm the selected action allowance and invoice schedule at checkout. Pro and Premium have action selectors whose capacity was not established in the retrieved page; a higher tier may change these totals. Enterprise is quoted. Self-hosted open source has no license charge and unlimited actions; self-hosted Enterprise is quoted. Neither figure includes operating infrastructure.

Count executed work rather than workflow names

Budibase’s pricing definition counts workflow step executions and row writes as actions. Custom SQL queries and API requests are excluded. Action allowances are hard monthly limits, so reaching one can require a tier change. Unlimited automation definitions do not establish unlimited cloud execution.

For a planning example, suppose each of the 500 monthly runs executes exactly four billable nodes. That produces 2,000 node executions before separately counted user writes or other activity. If there are also 500 distinct billable user saves outside those nodes, the estimate becomes 2,500 actions. Do not count a node’s write again unless the vendor’s meter treats it as another billable event.

Write down the assumptions behind that estimate: which branches execute, whether a request runs an approval and a notification separately, and whether failed attempts are retried. Then compare a small controlled batch with the account’s usage display. The final tier and full annual subscription remain unresolved until the measured meter behavior and selected allowance agree.

Budibase’s automation documentation describes triggers followed by actions, with live execution attached to published apps. Its loop documentation explains that actions can repeat across records. A single button click that processes many requests therefore needs a different estimate from one that processes one request.

Make the role model part of the purchase decision

The role documentation separates organization administrators, creators, and end users. End users use published applications without builder access. Workspace app roles control access to data and screens, and higher roles inherit lower-role visibility. Assigning everyone creator access for convenience changes both the access model and the buying scenario.

List the operations each person needs: submit a request, view their own request, approve an assigned request, or maintain the application. Ask the vendor to identify the plan that supports the controls you will configure. The Budibase versus Appsmith comparison considers the builder choice if your existing data and permission model make either a candidate.

Run a purchase decision through the app and its output

Create synthetic request PR-208 for ten replacement parts at $40 each, totaling $400. Include requester ID, approver ID, supplier reference, status, and a revision number. Give two end users requester roles and two approver roles. Keep the creator separate. Use a permitted test data source and a notification destination controlled by the evaluator.

The requester submits PR-208. Configure the backend workflow to validate the input, record the request, and route it for review. Budibase supports on-demand automations invoked from the app with defined input fields. The documented default is asynchronous execution, so the interface should not display a completed approval merely because a button was clicked.

Have the assigned approver accept the request, then attempt the same action as a requester and as an unassigned approver. Check the underlying record after each attempt. A hidden button is insufficient evidence that unauthorized changes are rejected. Repeat a submitted action and confirm that the configured workflow does not create a second purchase request or send duplicate downstream instructions.

Change the quantity to twelve after approval, making the proposed total $480. Use a declared rule that requires a new decision for the changed revision. The expected output should retain the earlier $400 approval and identify $480 as awaiting review. These are acceptance requirements for your application, not promised behavior from installing the tool.

Check the automation history for successful, stopped, and failed runs. The documentation explains how to inspect a failed step and notes that chaining can trigger further automations after a row action. Record your chaining setting and include its extra executions in the workload estimate. Confirm log retention on the selected subscription before relying on it for later investigations.

Add the operating work to self-hosted costs

Budibase’s installation documentation assigns server operation, security, maintenance, and troubleshooting to the self-hosting team. Budget hosting, persistent storage, backups, monitoring, patching, and recovery time. Put an owner and cost assumption next to each. No infrastructure total is estimated here because the deployment and recovery requirements are unknown.

For a licensed installation, check the documented outbound licensing requirements against your network policy. Self-hosting does not by itself establish an offline deployment. If the main goal is choosing a different app builder, the Retool alternatives comparison covers other approaches without treating hosting as the whole decision.

Where Permute fits in reusable business outputs

Permute is the connected-data and custom-app software we sell. We help connect permitted business records and apply declared rules that applications and structured reporting can reuse. For a purchase workflow, that starts with identifying the request revision and preserving the relationship between its amount, decision, and source evidence.

A configured output can bring accepted requests together with purchasing records while preserving permissions and freshness. It needs verified source access and a defined correction path. The enterprise app development article covers how to scope that work around an existing business process.

Limits of that approach

Permute does not reduce Budibase’s usage meter, reproduce its app designer, or automatically migrate its workflows. We do not decide who has spending authority. Any external action needs a supported, explicitly authorized, permissioned implementation; a report showing an approval does not itself issue a purchase.

Export and prove the workflow before moving it

Budibase’s workspace export instructions distinguish edited and published versions and allow internal rows to be included or excluded. Data-source configuration and credentials can remain in the export, so protect it and check the available encryption option. Record which version you are moving and which secrets need replacement.

The server migration documentation says external databases need separate backups and the destination needs access to the same external resources. Recheck network access, role assignments, notifications, and automation settings after import. Run PR-208 again against test destinations, including the rejected approval and duplicate submission, before enabling production writes.

The five-person pilot needs a usage budget as well as a subscription price. Count the executed work, confirm the selected allowance, and check permissions with a complete purchase request. Cloud makes sense when its plan covers that workload and the required controls. Self-hosting belongs in the comparison when the team can operate it and has included that work in the budget.

Questions about Budibase cost and usage