Base Captain and Noloco
Written by Base Captain's founder. Checked on .
We build Base Captain, so we are not neutral. Every fact about Noloco below is from its own pages, linked, on the date above; write to us if one is wrong.
In short
Noloco builds portals and internal tools on your data, in its own tables or synced with Airtable, Google Sheets or a SQL database, with an AI assistant to build them. Base Captain is the software and its database in one, built and changed by asking.
Noloco’s permissions are as fine-grained as Base Captain’s. The difference that matters most is elsewhere: each change comes as a card to apply, and going back brings the data back with it.
What Noloco does well
- Permissions.
- Roles, and rules for which records and which fields each role may see and change; its record rules “work at the database/API level.” Noloco’s page
- Your data where it is.
- Noloco Tables, or Airtable, Google Sheets, PostgreSQL, MySQL, Xano and Supabase in two-way sync. Noloco’s page
- Client portals.
- Clients get their own branded view, with as much access as they need; the Build plan counts up to 1,000 of them. Noloco’s page
- An AI assistant.
- Nola adds tables, relationships, screens and workflows from a conversation. Noloco’s page
- Versions and record history.
- Revert the editor to an earlier version of the app or publish one, and see every change to a record. Noloco’s page
Where Base Captain differs
- Every change shown first.
- You ask in plain words, and the change comes as a card that says what gets added, who sees it and how many records it touches, and any data it would drop. Nothing changes until you apply it.
- Going back includes your data.
- Before each change to how a base works, a copy of its data is saved. Within an hour the base can go back to it, data and all; later, a new change undoes it and keeps the records entered since.
- A history you can undo.
- Every change is recorded with who made it and how. A change can be undone from the history, and a deleted record restored.
- Work that moves itself.
- Workflows take a record from step to step, and agents, in Base Captain or on your own machine, do the steps you give them, with an approval wherever a person should decide.
- No code to read.
- Base Captain writes code for your base where a change needs it, and tries it before you apply it. Nobody on your team writes it or has to read it, even when something goes wrong; it is one click away on the change, and in its place in the base, for whoever wants to read or change it.
- Everything out at once.
- Every list downloads as an Excel or CSV file, and a builder downloads all of the base’s data in one zip file, with its files, whenever they like.
Prices
- Free
- $0
- 50 active clients, 2,000 records
- Build
- $79 a month, or $65 a month billed yearly
- 10 team seats, then $6 a seat ($5 yearly); 1,000 active clients; 25,000 records
- Enterprise
- On request
- Set with Noloco
Each plan includes monthly AI credits; more records and credits cost extra.
Noloco’s pricing page, checked on .
Choose Noloco if…
- Your data should stay in Airtable, Google Sheets or your own SQL database, in sync. Base Captain keeps the data in your base. Base Captain connects to other tools through webhooks, in and out, and through the MCP servers of services such as Notion, Linear or Stripe, which you or the assistant set up, and takes payments through Stripe and PayPal.
- You run a portal for many outside clients and want to design its screens yourself.
- You need an ISO 27001 certificate, or your data in Ireland, where Noloco’s servers are.
Moving over
- Out of Noloco.
- Each table has an export button for all its records, as CSV; a linked field comes out as two columns, its text and its Noloco id. Noloco’s page
- Into Base Captain.
- Put each table on a sheet of one workbook, keep the text column of each link and delete its id column, and give the workbook to the assistant.
- What stays behind.
- Screens, roles, workflows and permissions; ask the assistant for the ones you need.