Event streams
A log many services read, as Kinesis does on our crypto platform.
Backend
Apache Kafka development services next to our streaming builds
We have no published Kafka build. We have shipped a Kinesis platform for 30,000+ concurrent users and an MQTT telematics feed, and we show where Kafka would take their place.
0Published builds on Kafka
4.4.0Latest Kafka release, 22 Oct 2026
18 Mar 2025Kafka 4.0.0 released
3.3.1Release that marked KRaft production ready
What we build
What we would take on with Kafka
Device feeds
Telematics normalised before storage, as on TruckFleet.
Kafka upgrades
Moves onto a 4.x release.
Consumers that scale apart
Services split so each one reads at its own pace.
Architecture
Where Kafka would sit
Kafka in the slot our Kinesis build fills
Sources
Mini-games and adsCrypto platform
MQTT telematicsTruckFleet Labs
Streaming
KafkaWhere it would sit
AWS KinesisResilient, auto-scaling
Services
.NET microservicesScalable architecture
FastAPIPython 3.13
Illustration. A dashed outline marks where the technology would sit. We have no published build on it.
Versions
Kafka 4 releases
The Kafka 4.x line
18 Mar 2025
Kafka 4.0.0
The first release of the 4.x line.
17 Feb 2026
Kafka 4.2.0
A feature release in the 4.x line.
22 May 2026
Kafka 4.3.0
The next feature release, patched to 4.3.2 in October.
22 Oct 2026
Kafka 4.4.0
The latest release.
Source: Apache Kafka downloads page, checked 3 November 2026.
Builds
The closest builds we can show you
Fintech, Hong Kong
Cryptocurrency marketing platform
The streaming half of the job: microservices on AWS Kinesis, 30,000+ concurrent users, first phase in one month.
30,000+Concurrent users the platform had to support
Logistics, fleet operations
TruckFleet Labs
The device half: MQTT position and engine data normalised before storage.
68 to 23Calls a day asking where a truck is
Fit check
When Kafka is the right call
Pick Kafka when
- Many services must read the same stream of events
- You need to replay events later
- Traffic arrives in bursts and the stream must absorb it
Look elsewhere when
- You need a published Kafka build to inspect, which we do not have
- A single queue between two services, where Redis or RabbitMQ is enough
- Your platform already runs on Kinesis and works
Explore
Same job, other tools
Pairs with
Where we used it
Stack
What Kafka usually ships with
AWSPython
Docker
Kubernetes.NET
Node.jsFAQs
What buyers ask first
Which Kafka version should we use?
The latest release is Apache Kafka 4.4.0, published on 22 October 2026. The 4.x line began with 4.0.0 on 18 March 2025.
Do you have a published Kafka build?
No. We say so on the first call and show the nearest work, which is AWS Kinesis and MQTT feeds.
Kafka or Kinesis?
The choice follows where your platform runs and who operates it. We have a published build on Kinesis and none on Kafka.
Who owns the code and the cloud accounts?
You do, from the first commit. Repositories and cloud accounts stay in your name.
Tell us what your event stream looks like
Thirty minutes on your events, your volumes and your platform. No sales pitch.