aklivity/zilla

Health v2 · maintenance only

Flags: no_license

Adoption not part of the score

1717 stars · 146 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

Zilla is a stateless, multi-protocol gateway for event-driven applications and AI agents, exposing Kafka and MQTT over HTTP, SSE, gRPC, MQTT, and WebSocket, and providing a governed MCP endpoint for AI agents. It is configured declaratively via a single zilla.yaml with shared routing, identity, authorization, schema validation, and telemetry.

Use cases

• expose kafka topics as rest apis
• bridge mqtt iot devices to kafka
• give ai agents a single governed mcp endpoint
• proxy grpc and server-sent-events to event streams
• secure kafka access with jwt auth and tls
• generate api gateway config from asyncapi or openapi specs
• route llm api traffic through one policy-enforced endpoint

When to choose

• you need non-kafka clients (browsers, iot devices) to consume or produce kafka events
• you want one gateway for both event streaming and AI agent/MCP traffic
• you prefer declarative, spec-driven (AsyncAPI/OpenAPI) gateway configuration
• you need protocol translation without writing custom bridges or middleware

When to avoid

• you need a simple reverse proxy for plain HTTP services only
• your stack is not JVM/Kafka-centric and you don't need protocol translation
• you require a managed SaaS gateway rather than self-hosted infrastructure

Facets

service · maturity active

api-gateway proxy routing middleware auth authorization websocket rpc streaming monitoring mcp llm-inference apis iot artificial-intelligence microservices backend web-development developer-tools security jvm self-hosted cross-platform cloud kafka mqtt grpc server-sent-events asyncapi openapi event-driven-architecture mcp-gateway event-gateway protocol-translation declarative-config messaging ai-agents docker kubernetes

Member repositories

For agents

markdown · JSON · MCP: product_card(name="aklivity/zilla")