stack_map
live architecture map of your stack - services, connections, status pills.
Visualisation, not a check. Aggregates architecture_facts emitted by every other Fizzgig tool you run, builds a graph of services + connections, attaches live status from each platform (Supabase, Cloudflare, Vercel, Stripe, OpenAI, Anthropic, Mapbox, GitHub, and 17+ more via the Statuspage adapter). Renders as a Mermaid diagram with a hub-and-spoke topology - your framework (or a "Your App" root) connects to each service; inferred edges are drawn dashed and labelled so a guess is never mistaken for a detection. Honest scope - sees packaged dependencies + env-var-detected platforms but NOT fetch()-based integrations (pair with fetch-url-scanner for full integration coverage). Gets richer the more Fizzgig tools you run.
your architecture, mapped.
anonymous mode - paste audit_log_ids from your recent fizzgig tool runs (each tool returns one) and stack-map aggregates them into a tier-grouped graph with platform status. the example below renders fizzgig's own stack from a recent dep-audit run.
after every other fizzgig tool runs.
every fizzgig tool emits architecture_facts as a side-effect of its check. stack-map reads those facts from your recent tool_runs and rebuilds your map. the more tools you run, the richer the map gets.
also: before any deploy, to spot upstream platform incidents that might have caused a flaky integration. when investigating "why does this feel slow?" - one of your platforms may be degraded right now.
- +
graph- nodes + edges + tiers - +
mermaid- ready-to-render syntax - +
statuses- per-platform status pills - +
unsupported_services- adapter-coming-soon hints - +
envelope- scale + cadence + paired tools - +
audit_log_id- every run is persisted
~25 platforms covered out of the box via the canonical Statuspage adapter:
supabase · cloudflare · vercel · stripe · openai · anthropic · github · resend · twilio · sendgrid · mailgun · linear · mongodb · planetscale · pagerduty · auth0 · clerk · mapbox · algolia · datadog · sentry · netlify · railway · fly · render
aws · azure · gcp adapters land in a future release.
stack-map reads only metadata from your tool_runs (which services were detected, with what evidence). it never sees your raw inputs - those were already discarded by the tools that emitted the facts. the architecture map is derived information, fully audit-trailed.