Pricing
Priced on Gateway count
Start free with the open-source gateway. Add support and enterprise identity when you go to production. Bundle the management layer at enterprise scale. No per-seat charges. No throughput metering.
Community
Zilla Gateway, open core. Run it yourself on any infrastructure.
Free
Unlimited gateways, self-managed.
All protocols: HTTP, MQTT, gRPC, WebSocket, SSE, TCP, TLS
JWT guards, TLS, schema validation, Prometheus and OTLP
Kafka: protocol mediation to and from Kafka, for non-Kafka clients
AI and MCP: MCP gateway, spec-driven tools from OpenAPI, tool discovery
Community support via GitHub and Slack
Aklivity Community License (source-available)
Plus
Zilla Plus Gateway. Hardened builds, enterprise identity, and support under SLA.
Contract
Per gateway. No minimum.
Everything in Community, plus:
OAuth, API keys, and vendor IdP guards including Azure AD
Hardened AMI and container images, Secrets Manager, CloudWatch, Syslog
Kafka: Kafka-native client proxying, secure public and private access, virtual clusters, AWS MSK, Confluent Cloud, Redpanda
AI and MCP: per-user identity on every tool call, semantic tool search, auto-sized eager tool sets, multi-node MCP sessions
Gold support: 12x5 coverage, 8-hour response
Zilla Console available as a flat-rate add-on
Enterprise
Zilla Plus Gateway with the Zilla Console management layer bundled in.
Contract
Per gateway. From 8 gateways.
Everything in Plus, plus:
Zilla Console management layer, bundled
API and Data Product catalog
Self-service developer portal
Governance, audit, and RBAC
Platinum support: 24x7 coverage, 2-hour response, named TAM
On-premises and air-gapped deployment

The Model
Two layers. Three tiers.
Every tier is built from the same two pieces. Layer A is the Zilla Gateway data plane, which serves the Kafka and MCP use cases. Layer B is the management layer: the Zilla Console, and the governance capabilities that sit on top of it.

Compare
Compare Tiers
One gateway, one meter, two ways to deploy it. The capabilities you need depend on which.


FAQ
Pricing Questions
Same engine. Zilla Gateway is the open-core build, source-available on GitHub, and you run it yourself. The headline difference is Kafka-native client proxying, which is Plus only. Plus also adds hardened AMI and container images, enterprise IdP and SSO integrations, and support under SLA.
Contract-based, on deployed gateway count. There is no per-user or per-seat charge, and no throughput or connection metering. Add a gateway and the price moves. Add a hundred users and it does not. The one item not priced per gateway is the Zilla Console add-on at Plus, which is a flat rate.
One standalone deployed instance, running as a VM, an AMI, or a container. Instances are counted individually, not grouped by cluster or environment. An HA pair is two gateways. A three-node scale-out group is three. You can price a deployment off your own architecture diagram.
Gold ships with Plus: 12x5 coverage, 8-hour response on Severity 1, and 1 business day on Severity 2. Platinum ships with Enterprise: 24x7 coverage, 2-hour response on Severity 1, 4 hours on Severity 2, and a named Technical Account Manager. Both include chat, email, phone, and the self-service portal.
Start with Community. The MCP gateway is open source: spec-driven tools from your OpenAPI specs, tool discovery, and the full MCP surface, with JWT authentication. Move to Plus when the catalog or the user base grows. Four capabilities are Plus: per-user identity on every tool call, semantic tool search, eager tool sets sized automatically, and MCP sessions served across a multi-node cluster. Enterprise is built around the Zilla Console, which manages Kafka. If you are not running Kafka, Plus is normally where you land.
Community does protocol mediation to and from Kafka. Non-Kafka clients speaking HTTP, MQTT, gRPC, WebSocket, or SSE reach Kafka through the gateway, with schema enforcement and identity applied at the edge. What Community does not do is proxy Kafka clients to Kafka. Kafka-native client proxying is a Plus capability: a Kafka client connects to Zilla Plus Gateway under your own domain, and Zilla Plus fronts the cluster with TLS, SASL, mTLS, API keys, and per-client rate limits enforced at the edge.
Yes. Every deployed Zilla Plus Gateway instance counts, in every environment. There is no production and non-production distinction. If you do not need Plus features outside production, run Community in dev and test at no cost. Same engine, self-managed.
Yes. At Plus the Console is an orderable add-on at a flat rate. It does not scale with gateway count. At Enterprise it is bundled into the tier, so there is no separate line. Adding the Console to Plus is not the same as buying Enterprise. Four capabilities stay Enterprise only: the API and Data Product catalog, the self-service developer portal, governance with audit and RBAC, and enterprise support workflows.
No. The gateway runs standalone in the Layer A data plane. The Zilla Console is Layer B, and it is optional at Plus.
Plus is the supported gateway. Kafka-native client proxying, managed-Kafka support, enterprise identity and schema-registry integrations, shared state across instances, Gold support, and the Console as a flat-rate add-on. Priced per gateway with no minimum, self-serve on AWS Marketplace. Enterprise adds the governance layer: the API and Data Product catalog, the self-service developer portal, and governance with audit and RBAC. It bundles the Console, upgrades support to Platinum with a named TAM, adds on-premises and air-gapped deployment, starts at 8 gateways, and is sold through a Private Offer.
Plus is available on AWS Marketplace as pay-as-you-go, including a free trial, or as a Private Offer. Enterprise is Private Offer only. Community needs no purchase. Clone it from GitHub.

Ready to get started?
Get started on your own, or request a demo with one of our real-time data experts.
Explore pricing
Straightforward, usage-based pricing with no per-connection surprises — start free and scale when you are ready.
Join the Community
Trade notes with the engineers running Zilla in production, and get help from the team in Slack or Discord.
