25 editable reference diagrams
DevOps Architecture Diagrams
Plan build, delivery and infrastructure workflows with DevOps architecture diagrams. These examples distinguish source control, artifact production, deployment approval and runtime verification so that a successful build is not mistaken for a healthy release.
Follow one change from commit to rollback. Record where credentials are used, artifacts are verified and deployment decisions are made. Choose rolling, blue-green or canary delivery based on compatibility, observability and the ability to reverse a failed change.
Choose a diagram for your design question
Open a reference to inspect its component flow and trade-offs, then adapt it in the browser-local editor. Manual editing does not require login; AI generation and account storage do.

CI CD pipeline architecture
Promote the same tested artifact.
6 components · 5 connections
Explore ci cd pipeline architecture →
GitHub Actions deployment architecture
Use short-lived deployment credentials.
8 components · 6 connections
Explore github actions deployment architecture →
GitLab CI CD architecture
Isolate runners from untrusted changes.
6 components · 5 connections
Explore gitlab ci cd architecture →
Jenkins pipeline architecture
Do not expose production secrets to every build.
6 components · 5 connections
Explore jenkins pipeline architecture →
Azure DevOps pipeline architecture
Separate build permissions from release approval.
6 components · 5 connections
Explore azure devops pipeline architecture →
Argo CD GitOps architecture
Git changes must have controlled ownership.
6 components · 5 connections
Explore argo cd gitops architecture →
Flux GitOps architecture
Reconciliation makes manual drift temporary.
6 components · 5 connections
Explore flux gitops architecture →
Terraform infrastructure architecture
Review destructive actions before applying plans.
6 components · 5 connections
Explore terraform infrastructure architecture →
Terraform state management architecture
State can contain sensitive resource information.
7 components · 4 connections
Explore terraform state management architecture →
Infrastructure as code architecture
Declarative intent still requires change review.
6 components · 5 connections
Explore infrastructure as code architecture →
Internal developer platform architecture
Build a paved path with an escape hatch.
7 components · 6 connections
Explore internal developer platform architecture →
Backstage developer portal architecture
Catalog ownership metadata must stay current.
7 components · 5 connections
Explore backstage developer portal architecture →
Preview environment architecture
Use sanitized data and automatic expiry.
7 components · 5 connections
Explore preview environment architecture →
Ephemeral test environment architecture
Track resource ownership before automatic deletion.
7 components · 6 connections
Explore ephemeral test environment architecture →
Blue green deployment architecture
Database changes must support both versions.
5 components · 4 connections
Explore blue green deployment architecture →
Canary deployment architecture
Compare reliable signals before expanding traffic.
6 components · 5 connections
Explore canary deployment architecture →
Rolling deployment architecture
Keep versions protocol-compatible during replacement.
6 components · 4 connections
Explore rolling deployment architecture →
Feature flag architecture
Plan safe defaults when configuration is unavailable.
7 components · 5 connections
Explore feature flag architecture →
Release orchestration architecture
Track artifact identity across every stage.
6 components · 5 connections
Explore release orchestration architecture →
Software supply chain security architecture
Verify both artifact signature and provenance policy.
7 components · 6 connections
Explore software supply chain security architecture →
Artifact repository architecture
Retention must preserve deployable release dependencies.
6 components · 4 connections
Explore artifact repository architecture →
Automated testing infrastructure architecture
Keep test credentials and datasets isolated.
7 components · 5 connections
Explore automated testing infrastructure architecture →
Policy as code architecture
Policies need versioning and testable exceptions.
6 components · 5 connections
Explore policy as code architecture →
Platform engineering golden path architecture
Standardization must address real developer friction.
6 components · 5 connections
Explore platform engineering golden path architecture →
Multi cloud deployment architecture
Avoid assuming identical semantics across providers.
7 components · 5 connections
Explore multi cloud deployment architecture →