Tool comparisons
ArchPilot overlaps with established tools, but each one has a different center of gravity. This page keeps the comparison practical: what the tool is best at, when to choose it, and what the reviewed official docs establish.
Quick orientation
Start here if you just need to know which workflow each tool is built around.
Multi-stack architecture discovery and ongoing governance
VS Code, CLI, CI, pull requests, and Cloud governance workflows
Choose this when: Choose ArchPilot when you want local architecture discovery, validation, maps, and a path from repo-level findings to team governance.
Official sourceArchitecture rules written as Java tests
Java bytecode and Java test frameworks
Choose this when: Choose ArchUnit when your team wants precise Java architecture rules expressed and reviewed as tests.
Official sourceJavaScript and TypeScript dependency rules
JavaScript and TypeScript projects
Choose this when: Choose dependency-cruiser when you need configurable dependency rules and graph output in a JS or TS codebase.
Official sourceWorkspace boundary enforcement in Nx
Nx workspaces, JS/TS linting, Nx Enterprise Conformance
Choose this when: Choose Nx boundaries when an Nx workspace already models projects and tags that should constrain dependencies.
Official sourceBroad static analysis and quality gates
Multi-language static analysis, CI, pull-request analysis, server workflow
Choose this when: Choose SonarQube when the main need is quality and security analysis, quality gates, PR decoration, and historical metrics.
Official sourceStructural analysis and visualization
Structure101 Studio, Workspace, Build, Dashboard, and language-specific analyzers
Choose this when: Choose Structure101 when architecture visualization, structure specifications, overlays, and build checks are the center of the workflow.
Official sourceCompare by need
These sections avoid a giant checkmark matrix. Each category explains what matters and summarizes how each tool approaches it.
Discovery matters when a team needs a useful architecture model before hand-authoring every rule.
Generated configuration
Smart Init generates an architecture model that teams can review before using it as a baseline.
Requires authored tests
Teams import classes and author rules against packages, classes, layers, slices, and cycles.
Configuration-driven
The tool initializes dependency-cruiser configuration rather than a broader architecture governance model.
Configuration-driven
Nx uses its project graph and configured tags or constraints.
Not found in reviewed docs
The reviewed pages do not establish Smart Init-style architecture discovery.
Not found in reviewed docs
The reviewed pages do not establish ArchPilot-style Smart Init generation.
Boundary checks keep local decisions from drifting as repositories grow.
Built in
Local validation checks module contracts and dependency boundaries against the configured model.
Built in
Package, class, layer, slice, and cycle checks are documented capabilities.
Built in
Forbidden, allowed, and required dependency rules are core documented workflows.
Built in
Module-boundary enforcement is a documented Nx capability.
Paid edition
The product page lists project architecture management in paid editions, but detailed boundary semantics need edition-specific docs.
Built in
Structure specs and diagrams define allowable dependencies and violations.
Teams need different levels of rule authorship, policy, exceptions, and decision context.
Built in
Rules, contracts, ADR checks, baselines, suppressions, and exceptions are part of the governance model.
Requires authored tests
Governance comes from the tests and rules the team writes.
Configuration-driven
Rules live in configuration and report violations by severity.
Configuration-driven
Teams express constraints through tags, lint rules, and Conformance rules.
Server-oriented
Quality gates and rule-based analysis are central workflows.
Configuration-driven
Architecture structure and violations are governed through specs, diagrams, build checks, and dashboard workflows.
Architecture feedback is easier to act on when it appears near the code and in delivery workflows.
Built in
The workflow spans VS Code, CLI, CI, and pull-request review without requiring local source upload.
Local
Rules run where the Java tests run, commonly through JUnit.
Local
CLI checks can run locally and in automation.
Built in
ESLint rules support JS/TS lint workflows; Conformance supports broader project checks.
Built in
CI-integrated pull-request analysis and decoration are documented workflows.
Built in
Studio, Workspace, Build, and Dashboard workflows are documented.
Maps and trends help teams explain why a finding matters beyond a single file.
Built in
Architecture maps, impact analysis, history, and trends connect findings to repository structure.
Not found in reviewed docs
The reviewed guide does not establish ArchPilot-style repository maps, impact analysis, or Cloud history.
Built in
Dependency graph output is part of the tool's purpose.
Built in
The Nx project graph is central to boundary enforcement.
Paid edition
Project architecture management is listed in paid editions; the reviewed pages do not establish ArchPilot-style local map artifacts.
Built in
Architecture visualization, overlays, measures, violations, and trends are documented.
Organization workflows help turn local findings into shared follow-through.
Built in
Cloud adds repository, team, organization, history, policy, and portfolio governance on top of local validation metadata.
Not found in reviewed docs
Repository, team, and organization workflows are not established in the reviewed guide.
Not found in reviewed docs
The reviewed docs do not establish repository, team, or organization governance workflows.
Paid edition
Language-agnostic Conformance is documented as an Nx Enterprise feature.
Server-oriented
Server-side quality and security governance is the documented model.
Built in
Build checks and dashboards support architecture governance workflows.
Claims are based on official product documentation, official repositories, or vendor pages reviewed on Aug 14, 2026.
Real repository evidence
Validation runs locally through the free extension and CLI. ArchPilot Cloud brings validated architecture results together for shared history, policy workflows, cross-repository intelligence, and organization-wide governance.
