C4 system context

Map an outreach platform, the person who uses it and its email provider.

Dispatch Service canvas at 108% zoom with a booking-events to carrier dispatch flow above four endpoint cards: POST load tender, GET load status, gRPC AssignDriver, and server-streaming StreamLoadStatus.

Reference diagram from Archdocs. See the YAML below for this template's contents.

A system context diagram names the people and external systems around a product. This fictional Cadence example connects a customer success rep to an outreach platform and SendGrid.

Adapt the context

Replace Cadence with your system's name. Change the person and external system to match its users and dependencies, then label each relationship with what crosses the boundary.

Keep internal services out of this view. If you need to show a worker or database inside the platform, use a separate container diagram so readers can distinguish external dependencies from implementation details.

The YAML uses local C4 nodes. It does not need shared objects from an Archdocs workspace.

Template YAML

Open in the editor Start free

apiVersion: archdocs/v1
title: Cadence system context
layout:
  algorithm: layered
  direction: right
nodes:
  - id: customer
    type: c4-node
    kind: person
    label: Customer Success Rep
    description: Builds sequences and enrolls contacts.
  - id: cadence
    type: c4-node
    kind: system
    label: Cadence
    description: Schedules outreach sequences and records delivery outcomes.
  - id: sendgrid
    type: c4-node
    kind: system
    label: SendGrid
    description: External email delivery provider.
relationships:
  - from: customer
    to: cadence
    label: Builds sequences and enrolls contacts
  - from: cadence
    to: sendgrid
    label: Sends email via HTTPS
    style: dashed