One event backbone. Zero hardcoded providers.
Any event source. Any business outcome. One platform. Here is the full multi-tenant, Kubernetes-native stack under every ready automation.
Connectors
- Stateless HTTP calls
- Lightweight, zero cold start
- REST / GraphQL / Webhooks
Agents
- Isolated K8s pods
- Long-running, stateful
- AI / LLM / Messaging
The full platform stack
Eight layers, one contract. Each layer is independently deployable and observable — and every request ultimately routes through the CloudEvents backbone.
Visual for operators, code for developers.
Auth, org-scoping, and the API every surface speaks to.
Matches events by pattern, cron, or webhook and runs the graph.
The one contract every integration speaks. Highlighted because everything routes through it.
Connectors call APIs; agents reason in isolated pods. Same packs power both.
Containerizes and deploys agents into isolated tenant namespaces.
Relational state, time-series event history, cache, and agent memory.
Multi-tenant cluster with encryption, network policies, and full observability.
What the stack gives you
CloudEvents Gateway
Every event source — webhooks, schedules, databases, messaging, APIs — normalized into the CloudEvents 1.0 contract on a Kafka backbone, so templates orchestrate across tools without custom glue.
TypeScript Agent SDK & CLI
Build and ship agents in TypeScript. Scaffold with init, run locally, and deploy with push — pure HTTP, no local Docker required.
Visual Workflow Builder
A visual drag-and-drop builder on a Prefect engine — 42 node types (switch, filter, loop, transform, HTTP, run-agent, connector-action, human-task, and more) plus live execution history.
Schema-as-Contract Connectors
Integrations are data, not code. Each connector is a versioned pack validated against a canonical, API-served schema before it can ship — the catalog scales without touching the core.
Real-Time & Observable
WebSocket live updates with auto-reconnect, plus OpenTelemetry, Prometheus metrics, Grafana dashboards, and a token-free public status page.
Multi-Tenant Security
JWT + RBAC (4 roles), per-tenant Kubernetes namespaces, org-scoped queries, TLS 1.3, and PII redaction — validated by a passed audit (47/47 CI gates).
Built on a modern, open stack
Why this architecture wins
Provider-agnostic by construction
There is zero hardcoded provider logic in the core. The same engine runs WhatsApp, Stripe, and Salesforce — and the next hundred — through the contract. A connector is only "done" with a provider pack, connector pack, full docs bundle, and working test targets: no half-finished, undocumented integrations.
Event-driven execution
Unlike polling-based platforms, Zervanor is event-driven. Workflows and agents wake only when a subscribed event — like stripe.payment.succeeded or github.issue.opened — flows through the Event Router.
Kubernetes-native runtime
Zervanor doesn't just call your APIs — it hosts your agents. Each agent is containerized and deployed into a multi-tenant cluster on GKE, with pod-level isolation and per-organization namespaces. Event history lives on TimescaleDB; observability runs on OpenTelemetry and Prometheus.