6 compilation phases, 250+ quality gates, technology targets and a closed taxonomy of 23 concerns.
A multi-phase compilation pipeline — like LLVM for enterprise systems. Seven deterministic stages transform a DMX specification into verified, deployable infrastructure.
Define system architecture in DMX — entities, APIs, data flows, security policies, infrastructure topology.
Syntax and correctness verification. Every reference, type, and constraint checked.
100+ cognitive passes across 6 phases. Pure IR transforms — no side effects, fully deterministic.
200+ emitters targeting Python/FastAPI, SQL, Docker, infrastructure, with Java/Spring Boot in testing. Next.js/React frontend is on the 2027 roadmap.
250+ quality gates: BLOCK (fatal), WARN (advisory), INFO (telemetry). OWASP-aligned security checks, performance checks, compliance mapping.
1,000+ generated tests per microservice across four tiers — contracts, behavior, security, enterprise. Nothing reaches the evidence pack unproven.
Test evidence, CycloneDX 1.5 SBOM, Source Map IR↔code, Build Fingerprint + Merkle root, Ed25519-signed Replay Certificate.
Define system architecture in DMX — entities, APIs, data flows, security policies, infrastructure topology.
Syntax and correctness verification. Every reference, type, and constraint checked.
100+ cognitive passes across 6 phases. Pure IR transforms — no side effects, fully deterministic.
200+ emitters targeting Python/FastAPI, SQL, Docker, infrastructure, with Java/Spring Boot in testing. Next.js/React frontend is on the 2027 roadmap.
250+ quality gates: BLOCK (fatal), WARN (advisory), INFO (telemetry). OWASP-aligned security checks, performance checks, compliance mapping.
1,000+ generated tests per microservice across four tiers — contracts, behavior, security, enterprise. Nothing reaches the evidence pack unproven.
Test evidence, CycloneDX 1.5 SBOM, Source Map IR↔code, Build Fingerprint + Merkle root, Ed25519-signed Replay Certificate.
One DMX specification, full-stack output across languages, frameworks, and infrastructure.
The compilation layer that transforms declarative specifications into verified, production-grade infrastructure. Every component below operates deterministically.
Each concern declares one technology in the spec; the compiler dispatches to the matching plugin. Default plus registered options below — and your own plugin extends any concern without a compiler fork. No vendor lock-in.
Register a plugin for any concern. The compiler dispatches automatically.
A build refuses to ship if a declared concern has no matching plugin.
The supported surface is a closed, versioned taxonomy — not a moving target.
The same data, read as what your current setup is missing rather than as a scoreboard.
| Dimension | With DevMatrix Assistants + deterministic compilation | Code assistants alone Copilot · Cursor · Claude Code | AI App Builders Lovable · Replit · v0 | Autonomous Agents Devin · Cognition | Internal AI Factories Globant Magnifai · Accenture myWizard |
|---|---|---|---|---|---|
| Output determinism | Byte-identical · same spec → same code | Probabilistic per completion | Non-deterministic per prompt | Non-deterministic per run | Opaque · vendor-controlled |
| Signed evidence pack | SBOM · Replay Cert · Merkle · Source Map | None | None | None | Vendor reports · not standardized |
| Audit traceability (IR ↔ code) | Every line traced to spec node | None | None | Logs only · not signed | Internal · not externally verifiable |
| Multi-language emission | Python · Java · Next.js · plugin-registered | Any (probabilistic) | Locked to vendor stack | Any (probabilistic) | Vendor-dependent |
| Closed-taxonomy / BYO plugins | 23 concerns · Plugin Registry | N/A | Vendor stack only | N/A | Vendor-bound |
| Multi-spec orchestration | Platform / Service / App hierarchy + cross-contract closure | File / function scope | Single-app scope | Ticket scope | Vendor-specific |
| Air-gapped deploy | Supported · signed image | GHE / Cloud only | Vendor cloud | Vendor cloud | Possible · negotiated |
| IP ownership | Spec + compiler version + emitted source all yours | Generated text yours · model not | Code yours · platform lock-in | Generated code yours · model not | Code yours · platform lock-in |
| Compliance posture (SOC 2 / PCI / DORA / EU CRA) | Evidence pack maps directly to controls | Vendor SOC 2 only | Limited | Limited | Vendor attestations |
| Reproducibility for auditors | Independent replay from spec + version | Not reproducible | Not reproducible | Not reproducible | Vendor-mediated |
DMX is a purpose-built specification language for declaring complete software platforms. One .dmx file describes entities, APIs, business flows, sagas, state machines, security policies, and infrastructure — the compiler handles the rest. Write directly (zero LLM) or use LLM-assisted authoring with critic validation. The spec is the auditable source-of-truth: every regenerated artifact is byte-identical and signed.
service "accounts" { version = "1.0.0" port = 8002 api_prefix = "/v1" database = "ledger_accounts_db" compliance ["SOC2", "PCI-DSS", "DORA"] depends_on { identity imports [Tenant, Customer] }}entity Account { @aggregate_root @tenancy(tenant, tenant_id) @soft_delete id UUID @pk @default($computed.uuid) tenant_id UUID @fk(Tenant.id) @not_null owner_id UUID @fk(Customer.id) @not_null iban String(34) @unique @sensitive currency String(3) @iso4217 @not_null balance Money @not_null @default(0) status Enum(ACTIVE, FROZEN, CLOSED) @default("ACTIVE") opened_at DateTime @default($computed.now)}api { POST "/accounts" { permissions = ["accounts:open"] request { owner_id UUID @required currency String(3) @required } response @entity(Account) @status(201) } POST "/accounts/{id}/freeze" { permissions = ["accounts:freeze"] triggers = Account.status -> FROZEN response @entity(Account) }}Declare how services in a platform talk to each other — synchronous HTTP, asynchronous events (message brokers are planned, not available today), or orchestrated sagas with transactional outbox. The compiler emits client, server route, broker wiring, and the compensation paths.
platform "LedgerPlatform" { modules { identity { spec = "identity.dmx" } accounts { spec = "accounts.dmx" } payments { spec = "payments.dmx" } audit { spec = "audit.dmx" } } // Sync HTTP — accounts resolves customer within its own request interactions { "I-10: Accounts resolves customer" { tier = 1 provider = identity consumer = accounts trigger = http(method="GET", path="/customers/{id}") response_schema = CustomerDTO timeout_ms = 500 idempotent = true } // Saga — atomic money transfer with compensation "I-11: Transfer saga" { tier = 1 orchestrator = payments participants = [accounts, accounts] trigger = saga("transfer.requested") steps = [debit_source, credit_target, settle] compensation = [reverse_credit, reverse_debit] outbox = true } // Async event — audit logs every state transition "I-12: Transfer audited" { tier = 2 producer = payments consumer = audit trigger = event("payments.transfer.settled") payload { transfer_id UUID @required } } }}Loading verified availability…