baseboard

Customise

Build the pages your team checks first

Every project page, Overview included, is rows of blocks: deploys, revenue, uptime, logs, a world map. Workspace owners pick the blocks, how wide each one is, which connections it reads and how it looks. Themes and your own name and logo go on top.

Edit page

Drag blocks where you want them

Turn on Edit page and every block gets a handle. Drop one beside another to share a row, or above or below to give it a row of its own.

  • Start from a template or a blank page, then add blocks from the catalogue
  • Up to 3 blocks a row. They share its width, so rows are always full and nobody sets pixel sizes
  • Each block is Small, Medium or Large, or Auto to keep its type’s own width
  • Move up and Move down buttons for keyboards, and a remove button on each block
  • Rename a page and give it an icon or a country flag for the sidebar

Block settings

Point each block at the right connections

A new block reads every connection in the project. Its settings narrow it to some groups or some connections, so one page can show production deploys beside staging errors.

  • Groups are labels owners give connections, such as Production, Staging or EU
  • A block scoped to a group picks up connections added to that group later
  • Options depend on the block: how many rows, which log levels, map or globe, days of history
  • Options left alone keep their defaults, so a block works the moment it’s added

The catalogue

101 blocks to build from

Each block reads from whichever connections in its scope can fill it. One with nothing to read asks you to connect a service.

  • Connection health

    A card per connection with the health of each part it offers, problems first.

    Works with any connection. Large by default. Options: show totals above the cards; only connections that need attention.

  • Status beacon

    One big light for everything in scope: green when all is well, amber or red with what needs a look.

    Works with any connection. Small by default. Options: pulse the light; list what needs attention.

  • Server map

    Connections as cards, a column per project and banded by group, each with its live status.

    Works with any connection. Large by default. Options: show; band by.

  • Deployment map

    Where every host, database and bucket in scope runs, as pins on a world map or globe coloured by status.

    Works with any connection. Large by default. Options: show as; let people switch between map and globe; pins show; draw the links made on the infrastructure page; lines are drawn as; keep moving after a drag; turn the globe by itself.

  • Uptime status

    A status-page view of every monitor: 30 days of daily bars, uptime percentages and response times.

    Needs uptime. Medium by default. Options: show response times; show open incidents.

  • Big number

    One figure, large, with a sparkline and its change on the period before.

    Works with any connection. Small by default. Options: figure; days in a period (sign-ups, active users, ai spend).

  • Custom metric

    A figure your own app counts (orders, queue depth, API calls), from every Custom API in scope that offers it: one big number with its change, or bars per day.

    Needs metrics. Small by default. Options: metric key (empty for the first one); show; days to show.

  • Ship heatmap

    Commits and deploys per day as a calendar of squares, darker on busier days.

    Works with any connection. Medium by default. Options: weeks to show; count.

  • Credit gauges

    A dial for every API allowance and balance in scope, filling toward its limit.

    Needs api credits. Medium by default. Options: only dials running low.

  • Recent deploys

    The latest deploys from every host in scope, newest first, with the commits each one changes and Make live where the host allows it.

    Needs hosting. Medium by default. Options: how many to show; production only.

  • App builds

    Builds and store submissions from every build service in scope, newest first, with retry.

    Needs app builds. Medium by default. Options: how many to show.

  • Errors

    Unresolved error issues, with resolve and ignore. New ones are those first seen since the project's live deploy, or in the last day where there's no host.

    Needs error tracking. Medium by default. Options: only errors new since the live deploy.

  • Job runs

    Recent background job runs from every job runner in scope, newest first, with replay where the runner allows it.

    Needs background jobs. Medium by default. Options: start on failed runs only; how many to show.

  • Data syncs

    Pipelines between systems with their status and last run, problems first, with Sync now where the provider allows it.

    Needs data syncs. Medium by default. Options: only failed or paused syncs.

  • Uptime

    Every monitor in scope, down first, and any incident still open.

    Needs uptime. Small by default.

  • Recent logs

    The newest log lines from every log store in scope, filtered by level, with a text search.

    Needs logs. Large by default. Options: show; how many to show.

  • Open pull requests

    Pull requests waiting in every repository in scope, most recently updated first.

    Needs source control. Medium by default. Options: include drafts; how many to show.

  • Recent commits

    The latest commits on each repository's default branch, newest first.

    Needs source control. Medium by default. Options: how many to show.

  • Sign-ups

    New users per day, added up across every sign-in provider in scope.

    Needs sign-in. Medium by default. Options: days to show.

  • Active users

    Distinct active people per day from every analytics provider in scope.

    Needs product analytics. Medium by default. Options: days to show.

  • Revenue and subscriptions

    Monthly recurring revenue and subscription counts from every billing provider in scope, with the payments that need attention.

    Needs billing. Small by default. Options: subscriptions needing attention to list.

  • Plans

    Live subscriptions and monthly recurring revenue per plan, across every billing provider in scope.

    Needs billing. Small by default.

  • One-time purchases

    Revenue per product from one-time purchases, net of refunds, then the newest purchases.

    Needs billing. Medium by default. Options: recent purchases to list.

  • Billing customers

    Every billing customer with their plan, state and monthly revenue, marked where they can sign in. Each opens their page on Users.

    Needs billing. Large by default. Options: how many to show.

  • AI spend

    What the AI providers in scope cost per day, and where it went by model, API key or project.

    Needs ai spend. Medium by default. Options: days to show; split by; how many to list.

  • Emails

    The newest mail every email provider in scope sent, with whether it was delivered, or received.

    Needs email delivery. Large by default. Options: how many to show.

  • Users

    Everyone who signed up or paid, joined by email across sign-in and billing, and the organisations they belong to. Each opens their own page.

    Needs sign-in or billing. Large by default. Options: show totals above the list.

  • Accounts

    The person's sign-in accounts, with ban and unban, and the organisations they belong to.

    Works with any connection. Small by default.

  • Billing

    The person's billing customers and their invoices, with refunds.

    Needs billing. Small by default.

  • Subscriptions

    The person's subscriptions, with cancel now or at the period's end.

    Needs billing. Small by default.

  • Purchases

    The person's one-time purchases, with refunds.

    Needs billing. Small by default.

  • Across your tools

    What every other connection knows about the person by their email: errors, job runs, logs, support, CRM, flags and mail.

    Works with any connection. Large by default.

  • Organisation

    The organisation as its sign-in provider has it, and the billing that looks like theirs.

    Works with any connection. Small by default.

  • Members

    Who is in the organisation, with their role. Each opens their own page.

    Works with any connection. Small by default.

  • Database browser

    Browse the tables of every database in scope, edit cells and add rows, and run SQL, where the database and your permissions allow.

    Needs databases. Large by default.

  • File browser

    Browse, upload, download and delete the files every store in scope holds.

    Needs file storage. Large by default.

  • Recurring revenue

    Monthly and annual recurring revenue across every billing provider in scope, one figure per currency.

    Needs billing. Small by default.

  • Plan mix

    Live subscriptions per plan as a ring, with each plan’s share.

    Needs billing. Small by default. Options: share of.

  • Trials ending

    Subscriptions on trial, the soonest to end first.

    Needs billing. Small by default. Options: how many to show.

  • Cancellations

    Subscriptions set to cancel at the end of their period, the soonest first, with the revenue each takes.

    Needs billing. Small by default. Options: how many to show.

  • Failed payments

    Subscriptions whose last payment failed (past due or unpaid), with what each is worth a month.

    Needs billing. Small by default. Options: how many to show.

  • New billing customers

    The billing customers created most recently, newest first, across every billing provider in scope.

    Needs billing. Medium by default. Options: how many to show.

  • Ended subscriptions

    Subscriptions that have been cancelled or have lapsed, with the plan and price they were on.

    Needs billing. Small by default. Options: how many to show.

  • Top customers

    Customers ranked by what they pay a month, as bars. Each opens their own page.

    Needs billing. Medium by default. Options: how many to show.

  • Revenue by currency

    Monthly recurring revenue and one-time purchase revenue in each currency you charge in.

    Needs billing. Small by default.

  • Subscription states

    How many subscriptions are active, trialing, past due, cancelled and so on, as bars.

    Needs billing. Small by default.

  • User count

    How many users every sign-in provider in scope has, and how many signed in recently.

    Needs sign-in. Small by default. Options: count as recently signed in within this many days.

  • Newest users

    The people who signed up most recently, newest first.

    Needs sign-in. Medium by default. Options: how many to show.

  • Banned users

    Everyone banned in a sign-in provider in scope. Each opens their own page, where they can be unbanned.

    Needs sign-in. Small by default. Options: how many to show.

  • Recent sign-ins

    The people who signed in most recently, newest first.

    Needs sign-in. Medium by default. Options: how many to show.

  • Dormant users

    People who have not signed in for a while, longest away first, with how many there are.

    Needs sign-in. Small by default. Options: away for at least this many days; how many to show.

  • Organisations

    The organisations in every sign-in provider in scope, newest first. Each opens its own page.

    Needs sign-in. Medium by default. Options: how many to show.

  • Largest organisations

    Organisations ranked by how many members they have, as bars.

    Needs sign-in. Small by default. Options: how many to show.

  • Noisiest errors

    Unresolved error issues ranked by how many events each has had.

    Needs error tracking. Medium by default. Options: how many to show.

  • Errors by level

    Unresolved issues split by level (fatal, error, warning, info), as bars.

    Needs error tracking. Small by default.

  • Errors by state

    How many issues are unresolved, resolved and ignored, as bars.

    Needs error tracking. Small by default.

  • Deploy cadence

    Deploys per day across every host in scope, failed ones marked apart.

    Needs hosting. Medium by default. Options: days to show.

  • Failed deploys

    Deploys that errored or were cancelled, newest first, with the commit each was built from.

    Needs hosting. Medium by default. Options: how many to show.

  • Live now

    What each host in scope is serving right now, per target, with its branch and commit.

    Needs hosting. Medium by default.

  • Host status

    How each host in scope is doing, with what it reports about the running app (machines started, crashes).

    Needs hosting. Small by default.

  • Store submissions

    App Store and Google Play submissions, newest first, with where each stands.

    Needs app builds. Medium by default. Options: how many to show.

  • Failed builds

    App builds that failed, newest first, with the error and retry where the service allows it.

    Needs app builds. Medium by default. Options: how many to show.

  • Job success rate

    The share of recent background job runs that finished without failing.

    Needs background jobs. Small by default.

  • Runs by task

    Recent runs per background task, with how many of each failed, worst first.

    Needs background jobs. Medium by default. Options: how many to show.

  • Job runs per day

    Recent background job runs per day, failed ones marked apart.

    Needs background jobs. Medium by default. Options: days to show.

  • Sync freshness

    How long since each data sync last succeeded, the stalest first.

    Needs data syncs. Medium by default. Options: mark as stale after this many hours.

  • Response times

    Recent response times for every monitor in scope as lines, with each one’s average.

    Needs uptime. Medium by default.

  • Incidents

    Uptime incidents, open ones first, with how long each lasted.

    Needs uptime. Medium by default. Options: only open incidents; how many to show.

  • Monitors down

    How many monitors are down or degraded, and which.

    Needs uptime. Small by default.

  • Log levels

    Recent log lines per hour, split by level, from every log store in scope.

    Needs logs. Medium by default.

  • Noisiest services

    Which services wrote the most recent log lines, and how many were errors.

    Needs logs. Small by default. Options: how many to show.

  • Stale pull requests

    Open pull requests nobody has touched for a while, the oldest first.

    Needs source control. Medium by default. Options: untouched for at least this many days; include drafts; how many to show.

  • Commits by author

    Who committed to each default branch recently, as bars.

    Needs source control. Small by default. Options: how many to show.

  • AI tokens

    Input and output tokens per day across every AI provider in scope.

    Needs ai spend. Medium by default. Options: days to show.

  • AI budget

    AI spend so far this month against a monthly budget, with where the month is heading.

    Needs ai spend. Small by default. Options: monthly budget in us dollars.

  • Prompt cache hits

    The share of input tokens served from the prompt cache, overall and per model.

    Needs ai spend. Small by default. Options: days to show.

  • Low balances

    API accounts below their low mark, near a plan limit, on trial or suspended, with where to top up.

    Needs api credits. Small by default.

  • Mail health

    How each email provider in scope is doing: sending status, bounce and complaint rates where it reports them.

    Needs email delivery. Small by default.

  • Inbound mail

    The newest mail received at your inbound addresses, newest first.

    Needs email delivery. Medium by default. Options: how many to show.

  • Mail outcomes

    How the newest sent mail went: delivered, opened, bounced and so on, as bars.

    Needs email delivery. Small by default.

  • Recent uploads

    The newest files at the top of a bucket, with their sizes.

    Needs file storage. Medium by default. Options: bucket (empty for the first one); how many to show.

  • SQL table

    The rows a read-only SQL query returns, from each database in scope that allows queries.

    Needs databases. Large by default. Options: sql; how many to show.

  • SQL chart

    A read-only SQL query drawn as bars: the first column labels each bar, the second gives its size.

    Needs databases. Medium by default. Options: sql (a label column, then a number column); how many to show.

  • SQL number

    One figure, large: the first cell a read-only SQL query returns.

    Needs databases. Small by default. Options: label; sql (the first cell is shown).

  • Their errors

    Error issues the person hit, found by the person’s email.

    Needs error tracking. Small by default.

  • Their job runs

    Background job runs for the person, found by the person’s email.

    Needs background jobs. Small by default.

  • Their conversations

    Support conversations with the person, found by the person’s email.

    Needs support. Small by default.

  • Their CRM record

    The person’s CRM record: company, stage and owner, found by the person’s email.

    Needs crm. Small by default.

  • Their feature flags

    The feature flags the person gets, with switches where the provider allows it, found by the person’s email.

    Needs feature flags. Small by default.

  • Their mail

    Mail sent to the person and any suppressions on their address, found by the person’s email.

    Needs email delivery. Small by default.

  • Organisation revenue

    What the organisation pays: its monthly recurring revenue, subscriptions and one-time purchases.

    Needs billing. Small by default.

  • Organisation errors

    Error issues the organisation’s members hit, the most events first.

    Needs error tracking. Medium by default. Options: members to look up.

  • Note

    Your own words on the page, with **bold**, *italics*, `code` and links.

    Works with any connection. Small by default. Options: text.

  • Links

    A list of links, one per line: a label, then the address.

    Works with any connection. Small by default. Options: links (one per line: label, then address).

  • Embed

    Another web page inside this one, such as a status page or a shared chart.

    Works with any connection. Medium by default. Options: page address (https); height in pixels.

  • Image

    A picture from an address, such as a diagram or a logo.

    Works with any connection. Small by default. Options: image address (https); what it shows, for screen readers; fit.

  • World clocks

    The time now in the places your team and customers are.

    Works with any connection. Small by default. Options: time zones, one per line (such as europe/london).

  • Countdown

    Days, hours and minutes to a date, such as a launch or a renewal.

    Works with any connection. Small by default. Options: what happens then; when (yyyy-mm-dd, or yyyy-mm-ddthh:mm).

  • Alerts

    The project’s alerts that fired most recently, open ones first.

    Works with any connection. Medium by default. Options: only open alerts; how many to show.

  • Connections

    Every connection in scope with what it does, grouped by kind of service.

    Works with any connection. Medium by default.

  • Team

    Who can open this project, with their role.

    Works with any connection. Small by default.

Themes

Make a theme in a minute, share it with the workspace

Start from one of 9 built-in themes (Onyx, Graphite, Midnight, Paper, Terminal, Ledger, Carbon, Boardroom and Swiss) or copy one and change it. Try it below.

Colours. Light or dark, a page colour, a foreground for text, icons and lines, and an accent with the text on it. The greys in between, for borders, panels and muted text, are worked out from the page and foreground, and each one can be set by hand.

Type and shape. A font, a density slider from dense to roomy, and corners from square to round.

Contrast checks. The editor warns when text on the accent gets hard to read, and shows the ratio.

Who sees what. Themes an owner saves are shared with everyone. Members pick their own, or get the workspace default.

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

Whitelabel

Your name on the dashboard, not ours

On Pro and Team, owners set the name and logo members see. Useful when the dashboard is something you hand to a client or a support team.

  • Your name in the header and the browser tab
  • Your logo, which doubles as the tab icon
  • Text across the dashboard, and the assistant’s replies, use your name too
  • Lock the default theme so everyone sees the same one
Compare plans

Pages as code

Keep layouts in your repo

A page is a small JSON file: rows of blocks with their size, options and scope. Export a project’s pages, review a change in a pull request and apply it from CI. Groups are matched by name, so one file works in every workspace.

{  "name": "Release day",  "icon": "icon:rocket",  "rows": [    [      { "type": "deploys", "options": { "productionOnly": true } },      { "type": "uptime" }    ],    [{ "type": "newErrors", "groups": ["Production"] }],    [{ "type": "logs", "options": { "minLevel": "error" } }]  ]}

npx baseboard-cli pages export and pages apply read and write them. Agents with an access token can do the same over MCP.

Pages as code in the docs

Start with Overview, then make the pages you’re missing.

Every project opens on Overview, one card per connection with problems first. Edit it, or add a page from a template whenever a team needs its own view.