
SaaS architecture diagram template
Client, edge, application and data layers · Services behind an API gateway and auth service · Third parties such as payments and email
Preview and use template →A C4 system context diagram is the zoomed-out first level of the C4 model: one box for your system, the people who use it and the systems it depends on. This example for a project tracking product shows three user roles, five external systems and labelled arrows saying what passes between them.
No account needed · Opens as your own editable page

Write down every type of user, including internal staff such as support agents. Roles matter more than job titles, because they explain why someone uses the system.
Include the external systems your product talks to directly, such as identity, billing and email. Leave out internal services: they belong on the next level down, the container diagram.
Describe what each relationship does in plain words, then add the protocol in brackets. An unlabelled arrow forces readers to guess, which defeats the point of a context diagram.
Yes. Duplicate the page and replace the system in scope with its apps, databases and services, keeping the people and external systems at the edges.
No. Open the template and edit it in your browser. Your work saves on this device. An account is optional if you want to sync your workspace.
Yes. Use Export in the editor to save a PNG, SVG or PDF, or download an editable .epicdraw backup.