baseboard
106 providers, one panel

The admin panel for your SaaS that you never got round to building.

Baseboard connects to the services you already run on, like Supabase, Stripe, Vercel and Postgres. Each customer becomes one record: who they are, what they pay and when they last signed in. Refunds, bans and rollbacks only run for the people you allow.

Free for one person and one project. No card, no password.

providers
106
kinds of service
16
connect with a sign-in
12
tools over MCP
67
kinds of alert
14

Works with the sign-in, billing, hosting and monitoring you already pay for.

All integrations
  • Supabase
  • Clerk
  • WorkOS
  • Auth0
  • Kinde
  • Better Auth
  • Firebase
  • Appwrite
  • PocketBase
  • Stripe
  • RevenueCat
  • GoCardless
  • Lemon Squeezy
  • Paddle
  • Polar
  • Chargebee
  • Postgres
  • Neon
  • Prisma Postgres
  • Turso (SQLite)
  • PlanetScale (MySQL)
  • MongoDB Atlas
  • Cloudflare D1 (SQLite)
  • Convex
  • MySQL / MariaDB
  • ClickHouse
  • Amazon Cognito
  • Amazon DynamoDB
  • Redis
  • Typesense
  • Algolia
  • Meilisearch
  • Vercel
  • Cloudflare Workers
  • AWS Amplify
  • Netlify
  • Render
  • Fly.io
  • Railway
  • Expo
  • App Store Connect
  • Google Play
  • GitHub
  • GitLab
  • Bitbucket
  • Gitea / Forgejo
  • Git (any HTTPS remote)
  • Sentry
  • BugSnag
  • Rollbar
  • PostHog
  • Mixpanel
  • Amplitude
  • LaunchDarkly
  • Statsig
  • Plausible
  • Resend
  • Postmark
  • Amazon SES
  • Mailgun
  • SendGrid
  • Loops
  • Intercom
  • Plain
  • Crisp
  • Help Scout
  • Zendesk
  • HubSpot
  • Attio
  • Trigger.dev
  • Inngest
  • QStash
  • Better Stack
  • Checkly
  • UptimeRobot
  • S3-compatible storage
  • Google Cloud Storage
  • Vercel Blob
  • UploadThing
  • Anthropic
  • Amazon Bedrock
  • xAI
  • Together AI
  • fal
  • DeepSeek
  • ElevenLabs
  • OpenAI
  • Postcoder
  • Twilio
  • OpenRouter
  • Ideal Postcodes
  • getAddress.io
  • Upstash Redis
  • Axiom
  • Datadog
  • Fivetran
  • Airbyte
  • Slack
  • Microsoft Teams
  • Discord
  • Google Chat
  • Telegram
  • Knock
  • Novu

How it works

Useful in the first ten minutes

Every page reads from whatever you connect, so a project with only Clerk and Stripe still gets a useful Customers page on day one.

  1. Name your app

    Make a workspace with your email address. There’s no password and no card.

  2. Connect sign-in and billing

    Sign in at Supabase, Stripe or another provider, or paste a key. The Customers page fills in straight away.

  3. Add the rest when you need it

    Hosting, errors, logs, jobs and databases each add their own page as you connect them.

  4. Invite your team

    Everyone joins read-only. Allow refunds, bans or rollbacks for the people who handle them.

What you get

The pages you’d otherwise build yourself

See each page in detail
Customers
Everyone who signs in, matched by email to what they pay. Look someone up once instead of opening Clerk and Stripe side by side.
Overview
One card per connection, worst first: failed jobs, monitors down, past-due subscriptions and unresolved errors.
Billing
Monthly recurring revenue per currency, revenue by plan, one-time purchases net of refunds, failed payments and subscriptions set to cancel.
Health and logs
Uptime monitors, unresolved errors from Sentry, BugSnag, Rollbar, PostHog or Datadog, and the newest log lines from Axiom, Datadog or PostHog.
Data browser
Browse tables in Postgres, Turso, D1, Supabase, Firestore or Convex, edit them where the database allows, and run SQL where it has it.
Deployments
Recent deploys from Vercel, Cloudflare Workers, Netlify and Render. Rolling production back is one click and a confirm.
Permissions
Everyone starts read-only. An owner allows each change, from refunds and bans to rollbacks and file deletes, person by person.
Audit log
Every read and every action, with who did it and when. Calls from agents are logged under the token that made them.
Usage and AI spend
Sign-ups per day, daily active users from PostHog or Amplitude, and Anthropic or OpenAI spend split by model, key or project.
Files
Buckets on S3, R2, Google Cloud Storage, Supabase Storage and more. Download links expire after five minutes.
Alerts
A post to Slack, Teams, a webhook or email when a deploy fails, a monitor goes down, a payment fails or a new error turns up.
Assistant
Ask about a customer or a failed job in plain English. It reads through the same tools as the pages and can only do what you may.

The dashboard

What your team opens every morning

Drawn from the dashboard’s own parts, with made-up customers and numbers. Each page fills in from the connections a project has.

Overview. One card per connection with problems first, and blocks of your own underneath.
Users. Everyone who signs in, joined by email to what they pay, with their errors and emails on the same record.
Billing. Recurring revenue for each currency, revenue by plan and the payments that need a nudge.
Deployments. Every deploy with its commit. Before an older one goes live you see which commits it would undo.
Members. Owners and members, the projects each person opens and what each one may change.

Access control

Decide who can look, and who can change things

Two roles, a set of projects for each person and a level for every action. Nobody can refund, ban or roll back until an owner allows it, and owners are held to that too.

  • Owners and members

    Owners invite people, set roles and choose which projects each member opens. Members see only those.

  • A level for every action

    Each action is Allowed or Not allowed, person by person. Reading starts on; changing data starts off.

  • Agents get no more than their member

    The assistant and access tokens act as a member, and a token can be narrowed to some tools and projects.

  • Every change has a name on it

    The audit log records who made each change, including the assistant or a token acting for someone.

How permissions work
Riya Anand’s permissions

Dashboard

Connect, change and remove connections and linksAllowed
Add, change and remove alert rulesAllowed

Reading data

List customersAllowed
List invoicesAllowed

Changing data

Refund invoiceAllowed
Ban userNot allowed
Promote deploymentNot allowed

On your phone

Look up a customer from anywhere

Baseboard works in your phone’s browser, with nothing to install. The pages you use most sit in tabs along the bottom, with every other page under More. Pages stack into one column and wide tables scroll sideways.

  • The same permissions as on a laptop: refunds and rollbacks still ask you to confirm
  • Ask AI sits in the header, for questions you’d rather type than tap through
  • Alerts post to Slack, Teams or email, so problems reach you away from your desk

Mission control

Put it on the wall

Make a page for the screen in the office: the server map banded by group, the deployment map as a globe that turns by itself, and uptime across the bottom. Problems show in red wherever they are.

Status wall and Incident room templates
  • Server map

    Every connection as a card with its live status, banded by your groups or by what each one does.

  • Deployment map

    Where each host, database and bucket runs, on a flat map or a globe, with hosts joined to their databases.

  • Pages of your own

    101 kinds of block in rows of one to three. Start from a template or an empty page, and scope any block to some connections.

Make it yours

Your colours, your fonts, your name on it

Pick one of 9 built-in themes or make your own: the greys, the brand colour, the fonts, spacing and corner radius. On Pro and Team, put your own name and logo on the dashboard and lock one theme for everyone.

Onyx. Dark zinc with an amber accent. The original.

Build or buy

Why not just build it with AI?

You could. A coding agent will join your users to Stripe in an afternoon. What it won’t do is keep that working across every provider, keep your production keys out of reach and decide who on your team may issue a refund.

  • It’s written with the keys in hand

    To test against real data the agent needs live keys. They end up in .env files, shell history and its context.

  • Internal code gets the least review

    It sits behind a login, so it’s checked less than the app your customers use. It’s also the code that can refund and delete.

  • Everyone is an admin

    The first version has one role. That lasts until you hire support and want them to look things up without issuing refunds.

  • Nobody owns it after the first week

    It works, so nobody opens it again until a provider changes its API or your customer list passes the first page.

Security

Built to hold the keys to production

An admin panel can refund money and roll back deploys, so Baseboard treats every key and every write as something to account for.

How Baseboard keeps keys
  • Every key sealed on its own

    Each secret gets its own data key, encrypted with AES-256-GCM and bound to its workspace, project and provider.

  • One place decrypts

    A single broker opens a key, makes the provider call and writes the audit entry. Nothing else in the app can read it.

  • Read-only until allowed

    Refunds, bans and rollbacks only run for members an owner has allowed, after a confirm. Agents are held to their member’s permissions.

  • Reads stay reads

    Plain queries run inside read-only transactions where the database allows it. Cell edits and write SQL are separate permissions, off until you turn them on.

Agents and scripts get scoped tokens

Make a token on the Agents & CLI page and point any MCP client at your Baseboard. A read token sees data, a change token can refund where its member may, and a setup token can connect providers. Or pick single tools, and keep a token to the projects it needs.

Keys never pass through an agent. The CLI reads them at a hidden prompt and won’t run without a terminal.

MCP, CLI and SDK
# MCP over Streamable HTTPPOST https://your-deployment.convex.site/mcpAuthorization: Bearer bb_… # Connect a provider without handing over the key$ npx baseboard-cli connect stripe --project k57abc

Pricing

Start free and read everything

A new workspace starts on Free, with no card, for one person. Pro and Team are billed per member and add changes (refunds, bans, rollbacks and the rest), alerts and your own branding.

Compare plans
  1. Free

    • 1 project
    • 1 member
    • 3 connections per project
    • Read-only
    • 7-day audit log
    • 20 assistant replies a month
  2. Pro

    £12.00a member a month

    • 3 projects
    • Any number of members, billed per member
    • Unlimited connections
    • Refunds, bans, rollbacks and other changes
    • 365-day audit log
    • 100 assistant replies per member a month
    • Alerts to Slack, Teams, webhooks and email
    • Your own name, logo and locked theme
  3. Team

    £20.00a member a month

    • Unlimited projects
    • Any number of members, billed per member
    • Unlimited connections
    • Refunds, bans, rollbacks and other changes
    • Full audit log
    • 400 assistant replies per member a month
    • Alerts to Slack, Teams, webhooks and email
    • Your own name, logo and locked theme

Questions

Before you connect anything

The short answers. The guides and the blog have the longer ones.

Read the blog
Why not build our own admin panel with AI?
For one table from your own database, you probably should. The work is in what comes after: every provider’s API, joining people across them, keeping production keys safe and deciding who may refund. That’s the part Baseboard does. See the comparison.
Do I have to change my app’s code?
No. Baseboard reaches your providers through their own APIs, with a one-click sign-in or a key you paste. The only code you might write is a Custom API endpoint, and only if you want Baseboard to show something no provider holds.
Which services does it work with?
106 providers across sign-in, billing, databases, hosting, errors, logs, email and support. If yours isn’t one, a Custom API endpoint covers it. See every integration.
Can our support team look people up without being able to refund?
Yes. Everyone joins read-only, owners included. An owner allows each change, such as refunds, bans or rollbacks, for each person who handles it. How permissions work.
What does Baseboard do with my keys?
Each one is encrypted on its own and bound to its workspace, project and provider. A single broker opens a key to make a call and writes the audit entry, and agents never see a key at all. Read the security page.
Can we put our own name on it?
On Pro and Team, yes: your own name, logo and a locked theme, so your team sees your company’s tool rather than ours.

Stop answering “is this customer paying?” from three dashboards.

Name your app, connect a sign-in provider and a billing provider. You can skip any step and come back.