deixic
Log inRequest a demo

Platform

Re-check your controls on a schedule.

Dex, waiting in the queue

Set a routine to re-run a control check every night, or when a connected tool sends an event. A failing control goes to a fix within your policy or to a named approver, and every run has a step, cost, and runtime limit.

Request early access

  1. What Dex should doReview the pipeline and flag deals that slipped
  2. Routine timingEvery Monday at 09:00 UTC
  3. Connector eventsAlso runs when a new escalation arrives in Zendesk
  4. Before taking actionDex will ask before taking action.
  5. Limits per runSteps, tool calls, tokens, cost, and runtime
  6. Where Dex posts updatesThe revenue channel in Slack
A routine: what to do, when it runs, and the limits on every run.

  • On a schedule

    Every hour, every morning, the first of the month, or any schedule you write.

  • When something happens

    A new ticket, a calendar change, or a pull request comment starts Dex as the event arrives.

  • Asks before it acts

    A routine stops and waits for approval before it changes anything that needs a named approver.

  • A budget on every run

    Set how long a run can take and what it can spend.

  • Monday pipeline reviews, too

    Routines also run the recurring business work, such as the nightly spend check.

The Routines page in Deixic, showing a daily SOC 2 drift check with its task, approval setting, and per-run limits.
A daily SOC 2 drift check keeps its approval rule and per-run limits.

Hand off the work that repeats

How it works in detail

Shared by every surface.

Use it with Dex on every surface, alongside company context that existing agents read over MCP.