Skip to main content

Enterprise Workflows

Team and Enterprise plans.

Multi-environment deployment​

PinPole supports independent deployment pipelines for ST (System Test), UAT, and PR (Production). The recommended promotion flow is:

Validated Canvas → Deploy to ST → Verify → Deploy to UAT → Sign-off → Deploy to PR
Do not promote directly to production

The ST and UAT stages confirm that the architecture behaves correctly in a real AWS account before production traffic is at risk. Never promote directly from canvas to production.

Team collaboration​

Shared canvases allow multiple engineers to work on the same architecture. Use role-based access control to enforce appropriate permissions:

  • Engineers should have write access to canvases in their domain
  • Deployment to PR should be restricted to senior engineers or release managers
  • Reviewers and stakeholders should have read-only access for design review without risk of accidental changes

Audit logging​

Enterprise plan only.

All actions in PinPole — canvas changes, configuration edits, simulation runs, recommendation applications, and deployments — are recorded in the audit log. Use this for:

  • Incident review — reconstruct the sequence of changes that preceded a production issue
  • Compliance — demonstrate that infrastructure changes followed an approved review and simulation workflow
  • Architecture archaeology — understand why a past architectural decision was made, including the simulation data that supported it