Operations

Access and delivery model

Least-privilege customer access with a narrow public demonstration boundary.

Documentation version 5.0.0 · 2026-09-07

Organizations and roles

A verified account belongs to one or more organizations. Owners invite engineers or viewers; engineers can open support requests; viewers can read entitled releases. Staff rights are not granted by self-registration or email domain.

Delivery

A valid, non-revoked, unexpired license is checked when a download link is created and again when it is used. Links are bound to the user and organization, expire after five minutes and are single-use. The archive hash is checked before delivery.

Public execution

Only two allowlisted, hash-bound engine functions are exposed. A separate subprocess accepts bounded JSON input; it does not execute submitted code, access arbitrary files or invoke a shell.

Operational responsibility

Production operators must configure HTTPS and email, restrict staff provisioning, protect the persistent volume, back up the database and review logs. This release is not a penetration-test certification.

Discuss a release-specific integration