Skip to main content
A worked example

Describe something. See what a reviewer would see.

This is an illustration, not the product — nothing here connects to a cloud account and nothing is created, changed or billed. What it shows is the shape of what your reviewer gets: a specific change, measured against your constraints, sitting still until a person decides.

Your request

Plain language. No vendor tooling, no module names.

A proposal that would exceed this is refused before anyone reviews it.

Nothing requested yetIllustration only

Describe something on the left and this panel will show what a reviewer on your team would be looking at — what it creates, what it costs, what it puts at risk, and the fact that it is going nowhere until someone approves it.

No cloud account is connected to this page.

What this is showing you

The point is the pause.

Anything can generate an infrastructure change. The part that matters is what happens between generating it and it becoming real.

01

It is specific

Not a description of roughly what will happen. The thing your reviewer reads is the thing that would run.

02

It is already checked

Your ceilings and permitted regions were applied before it reached a person. Reviewing is a decision, not an investigation.

03

It is waiting

It stays exactly here until a named person approves it — or, where your admin has turned it on, an auto-approval rule they wrote for plans that only add new resources. It is not a formality to skip in a hurry.

Now try it for real.

The sandbox runs this loop end to end against a simulated AWS: a priced quote, the change, a real approval, the apply and the check afterwards.