Enterprise architecture
as code
Scapius compiles a plain-text model of your systems into consistent, filtered views. The model lives in git, changes are reviewed like code, and every diagram stays true to one source.
The diagram is already wrong
Architecture lives in exported pictures, and every change to the estate makes them a little more wrong. Everyone quietly stops trusting them.
Exported pictures
landscape_v3_final.pptx
exported 8 months ago
landscape_v3_final_FINAL.pptx
team drive, unclear
context-diagram.png
wiki, author left
Each copy aging separately.
A model that compiles
workspace.ea
Landscape
currentContainer view
currentThreat model
currentChange the model and every view follows.
Built for enterprise architects and platform teams who own the picture of how systems fit together.
Write the model, compile the views
Define systems, applications, and data in the Scapius DSL. The compiler turns them into views: the diagrams and dashboards your teams read, each one filtered, styled, and holding the layout you saved.
system core_banking "Core Banking" {description "Ledger and account management"criticality "Mission-Critical"app payment_api "Payment API" {owner "Payments Team"lifecycle { phase "Run" }}}data_object transaction_record "Transaction Record" {data_classification "Confidential"}payment_api writes transaction_record "Posts entries" {cardinality OneToMany}
How it works
Model
Write your estate in .ea files: capabilities, systems, apps, data objects, and the relationships between them. Plain text, in git, next to the work it describes.
Compile
The compiler validates the model against the grammar and your workspace configuration, then reports diagnostics with exact source locations.
Explore
Open the compiled views. Each one filters the model through inclusion rules, applies your styles, and keeps its layout across edits.
The toolchain
One compiler sits underneath everything: the editor, the views, and the command line all work from the same semantic model.
Your workspace
git.ea files and a manifest, versioned next to the work they describe.
Validating compiler
ANTLRA grammar-based parser turns .ea files into a semantic model of your estate. Errors come back as precise diagnostics with source context, so a broken model tells you what is wrong and where.
Compiled views
ViewsEach view selects part of the model through inclusion rules, applies your styles, and keeps its layout across edits.
Language server
LSPAutocomplete, live diagnostics, navigation, and formatting for the DSL in VS Code.
Command line
CICompile and check workspaces from the terminal. The same commands run in CI, so an invalid model fails the build.
Questions
How do I get it?
Scapius is in v1.0 beta and access starts with a conversation. Reach us through the GitHub organization and we will set you up.
Where does my architecture model live?
In your git repository, as plain-text .ea files. During the beta the whole toolchain, compiler, CLI, and API, runs where you run it, against files you control.
Do I have to use VS Code?
VS Code is the supported editor today, through our extension. The editor features are served by a language server speaking LSP, and the files are plain text, so any editor can edit them; you lose the completions and live diagnostics, not the model.
Does it replace my diagramming tool?
For architecture, that is the goal. You stop drawing diagrams and start compiling them: the model is the source of truth, and landscapes, container views, threat models, and dashboards are outputs. Drawing tools remain the right choice for everything that is not a model.
See it on your own estate
The fastest way to evaluate Scapius is to model one slice of your architecture in the beta: one domain, a handful of systems, one landscape view.