Define architecture-as-code
Capture modules, dependencies, boundaries, contracts, and architecture rules in repository-local configuration.
How it works
A local-first workflow that turns architecture checks into a shared governance record.
ArchPilot separates validation from governance. Validation runs locally in VS Code and the CLI. ArchPilot Cloud stores only architecture metadata so teams can govern architecture across repositories and time.
This gives engineering teams a consistent software architecture workflow from the VS Code extension and CLI through CI and ArchPilot Cloud, with guardrails that keep architecture intact as delivery speeds up.
Five-step flow
Architecture-as-code moves from local validation to durable Cloud governance.
See how architecture moves from local checks into continuous team-wide governance.
Overview
ArchPilot keeps architecture validation local and makes governance shared.
The workflow is designed so developers get architecture feedback early, engineering teams can run the same checks in CI, and the cloud becomes the place for governance visibility rather than hosted scanning.
Validate locally in VS Code and CLI
Engineers run deterministic validation before architecture drift reaches review or CI, including drift introduced by faster AI-assisted changes.
Run checks in CI
GitHub Actions reinforces the same validation workflow for pull requests and main-branch automation.
Publish governance snapshots
Validated architecture metadata is uploaded without syncing repository source code.
Govern across repositories in Cloud
ArchPilot Cloud connects repositories into shared ownership, posture, policy, and history views.
Architecture-as-code
Generate local architecture artifacts teams can review.
ArchPilot turns repository structure into reviewable architecture metadata before validation results are promoted into automation or Cloud.
- Repository-local architecture metadata
- Generated artifacts for review
- A repeatable starting point for policy checks
Architecture-as-code
VS Code validation
Validate architecture where developers make changes.
The VS Code flow gives engineers fast local feedback on architecture metadata, findings, and validation status before changes leave the editor.
- Local validation feedback
- Architecture findings in developer context
- Same model as CLI and CI
Local validation
Governance upload
Publish validated metadata when the repository is ready.
After local or CI validation, teams upload governance snapshots that Cloud can organize without receiving repository source code.
- Metadata-only upload boundary
- Repository history from validated snapshots
- Governance-ready outputs for Cloud
Upload
Cloud governance
Govern architecture across repositories and teams.
Cloud turns published snapshots into an operating view for architecture posture, findings, ownership, policies, exceptions, and history across the organization.
Cloud result