01 Architecture
Runtime Architecture
The whole system at a glance: who calls the API, what the API trusts, and where the data actually lives.
Ten components and one obvious path. An operator in a browser and a customer server both resolve identity through the same dependency, the API hands the request to the snapshot service, and the decision is made by a pure evaluator. The two data stores sit outside the control plane, and the Redis cache sits inside a boundary with no authentication at all.
What to look for
- Follow the green rail left to right: it is the read path a customer server walks on every check.
- Switch to the Trust levels view to compare what a Bearer JWT and an SDK key are each allowed to do.
- The four dashed boxes are the trust boundaries. Render Key Value is the interesting one.