Menu

1 / 5

Neon Realtime vs Supabase Realtime

DEV Community: postgres·kuberdenis·19 days ago
#bpdjhFQr
#devtopostgresql#devto#dev#neon#supabase
Reading 0:00
15s threshold

Neon shipped Realtime on October 15, 2026. You subscribe to a SQL query, and Neon keeps the result up to date as the data changes. Neon hasn't published latency numbers yet, so I measured it.

I compared it with polling, LISTEN/NOTIFY, and both flavors of Supabase Realtime, on 10,000 and 1,000,000 rows. Everything ran on October 28, 2026 in Frankfurt.

TL;DR

Median time from UPDATE to an up-to-date result on the client, at 10k and 1M rows:

Neon Realtime: 40–46 ms for filters, joins and top-10 queries. That's one network round trip from my laptop. The change usually arrived within 8 ms of the write's commit ack.

Supabase Broadcast: 58–60 ms on a plain filter. Joins and top-10 need a refetch, so 108–115 ms.

LISTEN/NOTIFY: 70–244 ms. Every change costs a second query.

Supabase Postgres Changes: 328–434 ms , and 1.1 s for the aggregate at 1M rows.

Polling every second: 414–546 ms , change or not.

The large aggregate used more bandwidth.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.