No. sigMAX is proprietary software. Its two editions, Core and Pro, are distributed under the terms supplied with the product. Public documentation and the use of third-party dependencies do not make sigMAX open source.

Core is the Docker Compose edition. Host and Config run on the same host, and WASM execution takes place in a container. Core has no dedicated isolation boundary for code execution.

Pro is the Kubernetes edition. It uses COS2000 as the WASM executor inside a virtual machine managed by KubeVirt. The VM separates the execution environment from the host services.

No. WASM memory rules and explicit imports constrain module behavior, but they are different from an infrastructure boundary. Core runs code in its container deployment on the same host as Host and Config. Pro adds the COS2000 VM boundary through KubeVirt. Neither topology eliminates the need to validate artifacts and configure permissions and resource limits.

No. The product has two editions: Core and Pro. Enterprise is an older name in the documentation. Studio refers to an interface, not a third edition or a separate execution topology.

See access and editions information and contact sigMAX for evaluation and deployment terms. The documentation does not promise anonymous repository access, public binary downloads, pricing or support commitments.

No. Core uses Docker Compose on one host. Kubernetes and the COS2000/KubeVirt execution model belong to Pro.

No. Pro identifies the Kubernetes and VM execution architecture. Hosting, support, storage backends, observability services and operational commitments depend on the package and deployment agreed for the project.

Host handles application requests and runtime-side capabilities. Config manages runtime configuration and artifact distribution. The runtime reference describes their interfaces and their relationship with the executor.

The intended generation flow uses controlled representations that deterministic generators and validators can process. LLM output should not become trusted executable code without validation. See LLM Boundaries.

Primitives are named interfaces between WASM logic and runtime capabilities, such as inputs, responses, structured data and allowed service calls. Their supported names, ABI and policy checks depend on the executor and runtime version. See Primitives.

WASM provides a portable binary target with explicit imports and exports. The edition determines where that binary executes: a container for Core or COS2000 in a KubeVirt VM for Pro. See WASM execution boundaries.

Yes. The implementation includes a PostgreSQL storage service with declared operations and schema tools, and MinIO file storage with named buckets and versioning. WASM code calls authorized host interfaces; it does not receive direct SQL connections or unrestricted filesystem access.

The project extension registry includes Traefik for reverse proxy and TLS, Authentik for identity, Redis for application cache, WireGuard for VPN access, and a monitoring stack. These services are selected and configured per project. See platform capabilities, networking and runtime integrations.

COS2000 is an operating system with its own network stack, native primitives, Radjae compiler, module publication API, local administration tools and execution diagnostics. It can call permitted external APIs and storage adapters. Its cache and local RAM workspace are temporary; persistent databases and object stores remain external services. Explore COS2000.

ObjectIR represents structured business data. DocIR represents document-oriented data for rendering. The distinction keeps business values separate from their presentation; support must be checked against the runtime and artifact version in use.

An Agreement records effective state after generation, validation or execution. Comparing this evidence with a Contract helps detect missing artifacts and other differences between intended and produced behavior.

Generative drift is the divergence between intended architecture and produced artifacts. Contracts, validation and agreement evidence make that difference inspectable.

FrontMark is the enriched Markdown layer used for this documentation and lightweight frontend content. Astro assembles the site, Svelte supplies interactive components, and Vite supports development and bundling. These frontend tools do not determine the Core or Pro execution boundary.