Just the Postgres.
No MAU fees. No egress. No anon key.
Basely provisions isolated Postgres databases in under a second. Bring your own auth (Clerk, Better Auth, whatever). Pay a flat rate that doesn't scale with your users.
Standard Postgres connection string. No SDK lock-in. Works with Prisma, Drizzle, or raw pg.
A May 2025 CVE found 10% of Supabase apps had tables fully readable via the public anon key. Basely has no anon key — your schema is only accessible via your scoped connection string.
Supabase's SQL editor runs as the Postgres superuser, silently bypassing RLS. Every Basely project is an isolated schema + scoped role. Nothing else has access.
Supabase's real production baseline is $110–120/mo after compute upgrades. Add $1,300/mo for auth at 500k users. Basely: $15/mo flat. No compute tiers, no egress, no MAU meter.
Basely vs Supabase
For teams who need Postgres, not a full BaaS.
* Supabase baseline: Small compute ($15) is too weak for production; Medium ($60) + Pro ($25) + egress = $110–120/mo typical. Auth at 500k MAUs based on published Supabase pricing.
Who switches to Basely
You moved to Clerk, Better Auth, or Lucia because Supabase Auth hit the MAU wall. Keep the Postgres — move it here. Flat rate, standard connection string, no re-architecture.
Supabase free tier pauses after 7 days. Pro covers 1 project. Builder covers 10 projects at $15/mo total — not $25 per project.
Claude and Cursor can create a project, run migrations, execute queries, and generate TypeScript types in a single prompt — with no human in the loop. MCP-native from day one.
Egress charges, compute tier jumps, MAU overages. Basely is $15/mo. That's the whole bill. No meters running in the background.
MCP — built for AI agents
Add to Claude Desktop or Cursor. Your agent can provision, migrate, and query without any human steps.
// claude_desktop_config.json
{
"mcpServers": {
"basely": {
"command": "npx",
"args": ["-y", "@basely-cli/cli", "mcp"],
"env": {
"BASELY_API_URL": "https://api.basely.cc",
"BASELY_API_KEY": "bly_..."
}
}
}
}# Tell Claude:
"Create a Postgres project called myapp, run this migration:
CREATE TABLE users (id SERIAL PRIMARY KEY, email TEXT UNIQUE NOT NULL);
then generate TypeScript types."
# Claude calls in sequence — no human steps:
create_project → DB ready, connection string returned
apply_migration → schema applied
gen_types → TypeScript interfaces written to src/db.tsCLI quickstart
Works with any Postgres client — Prisma, Drizzle, raw pg, psql.
# Install
npm install -g @basely-cli/cli
# Connect
basely auth setup --url https://api.basely.cc --key <your-key>
# Create a database (under a second)
basely projects create myapp
# Run a migration
basely migration push myapp --name 001_init --file schema.sql
# Generate TypeScript types
basely gen types myapp --out src/db.tsREST API
/auth/signup/auth/login/auth/keys/projects/projects/projects/:id/query/projects/:id/schema/projects/:id/migrations/projects/:idPricing
Flat rate. No credit card to start. No meters.
No egress fees · No MAU fees · No compute tiers · No surprise charges
Running Supabase in production? You're likely paying $110–120/mo before auth overages. Switch to Basely for $15/mo.