deixic
Log inRequest a demo

SurfacesAvailable

Every fix Dex makes has a receipt here.

Dex, waving hello

The app holds the compliance work from start to finish. Each failing control gets a thread with the changes Dex made, the approvals waiting on a named person, the decisions left to the company, and the read-back check that closed it.

Request early access

One thread for one failing control.

Example thread with demo data. Control CC6.3, production access, is failing.

  1. Ran within policy

    Dex disabled the unused API key on the build account, read the key list back, and confirmed it is gone.

  2. Waiting for approval

    Removing two production admin grants from a departed contractor waits in the queue for Priya Shah, the named approver.

  3. Decision for the company

    Accepting the risk on a legacy service account is outside Dex's authority. It is not run and sits in the thread as a decision.

  4. Closed

    After the approval, Dex removed the grants, read them back, attached the evidence to the test in your compliance platform, and re-ran it. The receipt lists each change, the approver and reason, and the times.

  • Failing controls and where each stands

    Each failing control shows whether Dex is working on it, a change is waiting for approval, a decision is with the company, or the test passes again.

  • Approvals in one queue

    A sensitive change waits for its named approver, who gives a reason. The decision is recorded with the result.

  • The receipt for every fix

    Each receipt keeps the before and after state, who authorized the change, how Dex read it back, and the evidence it attached to the test.

  • Your own agents read the same records

    Claude Code, Codex, and other agents read the company context and records over MCP.

  • Other work, same thread

    Hand Dex any other task the same way. Agent status and month-to-date spend by agent sit in the same app.

A SOC 2 thread in Deixic with a verified required-reviews fix, a named production-access approval, and a company decision still open.
See the fix, the approval, and the company decision in one thread.

From a failing control to a verified fix.

SOC 2 examples with demo data in the Deixic app.

Compliance work showing open tasks, accountable owners, due dates, and findings.
One place for the control work and the decisions still with your company.
Dex explains a failing required-reviews control and the bounded GitHub setting change.
Start with the failing control and the exact setting behind it.
A named production-access approval request for Priya, with two accounts and the readback plan. No change has run.
Sensitive changes wait for a named approver.
A control thread lists the before and after setting, readback evidence, and passing re-test.
Read back the setting, attach evidence, and re-test the control.
Offboarding work lists completed account removals and a service-account owner decision that remains open.
Company decisions remain visible until an accountable person resolves them.

All surfaces.