StrixGovernance
How it worksDemoTry itPricing
Talk to us

Simulator · illustrative · invented data

Click through the governed path.

This simulator uses a simplified detector, not the product's engine, so its results can differ. The demo shows real engine output.

The steps of the governed path

Interactive request path

Simulation payload

Security policy rules

Policy allow · Payload satisfies the selected egress rules.

Open simulator evidence

Ready to simulate a sample request

What actually changes

4 identifiers replaced before anything leaves.

Invented demo data. The model step is simulated: no external model is called and no real patient data is used.

1 · Your workflow sends

Raw request inside your network. Identifiers highlighted.

Claim 2026-04417 for patient Maria Delgado (MRN 00482913, DOB 1958-03-14). Member ID NW-7731902. CPT 93000 was denied as not medically necessary. Draft an appeal for Maria Delgado citing the cardiology notes.
2 · The model sees

De-identified request that crosses the boundary.

Claim 2026-04417 for patient [PATIENT_1] ([MRN_1], [DOB_1]). [MEMBER_ID_1]. CPT 93000 was denied as not medically necessary. Draft an appeal for [PATIENT_1] citing the cardiology notes.
3 · The model answers

Response as returned, still holding placeholders.

Run the simulation to see this step.
4 · You receive

Approved references restored inside your boundary.

Run the simulation to see this step.

Replacement map (held inside the boundary, never sent): [PATIENT_1] = patient · [MRN_1] = mrn · [DOB_1] = dob · [MEMBER_ID_1] = member id

Current step

01

Intercept

Your workflow sends a request through a boundary you control, before it reaches an external model.

1 / 3

Runs you perform here are kept in this browser. See the simulator's evidence.

© 2026 Strix · Governed EgressSecurity ·Privacy ·Terms