Search docs
Docs searchLocal vs Cloud
Local Validation vs Cloud
Understand how local ArchPilot validation and ArchPilot Cloud work together so teams can move from single-repository validation to shared architecture governance intentionally.
This is the core product model: architecture validation happens locally, governance upload connects that work to Cloud, and Cloud makes architecture visibility, ownership, and governance operational across the organization.
The simple model
- Validation happens locally in the extension or CLI.
- Governance upload is optional.
- Cloud stores governance metadata, snapshots, findings, and ownership-aware history.
- Cloud is not a hosted replacement for the local validator.
What moves to Cloud
- Repository identity and repository-level governance context
- Validation findings and finding lifecycle state
- Architecture score, readiness, risk, and enforcement signals
- Snapshot history over time
- Ownership and organization governance metadata
What does not change when you use Cloud
Developers still run architecture validation locally or in CI. Cloud does not take over that step.
What changes is the operating model: local results become shared architecture history, cross-repository findings context, ownership-aware posture, and organization-level governance signals.
When Cloud is worth adding
- When one repository is no longer the whole story
- When teams want architecture drift detection and posture visibility over time in a shared workspace
- When ownership, exceptions, and policy workflows need an organization view
- When architecture governance needs to scale beyond one developer or one repository
Plan note
Local validation and CI validation are available on all plans.
Cloud capacity and advanced governance workflows vary by plan.