Skip to content

FAQ

Not directly as unchecked final code. It produces controlled representations that deterministic generators and validators can process.

sigMAX Core is the open source foundation of sigMAX. It provides contracts, agreements, deterministic generation, WASM execution, runtime primitives, validation, drift detection, generated documentation, and a minimal Studio interface.

Yes. Core is intended for local, open source and self-managed usage. It is not a managed SaaS platform by itself.

sigMAX Enterprise is available at https://sigmax.build.

Is sigMAX Enterprise the same thing as sigMAX Build?

Section titled “Is sigMAX Enterprise the same thing as sigMAX Build?”

Yes. The professional product name is sigMAX Enterprise. The public URL is https://sigmax.build, but the edition should be described as sigMAX Enterprise.

Enterprise adds professional and managed capabilities around Core, such as hosted workflows, managed runners, Kubernetes deployment, ingress configuration, Traefik or equivalent reverse proxy support, extended storage, RBAC, audit logs, governance and commercial support.

Studio is the name of the sigMAX interface. Core includes a minimal Studio interface for local inspection, while the full Studio experience belongs to professional and Enterprise contexts.

Core includes a lightweight Studio interface and FrontMark-based content exposed through Nginx. It should not be described as a generated full application frontend.

No. In Core, Nginx exposes the lightweight Studio interface and FrontMark content. Reverse proxying generated services belongs to Enterprise-style infrastructure, where tools such as Traefik may be used.

No. Dapr can be used internally. Public exposure should stay narrow and intentional.

Not by assumption. Core should remain explicit about what is implemented.

Does Core provide multiple storage choices?

Section titled “Does Core provide multiple storage choices?”

No. Core should not be described as offering a menu of selectable storage products. Extended storage choices such as MinIO belong to Enterprise contexts when the architecture requires them.

No. Redis is not a default Core dependency. It may be introduced in Enterprise or specific deployment architectures when required.

Runtime primitives are explicit host capabilities exposed to WASM modules. They allow controlled access to inputs, responses, ObjectIR-like output, logs, metrics, JSON helpers, HTTP calls, secrets, state and other bounded runtime operations.

The host runtime primitives are implemented in Rust. The C-compatible part is the c_repr binary layout used to exchange selected typed values with WASM modules.

WASM provides a portable and isolated execution target. It helps keep generated business logic inside a controlled sandbox with explicit imports and runtime capabilities.

ObjectIR is the structured object representation used for typed business data, API responses, validation payloads and event-like runtime state.

DocIR is the document-oriented representation used for generated documentation, reports, pages and rendered outputs.

The separation keeps business state and rendered document state traceable without mixing presentation concerns into structured runtime data.

An Agreement represents the effective state after generation, validation or execution. It is used to compare what was actually produced with what the contract expected.

Generative drift is the divergence between intended architecture and produced artifacts. sigMAX uses contracts, agreements and validation to make this drift detectable.

FrontMark is the enriched Markdown layer used for documentation and lightweight frontend content. It supports patterns inspired by MkDocs Material, such as admonitions, tabs and diagrams.

Astro assembles the documentation site and static routes, Svelte provides interactive islands, and Vite provides the frontend development and bundling layer.