C4 system context diagram template

C4 level 1: the system in scope, the people who use it and the external systems it depends on, with a legend.

Use this templateFree, opens in your browser. No sign-up.

C4 system context diagram template
Customer [Person] Browses and buys products
Support agent [Person] Handles orders + refunds
Online store [Software system] Catalog, cart, checkout, orders
Payment provider (Stripe) [External]
Shipping carrier API [External]
Email service (SendGrid) [External]
ERP: stock + invoicing [External]
Legend
Person
System in scope
External system
C4 level 1: who uses the system and what it talks to. No technology details yet.
System context: Online store
browses, orders [HTTPS]
manages orders
takes payments
books shipments
sends confirmations
syncs stock + invoices
The C4 system context diagram template as it opens in Kelvo: 10 boxes, 1 sticky note and 6 links.

What's on the board

  • Legend
  • Customer [Person] Browses and buys products
  • Support agent [Person] Handles orders + refunds
  • Person
  • System in scope
  • Online store [Software system] Catalog, cart, checkout, orders
  • External system
  • C4 level 1: who uses the system and what it talks to. No technology details yet.
  • Payment provider (Stripe) [External]
  • Email service (SendGrid) [External]
  • ERP: stock + invoicing [External]
  • Shipping carrier API [External]

How to use this template

  1. Click Use this template. It opens in the Kelvo app as a new board, saved in your browser.
  2. Double-click any box to change its text. Replace the examples with your own content.
  3. Sketch, then convert. Draw boxes and arrows with the pen, select the strokes and click Convert sketch: they become real boxes and links.
  4. Ask Kelvo right on the board (Pro). With Pro, type @kelvo and what you want in any box or text, for example “@kelvo add error handling”, and press Enter. The change is made there and the request disappears; ⌘Z undoes it.
  5. One page per level. Put the C4 context view on one page and the container view on the next, so each diagram stays readable.

Good for

  • architect
  • c4
  • architecture
  • system context
  • Agreeing on boundaries and responsibilities between services
  • Recording why a design was chosen (and what was rejected)
  • Comparing integration options side by side

Related templates

  • C4 container diagram template previewC4 container diagram

    C4 level 2: the apps, APIs, databases and queues inside the system boundary, with the technology on each link.

  • C4 component diagram template previewC4 component diagram

    C4 level 3: the components inside one container, what each is responsible for, and how they reach databases and external systems.

  • Microservices with API gateway template previewMicroservices with API gateway

    Clients behind an API gateway, services that each own their database, and an event bus for asynchronous work.

  • Event-driven architecture template previewEvent-driven architecture

    Producers publish facts to a broker; independent consumers react — with the design rules that keep it reliable.

  • LLM application architecture template previewLLM application architecture

    Production building blocks around a model: gateway, guardrails, orchestrator, cache, vector DB, tools and observability.

  • LLM agent loop template previewLLM agent loop

    How a tool-using agent plans, calls tools, observes results and updates memory until the goal is met, with guardrails.

All solution architecture diagram templates · All templates

Use the C4 system context diagram template