sigMAX Core
sigMAX Core
Section titled “sigMAX Core”Core is the single-host edition of sigMAX. Docker Compose runs Host and Config on the same machine, and business WebAssembly executes inside the containerized runtime. Core is proprietary software; it is not an open source or community edition.
Compare with Pro Request access
Deployment model
Section titled “Deployment model”| Element | Core architecture |
|---|---|
| Deployment | Docker Compose on one host |
| Platform services | Host + Config on that same host |
| WASM execution | Inside the containerized runtime |
| Dedicated execution isolation | None; no separate executor VM |
| Runtime implementation inspected | Rust host with Wasmtime |
| Licensing model | Proprietary; access and delivery terms are provided separately |
This is the product deployment model. The services share the machine and its operating-system kernel through the container layer.
Execution boundary
Section titled “Execution boundary”Core does not isolate WASM execution in a dedicated VM or independent execution environment. The WASM engine still checks linear memory, imports and execution budgets. These are runtime controls within the container, not the VM boundary provided by Pro.
The inspected Rust implementation embeds Wasmtime in the runtime process. Its performance and safer instance policies control whether guest state can be reused. Neither policy creates a separate process or a VM for each invocation.
See WASM execution boundaries for the distinction between engine checks, instance reuse and deployment isolation.
Working with Core
Section titled “Working with Core”The capability catalog covers application services found in the implementation: PostgreSQL, MinIO files, Redis cache, reverse proxy and TLS, authentication, private VPN access and monitoring. Studio operates these selected extensions alongside contracts, generation and frontend content. Their availability in a delivered Core package depends on its configuration.
Core follows the same contract-first model as Pro:
- Define the application, component responsibilities and binary capabilities in contracts.
- Generate executable artifacts from validated structured pseudo-code.
- Compare the result recorded in agreements and inspect drift.
- Operate and observe the application within the Core deployment boundary.
Choose Core when a single-host deployment and its shared execution boundary fit the application. Choose Pro when the architecture requires Kubernetes and COS2000 execution in KubeVirt VMs.
Implementation and delivery status
Section titled “Implementation and delivery status”The inspected sigMAX_runtime sources contain the Rust runtime, Studio services and container orchestration through the Docker Engine API, with Docker and Podman support. They do not yet contain a verified Core Host + Config Compose distribution. Application topology management through the Engine API is distinct from packaging the Core platform with Compose.
This page defines the Core architecture; it does not advertise a ready-to-download Compose bundle, public image names or installation commands that have not been supplied. Consult deployment generation and access and editions for that distinction.
Core and Pro
Section titled “Core and Pro”| Criterion | Core | Pro |
|---|---|---|
| Platform | Docker Compose | Kubernetes |
| Host + Config | Same host | Kubernetes deployment |
| WASM executor | Containerized Rust runtime | COS2000 in a KubeVirt VM |
| Dedicated VM boundary | No | Yes, around the executor |
| Edition license | Proprietary | Proprietary |
Studio is an interface associated with the platform, not a third edition. The former Enterprise name is superseded by Pro.