Skip to content
Features

An admin tool built like an actual product.

Suparbase started as a wrapper around PostgREST and grew into a complete Supabase workspace: row editing, RLS debugging, storage, auth users, AI, raw SQL, audit history. Everything below ships today.

Headline features

The six you'll use every day

These are the day-one wins. They take five minutes to learn and the rest of the product builds on them.

Everything else

Day-two features

The bits you reach for when something specific happens: a CSV import, a deleted user, a debugging session. They're all there.

  • Seven archetype admins

    Users, Content, Logs, Commerce, Tasks, Messages, plus a Generic fallback. Each ships purpose-built list + detail views matched automatically from AI analysis.

  • Storage browser

    Bucket list, prefix navigation, drag-drop upload, multi-select delete, 1-hour signed URLs, public URL copy. Same encrypted key as PostgREST.

  • Auth users admin

    Wraps /auth/v1/admin/*. Invite, generate recovery links, ban/unban, delete. Gracefully degrades when the connection's stored key isn't service_role.

  • Bulk ops + CSV in/out

    Bulk delete, bulk update, CSV/JSON export with filter awareness, chunked CSV/JSON import with abort-or-skip on row errors.

  • Encrypted credentials

    AES-256-GCM at rest. The plaintext API key never persists to disk, and never touches a browser. Same vault holds the optional direct-Postgres URL.

  • Server-side PostgREST proxy

    Every read and write routes through an authenticated Next.js route handler. The browser holds only a session cookie. Rate-limit buckets per verb class.

  • Audit log + recent activity

    Every write hits an audit table keyed to user, connection, table, primary key, and verb. The dashboard surfaces the last 10 entries with click-to-row.

  • Saved views + filter chips

    Pin search + filter combinations to any table. Filter by column with operators (eq, neq, lt, gt, ilike, in, is null). Sharable URL state.

In practice

Three flows you'll recognise

These are the moments where Suparbase replaces five other tools.

  1. AI write flow

    You: "set status to cancelled on all orders older than 30 days". The agent calls get_table_schema, then count_rows, then propose_update with a preview of 5 affected rows. A yellow diff card appears. You hit Apply. The server re-validates and runs the PATCH; a row appears in the recent-activity feed.

  2. Connection setup flow

    Sign up, paste your project URL + API key. The key is AES-256-GCM encrypted before the row commits. The first dashboard load runs an AI schema analysis (optional, falls back to heuristics) so tables get the right archetype + display name automatically.

  3. Debug an RLS policy

    Open the RLS page, paste your direct Postgres URL once (encrypted in the same vault). Browse policies grouped by table, then simulate a request: pick a role, paste request.jwt.claims, click Run. SELECT/INSERT/UPDATE/DELETE allow-or-deny shows for each verb, all inside a transaction that always rolls back.

Drop in your Supabase key and ship.

Five minutes to set up. Free to self-host. No credit card on the hosted plan.