Cloud incident runbooks for non-enterprise teams

The moment someone realizes they have a problem is when they're trying to troubleshoot something — a DDoS event, a VPC misconfiguration, a compute instance that won't respond — and support takes days while the outage clock runs. They're searching documentation, finding nothing specific, and realizing the vendor's own support team 'doesn't adequately understand or address questions.'

This gap persists because cloud vendors write documentation for their own architecture, not for failure scenarios in real-world configurations. The engineers who know how to actually debug these situations are either inside the vendor (where writing runbooks isn't their job) or scattered across individual companies who solved it once and never wrote it down. There's no structural mechanism to aggregate that knowledge into something actionable.

When users say support 'cannot log into my files and fix them,' they're describing a problem that a good runbook partially solves — not by replacing human help, but by letting the engineer self-diagnose and act before support ever responds. When they say they 'need to contact the help desk to find some tool or setting,' that's a documentation failure that a well-structured, searchable runbook library directly addresses.

This is a business because the specific failure scenarios recur across thousands of companies running similar architectures. A DDoS response runbook for Akamai Cloud is useful the first time and every time after — and as infrastructure evolves, runbooks need maintenance, which creates ongoing subscription value. The buyer is an engineering manager or VP of Engineering who has experienced an incident where the team was stuck for hours doing something that should have taken 20 minutes.

What to build

Build a searchable, version-controlled runbook library covering common failure and configuration scenarios for Akamai Cloud, Alibaba ECS, and Alibaba VPC — written by practicing IaaS engineers, reviewed for accuracy, and structured as step-by-step decision trees that a mid-level engineer can follow without vendor support.

Where to start

Launch with DDoS response and VPC troubleshooting runbooks for Akamai Cloud specifically — the complaint about support failing during DDoS attacks is explicit and urgent, the scenario is well-defined, and the stakes are high enough that engineering managers will pay immediately if the runbook demonstrably works.

The hard part

Keeping runbooks accurate as cloud providers update their interfaces and APIs — a runbook that references a UI element that moved three months ago actively harms the user during an incident, so you need a systematic update process before you have revenue to fund it.

How it makes money

Annual subscription per company, priced by team size — flat access to the full library with a higher tier that includes community review of the company's own custom runbooks.