A client portal can have a small internal team and a large outside audience, so one per-user number is not enough to price it. Current Noloco pricing uses Free, Build, and Enterprise offers. For Build, calculate the base subscription, activated team seats, records, and any additional AI credit demand before approving the budget.
Noloco is worth evaluating when a portal over the required data sources fits its controls and usage allowances. Keep a working legacy subscription when its features and price still fit. The current Build offer does not by itself justify moving an existing app or prove that every older plan description is wrong.
Distinguish a new Build purchase from a legacy plan
Noloco’s 2026 pricing announcement introduces Build and says existing Starter, Pro, and Business customers can retain their plans and prices. Its older pricing documentation still describes those earlier tiers. Use the current pricing page for a new purchase and the account’s actual terms for an existing subscription.
Write the intended app, account, billing period, internal staff, external clients, and data population into the purchase scope. Count users by their role in this implementation rather than by a generic estimate of people who might visit. Ask the vendor to confirm the classification of contractors, partners, and client administrators.
The Softr pricing comparison offers another way to structure a portal budget. Compare the same number of internal staff, outside clients, and records over the same billing period. A larger external allowance does not remove the need to check data permissions and the specific source connection.
Read the current base and expansion rules together
The official pricing page lists Build at $65 per month billed annually or $79 billed monthly. The annual offer includes ten team seats, 1,000 clients, 25,000 records, and 250 monthly AI credits. Its annual table lists additional activated team seats at $5 and additional 25,000-record blocks at $25. Enterprise is custom-priced.
| Budget input | Current annual Build offer | What to confirm |
|---|---|---|
| Base subscription | $65 monthly equivalent | Annual commitment and tax |
| Activated team seats | 10 included, then $5 per extra seat | Classification and deactivation |
| Records | 25,000 included, then $25 per additional 25,000 | Per-app scope and synced records |
| Clients | 1,000 included | Treatment above the allowance |
| Enterprise | Custom quote | Required controls and support |
Record counts need the same care as user counts. Include the tables the app requires, their relationship records, and the retention period for history. A portal with few customers can still accumulate many operational rows. Do not budget only the visible customer list when transactions and line items are also required.
Use the offer’s activated-seat definition (accounts added and not disabled) when estimating staff charges. A dormant staff account and a disabled account may be treated differently. Establish an owner for removing access and checking the next bill when staff leave or an agency engagement ends.
Calculate an annual portal scenario
Assume a hypothetical Build purchase with fifteen activated team seats, no more than 1,000 clients, and 50,000 eligible records in one app. Using the annual rates cited above, the monthly equivalent is $65 + (5 × $5) + $25 = $115. The twelve-month equivalent is $1,380 before tax and additional credits.
The assumptions matter: five seats exceed the included ten, and one record block exceeds the included 25,000. This example does not establish the monthly-contract price for those add-ons or how a mid-term change is prorated. Confirm the exact order form and expansion timing before treating the arithmetic as an invoice forecast.
Keep the subscription separate from source-system charges and the work of building the portal. The app may need data preparation, identity matching, permission design, training, and ongoing administration. Estimate those tasks from the intended workflow rather than claiming an unsupported implementation allowance or return on investment.
Verify the source and synchronization path
List the tables and fields the portal must read, the fields it may change, and the source that remains authoritative. Check the exact source connection in the quoted plan. An app that imports a spreadsheet once and an app that relies on continued synchronization have different operating requirements.
Run a proposed acceptance scenario using a permitted sample: add a record in the owning source, update it, then remove or revoke it. Observe when each change reaches the portal and how errors appear. Record the observed behavior; the existence of a source logo on a pricing page does not establish the timing or deletion semantics for your configuration.
Decide how long history must remain visible and which records can be archived. If a completed transaction remains needed for a customer dispute, deleting it to fit an allowance creates a different problem. Price the required retention scope and ask how archived or synced records count before planning a cleanup.
Test client isolation at the data boundary
Noloco’s filter documentation distinguishes view filters from record-level permissions enforced at the API layer. Use that distinction when reviewing a client portal. A page displaying only one client’s rows is not sufficient evidence that another client’s records cannot be requested.
Create separate evaluation accounts for internal staff, Client A, and Client B. Check access to records and sensitive fields through the paths available to each role, then revoke an account and repeat the checks. These are proposed acceptance steps, not a report of a hands-on Noloco test.
Noloco’s role and permission documentation discusses record and field controls, but some plan references use legacy names. Obtain written confirmation that the controls needed for the portal are included in the exact current offer. Keep unresolved plan wording separate from observed permission behavior.
Retain a way to recover the business workflow
Keep an inventory of the portal’s tables, relationships, roles, formulas, and workflows. Ask which artifacts can be exported and whether they can be used outside the product without reconstruction. A CSV of rows can preserve data while leaving the access rules and calculations behind.
Practice recovering the required source records and document a rollback plan before switching an existing portal. Preserve identifiers so links to customer accounts and historical transactions remain explainable. Compare the replacement’s output with the accepted source rather than relying on a visually similar page.
The enterprise app development process covers ownership and acceptance beyond the editor. Assign someone to manage the data connection, permission changes, and release review. A low base price is useful only when the organization can keep the workflow operating after the initial builder moves on.
Where Permute fits behind a connected portal
Permute sells connected business data, custom applications, and governed analysis. We can scope permitted HubSpot, Shopify, or accounting records with declared entity mappings and business definitions for an application. This is a separate data decision from buying Noloco; no native Noloco integration is promised here.
We can reuse those definitions across a recurring report and a custom application, with source references and current permissions. An operations manager can inspect which records explain a client’s balance or order exception. That scope is useful when the portal’s obstacle is inconsistent data across sources rather than its page layout.
Inspect the records behind a portal calculation
Start with a permitted data sample and the client-level result the app must reproduce.
Keep quote terms and application controls explicit
We do not set Noloco pricing, guarantee legacy entitlements, or certify a portal configuration from its plan label. The annual example excludes additional credits, source subscriptions, tax, and delivery work. This data workflow reads permitted source records; any proposed source-system write requires a supported and approved execution path.
A portal buyer still needs to approve the retained record scope, client permission rules, and operational owner. Keep a current app when those requirements are met and a change would mainly recreate working behavior. Reprice a larger workload before assuming the original small-app calculation still applies.
Budget the portal at its required operating scope
Noloco pricing depends on activated staff, client classification, records, and usage as well as the base plan. Keep current Build terms separate from retained legacy subscriptions and match the billing period before comparing totals. Confirm the source path and client permissions with representative checks. Use the resulting scope to decide whether the subscription supports the portal you need.
Review a portal data and access scope
Bring the proposed audience, records, and the client boundary the application must enforce.
Questions about a Noloco portal budget
Can unused accounts still affect the budget?
The current offer describes activated team seats, so do not assume that a month without logins removes a seat charge. Confirm deactivation and billing behavior for the account. Access removal and the commercial seat count should be checked together.
Should an existing Pro customer switch to Build?
Compare the actual retained features and renewal price with the required workload under Build. The 2026 announcement permits existing customers to retain their plans. Switching needs a concrete capacity or feature benefit, not just a newer plan name.
Does the credit allowance establish how many apps can be built?
No fixed number of completed apps is established by the calculation here. Use representative tasks to measure demand and confirm top-up rules. Include runtime and maintenance activity if they consume the same allowance.