Main
Demonstration Workspace
You're looking at a showcase of the Architecture as Code framework -- not a real client. BelFoot FC is a fictional football club from Jonas Van Riel's book Leading with Capabilities, used here as a reference case with a fully modeled capability map, bounded contexts, and entity relationships.
A control center for architecture-as-code -- C4 on the outside, Claude Code on the inside.
Architecture documentation shouldn't be a side project. It should be a side effect.
This site -- every diagram, every system description, every deployment view -- is generated directly from code. Change the model, push to Git, and the documentation updates itself. The Claude Code skills bundled with this framework read and write the same model, so AI-assisted development uses your architecture as context instead of guessing.
What you're looking at is BelFoot FC's full digital architecture: 28 software systems, 13 bounded contexts, 4 environments, zero manual upkeep. The diagram below shows one of five organizational groups -- click any box to start the journey.
-
From Business to Infrastructure
Trace from a business capability through bounded contexts and software systems down to the infrastructure that runs it. See all five organizational groups and 13 bounded contexts.
-
Browse 28 software systems with auto-generated diagrams, and four animated workflows showing how systems collaborate at runtime.
-
Multi-cloud deployment across on-premise, Azure, and AWS -- with deployment views per environment for production, acceptance, test, and development.
-
Business domains mapped to data entities and software systems
-
From fans and sponsors to coaches, analysts, and IT architects
-
Commercial, Corporate, IT, Operations, and Sporting -- each with its own landscape view
-
Browse every system with auto-generated diagrams, dependencies, and documentation
-
Production (multi-cloud), acceptance, test, and development
-
Strategic decisions with full context, consequences, and audit trail
- Auto-generated C4 diagrams at every level -- landscape, context, container, component, deployment
- Bounded contexts and capability maps linking business domains to software systems
- Deployment views per environment -- see exactly where containers run across production, acceptance, development, and test
- AI-powered automation -- every system on this site was generated using Claude Code skills
- Git-based governance -- every change goes through branch, pull request, review, merge, auto-deploy
- Business capabilities mapped to IT systems -- see which software supports which part of the business
- Impact analysis before any change -- trace from a business capability down to the infrastructure that runs it
- Architecture decisions are transparent -- every strategic choice is documented with context and consequences
- Documentation stays current by design -- generated from the same code that defines the architecture
But what about TOGAF / ArchiMate / Lean IX?
Great question -- and one that comes up in every architecture conversation.
This site uses C4 + Structurizr deliberately. Not because TOGAF and ArchiMate are wrong, but because they solve different problems at a different pace.
| C4 / Structurizr | ArchiMate / TOGAF | |
|---|---|---|
| Focus | Software systems, containers, components | Enterprise & solution: strategy, capabilities, cross-system flows |
| Audience | Development teams, tech leads | Enterprise & solution architects, governance boards |
| Maintenance | DSL-as-code in Git, auto-generated on every merge | Typically a separate modeling tool, manually maintained |
| Time to value | Days | Months |
| Process modeling | Not its job (use BPMN) | Built-in motivation, business process, and migration views |
C4 is intentionally narrow. It answers "what software do we have, how does it connect, and where does it run?" -- and keeps that answer current because it lives in the same Git workflow as the code.
ArchiMate answers broader questions -- strategy, business processes, data flows across the enterprise. If your organization needs that, C4 doesn't replace it. But C4 feeds into it: the Application layer in ArchiMate maps directly to C4 models.
Our approach: Start with C4 to get immediate, maintainable value. If the organization later adopts ArchiMate or Lean IX, nothing is wasted -- the C4 models slot right into the application architecture viewpoint.
Bring this to your organization
This framework can be set up for any enterprise -- from startups to large organizations with hundreds of software systems. Interested in what this could look like for your landscape? Get in touch.