C4 container diagram template

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

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

C4 container diagram template
Online store [system boundary]
Customer [Person]
Web app [React SPA]
Mobile app [iOS / Android]
API application [Node.js, REST]
Database [PostgreSQL]
Search index [OpenSearch]
Message queue [RabbitMQ]
Worker [background jobs]
Payment provider [External]
Email service [External]
Containers: Online store
uses [HTTPS]
uses
JSON / HTTPS
JSON / HTTPS
reads, writes [SQL]
queries
publishes [AMQP]
consumes
sends [SMTP]
charges [HTTPS]
The C4 container diagram template as it opens in Kelvo: 10 boxes and 10 links.

What's on the board

Online store [system boundary]
Web app [React SPA] · Mobile app [iOS / Android] · API application [Node.js, REST] · Database [PostgreSQL] · Search index [OpenSearch] · Message queue [RabbitMQ] · Worker [background jobs]

Also on the board

  • Customer [Person]
  • Payment provider [External]
  • Email service [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
  • containers
  • 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 system context diagram template previewC4 system context diagram

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

  • 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 container diagram template