Viaduct

Viaduct

Clarity at every level.

One architecture model. Connected knowledge. Shared context for your team and AI agents.

Start free. No account required.

Context: System boundary. Containers: Services and APIs. Components: Business logic. Code: Implementation
01A system, seen as a whole.ContextContainersComponentsCode

Every connection.In context.

Follow a request from the system boundary to the API contract. Keep documentation where it belongs.

From an empty canvas to a connected architecture.

Viaduct + MCP

Give your agentsthe whole picture.

Architecture, contracts and decisions — available as working context.

How the MCP server and change sets work

Which service owns account limits?

Accounts API
GET /accounts/{id}
LimitPolicy

What the agent reads back over MCP

  1. Model
  2. Change set
  3. Commit evidence

Build from shared understanding.

Open the editor
Answered before you have to ask

What does it cost?

Nothing. Viaduct is free — every level, the MCP server, collaboration and change sets included. There is no trial that ends and no feature held back behind a plan. If you want the work to continue you can donate, and that buys nothing but the work continuing.

What is the AI assistant, and what does it cost me?

It writes the parts of a model people leave blank: descriptions for elements that have none, names for unnamed flow steps, and a review of the whole model that points at real elements rather than giving generic advice. It runs on our provider, so there is no key to obtain and nothing to configure, and every account gets a monthly allowance of it. Nothing it suggests is applied on its own — you see the text and press a button, or you do not.

Do I need an account?

Not to draw. The editor opens with a sample model and works entirely in your browser, where the model stays on your machine and never reaches our servers. An account is for the things a browser cannot do alone: keeping a project across devices, sharing it with your team, and serving it over MCP.

Where does my architecture live?

On servers inside the EU, along with the backups. Without an account it lives in your browser and nowhere else. Either way you can export the whole model as JSON, and any container’s contracts as an OpenAPI document, whenever you like.

What can an AI agent do with it?

Read the model and write to it: Cursor, Claude Code, Claude Desktop or any other MCP client can ask what talks to what and over which contract, and can add services, endpoints, connections and documentation back. Access needs a personal token you issue yourself, scoped to your projects, and revoking it ends the access immediately.

How is this different from a diagramming tool?

A diagram is a picture; this is a model. An element exists once and appears on every level it belongs to, so a rename or a new dependency shows up everywhere at once. The endpoints on a container are a real OpenAPI document, not labels on a box — which is what makes the whole thing readable by something other than a person.

Can I bring what I already have?

Import an OpenAPI specification and the endpoints land on the container with their parameters, request bodies and responses. Models export and import as JSON, so moving a workspace — or keeping a copy outside this service — is a file.