Your cluster.
Your evidence.
Run InfernoSIM jobs inside your AKS cluster, with inputs and evidence in your storage. Add a shared operating model for the same open-source test engine.
Execution stays
in your AKS cluster.
The operator creates simulation Jobs. Your configured Workload Identity connects those Jobs to your input and evidence storage.
Blob or PVC inputs
One-off runs or schedules
Workload Identity
Blob or PVC outputs
Your application command, dependencies and Azure services may make network requests according to your configuration. Configurable network restrictions do not imply that every possible external call is blocked.
Choose the operating
controls you need.
Core capture, replay, contract checks and agent reliability stay free in the open-source engine. Azure pricing covers the installed commercial extension.
| Capability | Open source | Azure Pro | Azure Enterprise |
|---|---|---|---|
| Capture, replay, fault injection, contract and agent checks | Included | Same engine | Same engine |
| Local execution & CI reports | Included | Included | Included |
| AKS one-off & scheduled simulation Jobs | Self-managed integration | Included | Included |
| Workload Identity, Blob/PVC inputs & evidence | Self-managed integration | Included | Included |
| Azure evidence-manifest verifier | Not an engine feature | Included | Included |
| Namespace policies & governance | — | — | Included |
| Entra group access bindings | — | — | Configurable |
| Network restrictions | Environment-controlled | Environment-controlled | Product configuration options |
| Operator replicas & disruption budget | — | Single operator | Multiple replicas & configurable budget |
| Submitted USD rate | Free · MIT | $0.41 per installed cluster-hour | $2.05 per installed cluster-hour |
| Example: 730 installed hours | — | $299.30 | $1,496.50 |
The 730-hour examples are not fixed monthly prices. Charges depend on installed cluster-hours, not test count. Infrastructure, taxes and external API/model costs are additional. Final availability, currency and charges follow the Marketplace offer when available.
Configuration is a start.
Validation is your next step.
Understand the boundary between product options, your Azure environment and the tests already performed.
Evidence integrity
The verifier detects file changes relative to a SHA-256 manifest. Hashes are not digital signatures or compliance certification. Protect evidence and manifests with your access and retention policies.
Enterprise controls
Namespace rules, identity bindings and network settings are configuration capabilities. Private Endpoint and customer-managed-key declarations do not provision or independently verify Azure controls.
Resilience and scope
Multiple replicas and a disruption budget need suitable cluster placement. They do not establish zone-failure tolerance. Marketplace lifecycle and billing still require validation through that flow.