Local Validation vs Cloud

The simple model

• Validation happens locally in the extension or CLI.
• Governance upload is optional.
• Cloud shows repository posture, snapshots, findings, inventory, ownership, policies, and history in a shared workspace.
• Cloud is the shared workspace for local validation results.

What moves to Cloud

• Repository identity and repository-level governance context
• Component, resource, module, and relationship inventory when available
• Validation findings and finding lifecycle state
• Architecture score, readiness, risk, and enforcement signals
• Rule IDs, rule categories, severity, and finding lifecycle state
• Snapshot history over time
• Ownership and organization governance context

What stays local

Developers still run architecture validation locally or in CI. Cloud turns those results into shared architecture history, cross-repository findings context, ownership-aware posture, and organization-level governance signals.

That operating model keeps validation close to the code while giving the organization a durable review workspace.

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 policies 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.

Free focuses on Repository Visibility, Team adds Repository Governance, and Growth adds Organization Intelligence.