deixic
Log inRequest a demo

Your own agents

Ask your own agent who still has production admin.

Connect Claude Code or Codex over MCP and it reads the access, change, and receipt records Deixic keeps for your SOC 2 controls. When its changes are routed through Deixic, the same policy, approvals, and receipts apply.

Request early accessSee the records an agent reads
Example questionWho still has production admin?
Your agent

Claude Code

Signed identity → MCP gatewayAccess granted per agent

Records stay in Deixic

Access
Who holds admin in GitHub, AWS, Okta, and more
Changes
What changed for CC6.2, who approved it, and why
Receipts
Before and after state, read-backs, signed and hash-linked
Authority
Read records; approval before a production change

The second agent receives its own identity and access; prior approvals do not transfer.

Connect your agent, then ask it a question.

Connect over MCP, choose the context and tools, and inspect the first routed request. Tools the agent uses directly remain under their existing controls.

  1. 01 · Connect

    Give Claude Code or Codex an identity.

    Use the MCP gateway over Streamable HTTP with signed identity.

  2. 02 · Ask

    Read the records.

    Ask who still has production admin, or what changed for CC6.2 last quarter.

  3. 03 · Route

    Send its changes through policy.

    A routed change runs within written policy or waits for a named approver, and each change that runs gets a receipt.

See the MCP gatewayAgent identityRecorded spend

The records your agent reads.

The same records the SOC 2 fixes produce, available to any MCP-capable agent you connect.

Access
Who has access to what in systems such as Google Workspace or Microsoft 365, GitHub, AWS or GCP, Okta, Rippling or Gusto, and Slack, among many more.
Changes and approvals
What changed for each control, who approved it, and the reason they gave.
Receipts
Before and after state and read-backs, signed and hash-linked to the previous record.
Policy
Which changes run within written policy and which wait for a named approver.

Delegate work to Dex.

Dex uses company knowledge, reviewed memory, and skills for account briefs, decks, code changes, and recurring work.

Meet DexRecurring tasksView pricing

Before you connect production work

Can Claude Code or Codex change things through Deixic?

Yes. A change routed through Deixic runs within written policy, waits for a named approver with a reason, or goes back to your team as a decision. Each change that runs gets a receipt.

Read about approval boundaries
Do we have to replace our current agent?

No. Connect an MCP-capable agent over Streamable HTTP with signed identity. Deixic checks calls routed through the gateway before using an upstream credential.

Read the connection contract
Which records does the agent read?

Who has access to what, what changed and who approved it, the receipts, and the policy. Other agents read this company context over MCP; Dex and Deixic Code use skills directly.

Read about the company layer
What stays outside Deixic's controls?

Tools the agent uses directly remain under their existing controls. Connecting an agent gives Deixic authority over the calls routed through it.

Trace an action's lifecycle

Connect your own agent to the records.

Request early access