Runs where developers work
The VS Code extension and CLI validate architecture locally so developers get feedback before they push or open a pull request.
ArchPilot Cloud
Keep software architecture visible, enforceable, and measurable across repositories and teams.
ArchPilot is a local-first architecture governance platform for engineering teams that need to move fast without losing architectural control.
Validation stays local in the VS Code extension and CLI. Governance visibility lives in the cloud. Only architecture metadata is synced for findings, scores, policies, exceptions, ownership context, and history.
No source code is synced or stored in ArchPilot Cloud.
Local-first architecture validation
Validation runs locally in the VS Code extension and CLI, not in a hosted scanner.
ArchPilot keeps the validation loop in the developer workflow so teams can work offline, get deterministic results, and run the same checks locally and in CI.
Deterministic and offline
Validation does not depend on a hosted scanning service. Teams can work offline and still get the same deterministic results.
Consistent from laptop to CI
The same local validation flow can run in CI, which keeps architecture enforcement consistent across developer workflows and automated pipelines.
Cloud governance workspace
The cloud workspace is for governance, visibility, and history across repositories.
ArchPilot Cloud organizes architecture metadata into a shared workspace for findings, scores, trends, policies, exceptions, ownership, and multi-repository governance.
Repository architecture visibility
Track governed repositories, synced findings, and architecture posture in a shared workspace instead of relying on local results alone.
Scores, trends, and history
Review repository scores and snapshot history over time so architecture changes stay measurable and visible beyond a single run.
Policies, exceptions, and ownership
Coordinate architecture governance with policy results, exception workflows, and ownership context across teams and repositories.
Security and privacy
Your code never leaves your environment.
ArchPilot Cloud does not store source code. Only architecture metadata is synced so organizations can use the governance workspace without moving proprietary code into the product.
The architecture metadata model is designed for teams with security, IP, and compliance concerns that still need shared architecture visibility and governance.
Examples of architecture metadata
- Findings and issues
- Repository architecture summaries
- Scores and trend snapshots
- Policy results and exceptions
- Governance and ownership context
AI-assisted development
Move fast with AI and vibe coding without losing architecture control.
Faster AI-assisted development increases the risk of architecture drift and rule violations. ArchPilot helps teams keep architecture signals visible even in fast-moving codebases.
Faster code changes increase drift risk
AI-assisted development and vibe coding help teams move quickly, but they also make it easier for architecture boundaries and rules to erode silently.
Catch architectural issues early
ArchPilot keeps architecture checks in the local developer workflow so fast-moving teams see problems before changes spread across the codebase.
Keep governance signals visible
Findings, scores, trends, and ownership context remain visible in the cloud workspace even when repositories are changing rapidly.
How it works
A simple flow from local validation to organization-wide governance.
Run validation locally, generate architecture metadata, sync that metadata to the cloud workspace, and govern from shared history and policies.
01
Run validation locally
Developers use the ArchPilot VS Code extension or CLI to validate architecture directly in their own environment.
02
Generate findings and metadata
The local validation run produces findings, scores, rule outcomes, and repository architecture metadata.
03
Sync metadata to Cloud
Only the governance metadata is synced to ArchPilot Cloud. The cloud does not need source code to store and organize the results.
04
Govern from shared history
Teams use the cloud workspace for visibility, policies, exceptions, ownership, and architecture history across repositories.
Key capabilities
Built around the governance workflows already present in ArchPilot Cloud.
Everything below reflects the current product surface and avoids roadmap promises.
Architecture validation
Run architecture checks through local tooling without moving validation into the cloud.
Findings and issues
Review synced findings and issue detail in a shared governance workspace.
Repository scores
Track architecture scores and posture as durable governance signals.
History and trends
Keep snapshot history over time so architectural drift and improvement stay measurable.
Policies and exceptions
Manage policy outcomes and approved exceptions as part of the operational governance record.
Ownership and multi-repository visibility
Connect repositories to teams and systems and view architecture posture across the organization.
Governance workspace
Use a shared cloud workspace to organize architecture metadata across repositories, teams, and time.
Start with local validation
Use local ArchPilot tooling for validation and ArchPilot Cloud for governance.
Keep source code in your own environment, sync architecture metadata, and give your organization a durable governance workspace.