Baserow pricing: count editors and viewers separately

You are about to invite an outside coordinator to a Baserow workspace. They need to read project records, while your operations team maintains them. Baserow pricing depends on that distinction: its subscription documentation bills every Cloud Premium collaborator, while Cloud Advanced bills Admins, Builders, and Editors and provides non-billable Viewer and Commenter roles.

Consider Premium for a small collaborating team whose access requirements it meets. Evaluate Advanced when read-only participation or differentiated permissions matter. Self-hosting fits a team that needs its own infrastructure and can maintain it. Keep an existing deployment when its permissions, capacity, and operating cost are acceptable; a lower advertised seat price alone does not justify moving a working app.

Price the same group of people on both Cloud plans

Baserow lists Cloud Premium at $10 per user per month on annual billing, or $12 on monthly billing. Advanced is $18 or $22 on the same respective terms. The official pricing page also lists a Free plan with 3,000 rows and 2 GB per workspace. Check the live checkout before purchasing; these published terms were checked October 23, 2026.

Take an illustrative workspace with five people who edit records and ten who only need to view them. Everyone participates for the full year. The calculations below use USD, exclude taxes, services, and any extra usage charges, and assume no negotiated discount. Premium is a cost reference here, not a claim that it provides the same read-only controls as Advanced.

For this mix of people, Advanced has a lower license total even though its rate per paid user is higher. That result changes when viewers become editors or everyone already needs editing access. Record the intended role beside each person in your budget. An informal description such as “occasional user” does not determine what they can do or how they are billed.

Keep workspace collaborators separate from people accessing a published application. Baserow’s pricing page lists an external app user allowance, which is a different category from the collaborator calculation above. Confirm the current allowance, authentication setup, and extra-user terms for a portal before extending this estimate to customers or suppliers.

If you are moving from Airtable, use the same roster and required actions in both estimates. Airtable pricing covers its workspace billing and reviewer permissions. A comparison based on different groups of users will obscure the cost of the workflow you intend to run.

Test the outside coordinator’s access before inviting everyone

Use a small fictional project register to define the acceptance check. Include a project identifier, coordinator, customer reference, completion date, and an internal cost field. Add one project the coordinator should see and another they should not. The expected output is a usable view of permitted work without exposing the restricted record or financial field.

Configure the intended roles in the candidate plan, then sign in with a separate test identity. Try viewing, changing, exporting, and following links to related records. Repeat after removing access. These are proposed checks, not reported test results. A successful login demonstrates authentication; it does not establish whether every record reached through that account is appropriate.

Record any failed requirement before deciding whether another plan or a different app design is needed. Do not solve a confidential-field problem by telling people which columns to ignore. If a reviewer must leave feedback, check that the selected role supports that action without also allowing unintended changes. Budget from the final configuration, including anyone promoted during the trial.

Separate self-hosted licenses from running the service

Baserow’s self-hosted licensing instructions describe a license tied to an instance and paid seats assigned by an administrator. Paid access is not automatically equivalent to every user on that installation. The instructions also warn Advanced buyers to purchase the required paid seats first, then invite free users after activation, so the upgrade does not count everyone as paid.

Request a quote or checkout estimate for that exact seat assignment. This article does not substitute the Cloud total for a verified self-hosted quote. Add hosting, storage, backup retention, monitoring, updates, and the person responsible for recovery. A server bill is only one part of that operating budget, and the staff time depends on your deployment.

The division of responsibility is explicit in Baserow’s deployment documentation: the vendor manages Cloud infrastructure, while self-hosted operators manage their deployment. Both can support a structured operations database. Choosing where it runs should follow your data location requirements and ability to operate it, with the same access checks in either case.

For another product with a hosting choice, Budibase pricing separates application licensing from deployment work. Compare the ongoing owner and recovery obligations as well as the subscription. Leave self-hosting out of the shortlist when nobody can take responsibility for the service after the initial installation.

Budget for restoring access and reconnecting the workflow

Baserow’s workspace export documentation supports portable exports of selected workspace content, but excludes members and permissions, published application domains, webhooks, and user-specific settings. Keep a separate inventory of those items before moving. An export containing records and application structure is not evidence that the destination is ready for outside users.

First rehearse the move with permitted sample data. Compare row counts and relationships, inspect attachments, and recreate access before inviting users. Reconnect external credentials and webhook destinations through their normal configuration paths. Submit a sample change and verify its downstream result; keep the old environment available until the responsible owner accepts the new one.

Moving from Cloud to self-hosted also changes the subscription. Baserow’s deployment instructions say the Cloud subscription cannot be converted into a self-hosted one: buy and activate the appropriate license, then cancel Cloud. Allow for overlap in the migration budget rather than assuming both environments fit inside one subscription.

If most participants are external customers, Knack pricing examines a portal budget based on record capacity and required controls. Compare the same access requirements rather than assuming unlimited users means equivalent permissions.

Where Permute fits: matching the records behind an app

Permute is the connected business data and custom application software we sell. Our interest in this buying decision is commercial. If your project register and accounting export use different customer identifiers, we can help define how those records match and preserve the source evidence. An uncertain match should remain visible for review before it becomes a customer total.

We can apply your declared definitions across a repeatable report or custom app. An operations lead can inspect which customer records were combined, where a project status came from, and how current the evidence is, subject to their access. That work concerns the meaning of the data behind the app, alongside the choice of editor and hosting arrangement.

Keep licensing and connection scope explicit

We do not sell Baserow licenses or administer its subscription terms. This article promises no native Baserow connector or write-back integration. Access to each source and the permitted workflow must be scoped before implementation. Enterprise app development covers that planning work when an application needs shared business data and permissions.

Choose from the approved roles and operating budget

Count the people who must edit and those who need narrower participation before pricing Baserow. Confirm the chosen plan meets their access requirements, then compare the full-year license amount on consistent billing terms. Include the operating owner and migration work if you are considering self-hosting. The next outside collaborator should arrive with a tested role and a known place in the budget.

Questions about Baserow subscriptions and access