ArchTruth
Sign inTry it free

Built for ServiceNow estates · read-only by design

Diagrams That Stay True to the CMDB — and Generate the Change Package

Stop redrawing what the CMDB already knows. ArchTruth generates the diagram from the records, you design what comes next as a layer over what exists, and the change request package and decision record fall out of the diff. Your coding agents keep all of it current — your instance stays read-only.

Try the playgroundBecome a design partner
  • No credit card
  • Never writes to your instance
  • Everything exports as plain text
archtruth.app/app/order-management · Q4 target · comparing
ArchTruth workbench: the DSL on the left, the canvas comparing the Q4 target layer with the current state, and the change list on the right
Screenshot of the ArchTruth workbench

  • < 15 s

    from CMDB scope to a bound diagram

  • 0

    writes to your ServiceNow instance

  • 100 %

    of generated nodes carry a record id

  • 412

    what an agent gets when it edits stale — never a clobber

01 · Product

Diagrams Nobody Has to Redraw

02 · How It Works

From CMDB Scope to Approved Change

  1. 01Step

    Connect and Pick a Scope

    OAuth to your instance, read-only. Search a business application or service; we walk cmdb_rel_ci to the depth you choose.

    • PKCE OAuth, tokens in a vault
    • Depth-bounded traversal
    • CSDM family grouping

  2. 02Step

    Edit as Canvas or Code

    The diagram is a readable DSL. Drag on the canvas or type — both edit the same text, and untouched lines never change.

    • Byte-stable comments and order
    • AI generate and AI edit
    • Conditional formatting from CMDB fields

  3. 03Step

    Design the Future as a Layer

    Add, remove, rewire on a layer over the current state. Compare shows exactly what moved, with the sys_ids behind it.

    • Change set with CI references
    • CR package: before, after, changes, description
    • ADRs tied to the layer

  4. 04Step

    Let Agents Keep It Current

    Claude Code and CI call the same typed edits through REST and MCP, with If-Match safety and an attributed audit trail.

    • Org-scoped API keys
    • 8 MCP tools
    • Every write attributed
Workspace overview with counts of diagrams, docs and decisions, this month's AI usage, the file list and the create cards
One workspace per team. Diagrams, design docs and decision records side by side, with the AI allowance in view.
Account-level decision register listing every ADR across workspaces with status, the diagram and layer it changed, approvals and dates
One register per account. Every decision across every workspace — status, the change it justified, who approved it — exportable as CSV.

03 · Agents

Your Coding Agent Maintains the Diagram

Plenty of tools speak MCP now; almost none make the write safe. Connect Claude Code with one line — it reads the DSL, proposes typed edits, and commits with If-Match, so a stale revision gets a 412 instead of silently overwriting an architect's work. Every write lands as a version attributed to the key.

  • list_diagrams · get_diagram · search_diagrams
  • patch_diagram with typed ops (add, remove, set, move, layer)
  • render_diagram as SVG · validate_dsl before saving
$ claude mcp add --transport http archtruth \
    https://archtruth.app/api/mcp \
    --header "Authorization: Bearer as_live_…"

> add a cache service called Redis between
  Orders and the orders DB in "Order Management — current"

  get_diagram    revision 7
  patch_diagram  addNode cache redis "Redis"
                 addEdge app.orders -> infra.redis
  ✓ revision 8 · version 12 · attributed to key claude-code

04 · Why ArchTruth

You Already Have Dependency Views. This Is Different.

Dependency Views and EA Workspace are good at showing what the CMDB knows — inside the platform. Diagram tools are good at drawing — disconnected from it. ArchTruth is built for the work that happens around a change: a diffable source of truth your agents can edit safely, and a CR package and decision record that write themselves from the diff.

Capability comparison: native ServiceNow views, general diagram tools, and ArchTruth
CapabilityNative views & EA WorkspaceServiceNow-native modelling appsVisio · Lucid · draw.ioArchTruth
Reflects live CMDB recordsInside the platformYes — built on CSDMManual copy, drifts by week twoEvery node carries the sys_id; refresh shows what moved
Diagram is diffable plain text—Not advertisedProprietary or XML formatsA readable DSL — reviewable in Git, versioned, byte-stable
Agents edit it safely—Not advertisedMCP, but no concurrency controlTyped ops with If-Match; a stale write gets a 412, never a clobber
Future state produces the CRPartial, in-platformFuture state, then commit backScreenshot into a Word docThe layer diff exports the CR package with the CIs behind it
Decisions cite the changeNative ADRs, separate from the diffVersioned diagramsSeparate artifactsNumbered ADRs linked to the layer, cited in the CR
Never writes to your instancen/a — is ServiceNowWrites back on approvaln/a — disconnectedNo non-GET call exists in the codebase

Keep your native views — ArchTruth reads the same records and never writes back. Use it where they stop: the change package, artifacts your team can review in Git, and agents that edit without clobbering. Established ServiceNow-native modelling apps (ins-pi and others) do current- and future-state design well and have done since 2015; the columns above reflect what their public listings advertise, not a claim about what their products can do. Compare them properly — we would rather lose a deal than win one on a misleading table.

See Your Own CMDB as a Living Diagram

Thirty minutes with a PDI or sandbox is all it takes. Leave with a diagram you can defend.

Book a walkthrough