Pricing
Every paid managed deployment is a 3-node cluster. Compute, Storage, and Network make up your monthly minimum, on AWS or Google Cloud. Transfer above your commitment is billed separately.
Free shared-host option
$0/month
Shared capacity at 100 KB/s with 7 days of telemetry retention. Same SDK, same connection string.
Start freeManaged tiers
Start with Launch, Scale, Performance, or Enterprise, then adjust throughput and storage. Your selected configuration sets the monthly minimum. Prices below are for AWS in the reference region.
A compact managed cluster for an initial production workload.
From
Loading
Reserved compute, storage, and transfer.
Monthly minimum, including when idle.
More provisioned storage for a growing managed workload.
From
Loading
Reserved compute, storage, and transfer.
Monthly minimum, including when idle.
Local NVMe storage for a higher-throughput workload.
From
Loading
Reserved compute, storage, and transfer.
Monthly minimum, including when idle.
Multi AZ placement with a larger local NVMe tier.
From
Loading
Reserved compute, storage, and transfer.
Monthly minimum, including when idle.
Run in your AWS or Google Cloud account. Your provider bills infrastructure directly. Capacity and commercial terms are agreed with you.
Loading
Contact salesCalculator
Loading clouds, storage profiles, and self-service limits.
Coming soon
A lower-cost, multi-tenant model with dynamic stream creation and automatic scaling. Start without reserving a dedicated cluster.
Keep history beyond your provisioned disk by moving sealed segments to object storage such as S3.
Connect existing applications to your Iggy deployment through a Kafka-compatible gateway using your existing Kafka SDK or client.
Billing model
FAQ
No. This page is a cost estimator. Signing up creates your account. You choose and confirm a deployment configuration separately before reserving paid capacity.
Your selected transfer commitment is included in the monthly minimum. Additional transfer costs are billed above that minimum at the published rates for your network scope and availability mode. Paid deployments have no broker throughput limit.
You can upgrade your managed tier to unlock additional features. Private connectivity starts at Scale, Local NVMe at Performance, and Multi AZ requires Enterprise approval. Moving an existing deployment from Network Drive to Local NVMe requires a planned migration with our team.
Launch and Scale include 7 days, Performance includes 30 days, and Enterprise includes 90 days. Telemetry retention follows your active managed tier.
Your full monthly minimum remains payable, including reserved compute, provisioned storage, the selected network throughput commitment, operations, and support. Unused transfer does not reduce the minimum.
Network Drive means cloud block storage such as EBS or Persistent Disk. It is not object storage.
The calculator shows a full UTC calendar month. Invoices prorate provisioned resources by the second for partial months.
No partition quantity is required upfront and there is no per-partition price. Partitions are hashed across one shard per vCPU on every node, so larger compute profiles spread them across more cores. Each partition keeps at least one segment on disk, so the provisioned storage and the topic segment size bound how many fit on a node.
Coming soon. Sealed segments will tier to object storage such as S3 so topics can keep history far beyond the provisioned disk, priced per GB-month as a Storage line. Until then retention is bounded by the provisioned Network Drive or Local NVMe capacity.