maki
A deploy console for AWS fleets. One dashboard for your AWS ECS fleet: what’s deployed, deploy history, DORA metrics, CI timelines. Read-only by design.
The origin is a straight line. Years of scaling software at Deliveroo taught Bass what a large fleet needs to stay calm under pressure. At Nory, he kept reaching for a single screen that just showed the whole fleet at once, and there wasn’t one. So he built maki to close that gap and make incident response faster, then opened it up under an MIT licence for anyone else running ECS.
The whole fleet, on one screen
Every ECS service as a card, grouped by app, with a single health bar across the top: what’s stable, what’s deploying, what’s degraded. The one view Bass kept wishing for during an incident.
What changed on production
A live, filterable feed of every deploy across the fleet: commit, author, duration, and result. When something breaks, the first question is always “what just shipped?” This answers it.
The deploy, broken down
Each deploy opens into its CI-to-rollout timeline: GitHub Actions stages, then the ECS rollout, with the full story of who shipped what, when right there.
DORA metrics, per service
Time to deploy, deploy frequency, and rollout median, with a 90-day lead-time trend splitting CI from rollout. The numbers a team needs to know if it’s getting faster, without leaving the console.
One dashboard, your whole fleet.
maki is open under an MIT licence. Browse the source, or say hello if it’s useful to your team.