Skip to content
Manybases
esc

Search pages and sections. Try a tool name, an error code, a route.

↑↓ navigate↵ openesc close
  1. Guides
  2. Introduction
  3. Overview
Docs

Guides · Introduction

Manybases documentation

Manybases is the backend for the apps you build for yourself: a database, authentication, file storage, server-side functions and hosting for each of your projects — provisioned by your AI agent in one command, with every limit published (up to 1,000 users per app on the paid plans).

Four ways in#

You are…Start here
Building with an AI agent (Claude, Cursor, any MCP client)Start with an agent, then Connect an agent and the tool reference
Writing an app's codeStart from code, then the SDK
Calling the API directlyAPI conventions and Errors, then the data and management references
Looking at your projects in a browserThe dashboard

Ten facts to know first#

  1. One account owns many projects; each project is one app's backend, entirely its own: database, files, users, keys, functions, site.
  2. Three keys: ak_ (the account, held by your agent), pk_ (publishable, in the app), sk_ (secret, on a server, born only in front of a human).
  3. Two hosts: api.manybases.com for the account key, proj-<id>.manybases.com for a project's data. The URL addresses; the key authorizes.
  4. Every table has one of eight access presets that says who reads and writes its rows. They replace row-level security. The default is prive.
  5. A key is shown once, then hashed. A revoked key is refused from the next request on, everywhere.
  6. Some gestures confirm in two steps (428 with a token); a few also need a signed-in human — delete a project or a user, change an app URL, create a secret key, open a table with rows to the public, set a secret's value or manage the account's shared secrets.
  7. Every publishable key signs users up, whoever created it: an agent can build the backend and enroll the first users. (Until 2026-09-07 one created by an agent could not.)
  8. Every refusal carries a code, a message and a hint written for an agent to correct itself; every response carries a request id that the project's log shows.
  9. Quotas are per account and block instead of billing: at a quota, reads keep serving, writes stop, nothing is deleted, and you are never charged past your plan.
  10. Your data leaves whenever you want: an export is a zip with a SQL dump, your files and a manifest.

The map#

AI readers: the plain-text index with a reading order is llms.txt.