Your business runs on decisions. But the conditions behind decisions keep changing.

Ex-Grapha shows which decisions need review when a condition changes.

MCP support for Codex and Claude Code

Ex-Grapha desktop app showing a payment provider orchestration graph

A single update can invalidate many prior decisions.

A policy, fact, or technical constraint can change.

Identifying every decision that needs review becomes a separate task.

Without Ex-Grapha

  1. Someone updates the source.
  2. Some decisions get reviewed.
  3. Others remain hidden.

With Ex-Grapha

  1. The new lead time is entered in Ex-Grapha.
  2. Ex-Grapha surfaces every connected decision that needs review.
  3. A human decides whether each one remains valid, or needs revision.

Without visible connections, teams are left to rely on memory.

Ex-Grapha graph view tracing downstream dependencies from Guard Webhook Updates to Report From Internal Ledger

How it works

  1. Map dependencies

    Link each decision to the requirements, assumptions, evidence, and earlier decisions it depends on.

  2. Change

    When a connected fact changes, Ex-Grapha marks the decisions built on it for review.

  3. Review

    Review the affected decisions and update only what needs to change.

Video upload limit is updated. The architecture decisions built on video size constraint now need review.

Show new team members why the project is shaped this way.

Someone joins the team. They can see the decisions, but not the reasons behind them.

With Ex-Grapha, they can start from any decision and trace what shaped it: assumptions, evidence, constraints, and earlier conclusions.

Ex-Grapha system graph showing the dependencies and dependents of Guard Webhook Updates
OpenAI Codex
Claude Code

Native support for OpenAI and Claude through MCP.

Ex-Grapha exposes your active graph through an MCP endpoint and includes setup flows for OpenAI Codex and Claude Code.

AI finds facts,Ex-Grapha reveals consequences.You need both!

  1. 01

    Map

    Ex-Grapha MCP gives AI a dependency map of your business decisions.

  2. 02

    Trace

    Before proposing a change, AI traces the supporting facts, existing constraints, and decisions the proposal would affect.

  3. 03

    Surface

    Conflicts become visible before the recommendation reaches your team.

Ex-Grapha Smarter recommendations and fewer mistakes from your AI.

Without Ex-Grapha

AI Chat Context unavailable

user One customer wants non-bypassable two-step admin transfer. Does it align?

AI model Yes. A non-bypassable two-step admin transfer is a strong security improvement: it reduces account takeover risk, enforces explicit authorization, and creates a clearer audit trail. I would accept the request and treat it as the safer default.

  • Sounds plausible, but misleading
  • Misses lockout recovery

With Ex-Grapha

AI Chat Graph connected

user One customer wants non-bypassable two-step admin transfer. Does it align?

Ex-Grapha MCP ex_grapha_get_graph_snapshot

Ex-Grapha MCPdependency map loaded ✓

AI modelrunbook +--> transfer support +--> transfer lockout x-- transfer

AI modelReject: if the customer is locked out, they cannot initiate the two-step transfer, so customer support has no recovery path.

  • Grounded in the incident runbook
  • Catches the lockout conflict

Built for decisions based on changing information.

Payment Service Architecture
Ex-Grapha graph showing provider APIs connected to downstream webhook architecture decisions.
Client Portfolio Allocation Review
Ex-Grapha graph showing the assumptions and allocation rules behind a client portfolio recommendation

Assumptions change. Their impact should be visible.

Ex-Grapha shows which decisions need review.

Stop carrying every decision in the back of your mind.

Tell us how to reach you. We will get back to you personally.

Prefer to choose a time directly? Open the calendar