baseboard

Product

Every page of Baseboard, and where its data comes from

Each page reads from the connections a project has. Connect Clerk and Stripe and you get Customers and Billing. Add Vercel and Sentry to fill in Deployments and Health. Nothing needs setting up twice.

Customers

One record per person, joined by email

The page you check before answering a support email. Search by email and see whether they signed in today, what plan they’re on and whether their last payment went through.

  • Everyone who signs in, from every sign-in connection, matched to what they pay
  • Their subscriptions, invoices and one-time purchases, with a refund button for each
  • Errors that hit them, their log lines, feature flags, support conversations and CRM record
  • Ban, unban and cancel where the provider allows it, for members who may

Overview and pages

A first page that shows what’s wrong, worst first

Overview is a page like any other. Anyone allowed to edit pages can turn on Edit page and add revenue, deploys, uptime, logs or a world map of where everything runs. How pages are built

  • One card per connection: failed jobs, monitors down, past-due subscriptions, unresolved errors
  • 101 block types to build your own pages from
  • Drag blocks into rows; each block can be scoped to some connections or groups
  • Pages are JSON too, so they can live in a repo and be applied from CI

Billing

Revenue without a spreadsheet

Reads from Stripe, RevenueCat, GoCardless, Lemon Squeezy, Paddle, Polar, Chargebee and Custom API. Trials don’t count as revenue, and app store subscriptions without a known price are counted separately.

  • Monthly recurring revenue per currency, never converted, from active and past-due subscriptions
  • Revenue by plan, with yearly and quarterly prices turned into a monthly amount
  • One-time purchases net of refunds, by product and newest first
  • Failed payments and subscriptions set to cancel, each with the customer’s email

Deployments

Roll back production in one click and a confirm

Hosts: Vercel, Cloudflare Workers, AWS Amplify, Netlify, Render, Fly.io, Railway and Expo. Source control from GitHub, GitLab, Bitbucket, Gitea / Forgejo and Git (any HTTPS remote) explains each deploy, read-only.

  • Recent deploys from every host, with the commit each one shipped
  • For any deploy, the commits that making it live would add or undo
  • CI status on the default branch, open pull requests and the latest commit
  • App builds and update groups from Expo, with retry where the token allows

Alerts

Hear about it before a customer tells you

Rules are checked every five minutes. Each problem is posted once, and more than five at a time fold into one summary.

  • 14 kinds of rule: Health, Deploy failed, Build failed, CI failing, Job failed, Data sync failing, Monitor down, New error, Payment failed, Subscription cancelling, Revenue level, Email bounced, AI spend and Credits low
  • Posts to Slack, Teams, a webhook or members’ email
  • A problem must show on two checks in a row before it’s posted, so a blip stays quiet
  • When the problem clears, Slack messages are edited to say resolved

Assistant

Ask in plain English

Ask why a payment failed, which jobs broke overnight or which customers are past due. It reads what you could read and does only what you may.

  • Open it from Ask AI in the header, or with ⌘K
  • Uses the same tools as the pages, as the signed-in member
  • Asks in the chat before running anything that changes data
  • Helps with setup: it asks what your app runs on and puts connect buttons in the chat

And the rest of the dashboard

  • Health

    Uptime monitors and incidents from Better Stack, Checkly, UptimeRobot and Custom API. Unresolved errors from Sentry, BugSnag, Rollbar, PostHog and Datadog, with the ones first seen since the live deploy marked new.

  • Logs

    The newest lines from PostHog, Axiom and Datadog, with a text search. Each customer’s page shows their own lines.

  • Data browser

    Tables in Supabase, Firebase, Appwrite, PocketBase, Postgres, Neon, Prisma Postgres, Turso (SQLite), PlanetScale (MySQL), MongoDB Atlas, Cloudflare D1 (SQLite), Convex, MySQL / MariaDB, ClickHouse, Amazon DynamoDB, Redis, Typesense, Algolia, Meilisearch and Custom API. Edit cells where the database allows it and run SQL where it has it. Edits and writes are separate permissions.

  • Jobs and syncs

    Runs from Appwrite, Trigger.dev, Inngest, QStash and Custom API, with replay. Syncs from Fivetran and Airbyte, with Sync now.

  • Files

    Buckets on Supabase, Firebase, Appwrite, PocketBase, Convex, S3-compatible storage, Google Cloud Storage, Vercel Blob, UploadThing and Custom API. Upload, download and delete; download links expire after five minutes.

  • Usage and AI spend

    Sign-ups per day, daily active users from PostHog, Mixpanel, Amplitude, Plausible and Custom API, and Anthropic, Amazon Bedrock, xAI, Together AI, fal, OpenAI and OpenRouter spend split by model, key or project.

  • Emails

    What was sent to a customer through Resend, Postmark, Amazon SES, Mailgun, SendGrid and Loops, with bounces and suppressions you can lift.

  • Infrastructure

    Every app, Worker, database and bucket a project runs, which one uses which, and a map or globe of where they run.

  • Flags and support

    A customer’s feature flags from PostHog, LaunchDarkly and Statsig, and their conversations from Intercom, Plain, Crisp, Help Scout and Zendesk.

  • Audit log

    Every read and change, with who made it. Calls from the assistant and from tokens are logged under their own names.

  • Permissions

    Everyone starts read-only. Owners allow each change person by person. How it works

  • On your phone

    Every page works in a phone’s browser. The main pages move to tabs along the bottom, the rest sit under More and wide tables scroll sideways.

  • Branding

    Put your own name and logo on the dashboard and lock a theme. Built in: Onyx, Graphite, Midnight, Paper, Terminal, Ledger, Carbon, Boardroom and Swiss. Themes and whitelabel

Your admin panel, without the sprint it would take to build one.

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