Arcwoven ARC-01 Repository-to-model workbench
The architecture is already in your repo. Arcwoven draws it out.
Paste a public GitHub repository URL and get an evidence-backed architecture model in your own private workspace — system boundaries, services, APIs, data stores, and dependencies, every element traceable to the source evidence behind it.
Capabilities
Source-backed architecture
Every model element is grounded in repository evidence you can open and inspect.
SysML v2-ready export
Carry reviewed models into MBSE toolchains, alongside diagrams, docs, and HTML.
Large repositories
Built to analyze substantial codebases, not toy examples.
Traceable implementation views
Follow any architectural claim down to the files and lines that implement it.
Private pilot delivery
Working with select teams on private repositories and deeper integrations.
01 Product
Diagrams drift. Evidence doesn't.
Hand-drawn architecture diagrams start aging the day they're made. Six months later, nobody is sure which boxes still exist.
Arcwoven takes the opposite approach: it derives architecture views from the repository itself. Automated analysis reads the code, configuration, manifests, and docs, then assembles a system model where every element carries links to the source evidence behind it.
When the code changes, re-import and re-derive — the model follows the repository, not the whiteboard.
TBL. 01 — Model coverage
02 Understanding
Generated first. Trusted after review.
Arcwoven is deliberately honest about what automation can and cannot promise. Generated outputs are provisional: produced from repository evidence and automated analysis, and possibly incomplete or wrong until a human has looked.
That's why evidence is the core of the product rather than a footnote. Each claim in the model cites the source that supports it, so review is fast: open the citation, confirm or correct, move on.
The model isn't finished when the analysis runs. It's finished when an engineer agrees with it.
The workbench is built around that review loop — generated analysis on one side, human judgment on the other, and a curated, defensible architecture model as the result.
03 Workflow
Four steps from repository to reviewed model.
Import evidence
Point Arcwoven at a public repository. It gathers code, configs, docs, and API definitions.
Review
Automated analysis produces a generated, provisional view of the system — with citations.
Model
You confirm, correct, and curate. The result is a human-reviewed architecture model.
Export
Take it with you — diagrams, documents, HTML, and SysML v2.
FIG. 02 — Import → review → model → export
04 Free account
Your own workspace. On the house.
A free account gives you a private, per-user workspace for importing public repositories and reviewing the models Arcwoven derives from them. No credit card — just an email and a password.
TBL. 02 — Repository import quotas
Free accounts import public repositories only. Pilot analysis currently focuses on TypeScript/TSX, Node, and React codebases. Private repositories and team workflows are part of the private pilot.
Bring a public TypeScript, Node, or React repository