Closed beta. Request access
Nexarch

Platform

A graph of the estate, written by the agents that build it.

Nexarch discovers your architecture from the repositories, infrastructure and documentation your agents work in, keeps it current as they ship, and gives your architects the controls to govern it.

What Nexarch knows.

Applications and components

Registered from repositories; monorepos become a project with one proposed application per deployable.

From init-project and update scans.

Data domains, data sets and stores

Logical data assets mapped to the physical stores that hold them, and which applications read and write them.

From code scans and agent observations.

Infrastructure

Your infrastructure as code becomes environments and the platform components they provision — Terraform and OpenTofu today.

From ingest-infra.

Technologies and integrations

Packages, APIs and platforms resolved against a global reference library; unresolved names are logged for review.

From dependency resolution.

Decisions

ADRs found in repositories and decisions recorded in sessions, with lifecycle and provenance.

From documentation discovery and agent sessions.

Controls and audits

Policy packs, the rules inside them, and the audit result per application.

From packs you install.
/workspace/data/model
Data sets mapped to the physical stores that hold them
/workspace/architecture/decisions
A decision record with its source repository and path
/workspace/controls
A control detail with its rule and the assessment result per application
/workspace/architecture/applications
Applications grouped by project with control assessment results

Before, during and after every change.

Beforethe agent pulls architectural context from the graph while it plans the change.

Duringthe agent codes using the context and constraints the graph provides.

Afterthe agent registers what it built — proposals put forward, design decisions raised for review.

/workspace · What grew, last 7 days
Architecture graph showing what grew in the last seven days

Humans where judgement lives.

Policy-gated writes

Before an agent can write, it must fetch your current policy bundle and present its hash with every change.

Provenance on every fact

Each entity and relationship records which repository it was observed in, which agent asserted it, and when.

Activation and review

Proposed applications need human activation, extracted candidates need review, and the audit trail records both.

/workspace/agents
Agents page with one card per machine and its registered runtimes

Two situations, one product.

Startup that built fast with agents

There is no architecture to recover, only one to discover. Nexarch discovers it as your team keeps shipping.

Enterprise adopting agents

You have architecture practices, and agent-assisted delivery is outrunning them. Nexarch gives your architects a graph that stays current without asking engineers to maintain it, and gives your governance a mechanism agents actually obey.

Closed beta

Closed beta. Onboarding teams now.

Tell us about your team and what you'd want Nexarch to prove. Requests are reviewed by a person, usually within two business days.

Request beta access