Operate
How a live App is watched, fixed and supported, from errors tied to the build that caused them to support inside the App.
A live App is watched, fixed and supported by the Startup's agents, around the clock. The founder sees what broke, what it cost and what was done, without carrying a pager.
Watch
Monitoring captures every error, log and trace, checks uptime and scheduled jobs, and ties each failure to the Version that caused it. A spike in failed Actions after a publish points at that publish.
The fix is usually a rollback: Version.deploy on the last good Version, one step, no record touched. The App lifecycle covers it.
Tell customers
When a check fails, Status pages opens an Incident and posts it at leaseline.app/. Subscribers get each update until it resolves.
| Verb | What it records |
|---|---|
Incident.open | Detection, each Interface it touches, and its severity |
Incident.acknowledge | Who is on it |
Incident.resolve | The time it ended, and the postmortem |
An Incident that touches a plan with an uptime promise counts against that promise, and the credit lands on the next Invoice.
Support inside the App
A question asked in the App opens a Conversation with the Customer's records attached, so nobody asks which one. The Success Manager agent answers most; the rest escalate to a person with the history in hand.
The ask control records each feature request as Evidence with the asker attached, so the next build is chosen from what Customers asked for.
Next
Your back office covers the screens the Startup's own team works in.