Baseboard for shipping
Ship, check the result and roll back from one page
Deployments brings recent deploys from every host together with the commit each one shipped, CI status on the default branch and open pull requests. Source control is only read, to explain each deploy.
The questions it answers
- “What’s in this deploy?”
- Each deploy shows the commit it shipped. For any deploy you can see which commits making it live would add or undo.
- “Is main green?”
- CI status on the default branch is on the page, with open pull requests and the latest commit.
- “Did the release break anything?”
- The Release day template puts deploys beside uptime, with new errors, failed jobs and error logs underneath.
- “Can an agent check for me?”
- Give it an access token with the Read scope and connect it over MCP. It can only change things if the token has the Change scope and its member is allowed to.
Templates to start from
All templatesRelease day
Deploys beside uptime, then what broke: new errors, failed jobs and error logs.
Code review
Open pull requests and recent commits side by side, with deploys underneath.
Shipping
What is ready to merge, a narrow list of what just landed, and production deploys.
Launch week
A week of sign-ups and active users next to new errors, then production deploys and uptime.
Read next
- Letting an AI agent near productionWhy handing an agent your Stripe key is a bad trade, and what scoped tokens do instead.
- Should you build your admin panel with AI?A coding agent will write the first version in an afternoon. Here’s where the time goes after that, and when building it is the right call.
- Guide: Agents and the CLIAccess tokens, MCP, the CLI and pages as code.
Connect your providers once, and every team has its pages.
Start free with one project and three connections. It reads every page and changes nothing until an owner allows it.