Mock demo for engineering and IT teams
Turn the runbook nobody reads into buttons.
Deploys, cleanups and health checks usually live in a wiki and in one person’s head. This demo shows them as a shared deck of buttons that run on the right machine and leave a record.
Try three buttons
- Diagnostics
Check disk and memory
Read-only health snapshot.
on
worker-04 - MaintenanceAsks first
Clear build cache
Scoped to one job folder. Asks first.
on
build-vm-02 - Deploy
Deploy web to staging
Build, push and restart the web service on staging.
on
stage-eu-01
Press a button. Output appears here.
The same task, two ways
From the wiki
- Open the wiki page (last edited 14 months ago)
- Find the right machine and a shell on it
- Copy the command, swap in the right values
- Hope nobody else is running something
From the deck
- Press the button
- It runs on the right machine with the right values
- Risky ones ask first
- Who, where and when are recorded
What changes for the team
Buttons, not pages
Each routine task is one button with a plain name, a target machine and a command anyone can read.
Ask before the risky ones
Mark a button as needing confirmation and it shows exactly what will run, and where, before it does.
Scheduled the same way
Any button can also run on a schedule, with the same record of what happened.