baseboard

Templates

Pages ready for release day, incidents and growth

A project’s pages are built from 101 kinds of block, in rows of one to 3. A template is a starting layout: pick one when you add a page, then add, move or resize blocks. Each block works across every connection in the project unless you scope it.

Engineering

  • OpsFeatured

    Server map, recent deploys and new errors since release, for the project.

    3 blocks

  • Release dayFeatured

    Deploys beside uptime, then what broke: new errors, failed jobs and error logs.

    5 blocks

  • Error triage

    Unresolved errors by level and every issue by state, over the noisiest errors to fix first.

    3 blocks

  • Delivery

    How often you deploy and how each host is doing, what is live and what failed, then app store submissions and failed builds.

    6 blocks

  • Code flow

    Pull requests nobody has touched for a while beside who has been committing.

    2 blocks

  • Code review

    Open pull requests and recent commits side by side, with deploys underneath.

    3 blocks

  • Shipping

    What is ready to merge, a narrow list of what just landed, and production deploys.

    3 blocks

  • App release

    App builds and store submissions beside web deploys, then the errors and uptime that follow a release.

    4 blocks

  • Ship rhythm

    A calendar of how often the team commits and deploys, over the commits and deploys themselves.

    3 blocks

  • Service check

    Only the connections that need a look, then job runs beside syncs with problems, over the warning logs.

    4 blocks

  • Everything

    One of every block, to see what the project has connected.

    14 blocks

  • Deployments

    What is live and what came before it, with the commits each deploy changes, then the app builds leading up to them.

    2 blocks

  • Logs

    The newest lines from every log store, at every level, with a text search.

    1 block

Backend

  • Backend as a serviceFeatured

    One console for the whole backend: the database with SQL, users, file storage, edge deploys and scheduled jobs, then mail, errors, AI spend and logs.

    13 blocks

  • Job health

    The share of background runs that succeed and runs per day, then which tasks fail most and how fresh each data sync is.

    4 blocks

  • Data desk

    Your own SQL as a figure, a chart and a table, with the newest uploads to storage.

    4 blocks

  • Database

    The tables and SQL across the top, then the syncs and jobs that write to them and the database errors in the logs.

    4 blocks

  • Sign-in

    Sign-ups and active users, everyone with an account, and the sign-in and welcome mail sent to them.

    4 blocks

  • Edge

    Where every host and database runs on a globe, production deploys beside each monitor, and the warnings they log.

    4 blocks

  • Data

    Browse your app's databases: their tables, cell edits, new rows and SQL.

    1 block

  • Files

    Browse, upload, download and delete the files your app stores.

    1 block

Operations

  • Incident roomFeatured

    Everything for an outage on one page: monitors, new errors, error logs and what shipped.

    5 blocks

  • Reliability

    Monitors down and response times, incidents beside the noisiest services, and log lines per hour by level.

    5 blocks

  • Mail room

    How each email provider is doing and how the newest mail went, over the mail coming in.

    3 blocks

  • Team board

    A countdown, world clocks and who is on the project, notes and links, recent alerts and connections, and an embedded page and image.

    9 blocks

  • On call

    Three narrow columns (uptime, new errors, failed jobs) over the warning logs.

    4 blocks

  • Status wall

    The server map with uptime beside it, for a screen on the wall.

    2 blocks

  • Data pipelines

    Every sync across the top, then job runs and error logs.

    3 blocks

  • Background work

    A wide list of every job run, with syncs that need attention beside it.

    2 blocks

  • Footprint

    Where every host, database and bucket runs on a world map, with each monitor and open incident beneath.

    2 blocks

  • Status board

    One big light beside every monitor, then only the connections that need attention. For a screen across the room.

    3 blocks

  • Messaging

    Every email your app sent with whether it arrived, and the failed background jobs that might have stopped one.

    3 blocks

  • Health

    What's down and what's breaking: every monitor and open incident, then every unresolved error with the new ones marked.

    2 blocks

  • Emails

    Everything your app sent, newest first, with whether it was delivered, and the mail received at your inbound addresses.

    1 block

  • Jobs

    Every recent background job run, with replay, and the data syncs between your systems, with Sync now.

    2 blocks

Product

  • GrowthFeatured

    Sign-ups and active users over the last month, with revenue and subscriptions beside them.

    3 blocks

  • SpendFeatured

    Recurring revenue and subscriptions beside what the AI providers cost per day.

    2 blocks

  • Morning checkFeatured

    One light for whether anything's wrong, the week's sign-ups and recurring revenue as big numbers, then new errors and what went live.

    5 blocks

  • Subscriptions

    Recurring revenue by currency and state, the plan mix, then trials ending, cancellations, failed payments and the customers who pay most.

    10 blocks

  • User base

    How many users there are and who has gone quiet, the newest sign-ups and sign-ins, banned users and the organisations they form.

    7 blocks

  • AI costs

    AI spend against a monthly budget, prompt cache hits and low API balances, over tokens per day.

    4 blocks

  • Launch week

    A week of sign-ups and active users next to new errors, then production deploys and uptime.

    5 blocks

  • Product health

    Active users wide with uptime beside them, and new errors across the bottom.

    3 blocks

  • Weekly review

    The week's sign-ups and active users, what changed in the code and what shipped.

    4 blocks

  • Support desk

    Every user with their plan and status to search, then the mail your app sent them and the errors they might be hitting.

    3 blocks

  • Revenue review

    Recurring revenue and sign-ups as big numbers beside revenue at risk, then which plans pay and the one-time purchases.

    5 blocks

  • Cost watch

    What the AI providers cost per day beside the credits left on prepaid APIs, with active users to weigh them against.

    4 blocks

  • Users

    Everyone who signed up or paid, joined by email across your sign-in and billing providers, and their organisations.

    1 block

  • Billing

    Recurring revenue and the payments that need attention, plans, one-time purchases and every billing customer.

    4 blocks

  • Usage

    Sign-ups and active users per day, what the AI providers cost, and the credits left on prepaid APIs.

    4 blocks

Copied, not linked

Picking a template copies its blocks into a new page. Change the page however you like; it won’t move if the template changes later.

Or write your own

Pages are JSON, so they can live in your repo and be applied from CI or by an agent with an access token. See the developer tools.

Start with Overview, add pages as you need them.

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