Start a project

Case study

StackPilot

Heroku’s own tools assume you are at a laptop, so a failed deploy or a crashed dyno waits until you get back to one. StackPilot puts fleet health, alerts and the fix on the phone in your pocket.

Client
In-house product
Year
2025
Platforms
iOS, Android, web
Our role
Design and engineering
Status
Pre-launch, product page
StackPilot web page: the headline See the signals, skip the surprises, beside a Today’s Ops summary
The public web pages.
StackPilot Ops screen: 4 apps need you, with the apps that need attention listed first
StackPilot Apps screen: eight apps, each with health, provider, spend and traffic
StackPilot app detail: release v47 failed, with a Rollback ready card naming v46 as the last good release
StackPilot Alerts: weekend mode on, with critical, warning and info groups
  1. Opens on the apps that need you, not on a list of everything.
  2. One row per app carries health, provider, spend and traffic, so the list doubles as a status board.
  3. Rollback sits beside the failed release and names the last good one.
  4. Weekend mode: criticals interrupt, warnings wait until Monday.
StackPilot for iOS and Android, current buildScreens at 2x

The problem

Heroku’s tooling is built for the desktop and the command line. When a dyno crashes, a deploy fails or an app starts throwing errors, you find out late and fix it later, because both need a laptop.

There was no good phone-native way to watch app health, get told the moment something changes, or restart a dyno from wherever you are.

What we built

A phone-first companion that talks to the Heroku Platform API: real-time status, push alerts when a dyno changes state, logs, and dyno control. The screens are organised around what needs attention now, not around the provider’s own menus.

StackPilot Ship Log: invoice-bot v47 failed with a migration error and a Roll back to v46 button, then this week’s deploys
StackPilot Cost screen: $392 projected against a $300 budget, with two cost leaks flagged

A failed release sits at the top of the log with its error and a one-tap rollback.

Spend is projected against the monthly budget. Apps that cost money on almost no traffic are flagged as leaks.

Results

StackPilot has not launched, so there are no usage numbers to report yet. They will appear here, with dates, after launch.

Verified
Against the running code on

Building something like this?