Architecture

The architecture is deliberately split between enforcement and operations.

This split matters for both engineering and procurement. The runtime handles enforcement where your application runs. The console handles policy workflow and operations only when your team needs that layer.

Runtime

Self-hosted on every plan

The runtime is the enforcement layer. It evaluates requests inside your environment and can run without the console on Starter.

Lives in your infrastructure
Exposes input, output, tool, and streaming evaluation endpoints
Loads local policy or connects to a console-managed policy workflow

Console

Growth / Enterprise

The console is the operating layer. It is where policies, traces, and team workflow are coordinated when you need more than local files.

Hosted by ZNYX in Growth
Optionally self-hosted in Enterprise
Designed around operational metadata by default in the hosted model

Request flow

Your application sends a prompt or tool request to the runtime.
The runtime resolves the policy for the given tenant, app, agent, and environment scope.
The runtime returns an allow, block, redact, warn, or transform decision.
Your application calls the model only after the input check passes.
Your application evaluates model output again before it is returned to the end user.

What belongs to the runtime and what belongs to the console.
Responsibility	Runtime	Console
Runs in customer infrastructure	Yes	Optional in Enterprise only
Evaluates live traffic	Yes	No
Stores local policy files	Yes	No
Coordinates policy workflow	No	Yes
Provides operational traces	Emits events	Stores and organizes them
Required on Starter	Yes	No

Architecture note

Growth is self-hosted runtime plus hosted console. Enterprise keeps the same architecture but gives you the option to place the console inside your boundary as well.

Deployment Patterns Compare Plans