BuiltForProd by Nexstella
Production that more than one person can run
Reducing key-person risk means production is defined in code, documented and run through shared processes, so no single absence stops it. BuiltForProd helps write it down, hand it over and, if you want, run it with you.
01 Sound familiar
Sound familiar?
-
Holidays are arranged around one engineer, and when that person is ill the whole company quietly hopes nothing breaks until they are back.
-
Access to the cloud, the domain and the pipelines sits in one person's accounts, and nobody else could say which of them actually matter.
-
Every incident ends the same way: the same engineer fixes it late at night, and the fix lives in their head rather than in a runbook.
The BuiltForProd Standard
Eight questions that show where one person holds the keys
The BuiltForProd Standard sets out eight properties of production. Step through them and ask each question with your key engineer out of the room.
-
Secure
If your key engineer left today, could you remove their access in an hour?
What changes
Access flows from one identity provider, so removing a person is one change, and nobody's personal login holds the company's cloud.
-
Reliable
Does production survive a failure while that engineer is offline?
What changes
Failure handling is designed in rather than done by hand, so common failures recover without someone waking up to nurse them back.
-
Observable
Would anyone else notice the warning signs before customers do?
What changes
Alerts reach more than one person on your team, each with a named owner, and dashboards explain themselves to someone who did not build them.
-
Scalable
Could a colleague handle a traffic spike without calling for help?
What changes
Capacity rules are written in code that anyone on the team can read and adjust through a normal review.
-
Automated
Is deploying a routine step anyone can trigger, or a ritual one person performs?
What changes
Releases run through a pipeline, so shipping depends on a reviewed change and an approval, not on one laptop and its secrets.
-
Recoverable
Does someone other than the key engineer know how to restore the database?
What changes
Restore steps are written down and practiced by more than one person, so recovery does not wait for a single phone to be answered.
-
Compliant
Could you show a customer's reviewer how access and changes are controlled?
What changes
Controls are enforced by the platform and keep records, so explaining them is not one engineer's afternoon spent searching consoles.
-
Operable
Could a new hire run production after reading what you have written down?
What changes
Runbooks, diagrams and a handover session leave production with the team, and BuiltForProd Managed can share the platform work if you want more hands.
02 A typical situation
What this usually looks like
Consider a growing software company with one infrastructure engineer who set up everything from the first server onward. That engineer is talented and tired, has turned down holidays, and is now the reason a large customer's security reviewer keeps asking who else could run the platform.
We would sit with the engineer to write down what exists and why, then move access and deployments onto shared, reviewed processes. Where it helps, BuiltForProd Managed engineers would share the platform work through the team's own access, so the knowledge no longer sits with one person.
03 Book a call
Take production out of one person's head
Book a call with BuiltForProd. List what only one person knows today, and the engineer will suggest where to start sharing it.
BuiltForProd by Nexstella: Nexstella's production engineering brand
Want the full picture? Read Ongoing engineering and platform support.
Also written for you: Managed platform operations , Console-built cloud to code .
Last updated