Vidulividuli
Run kafka on kubernetes with ease
Surge Messaging Service

Run kafka on kubernetes with ease

Managed Kafka that automates the operational aspects of running brokers on Kubernetes. Launch clusters faster, configure topic defaults with less friction, and spend less time on day-2 operations.

Kafka 4.1
Current engine support
KRaft
No wasted ZooKeepers
Pre-tuned
Low overhead
Automate Kafka operations

Harness the power of Kafka without the toil

Teams adopt Kafka for durable event streams, decoupled services, and asynchronous workflows. The friction comes from operating the cluster, choosing the right topology, tuning defaults, and managing ongoing changes. Surge automates those operational layers.

Cluster operations overhead

Cluster operations overhead

Pain point before
Set up brokers, controllers, storage, and cluster layout manually
Pain point afterProvision Kafka with production-ready layouts
Topic configuration sprawl

Topic configuration sprawl

Pain point before
Recreate partitions, replication, and cleanup settings topic by topic
Pain point afterDefine topic defaults once and apply them consistently
Day-2 tuning burden

Day-2 tuning burden

Pain point before
Adjust leader behavior and process settings through scattered ops work
Pain point afterManage operational tuning from one interface
Simple workflow

From Kafka setup to production in three steps

Surge gives teams a faster path to managed Kafka by automating the operational setup and surfacing the controls that matter.

Choose your cluster layout
01

Choose your cluster layout

Start with a combined layout for testing. Use independent controller and broker pools for production-oriented operation and scaling.

Set operational defaults
02

Set operational defaults

Configure topic defaults like partitions, replication factor, compression, and cleanup policy before teams begin creating streams.

Deploy and monitor
03

Deploy and monitor

Launch the cluster, create topics in the console, and tune leader or process settings without stitching together separate operational tools.

Everything you need

Operations automated where they usually get messy

Surge keeps the power of Apache Kafka while reducing the operational work around cluster setup, topology decisions, topic defaults, and ongoing tuning.

KRaft protocol

KRaft protocol

Kraft supercharges your operations with resource savings, faster failover, and many more benefits.

Flexible node layouts

Flexible node layouts

Choose combined nodes for simpler deployments or split controllers and brokers for production usage.

Topic defaults

Topic defaults

Set default partitions, replication factor, min in-sync replicas, cleanup policy, compression, and more in one place.

Cluster controls

Cluster controls

Configure operational settings like auto rebalance, unclean election, and many more without manual config wrangling.

Production sizing controls

Production sizing controls

Tune CPU, memory, disk, and node counts to fit your throughput and durability requirements.

Topic management

Topic management

Create, inspect, and update managed topics directly from the product interface instead of relying on disconnected workflows.

Perfect for

Solve domain problems with versatile approaches

Microservices

Event-driven communication

Use Kafka as the backbone for service-to-service events, domain event propagation, and asynchronous workflows while reducing operational overhead.

  • Durable event streams for decoupled systems
  • Topic defaults for consistent service onboarding
  • Easier operational management as services grow
Background Processing

Async jobs and queue-backed workloads

Run task pipelines, notifications, ingestion jobs, and processing workflows on Kafka without hand-building the cluster operations around them.

  • Better separation between apps and workers
  • Configurable replication and durability settings
  • Operational tuning exposed in the platform
Streaming Data

Real-time ingestion and event pipelines

Capture high-volume application events, telemetry, or business data in streams that downstream consumers can process independently.

  • Partitioned topics for scalable consumers
  • Centralized defaults for stream consistency
  • Modern Kafka foundation with KRaft
Simple, transparent pricing

Pay for compute, not extra overheads

Surge pricing is based on the broker resources you provision. Size your cluster for the workload you need, see cost estimates while configuring, and let the platform automate more of the operational side.

CPU
$20
per vCPU / month

Dedicated compute.

RAM
$10
per GB / month

Dedicated memory.

Disk
$0.15
per GB / month

Simple linear scaling.

Resource-based pricing

Resource-based pricing

Pay for CPU, memory, and storage based on the Kafka cluster you run. No opaque packaging or surprise billing tiers.

Up-front cost visibility

Up-front cost visibility

Configure controller and broker pools with visibility into what you are provisioning before deployment.

Less ops work, lower TCO

Less ops work, lower TCO

Save engineering time and DevOps cost by reducing cluster setup, configuration drift, and routine operational work.

Technical specifications

Production-ready scalable specs

Engine

Kafka versions4.0.0 and 4.1.0
Cluster architectureKRaft, no ZooKeeper
Deployment scopeSingle-region

Compute & storage

CPU options0.125 to 16 vCPUs per node
Memory options512 MB to 32 GB per node
Storage5 GB to 4 TB per node

Topology

Combined node layout1 to 9 nodes
Controller pool1 to 5 nodes
Broker pool1 to 15 nodes

Operational controls

Topic controlsPartitions, replication, compression, etc
Leader controlsAuto rebalance, imbalance checks, etc
Process controlsHeap, threads, etc
Why Surge?

Greatly simplified operations

Feature
Without Viduli
With Viduli
Cluster setup
Assemble infrastructure, topology, and networking by hand
Launch a production-ready Kafka cluster in minutes
Cluster architecture
Own the architecture and operational complexity yourself
Modern KRaft architecture with no ZooKeeper
Topic defaults
Repeat settings per topic and risk drift
Centralized defaults for partitions, replication, and cleanup
Production topology
Extra design work for broker and controller layouts
Combined and independent node layouts built in
Day-2 operations
Tune broker behavior through manual ops work
Auto-tuning with manual overrides
Topic management
Use extra tools and fragmented workflows
Create and update topics directly in the console

Launch Kafka without management overheads

Use Surge to automate the operational aspects of Kafka and move faster on event-driven systems.

Questions?

Frequently asked questions