For enterprise architects

Model your landscape once. Let your pipelines keep it current.

Every EA tool dies the same way: the model rots faster than a handful of architects can update it. Dependra answers that structurally — and gives you a defensible number to end the rationalisation debate.

“The wiki rotted, nobody updates the tool, and rationalisation is a turf war.”
What we hear from every head of EA
The staleness problem

Answered structurally, not with more reminders.

You have bought the tool before. Six months later the diagrams lie, even though three people who cared chased three hundred who didn't.

Dependra removes the chasing. Wire it in once and the model moves at the speed of your codebase, not your documentation backlog.

01
CI publishes manifests
Commit a YAML manifest beside your code; the dependra CLI or GitHub Action publishes it on deploy.
02
Agents inventory repos
Point a coding agent at a repo over the MCP server and it pushes components, dependencies and datasets.
03
Monitoring feeds health
Post a health signal from whatever already watches your estate; it enters at infrastructure and climbs the graph.
04
Architects curate
Draw on the canvas. Every node is a real asset, so diagrams never drift from the model.
The paste-in import always previews a diff before it writes. From CI, your pull request is the gate.
Rationalisation

From the loudest architect's opinion to a defensible, cost-quantified map.

01

TIME quadrants, auto-scored

Tolerate, Invest, Migrate, Eliminate — from technical and functional fit, rolled up to portfolio medians. Every score decomposable.

02

Obsolescence, surfaced early

The tech radar syncs end-of-life daily and maps it to the components that run it, before a vendor pulls support.

03 Business+

Structural risk, priced

Single points of failure, brittle chains and insecure transports, each with an estimated financial exposure.

04 Enterprise

EA answers “so what”

A degraded component surfaces on the objective it threatens — your work visible where strategy is set.

Dependra portfolio analysis: applications on the TIME quadrant with a technical and functional fit breakdown
Portfolio analysis: TIME quadrants from auto-computed fit.
Dependra infrastructure topology: on-premise and cloud providers, zones and subnets, with VPN, peering, direct-connect and internet connectivity between them
Topology: where systems actually run, and how zones interconnect.
Table stakes, then more

EA is the floor. Impact intelligence is the ceiling.

The complete EA model you would expect, graph-native underneath. Then the layer no EA suite has: what a failure actually costs, who it hits, and which compliance clock it starts.

Applications core
Components core
Dependencies core
Capabilities core
Business domains core
Actors core
Hosting topology core
Diagrams core
Revenue, fines, sanctions & SLAs impact
Regulatory exposure impact

Map a slice of your estate this afternoon.

Point your coding agent at a repo or paste a manifest, watch the landscape populate, then run your first blast radius.

14-day trial · No payment required · EU-sovereign hosting