I’m very excited about this. Coming next to the Neon backend: realtime.
Sync is incredibly hard to get right - especially if the goal is to make it great to work with, support as many database query use cases as possible, and scale well.
Sync coming to Neon was probably obvious to many after our announcement that the Electric team is joining Databricks but we can finally announce it officially today!
The Electric team is building sync for Neon. I asked @thruflo about joining Databricks and their first few weeks at the company: neon.com/blog/electrifying-n…
I’m very excited about this. Coming next to the Neon backend: realtime.
Sync is incredibly hard to get right - especially if the goal is to make it great to work with, support as many database query use cases as possible, and scale well.
Sync coming to Neon was probably obvious to many after our announcement that the Electric team is joining Databricks but we can finally announce it officially today!
The Electric team is building sync for Neon. I asked @thruflo about joining Databricks and their first few weeks at the company: neon.com/blog/electrifying-n…
The @neondatabase team are all in London this week, and we're hosting a meet-up this evening.
Come join us to talk about, anything dev/ai, all the new features of Neon, along with maybe a sneak peek of something new.
luma.com/neoncom-0ce4
PGlite + real-time sync have emerged as key primitives in an era where millions of apps are deployed by agents.
We’re excited to announce @ElectricSQL is joining team Neon at Databricks to build the world's most advanced Postgres backend platform.
neon.com/blog/electric-joins…
Introducing Electric Circuits ⚡️
Turn any static Postgres query into a live, reactive dataflow — incrementally maintaining results and streaming only what changed, all the way to your app.
Static queries in. Live applications out.
Checkout the blog post and repo in 🧵
This is Electric Circuits: a new primitive that turns any static database query into a live one — fine-grained reactivity, end to end, from Postgres to your app.
Built on DBSP and @DurableStreams
Agents need a durable, replayable stream of state — fast enough to sit in the hot path.
Durable Streams is that primitive: an append-only event log made low-latency with wire-format storage and a WAL.
Our Rust server hits ~1M appends/sec on 4 vCPUs 📷
I've been writing a @DurableStreams server in Rust to see how fast it can be.
It reaches nearly a million appends per second on a single 4 vCPU box — an order of magnitude faster than current reference server 🧵
Find out more about what’s driving the milestone, how PGlite got here, and where embedded Postgres goes next.
Read the post: electric.ax/blog/2026/06/25/…
PGlite has passed 10 million weekly npm downloads 🤯
On our blog we spills the beans on what’s driving the growth, and how its used for AI apps, dev tools, sandboxes, CLIs, and test suites from incredible teams like @Prisma, @supabase, @Firebase, @Netlify and @awscloud. 🔗🧵
Just Shipped: Flue 1.0 Beta
Flue is the TypeScript framework for building the next generation of agents, designed around an open agent harness with zero LLM lock-in. It’s like Astro, for agents.
Flue 1.0 has been redesigned around three core primitives:
🔁 Workflows — structured automations designed for background work, where your code drives the agent from start to finish.
🧭 Agents (New!) — autonomous, stateful loops where the model drives itself to complete a given task.
📡 Channels (New!) — connect agents to Slack, GitHub, Linear, Discord, Teams, and more. Flue handles the boilerplate for you.
Everything shares the same durable foundation, powered internally by Pi, Vite, and Durable Streams. Deploy anywhere, use any LLM, and recover running agents across restarts and downtime.
We’ve talked to a lot of teams building agents, and keep hearing the same thing: getting to production is hard work. We built Flue to help change that.
Flue 1.0 Beta is available today. Give it a try and let me know what you think!