Redpanda, read like Kafka.
Basalt speaks the Kafka protocol to your Redpanda cluster. Same consumer groups, same offsets, same ordering, with nothing extra to run.
Overview
How it works.
Basalt joins Redpanda as a standard consumer group. Partitions are read in order and offsets commit only after the write is durable. Schemas are read from Redpanda's built-in Schema Registry when it is enabled.
Setup
Set it up in three steps.
01
Add the source
Give Basalt your broker addresses and a SASL user. It works with self-hosted clusters, Redpanda Serverless and BYOC.
# connect clickstream from Redpanda Serverless basalt source add clicks --redpanda clickstream --sasl scram-sha-256
✓ joined consumer group basalt-clicks
✓ 24 partitions streaming · lag 0
02
Shape it with a view
Write plain SQL over the source. Basalt keeps the view current with every record and tracks lineage back to the topic, partition and offset.
CREATE MATERIALIZED VIEW revenue_by_min AS SELECT date_trunc('minute', ts) AS minute, currency, sum(amount) AS revenue, count(*) AS payments FROM payments WHERE status = 'captured' GROUP BY 1, 2;
03
Read it from anywhere
Every view is an endpoint the moment it exists. Call it over REST, connect with any Postgres client, or use the SDK from your app.
curl https://api.basalt.dev/v1/views/revenue_by_min?limit=5 \ -H "Authorization: Bearer $BASALT_TOKEN"
✓ 200 OK · 5 rows · served from eu-north-1 in 3.1 ms
Included
What you get.
01
Exactly-once commits
Offsets commit with the write, so restarts and rebalances never double-count.
02
Schema Registry
Avro and Protobuf subjects are read from Redpanda's registry and typed on arrival.
03
Serverless ready
Works with Redpanda Serverless, BYOC and self-hosted clusters.
04
Offset replay
Rewind to any offset or timestamp and rebuild a view from the topic.
Related
