Docs
From zero to a live Postgres URL in three commands.
Start here
Quickstartterminal
npm install -g @batadata/clibata loginbata create my-appAll docs
Get started
Your first database, and what it will cost you.
- QuickstartCreate a Postgres database, run a query, and point your app at it.
- Move your Postgres to BataDBOne command moves any Postgres in: where each host keeps its direct URL, what the import checks, the cutover, and handy commands.
- ConnectingPooled and direct connection strings, Prisma, scale to zero, and SQL over HTTP.
- Pricing and billingRates, plans, the free allowance, spend caps and how usage is measured.
Guides
Hooking up agents and moving an existing app over.
- Agents quickstartDrive BataDB from an agent: scoped keys, the bata CLI and the MCP server.
- App keysThe key for a deployed app: never expires, rotates without downtime, limited to the tables you grant.
- Migrate from NeonMove a Neon or any Postgres database into BataDB with bata import.
- Migrate from PrismaMove a Prisma app to BataDB and Turbine ORM: data first, then code.
- Turbine ORMUse the Turbine ORM with BataDB over TCP or edge HTTP, with query telemetry.
- PowDB sandboxesPull a branch into a local PowDB copy for agents and offline work.
- Reporting an issueTell BataDB something is wrong from the CLI, an agent or the console, with your project state attached.
Reference
Every command and every flag.