SQLStreams

the messaging platform that is just Postgres

You last visited on 9999-99-99 Show what's new since then

Start Here

Updated
STICKY Quickstart
2026-09-12
2026-09-11
brandon Site Admin brandon profile

It's Kafka on Postgres.

You can do cool things like this

postgres 18 · wasm · local to this tab
message_log_1 auto re-runs
SELECT id, payload
FROM message_log_1
ORDER BY id DESC;
idpayload
8{"desc":"reprint label","order_id":4008}
7{"desc":"hold for pickup","order_id":4007}
6{"desc":"split shipment","order_id":4006}
5{"desc":"void invoice","order_id":4005}
4{"desc":"restock shelf","order_id":4004}
3{"desc":"pack crate","order_id":4003}
2{"desc":"refund card","order_id":4002}
1{"desc":"ship pallet","order_id":4001}
8 rows
consumer_group_cursor_1 auto re-runs
SELECT g.name, c.claimed
FROM consumer_group_cursor_1 c
JOIN consumer_group_config g ON g.id = c.consumer_group_id;
nameclaimed
billing0
1 row
consumer 1 (billing)
billing's cursor is at 0 — its first run claims from the start of the log.
no runs yet
New group = its own cursor, reads everything. Existing group = one cursor, disjoint ranges.
SELECT id, payload
FROM message_log_1
ORDER BY id DESC;
idpayload
8{"desc":"reprint label","order_id":4008}

Board

Threads Last post
Getting Started first produce and consume, why SQLStreams, benchmarks, and the roadmap
4
Quickstart
Concepts queue & log, the shape of the API, lifecycle, handler outcomes, consumer group config, message key, ordering, routing, fan-out, architecture, table design
11
The Shape of the API
Guides transactional produce, side effects & retries, replay, dead letters, where a new group starts, ordered delivery, consumer tuning, consumer timeouts, schema versions, migrations, schedules
11
Upgrades & Migrations
Reference one thread per handle and instance — every verb and every config field with its default, checked against the shipped library
15
API reference
Troubleshooting every SQL error code and log event, one thread each
108
compaction_read_cost [SQL0095]
Compare Kafka · RabbitMQ & SQS — shipped behavior only, no wishful checkmarks
3
SQLStreams vs. Kafka
Decision records the why behind shipped behavior — every settled design decision, append-only
525
0576 — CLI --output json

Announcements

Posted
updated since your last visit read purple links — already visited