Archally Features & Capabilities

Discover how Archally transforms your architecture documentation into a living blueprint that evolves with your system.

v2.6 Schema Version March 2026
30+ Entity Types Concepts, operations, rules, decisions, stories, quality, org, roadmaps, value streams
Typed IDs ID System CMD###, EVT###, QRY###, SR###, D###, US###, VS### — traceable cross-references
4+ Output Formats OpenAPI 3.1, AsyncAPI 3.0, OpenRPC, Arazzo, JSON Schema
5 Viewer Modes Complete, Layers, Concepts, Domain, Architecture
11 Example Projects E-commerce, oil & gas, real estate, podcast studio, and more

Product Timeline

View Full Changelog →
Blueprint Designer 0.1 Released
  • Core DSL syntax
  • Context map diagrams
  • Basic code generation
Blueprint Designer 0.2 Coming Soon
  • Enhanced visualizations
  • Test generation
  • Decision tracking
Model

Capture your system as a typed blueprint

Define domains, operations, rules, decisions, and quality attributes in structured YAML. One model becomes the single source of truth for everything downstream.

Domain-Driven Design Schemas

Model bounded contexts, aggregates, entities, commands, events, queries, and domain stories using typed YAML schemas. Each element carries an explicit ID (CMD001, EVT001, QRY001) for cross-referencing across the entire blueprint.

Business Rules & Decisions

Capture invariants, state transitions, and governance rules alongside the model. Architecture Decision Records link motivation to implementation — so when someone asks "why was this designed this way?" the answer is traceable.

Quality Attributes & Governance

Define SLOs, SLAs, security policies, compliance requirements, and observability expectations as structured model data — not prose in a wiki. Quality attributes travel with the operations they govern.

User Stories, Use Cases & Roadmaps

Express requirements as user stories (US###), use cases (UC###), and milestones (MS###) directly within the blueprint. Delivery priority, personas, and acceptance criteria live next to the architecture they describe.

Value Streams & Motivation

Map end-to-end value delivery flows (VS###), goals, risks, assumptions, and evidence chains. The motivation layer connects business intent to technical design — visible and reviewable in one place.

Organizational Structure

Model parties, departments, teams, and ownership alongside the technical architecture. Know which team owns which bounded context, which department sponsors which service, and who to contact when contracts change.

Visualize

Explore your system interactively

Two complementary viewers render the same model for different audiences — architects navigating the full ontology, and domain experts collaborating through Event Storming.

Blueprint Viewer

An interactive graph of your entire system — bounded contexts, operations, dependencies, and contracts — rendered with layout algorithms and domain clustering. Navigate, filter, and zoom across thousands of entities.

Layered Views

Switch between focused perspectives: design concepts, domain operations, architectural structure, or the complete ontology. Each view is a projection of the same model — no separate diagrams that drift.

Event Storming Viewer

The same blueprint, translated into DDD Crew-style Event Storming diagrams. Choose Big Picture, Process, or Software Design level. Domain experts and developers collaborate on the same visual language.

As-Is / To-Be Comparison

View your system at any migration state — the current baseline, a proposed future, or any point in time. Diff visualization highlights what changed, what moved, and what broke between states.

Desktop & Web Deployment

Run the viewer as a native desktop app (Tauri — fully offline, ~5-10MB), a standalone static site for team sharing, or a local dev server. The same experience, three deployment modes.

Generate

Produce specifications from the model

One blueprint generates multiple contract specifications in industry-standard formats — consistent by construction, not by manual effort.

OpenAPI 3.1

Generate REST/HTTP API specifications directly from blueprint operations. Paths, schemas, security definitions, and error responses are extracted from the model — including Problem Detail error formats.

AsyncAPI 3.0

Generate event and messaging contract specifications from domain events. Topics, routing keys, payload schemas, and broker configurations are derived from the operations and their exchange protocols.

OpenRPC & Arazzo

Generate JSON-RPC service specifications (OpenRPC) and workflow orchestration specs (Arazzo) for services that go beyond REST. The model captures the protocol; the generator produces the right format.

Data Models & Test Cases

Extract shared JSON Schema components, infrastructure topology, quality metrics, domain stories, and test scenarios — all from the same model. Each generated artifact is consistent with every other.

Evolve

Track changes as structured migrations

When your system changes, express the change as a migration — with structured diffs, rationale, and regenerated artifacts. The model stays current because it is how changes are planned.

Migration Change Sets

Express changes as structured add, modify, or delete operations on any entity type — concepts, operations, rules, contracts, or infrastructure. Each migration carries a date, status, description, and rationale.

Point-in-Time Snapshots

View the system at any migration state. Compare the architecture before and after a change — see exactly which entities, dependencies, and contracts were affected.

Version History in Git

The blueprint lives in your Git repository alongside your code. Branching, merging, and code review apply to architecture decisions the same way they apply to implementation.

See these capabilities in action

Explore real demos at enterprise scale, or discuss how these capabilities apply to your team's challenges.