Docs
Ship against dedicated Postgres, from the console
Short operational guides for the IndicBase dashboard. For HTTP details, see the developers reference.
Get started
Create an account, then create a project. IndicBase provisions a dedicated PostgreSQL database in the region you select from the catalog. The dashboard redirects to that project when it is ready.
SQL Editor
The SQL Editor runs PostgreSQL against your project database. Query history is stored per project. Destructive statements are your responsibility — use migrations for schema changes you need to replay.
Table Editor
List tables, inspect columns and keys, filter rows, and page results. Column and row mutations go through authorized project APIs, not a browser-side database.
Row Level Security
RLS policies live on your Postgres instance. Define SELECT, INSERT, UPDATE, and DELETE policies in SQL or from the console preview, then enable them before exposing Data APIs to clients.
Billing
Free, Pro, and Team include a monthly quota for projects, MAU, database size, egress, cached egress, and file storage. After you exceed an included quota, usage-based overages apply at the rates published on the pricing page. Enterprise contracts can set custom limits, SLAs, and billing. Manage invoices from the workspace billing page after you sign in.
CLI
The IndicBase CLI talks only to https://indicbase.com public APIs. Run `indicbase login` for device authorization, or set INDICBASE_API_KEY. Credentials are stored in the OS keychain when available. Commands never print API key values or database passwords.
Terraform
The Terraform provider is source-distributed from this repository and is not published to the Terraform Registry. Configure provider "indicbase" with INDICBASE_API_KEY. Resources map to stable public APIs: projects, functions, storage buckets, vector collections, and webhooks.
MCP
POST https://indicbase.com/api/mcp with a project or workspace API key. Tools inherit the key's scopes. Destructive tools require confirm=true. MCP never returns database URLs, AWS credentials, or unrestricted SQL.
GitHub
Connect GitHub from the dashboard Integrations page. OAuth requires GITHUB_CLIENT_ID and GITHUB_CLIENT_SECRET on the IndicBase deployment. If those are unset, the UI reports NOT_CONFIGURED and does not claim a connection. Access tokens are encrypted at rest and never sent to the browser.
Vercel
Connect Vercel with OAuth when VERCEL_CLIENT_ID and VERCEL_CLIENT_SECRET are configured, or store a scoped token after live validation against the Vercel API. Project IDs are never invented — linking only uses IDs returned by Vercel for that account.
Next.js
Install @indicbase/sdk, set INDICBASE_URL=https://indicbase.com, INDICBASE_API_KEY, and INDICBASE_PROJECT_REF. Use the SDK from server code. Never expose the API key to the browser.
Node.js
The same JavaScript SDK works in Node.js services. All requests go to /api/v1/{projectRef} with X-API-Key. Billing quotas and scopes are enforced server-side.
Python
Install the indicbase package from packages/python. Client(base_url, api_key, project_ref) uses the public v1 API. Do not duplicate the SDK in application code.
PostgreSQL
Use the dashboard connection string with psql, Prisma, Drizzle, or SQLAlchemy. CLI `indicbase db schema` and `indicbase db metadata` inspect catalogs without returning credentials. Migration apply/rollback remain dashboard session operations.
Webhooks
Create endpoints with POST /api/v1/{projectRef}/webhooks. Signatures use t=,v1= HMAC. The signing secret is returned once at creation and never stored in Terraform state after apply.
Ready to provision? Create an account.