Skip to content

Interactive Architecture & Dashboard Tour

Experience how Diverge orchestrates delta deployments, header/cookie routing, database schema isolation, serverless scale-to-zero hibernation, autonomous AgentTask Macaroon sandboxes, and diverge doctor diagnostics right in your browser—before installing a single CRD.


Use the step buttons below (or press ← / → when focused inside the tour) to step through the lifecycle of PR #42 (feat/instant-payouts) on a 3-service e-commerce stack (storefront-web, checkout-api, fulfillment-worker).

Diverge Control Plane Simulator Namespace: demo-staging · 3 Baseline Pods · 0 Preview Pods
Step 1 of 6
Step 1 · Shared Baseline Stack (0 Open PRs)

Your Staging Cluster Before Any Pull Requests Open

Three microservices run in demo-staging alongside shared PostgreSQL, Kafka, and Flipt feature flags. All traffic flows through diverge-proxy to baseline v1.4.0 pods.

<div class="dv-topo-grid">
<div class="dv-node dv-node-proxy" id="dv-s1-proxy">
<div class="dv-node-head">
<span class="dv-badge dv-badge-orange">Ingress / L7 Router</span>
<code>diverge-proxy</code>
</div>
<div class="dv-node-meta">Header &amp; <code>?_diverge_env</code> cookie aware</div>
</div>
<div class="dv-node" id="dv-s1-web">
<div class="dv-node-head">
<span class="dv-badge dv-badge-green">Baseline 1/1</span>
<code>storefront-web</code>
</div>
<div class="dv-node-meta">Image: <code>v1.4.0</code> · Next.js / Go BFF</div>
</div>
<div class="dv-node" id="dv-s1-api">
<div class="dv-node-head">
<span class="dv-badge dv-badge-green">Baseline 1/1</span>
<code>checkout-api</code>
</div>
<div class="dv-node-meta">Image: <code>v1.4.0</code> · Propagates <code>x-diverge-env</code></div>
</div>
<div class="dv-node" id="dv-s1-worker">
<div class="dv-node-head">
<span class="dv-badge dv-badge-green">Baseline 1/1</span>
<code>fulfillment-worker</code>
</div>
<div class="dv-node-meta">Image: <code>v1.4.0</code> · Topic: <code>orders.events</code></div>
</div>
<div class="dv-node" id="dv-s1-pg">
<div class="dv-node-head">
<span class="dv-badge dv-badge-blue">PostgreSQL 16</span>
<code>schema: public</code>
</div>
<div class="dv-node-meta">Table: <code>orders</code> (4 baseline rows)</div>
</div>
<div class="dv-node" id="dv-s1-flipt">
<div class="dv-node-head">
<span class="dv-badge dv-badge-purple">OpenFeature / Flipt</span>
<code>namespace: default</code>
</div>
<div class="dv-node-meta">Flag: <code>instant_payouts = false</code></div>
</div>
</div>
<div class="dv-console" id="dv-s1-console">
<div class="dv-console-bar">
<span>HTTP Trace &amp; JSON Response</span>
<code id="dv-s1-status">200 OK · 14ms · Baseline Route</code>
</div>
<pre class="dv-console-pre" id="dv-s1-output">$ curl -s https://shop.preview.example.com/api/checkout | jq .

{ “service”: “checkout-api”, “version”: “v1.4.0”, “environment”: “baseline (demo-staging)”, “db_schema”: “public”, “feature_flags”: { “instant_payouts”: false }, “settlement_eta”: “T+2 business days” }

<div class="dv-delta-cards">
<div class="dv-delta-card dv-delta-reused">
<div class="dv-delta-row">
<strong><code>storefront-web</code></strong>
<span class="dv-badge dv-badge-gray">Reused from Baseline (0 extra pods)</span>
</div>
<p>Forwards incoming <code>x-diverge-env: pr-42</code> header to downstream <code>checkout-api</code>.</p>
</div>
<div class="dv-delta-card dv-delta-deployed" id="dv-s2-delta-card">
<div class="dv-delta-row">
<strong><code>checkout-api-pr-42</code></strong>
<span class="dv-badge dv-badge-orange">Delta Deployed (1 pod · $0.012/hr)</span>
</div>
<p>Injected with <code>DIVERGE_PREVIEW_SCHEMA=preview_pr_42</code> and Flipt namespace <code>preview-pr-42</code>.</p>
</div>
<div class="dv-delta-card dv-delta-reused">
<div class="dv-delta-row">
<strong><code>fulfillment-worker</code></strong>
<span class="dv-badge dv-badge-gray">Reused + Ephemeral Topic <code>pr-42.orders.events</code></span>
</div>
<p>Zero duplicate worker pods needed unless worker code changes in the PR.</p>
</div>
<div class="dv-delta-card dv-delta-db">
<div class="dv-delta-row">
<strong>Postgres Schema <code>preview_pr_42</code> + Atlas</strong>
<span class="dv-badge dv-badge-blue">Isolated DDL</span>
</div>
<p><code>ALTER TABLE preview_pr_42.orders ADD COLUMN payout_rail TEXT DEFAULT 'RTP_INSTANT';</code></p>
</div>
</div>
</div>


  1. Delta Deployments (PreviewGroup & diverge diff): Instead of cloning storefront-web, checkout-api, and fulfillment-worker for every PR, Diverge deployed only checkout-api-pr-42—cutting preview compute by 67% on a 3-service stack (and >90% on a 25-service stack).
  2. Zero-Extension Browser Testing (?_diverge_env=pr-42): Clicking a shareable URL sets an HttpOnly _diverge_env=pr-42 cookie in diverge-proxy and injects the floating Preview Switcher Banner so reviewers can toggle back to baseline with one click.
  3. Full-Stack State Isolation: Each preview automatically receives an isolated PostgreSQL schema (preview_pr_42) migrated via Ariga Atlas, an isolated Flipt feature flag namespace (preview-pr-42), and isolated Kafka topics (pr-42.orders.events).
  4. Serverless Scale-to-Zero (activator-proxy --wake-splash): Idle previews scale down to 0 pods and wake seamlessly with a 202 Accepted HTML splash screen that polls GET /-/wakeup-status until ready.
  5. Cryptographic AgentTask Governance: Autonomous coding agents run in gvisor/kata sandboxes with HMAC-SHA256 Macaroon capability caveats (max_cost_usd, max_tokens, allowed_models) enforced live on every POST /api/v1/agenttask/meter call.
  6. Actionable Diagnostics (DIV-101–DIV-110): diverge doctor surfaces deterministic error codes linked directly to the Troubleshooting Playbook.