The architecture behind every diagram

Build and maintain one connected C4 model

Create every C4 view from one reusable architecture model, collaborate visually, and let AI agents explore the architecture through MCP.

400 architecture items free · No credit card required

Explore connected architectureLive UXXU model · no sign-up
Activate the diagram to pan, zoom and explore. Open full-screen model ↗

One element. Every related view.

Change the model once. Keep the story consistent.

A payment provider can appear in the big picture and in a detailed checkout view. Reuse the same element so its name and description stay connected while each diagram keeps its own layout. Try a rename below.

Try a shared-element editLocal illustration · no account needed
Context view: Commerce platform connects to Payment providerContext viewCommerce platformTakes payments throughPayment providerContainer view: Checkout API connects to Payment providerContainer viewCheckout APIAuthorizes payment via HTTPSPayment provider

Both views use “Payment provider” from the same model element.

This illustration runs in your browser. In UXXU, reuse an existing element in another diagram to keep its model properties connected; each view keeps its own layout.

Keep an architecture library behind the canvas

Find and reuse the elements that already describe your system. The object model gives the team a shared place to maintain names, responsibilities and properties before selecting what each diagram shows.

UXXU object model listing reusable architecture elements and their descriptions
The object model holds architecture elements independently of a diagram’s layout.

The right depth for the conversation

Four C4 levels, one architecture

Start with context. Add detail where it helps someone make a decision. You do not need all four levels for every system.

01 / Context

People and system boundaries

Show who uses your system and which external systems it depends on.

Explore this level →

02 / Container

Applications and data stores

Connect services, applications and stores with named communication paths.

Explore this level →

03 / Component

Inside one container

Explain the responsibilities and dependencies within a selected application.

Explore this level →

04 / Code

Implementation detail

Use class diagrams for the classes, interfaces and relationships inside a component.

Explore this level →

Deployment is supplementary: show how runtime instances map to infrastructure. Explore deployment diagram examples. See the official C4 diagram definitions.

Inside the product

See how architecture takes shape

70-second product tour, using recorded UXXU editor footage. Read the captions.
UXXU visual editor showing architecture elements, relationships and the model navigation controls
The visual editor: architecture elements, named relationships and navigation in one workspace.

Give AI agents architecture they can inspect

Connect a compatible MCP client to your organization. Ask it to find dependencies, explain a system boundary or propose a model update grounded in your architecture.

Connect the UXXU MCP →

codeToC4 · Early access

Start from your repository

Repository analysis is being developed to generate a starting model for review. Join the early-access waitlist; visual modeling and MCP are available independently of this workflow.

Explore codeToC4 early access →

Work through a real architectural question

Go beyond a three-box example

Follow checkout dependencies, review a ride-sharing boundary or inspect a banking system boundary. These public diagrams can be explored without registering.

E-commerce platform

Trace checkout across clients, services, owned stores, a message broker and external providers.

26 visible elements · 30 relationships

Explore this model →

Ride-sharing platform

Review riders, drivers, dispatch and the external services around a ride-sharing system.

15 visible elements · 14 relationships

Explore this model →

Core banking platform

Review banking users, payment networks and external verification dependencies around one system boundary.

12 visible elements · 11 relationships

Explore this model →

Counts verified from public diagram data on October 1, 2026. These are diagram counts, not complete workspace usage or proof of the creator’s subscription. Each example’s visible elements fit within the 400-item allowance.

Choose the workflow you will maintain

Compare C4 model tools

UXXU combines visual modeling, shared architecture elements and MCP access. Other tools make different tradeoffs. This comparison is written by UXXU; use the linked vendor sources and try your own model before choosing.

C4 tool workflows and evaluation guides
ToolPrimary workflowConsider it forEvaluation
UXXUVisual editing over connected architecture elements, with MCP access.A shared architecture workspace for humans and agents.Try the live model
StructurizrDSL models with multiple views; local and server tooling.Teams that want architecture authored as text and reviewed with code.UXXU vs Structurizr
IcePanelCollaborative visual modeling, reusable objects and message flows.Teams that explain system behavior visually and review future designs.UXXU vs IcePanel
LikeC4Open-source architecture DSL with interactive views and documentation embeds.Teams that want architecture definitions in Git and custom documentation integration.UXXU vs LikeC4
Draw.ioGeneral-purpose diagram editing with C4 shapes and templates.Teams creating occasional diagrams alongside other visual documentation.UXXU vs Draw.io
ArchylC4 documentation with repository discovery, YAML authoring and drift checks.Teams evaluating code-connected documentation and architecture conformance.UXXU vs Archyl

Vendor descriptions reviewed October 1, 2026. Feature availability and pricing may change. Use the practical C4 tool evaluation guide.

Room for a useful first model

Start free. Pay when your model or team grows.

Free

€0

One user. Up to 400 architecture items. Unlimited projects and diagrams. No credit card required.

Start your free model →

Paid seats

€12 / seat / month

Or €120 per seat, billed annually. Unlimited architecture items, projects and diagrams. All paid seats include the same product functionality.

See pricing and billing details →

Architecture items include systems, actors, applications, containers, components, stores and groups. Diagrams are not counted as items. Paid prices exclude applicable taxes.

Questions before you choose a C4 tool

Is UXXU a free C4 diagram tool?

Yes. The free plan supports one user and up to 400 architecture items, with unlimited projects and diagrams. No credit card is required. Paid seats remove the item limit.

What is the difference between a C4 model and separate diagrams?

A model gives an element a shared identity. Reuse it across diagrams, and changes to its model properties appear wherever it is used. Each diagram remains a view with its own layout and audience.

Does UXXU support all four C4 levels?

UXXU has Context, Container, Component and Code (class diagram) views. Use only the levels your team needs. Deployment is a supplementary diagram that maps runtime instances to infrastructure; it is not the fourth C4 level.

Can I try an example without registering?

Yes. The public models on this page support interactive exploration without an account. Create a free account when you want to save and maintain your own architecture.

Can I generate a C4 model from a Git repository?

Repository analysis through codeToC4 is in early access, with a waitlist. It is intended to generate a starting model for human review. You can already model visually and use the UXXU MCP to work with an existing architecture.

Can AI coding agents read and update my C4 model?

Yes. UXXU exposes architecture tools through an organization-scoped MCP endpoint authenticated with an API key. A compatible client can inspect and update the model within the key’s permissions. See the MCP setup guide for supported connection requirements.

How do I choose between UXXU, Structurizr and other C4 tools?

Start with how your team maintains architecture. Test a shared-element rename, a cross-level review and a documentation embed. Compare visual collaboration, Git-based authoring, deployment options and the cost for your actual team size.

Try the workflow, then go deeper

Each guide includes a diagram, an interactive model or a downloadable example you can use in your own review.

Learning the notation first? Visit the C4 model educational hub.

Make your next diagram part of a model.

Start with one system, reuse its elements and add the views your team needs.