A database your AI agent builds and runs for you.

Ask Claude for a recipe box, a CRM, or a reading list. It creates a Base76 base, designs the fields, and saves your records. The data stays after the chat ends. Open it in a browser, query it from a script, or send someone a link.

Join the beta See what you can build

Closed beta. Join the waitlist and you'll get an email when you're in. Beta accounts are free.

Three steps from a chat to saved data

Nothing to provision, no connection string, no schema to write by hand.

Add the connector
In Claude, add a custom connector with this URL, then sign in. Your personal workspace already exists.
https://mcp.base76.com/mcp
How to add a connector in Claude
Ask for what you want
Make me a recipe box. Recipes have ingredients, cook time, a cuisine, and a photo. I want to filter by what I can make on a weeknight. Start with the three below.
- create_basetim/recipes
- define_collectioncuisines
- define_collectionrecipes
- create3 records, private
It's saved
Open the base at app.base76.com, ask a different agent about it tomorrow, or share one recipe as a page. Every record has history, so an agent's mistake is one restore away.

What people build

Each guide has the prompt, the schema, the API calls, and the share page, checked against the live service.

Recipe box
Two linked collections, ingredient lists, and a recipe card you can text to someone.
- Relations
- List fields
- Record templates
- Share links
Watchlist
One collection, a poster wall, and a one-file page that updates live.
- Select fields
- Realtime SDK
- Collection templates
- Bulk import
Notes
Save a conversation in one sentence and find it next month from any agent.
- save_note
- Search
- Markdown links
- Scripts
Headless CRM
Four linked collections, pipeline totals, and a contact page with the whole history.
- Natural keys
- Inverse relations
- Aggregates
- Timeline templates
- Guests
Prompt library
Prompts with version history, served as markdown any tool can fetch.
- Upsert
- Collection share links
- Markdown output
- History

What you move to when the spreadsheet stops working

Most of this data starts in Google Sheets, and plenty of it should stay there. A base is for the point where you're copying ids between tabs and your agent has to guess what each column means.

	Google Sheets	Base76 base
Setup	You build the columns	Your agent designs the fields from a sentence
Values	Data validation where you set it up	Every field has a type, checked on every write
Linked data	Lookups over copied values	Relations that stay linked, with delete rules
Undo	Version history for the file	History per record, and restore the whole base to any point in the last 30 days
Sharing	Share or publish the file	Share one record, one collection, or the whole base as a read-only page
Agents	Through the Sheets API	MCP and REST built in, and every write reports who can see the data

Sheets is the better tool for formulas, charts, and pivot tables. Base76 has none of those.

Your agent is the interface

Everything the agent can do goes through one API, so a script or a throwaway page gets the same reach. The app at app.base76.com is there for browsing and editing.

MCP for assistants

27 tools, including find, aggregate, search,define_collection, set_template, and share. Sign in once with OAuth.

https://mcp.base76.com/mcp

REST for scripts

JSON in, JSON out, with an API key. Errors name the field and say how to fix the call.

curl -s https://api.base76.com/v1/bases/tim/recipes/find \
  -H "Authorization: Bearer $B76_KEY" \
  -H 'content-type: application/json' \
  -d '{"collection": "recipes",
       "where": {"rating": {"gte": 4}},
       "sort": "-rating"}'

A realtime SDK for pages

One ES module, no install. Queries stay live over a WebSocket and resume after a dropped connection.

import { base } from
  "https://api.base76.com/sdk/v1.js";

const db = base("tim/watchlist",
  { token });
db.collection("movies")
  .where({ status: "watching" })
  .onSnapshot((rows) => render(rows));

A link for every record

Templates turn records into pages: a recipe card, a poster wall, a contact with their history. Share links are read-only and revocable. Add .md and the page comes back as markdown for the next agent.

https://app.base76.com/s/b76s_…/chana-masala-pf6m3wx0.md

Each base also publishes its own llms.txt with its real field names and sample calls, so code an agent writes matches your schema. Start with the agent guide.

Private until you share it

A new base is visible to you alone. Every write returns its audience, like private, so the agent knows who else will see the data.
Removing a field or dropping a collection shows how many records it touches and waits for a yes. Rewinding a base waits for one too.
Each record keeps its history. A whole base can go back to any point in the last 30 days, and that restore can be undone too.
Export the whole base, schema and records, whenever you want.

The beta is free

Base76 is in closed beta. Beta accounts are on the Free plan. Reads aren't metered, and if you go over a limit, writes pause while reads keep working.

Bases: 10
Data: 500 MB
Files: 2 GB
Writes per month: 100,000
Records in semantic search: 25,000
Record history: 30 days
Guests per base: 5

Join the beta

From the articles

Before bases, Base76 wrote about when a small business should replace its software. Those articles are still here.

Decision guideSep 26, 2026
Best Survey Software for Small Businesses
Best survey software for small businesses: compare workspace forms, hosted survey tools, self-hosted systems, and a narrow custom workflow before you migrate.
Decision guideSep 18, 2026
Typeform Alternatives for Small Teams
Typeform alternatives for small teams, comparing a simpler hosted form tool, self-hosted software, and a narrow custom intake workflow before migration.
Decision guideAug 8, 2026
Can AI Coding Agents Replace SaaS?
AI coding agents can replace narrow, stable business workflows. This framework shows where owned software is practical and where SaaS still wins.

All articles