Creative & technical
Software architecture template
Clients, services, data stores, integrations and cross-cutting concerns. Use relationships for calls between services so the tree stays clean.
- Best for
- Engineers
- Goal
- Map systems, services, data and risks
- Layout
- Mind map (balanced)
- Topics
- 21
How to use it
- Keep the tree for ownership; use relationships for dependencies.
- Add links to repos or docs.
- Export SVG for design docs.
- Press Tab to add detail under any topic and Enter for another at the same level.
What’s inside
The full structure as text — the same content you get in the editor.
- System name
- Clients
- Web app
- Mobile app
- Services
- API gateway
- Auth service
- Core service
- Worker / jobs
- Data
- Primary database
- Cache
- Object storage
- Integrations
- Payments
- Cross-cutting
- Observability
- Security
- CI/CD
- Risks & open questions
- Clients
Last reviewed 2026-10-30. Placeholders are deliberately generic — replace them with your own facts and sources.