Supabase-compatible. Built for agents.

Every project gets its own isolated stack in the EU. Keep supabase-js — change the URL and keys. Nothing else.

EU-hosted
Daily encrypted backups
Supabase-compatible

your-app · productionEU · Nuremberg

Postgres 17Running
Auth · email, Google, GitHubRunning
REST & GraphQL APIsRunning
StorageRunning
RealtimeRunning
Edge FunctionsRunning

BackupsDaily · encrypted · 30 days

Restore testWeekly · automatic

lib/supabase.tsunchanged

import { createClient } from '@supabase/supabase-js'

export const supabase = createClient(
  process.env.SUPABASE_URL,      // your Basequel URL
  process.env.SUPABASE_ANON_KEY  // your Basequel key
)

Runs in production for

Prospelprospel.app
AutoGenShortsautogenshorts.com
Intelligointelligo.study
LatticeRunlatticerun.com
GenKidgenkid.app
Selfscriptselfscript.app

The problem

Great for one app. Awkward for ten.

Supabase is a brilliant way to start. Run a portfolio of apps on it — with agents doing real work — and the seams show.

One account per app

Every app ends up in its own account. Separate logins, separate keys, separate dashboards to keep straight.

Agents see one account at a time

Connect an agent and it only reaches the account it signed in to. The rest of your projects are invisible to it.

Quotas throttle you

Hit a usage quota and your project slows down. It rarely happens at a convenient moment.

Basequel puts every project in one place, each on its own isolated stack. One agent connection reaches all of them — within the scopes you grant.

Get early access

The platform

Everything Supabase gives you. Isolated, per project.

The same building blocks and the same client libraries. Each project runs as its own stack, so one busy app never shares a database with another.

Isolated by default

Every project is its own stack.

Postgres, Auth, APIs, Storage, Realtime, Edge Functions and Studio — provisioned per project, not shared. Point supabase-js at the new URL and keys and your app carries on.

Postgres 17

A full, current Postgres. Your schema, extensions and SQL, as they are.

Auth

Email, Google and GitHub sign-in, compatible with the Supabase Auth client.

REST & GraphQL

APIs generated from your schema automatically. No server code to write.

Storage

Buckets for files and images, with the policies you already use.

Realtime

Subscribe to database changes and broadcast to connected clients.

Edge Functions

Run server-side logic next to your data, migrated straight across.

Studio

The familiar dashboard for tables, SQL, auth users and storage.

Optional

A direct Postgres endpoint for serverless apps.

Using Drizzle, Prisma or pg from a serverless function? Switch on a public, TLS-encrypted Postgres endpoint for that project only. Off unless you need it.

Migration

Move from Supabase Cloud in one command.

Everything comes across. Your users don’t notice.

Copy
One command copies schema, data, Auth users, Storage files, scheduled jobs and Edge Functions.
Test
Point a branch or staging build at the new URL and keys. Passwords keep working. Scheduled jobs arrive paused, so nothing runs twice.
Switch
Re-copy right before you switch to pick up the latest data. URLs and keys stay the same, so there’s nothing to redeploy twice.

migrate · supabase cloud → basequelillustrative

→SourceSupabase Cloud project
✓Schemacopied
✓Datacopied
✓Auth userscopied · passwords keep working
✓Storage filescopied
✓Scheduled jobscopied paused · nothing runs twice
✓Edge Functionscopied
→Readyre-copy before switching · URLs and keys unchanged

Shown for illustration. Migration tooling is available to early-access projects.

Agent-native

Built for the agents that build your apps.

Give Claude, Hermes or your own agent one connection to every project — with guard rails you set.

MCP server
Works as a claude.ai connector over OAuth, and with Claude Code, Hermes and other agents via tokens.
The basql CLI
The same capabilities from a terminal or a script, for humans and agents alike.
Scoped tokens, read-only by default
Tokens are limited to the projects and actions you choose. SQL is read-only unless you say otherwise.
An audit log of every call
See which agent did what, when, and under which token.

Connect your agent Join the waitlist

Example agent sessionillustrative

You

Which tables in my shop project don’t have row-level security on?

list_projectsread
describe_schema project=shopread
run_sql read-onlyread

Agent

Two tables have RLS switched off: orders and coupons. I can draft policies, but applying them needs a token with write scope for shop.

Audit log
Agent	Tool	Scope
claude.ai	run_sql	shop · read
claude.ai	describe_schema	shop · read
claude.ai	list_projects	all · read

Agent access is in active development. Tool names are illustrative.

Security & backups

Your data stays in the EU. Your backups prove themselves.

A backup you’ve never restored is a hope, not a plan. Basequel restores one automatically every week.

Region

Germany

Hosted with Hetzner in Nuremberg. Your data stays in the EU.

Transport

Strict TLS

Every request goes through Cloudflare with strict TLS, end to end.

Isolation

One stack per project

No shared database between projects. One app can’t starve another.

Backups

Daily, encrypted

Encrypted daily backups to off-site object storage on Cloudflare R2, kept for 30 days.

Verification

Weekly restore test

An automatic restore every week proves the backups actually come back.

Agents

Scoped and audited

Read-only SQL by default, tokens limited to what you grant, every call logged.

A week of backups

Encrypted daily backup → R2
Automatic restore test

Monbackup
Tuebackup
Wedbackup
Thubackup
Fribackup
Satbackup
Sunrestore test

Each backup is kept for 30 days. Days shown are illustrative of the weekly cadence.

FAQ

Questions, answered.

Anything else? Mention it in the waitlist form and we’ll reply.

Do I have to change my app code?

No. Basequel is Supabase-compatible, so your app keeps using supabase-js. Only the project URL and keys change.

What does a migration from Supabase Cloud copy?

Schema, data, Auth users, Storage files, scheduled jobs and Edge Functions — in one command.

Auth users keep their passwords, so nobody has to reset anything. Scheduled jobs are copied paused, so nothing runs twice while you test.

How do I switch over without losing recent data?

Re-copy right before you switch. The re-copy picks up the latest data and keeps your Basequel URLs and keys the same, so the build you tested is the build you ship.

Where is my data hosted?

In Germany, on Hetzner infrastructure in Nuremberg. All traffic goes through Cloudflare with strict TLS.

How are backups handled?

Every project is backed up daily, encrypted, to off-site object storage on Cloudflare R2, with 30-day retention. An automatic restore test runs every week to prove the backups restore.

Can I connect with Drizzle, Prisma or pg directly?

Yes. Each project can switch on an optional public, TLS-encrypted Postgres endpoint for serverless apps that talk to Postgres directly. It’s off unless you need it.

Which agents can connect?

Basequel’s MCP server works as a claude.ai connector via OAuth, and with Claude Code, Hermes and other agents via tokens. There’s also a CLI, basql. Tokens are scoped, SQL is read-only by default and every agent call is written to an audit log. Agent access is being built now and will reach early-access projects first.

Is Basequel used in production?

Yes. It runs in production today for Prospel, AutoGenShorts, Intelligo, LatticeRun, GenKid and Selfscript — products from Sequel AI, the team behind Basequel.

How much does it cost?

Basequel is in early access. There’s no self-serve sign-up or billing yet. Join the waitlist and we’ll talk you through it when your project is onboarded.

Early access

Bring your projects to Basequel.

We’re onboarding projects in small batches. Tell us a little about yours and we’ll be in touch.

Supabase-compatible — keep supabase-js
One-command migration from Supabase Cloud
EU-hosted, daily encrypted backups, weekly restore tests
MCP server and CLI for your agents