Enterprise · Controlled and Regulated Environments

The same compiler.
Inside your perimeter.

DevMatrix runs as a hosted service by default. When a security boundary, a regulator or an auditor requires something else, the deployment model and the evidence follow — without a second product and without a second compiler.

Deployment Models

Cloud SaaS is the default. The other three follow your perimeter.

The hosted console at devmatrix.dev is where DevMatrix runs unless something says otherwise. Self-hosted, air-gapped and hybrid exist for organizations whose security boundary requires the compiler to run inside it.

Cloud SaaS

devmatrix.dev

The default. Author specs and compile through the hosted console — no infrastructure to run, and the same compiler as every model below.

Self-hosted

Your Kubernetes / OpenShift

For organizations whose security boundary will not let the work leave it. The compiler runs on your cluster; specs and emitted artifacts never cross your network.

Air-gapped

Zero external network

For perimeters with no external network at all. A signed compiler image runs the build pipeline fully offline — defense, banking core, classified workloads.

Hybrid

SaaS authoring + on-prem compile

Keep the hosted authoring experience and move only the compile. Specs are written in the SaaS console; compilation is routed to a controlled runner inside your perimeter.

Regulated industries

The domain lives in the specification, never in the compiler.

A regulated platform is not a different product here. It is the same compilation, with the obligations written down where they can be checked.

The compiler has no industry in it

No hardcoded assumption about banking, healthcare, fintech or logistics anywhere in the compiler, its intermediate representation or its passes. The same compiler produces a PCI-DSS ledger, a health platform or a logistics backbone purely from differences in the specification.

Your frameworks are declared, then checked

A platform names its compliance profiles in its own specification. Each name is validated against a closed registry before compilation starts — an unregistered framework is rejected at authoring time, with the reason, rather than silently producing a build nobody can sign.

Your perimeter decides where it runs

Self-hosted, air-gapped and hybrid keep specifications and emitted artifacts inside your network. The choice changes where the compiler executes, never what it emits.

Evidence is emitted, not assembled afterwards

Every compile produces its own evidence pack as part of the build. Nothing is reconstructed for an audit months later from commit history and memory.

The registry of accepted compliance profiles, and every attribute a profile can declare, is documented in the DMX language reference

Evidence-ready by construction

The auditor arrives and asks where this line of code came from.

In most organizations that opens weeks of archaeology. Here the answer is a file: every emitted line traces to its specification node, and any third party can rebuild the artifact from the specification plus the compiler version.

SBOM · CycloneDX 1.5

Component inventory of every emitted dependency, signed and timestamped per build.

Source Map · IR ↔ Code

Every emitted line traced to its DMX spec node. Auditor-grade traceability.

Replay Certificate · Ed25519

Cryptographic proof the build is reproducible from the spec + compiler version.

Build Fingerprint + Merkle Root

Byte-deterministic hash tree over the full artifact tree.

Threat Model

Auto-derived from the IR. Lists assets, trust boundaries, and mitigations.

Capability Manifest

Declared capabilities (auth, RLS, encryption, rate limiting…) wired into the build.

Compliance Report

Per-spec dossier of controls covered, gates passed, and unresolved waivers.

Audit Trail

Append-only event log of every compilation, signed and tamper-evident.

Maps to the controls your auditors cite

SOC 2 Type II
CC7 / CC8 — change management + system operations
PCI-DSS v4
Requirement 6 — secure development + change control
DORA Article 9
Digital operational resilience + ICT change management
EU Cyber Resilience Act
Annex I — component inventory + integrity
NIS2 Directive
Supply-chain controls + incident reporting
SOX § 404
IT general controls — change + access management

DevMatrix holds no certification or attestation under these frameworks and does not claim one. What it produces is the structural evidence an assessment consumes — the inventory, the traceability, the reproducibility proof and the control coverage listed above. The assessment itself is your auditor's.

Every way in is a technical one.

No discovery call before the engineering. Pick the door that matches what you still need to know.

Request a technical review

The reference build, its output, and its evidence pack — walked through by an engineer.

Review your case

Your system, your timeline, your regulatory framework.

Read it before you talk to anyone

Breaking the Compiler Wall: the intermediate representation, deterministic generation, compile-time quality assurance and the compliance artifacts.

Request Technical Review
Tell us about your organization and use case, and we’ll review your application.

Already have an account? Sign in