sigMAX Enterprise

sigMAX Enterprise is the professional and managed edition of sigMAX.

It can provide hosted workflows, integration support, extended validation, professional packaging, operational assistance and managed deployment capabilities without changing the Core principles.

The Enterprise version is available at https://sigmax.build.

Relationship With Core

sigMAX Enterprise builds on the Core foundation:

contracts;
agreements;
deterministic generation;
WASM execution;
runtime primitives;
generated documentation;
validation;
drift detection.

They do not redefine Core. They extend the surrounding operational, governance and deployment experience.

When Enterprise Helps

Enterprise is useful when the project needs more than a local or self-managed generation workflow.

Typical cases include:

professional packaging and delivery review;
shared generation workflows for several users or teams;
managed runners or managed virtual machines;
private templates and controlled component registries;
extended validation before generated artifacts are accepted;
deployment assistance for Kubernetes or cloud-native environments;
stronger audit, governance and access-control requirements.

The goal is not to make Core less capable. The goal is to support teams that need managed operations, review gates, repeatability and assistance around the same contract-first model.

Professional Capabilities

sigMAX Enterprise may provide professional capabilities around delivery, packaging and operations.

Capability	Included
SaaS workflows	✅
Managed runners	✅
Managed VMs	✅
Kubernetes deployment	✅
Private templates	✅
Component registries	✅
Extended validation pipelines	✅
Professional packaging	✅
Operational assistance	✅
Commercial support	✅

Enterprise Capabilities

Enterprise usage may add stronger platform and governance features:

Capability	Included
Enterprise RBAC	✅
Audit logs	✅
Advanced governance	✅
Managed deployment policies	✅
Managed network boundaries	✅
Reverse proxy or ingress configuration	✅
Different storage solutions	✅
Private infrastructure integration	✅

Governance And Audit

Enterprise contexts usually need stronger answers to operational questions:

Question	Enterprise concern
Who changed an intent, contract or template?	User identity, review trail and approval history.
Which generator version produced an artifact?	Generation provenance and reproducible evidence.
Which artifact was deployed?	Release metadata, hashes, image tags and environment records.
Which validation failed or was waived?	Audit logs and explicit acceptance decisions.
Which runtime boundary is exposed?	Managed network, ingress and policy review.

These features should make the expected/effective model easier to operate at team scale.

Deployment Boundary

Enterprise deployment may include reverse proxies, ingress rules, managed certificates, private networking, Kubernetes resources, backup policies or storage integrations.

Those capabilities belong around the generated system. They should not blur the internal sigMAX rule: generated business logic still runs behind contracts, validated WASM artifacts and declared runtime primitives.

Contact

For professional or enterprise usage, contact IA86 Computer Consulting through the contact page or visit https://sigmax.build.

Boundary

These capabilities belong to sigMAX Enterprise.

They should not be presented as default sigMAX Core behavior. Core can run locally and expose its minimal Studio interface through Nginx, but reverse proxying, managed infrastructure and selectable storage solutions belong to Enterprise contexts.