Making risky changes safely
See the blast radius, the tests and the way back before a change is made.
Most of this page describes planned work. Only design pressure-testing works today.
The problem
Teams make changes without a clear view of blast radius or rollback paths. Larger companies also need private deployment, admin controls and compliance reporting before they can adopt a tool like this.
What works today
In our internal prototype, inside our team only. It is not available to customers yet.
- Design pressure-testing reviews a proposed design for failure modes and scaling limits.
- It returns review notes listing risks and open questions.
What is planned
Targets, counted from the plan's first month, February 2027. They may move.
- The safe-change workflow: blast-radius checks, suggested tests and rollback steps before a risky edit, as a change plan for your approvalNo target yet
- An audit log of every stepNo target yet
- A self-hosted option for enterprise pilotsQ1 2028
- Private deployment, admin controls and compliance reportingFrom Q3 2028
Example: changing a retry policy
Invented example of a planned feature. The team and the services are made up.
An invented team wants to change how its payment client retries. In the planned workflow, Belay would list the services that call the client, suggest tests that cover them, and write out the rollback steps. Then it would wait for approval.
We are looking for design partners
5 to 8 engineering teams that work on large or legacy codebases.