Clear answers about the runtime, the console, and what each plan is actually buying.
Straight answers on what is open source, what is hosted, what is self-hosted, and what the Growth console retains by default.
The runtime is offered as open source on GitHub. The hosted console, policy operations workflow, and enterprise deployment services remain part of the commercial plans.
The open-source runtime covers self-hosted evaluation, built-in detectors, SDK integration, Docker and Kubernetes deployment options, and local policy-file workflows.
Growth adds the hosted console for policy rollout, operational traces, and team workflows. Enterprise adds custom packaging, support, and the option to self-host the console as well.
The runtime stays in your infrastructure on every plan. ZNYX does not position Growth as a hosted runtime tier.
The Growth operating model is metadata-first by default. Hosted traces are intended to show identifiers, decisions, detector summaries, and latency rather than prompt and response bodies.
Yes. Enterprise can be packaged with both the runtime and the console self-hosted, with custom pricing and deployment planning.
Starter is the runtime-only path. Growth is for teams that want a hosted control plane. Enterprise is for organizations with custom deployment, procurement, or security requirements.
Not yet. Security and governance capabilities are implemented in the codebase today, but formal certifications, contractual SLAs, and published latency targets are on the roadmap rather than publicly attested. Reach out for Enterprise if you need a written commitment on any of these before published attestations are available.
Need a deployment answer, not a marketing answer?
Use pricing for plan selection and the technical docs for implementation details. For anything specific to procurement or architecture review, email support directly.