Serverless No brokers to run, no capacity to reserve.
Serverless Kafka as the event bus behind your services
Durable, always-on messaging between your microservices — with a 99.99% uptime SLA and no brokers, no capacity planning, and no on-call rotation for Kafka itself.
- No brokers to size
- 99.99% uptime SLA
- EU data residency
- Free migration
Example monthly invoice
10 MiB/s in · 20 MiB/s out · 7-day retention- Data in10 MiB/s × $25
- $250
- Data out20 MiB/s × $25
- $500
- Storage7 days of writes ≈ 6.3 TB × $20
- $126
- Public internet trafficData sent and read, any volume
- $0
Illustrative example at list price — one producer service, two consuming services reading the same stream independently. Model your own workload.
- 99.99%Contractual uptime SLA
- ZeroMaintenance windows
- $0Extra fees for public internet traffic
- 11 9sData durability
Why teams move
Why teams stop self-managing their event bus
Kafka disruptions become someone's 3am page. We carry the operational burden and put it behind an SLA with service credits.
-
No on-call rotation for Kafka itself
No brokers to count, no partitions to plan, no upgrades to schedule. Capacity follows your traffic automatically and we carry the pager for the platform.
-
No capacity planning before a launch
Capacity follows your traffic within seconds, so a new service going live doesn't need a broker-sizing exercise ahead of it.
-
Predictable, per-hour billing
Billed for what you actually use, per started hour, with a hard spend cap available per cluster — a traffic spike from a marketing push can't turn into a surprise invoice.
What you get
What your services get
One durable log, standing behind however many services need to read from it.
-
One durable log, many readers
Order processing, notifications and audit logging can all read the same stream independently — as separate consumer groups, at no extra cost per consumer.
11 9s durability
-
Works with your client libraries
Kafka-compatible with the tools your team already uses — no proprietary client to adopt in your services.
Free migration
-
An SLA your services can depend on
A contractual 99.99% uptime SLA with service credits, not a marketing number — clusters span independent failure domains, and a lost node is replaced in seconds.
Under 4.4 min downtime / month
Reliability & performance
The numbers we sign up to
With service credits attached when we miss them.
- 99.99%Uptime SLAUnder 4.4 minutes a month, with service credits
- ZeroMaintenance windowsUpgrades and scaling with no downtime for you
- 11 9sData durabilityEvery write on durable, verified storage
- <60 sCapacity changesScale up for a peak, down the same evening
FAQ
Common questions about event-driven apps
Do I need to run or size brokers myself?
No — it's fully serverless. There's nothing to size and no capacity to reserve up front. You create a cluster, get an endpoint, and capacity follows your traffic automatically.
What happens if there's an outage?
Production clusters carry a contractual 99.99% monthly uptime SLA with service credits if we miss it. See security for how we run the underlying infrastructure, and our status page for live status.
Can different services consume the same events independently?
Yes. Multiple consumer groups can read the same topic independently — order processing, notifications and audit logging can all subscribe to the same stream — and reading data out is never billed extra for public internet traffic, regardless of how many services are consuming.
Is our event data stored in the EU?
Yes, by default. Data is processed and stored in the EU; other regions, including the US, are available on request. See security for the full detail.
Give your services an event bus you don't have to run
Tell us about your services and traffic, and we'll help you plan the move.