// the find
vanus-labs/vanus
Vanus is a Serverless, event streaming system with processing capabilities. It easily connects SaaS, Cloud Services, and Databases to help users build next-gen Event-driven Applications.
Vanus is a Kubernetes-native event streaming system built on top of a custom message queue, with CloudEvents support and built-in filter/transform capabilities at the broker level. It targets teams who want an event bridge between SaaS, databases, and cloud functions without running Kafka. The project has been effectively abandoned since March 2024.
Native CloudEvents spec support is first-class, not bolted on — events are typed and routed in CloudEvents format throughout. The filter and transformation pipeline runs inside the broker itself, so you don't need a separate stream processor for basic routing logic. The Go workspace layout with separate modules per component (client, lib, api, pkg) means you can take only what you need without pulling the whole system. CEL-based event filtering (pkg/cel) is a clean approach — same expression language used in Kubernetes admission webhooks.
Last commit was March 2024 and there's a Vanus Cloud product that appears to have been the real focus — this OSS repo looks like it was abandoned when the company pivoted or shut down. The architecture requires etcd plus six separate Kubernetes deployments (controller, root-controller, store, gateway, timer, trigger), which is a lot of moving parts for something positioning itself as simpler than Kafka. No documentation on persistence guarantees, replication factors, or what happens when the store nodes lose quorum — critical questions for anything you'd actually trust with events. The README is thin and the linked docs site may not exist anymore given the project state.