Comparison

ntail vs. Confluent Cloud: price and simplicity, side by side

Published 2026-08-09 · 4 min read

Confluent Cloud is the best-known managed Kafka service, and for a lot of teams it's the default they compare everything else against. ntail is a smaller, European alternative built on the same idea — a fully managed streaming service you don't have to operate — with a different pricing model and a different home for your data. Here's how the two actually compare, using one real workload rather than a marketing slide.

The workload

10 MiB/s of compressed data in, 20 MiB/s of compressed data out (a common 2× fan-out), 7‑day retention. That's roughly 6.3 TB retained at any time — a mid-sized production stream, not an edge case.

Pricing, side by side

ntail vs. Confluent Cloud — pricing model and example cost
ntailConfluent Cloud (Standard)
Pricing modelPay as you go, per started hourData in, data out, storage — nothing elseConfluent Compute Units (CKUs), sized to throughputPlus separate data in, data out & storage fees
Data in / out$25 per 1 MiB/s / monthCompressed, volume discounts from 100 MiB/s$0.05 per GBCompressed on the cluster interface
Storage$20 per TB / monthSingle-copy pricing$0.08 per GB-monthBilled on ~3× post-replication volume
Public internet traffic$0 — never meteredIncluded in the per-GB in/out rate
Example monthly cost10 MiB/s in · 20 MiB/s out · 7-day retention$876$6,136
Minimum commitmentNone — 1 MiB/s in + 1 MiB/s out floor (≈$50/mo)None on Standard, but CKUs are sized upfront

Illustrative, list-price figures. The Confluent Cloud model — CKU sizing, per-GB data in/out, ~3× replicated storage — and ntail's own pricing are both modeled in full in our pricing calculator FAQ. Ask us for a quote modeled against your actual bill.

Simplicity: nothing to size

The bigger difference day to day isn't just the total — it's what you have to think about to get there. Confluent's Standard tier prices by CKU, a unit of throughput you size for your workload and resize as it changes. ntail has no unit to size: you send data, you read data, and capacity follows automatically.

  • No CKUs to size or resize — ntail scales with your traffic in seconds, not a support ticket.
  • No separate bandwidth line to forecast — public internet traffic is $0, at any volume, so growth in usage doesn't turn into a growing bandwidth bill.
  • Pay as you go, billed per started hour — no annual commitment, and a per-cluster spend cap if you want a hard ceiling.

A European company, on our own European infrastructure

ntail is operated by Factual Tech AB, a company registered in Sweden. Customer data is processed and stored in the EU by default — other regions, including the US, available on request — on infrastructure we operate ourselves, not rented capacity from a non-EU hyperscaler. For teams with stricter residency or sovereignty requirements, we can also run fully off the public cloud as a dedicated cluster, in a specific region of your choice. See how we handle security for the full detail.

Which one is right for you

If you already run on Confluent and it's working, that's a reasonable place to stay. But if bandwidth and CKU sizing are showing up as the largest, least predictable lines on your invoice — or your data needs to stay in the EU, off a US hyperscaler's infrastructure — it's worth modeling your own workload against ntail's pricing, or seeing how ntail compares to the other managed streaming options.

Send us your Confluent bill

We'll model the same workload on ntail, line by line, and show you exactly where the saving comes from — no obligation.