Kevin De Porre

Member of Technical Staff @databricks working on @neondatabase. Previously Founding engineer @ElectricSQL & CRDT researcher 👨‍🔬 @softlab_brussel.

[Dante @dantegaleazzi]

goodbye supabase,

hi @neondatabase and your 100 free projects 🙌

[Kevin De Porre @KevinDP55]

@samwillis @harrysolovay Totally! I just don’t want to impose every user of our SDK to have to use effect, but if it would make sense to provide an effect client wrapping the plain SDK then i would be happy to!

[Nikita | Scaling Lakebase Postgres @nikitabase]

Can a single database architecture satisfy both vibe-coded and large scale enterprise apps?

The same approach makes small database ultra cheap to run and branch can also make a large one faster and easier to operate. We call this architecture Lakebase.

[Kevin De Porre @KevinDP55]

@neondatabase Realtime v0.1.2 now supports React Native! 🎉
One todo app, running on native and web. Make a change in either and watch it sync to the other 👇

[Sam Willis @samwillis]

I’m so very excited that Neon Realtime is out! 🚀🎉
Live reactive SQL queries, straight from Postgres
Subscribe to ANY query from the front end, and it will been updated in realtime.
To do this we built a brand new sync/query engine, running inside Postgres.
For anyone who’s worked on a sync engine, being inside Postgres is a bit like being in a sweet shop, it’s all we ever wanted! Everything we could possible need is just there and ready to use.
We’re going to be writing more about how we built it in the coming weeks, but want to say I’m indelibly proud of what the team have achieved, it’s very VERY cool.
I’m looking forward to seeing how our users get on with it!
If you have any questions, give me a shout!

[Anthony Giuliano @ant_giuliano]

As a longtime @neondatabase user, there is one feature that I have always wanted.

Well...

[Kevin De Porre @KevinDP55]

Today we released Realtime for Neon databases. It's very simple to use and fast! Available for everyone in public beta. Try it out and let us know what you think about it 🐘 @neondatabase

[Neon @neondatabase]

Neon now has realtime, built by the team behind Electric. Turn any SQL query into a live query, joins and aggregates included. All inside Postgres, and ready for agents.

It’s in public beta and available in all Neon plans. Give it a try and tell us what you think!

[Kevin De Porre @KevinDP55]

We’re building some really amazing stuff here. Sync for Neon is going to be big! 🔥

[Andre Landgraf @andrelandgraf]

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: https://t.co/raOgKECI6r

[Sam Willis @samwillis]

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.
https://t.co/vJuvqFrJuH

[Neon @neondatabase]

The Neon backend is GA. A complete set of primitives for apps and agents built around the database, with open standards, no lock-in, and branching-first by design.

Starting with: Lakebase Postgres, Object Storage, Functions, Managed Better Auth, and AI Gateway. More to come.

[Neon @neondatabase]

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.

https://t.co/IS6HpwcdYo

[Kevin De Porre @KevinDP55]

Very happy to be joining @databricks as they acquired @ElectricSQL! This is an exciting opportunity to build the databases and agents of the future 🐘✨

[Ali Ghodsi @alighodsi]

Excited to share that we've acquired ElectricSQL, the team behind PGlite. Agents need super fast Postgres and this team built an amazing WASM (WebAssembly) implementation of postgres that runs in your browser, but can sync back with Postgres instances asynchronously. Exactly what blazing fast AI agents today need. Excited to supercharge our 𝐋𝐚𝐤𝐞𝐛𝐚𝐬𝐞 𝐏𝐨𝐬𝐭𝐠𝐫𝐞𝐬 offering with these capabilities.

https://t.co/tIww5fLekt

[Valter Balegas @balegas]

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

[Kevin De Porre @KevinDP55]

@opwizardx The protocol defines a normalized format. For each coding agent (Claude Code, Codex, etc.) we define a normalizer and a denormalizer. Sharing a session normalizes it. Importing a shared session denormalizes it.

[Kevin De Porre @KevinDP55]

Your sessions live on one laptop, inside one agent. Your teammate uses a different one. No way to collaborate.

So I built Capi: share a session as a URL, resume it from any machine, in Claude Code or Codex.

(1/4) 🧵

[Kevin De Porre @KevinDP55]

@opwizardx I actually had Claude recover old sessions from time machine backups 😅 didn’t ask for it though.. it realized it got wiped after 30 days, figured out i had time machine backups and went to find it back!

[Kevin De Porre @KevinDP55]

Agent sessions are append-only logs, a perfect match for @ElectricSQL's @DurableStreams. Just had to write the agent-agnostic session protocol on top.

Try it yourself — it's open source: https://t.co/r41eCHvjRR

[Kevin De Porre @KevinDP55]

Sharing a session is great for research. But real work has code too. Capi hooks sessions into git: every commit is a checkpoint. Resume a teammate's session at any commit — session state + code line up automatically.

[Sam Willis @samwillis]

Multi-session/connection support for PGlite landing soon! 🚀
We have a POC that passes almost all the Postgres regression tests:
- Concurrent connections
- Parallel scans
- Locks, cancellation & notify
This has been a major ask & we're getting close!
Draft PR with details in 🧵