ElectricSQL

ElectricSQL

@electric.ax

The agent platform built on sync. https://electric.ax - see also @pglite.dev

955 followers410 following76 posts

Electric Agents 0.6 is out, with a whole bunch of DX and AX improvements,, including local and remote agent runners, desktop and mobile apps. If you haven't tried it yet, now's a great time to dive in: electric.ax/blog/2026/06...

electric.axElectric Agents 0.6 | ElectricElectric Agents 0.6 rounds out the platform launched in April with a broader SDK and runtime surface for long-lived entities, StreamDB state, runners, wakes, signals, schedules, app APIs, and multi-ag...

Introducing Electric Agents! Agents are not compute. Agents are data. Multi-agent is a sync problem. Electric Agents is the first agent platform built on sync. Use it to build scalable, collaborative, long-lived multi-agent systems: 🧵👇

View full thread

Introducing Electric Agents! Agents are not compute. Agents are data. Multi-agent is a sync problem. Electric Agents is the first agent platform built on sync. Use it to build scalable, collaborative, long-lived multi-agent systems: 🧵👇

View full thread

Introducing Electric Agents! Agents are not compute. Agents are data. Multi-agent is a sync problem. Electric Agents is the first agent platform built on sync. Use it to build scalable, collaborative, long-lived multi-agent systems: 🧵👇

ElectricSQL reposted

PGlite v0.4 is out 🚀 PostGIS, connection multiplexing, and a major architecture refactor - bringing embedded Postgres closer to native. Now at 13M+ weekly downloads and showing up everywhere from CI to browser-based dev environments. electric-sql.com/blog/2026/03...

electric-sql.comAnnouncing PGlite v0.4: PostGIS, connection multiplexing, and a new architecture | ElectricSQLPGlite v0.4 adds PostGIS, connection multiplexing, and a refactored architecture that decouples initdb from the main WASM binary.

AI makes code cheap. The scarce asset is now the system's self-knowledge. Specs and contracts were always valuable—but too expensive to maintain. So we invested sparingly, specs drifted, and we read the code instead. That calculus has flipped with coding agents. electric-sql.com/blog/2026/02...

electric-sql.comConfigurancy: Keeping Systems Intelligible When Agents Write All the Code | ElectricSQLAI makes code cheap; the scarce asset is the system's self-knowledge. Configurancy is the layer that lets bounded agents coherently co-evolve a system.

1/Hosted durable streams is live on Electric Cloud! Persistent, resumable event streams over HTTP. Reads served from CDN, tested to 1M concurrent connections. 240K writes/second. 5M writes/month free.

1/Hosted durable streams is live on Electric Cloud! Persistent, resumable event streams over HTTP. Reads served from CDN, tested to 1M concurrent connections. 240K writes/second. 5M writes/month free.

View full thread

3/ Agentic apps need a different coordination model. Request/response assumes two parties taking turns. Three agents and two users acting at once need a shared log everyone can read, resume, and react to. That's durable streams.

4/Coming soon: - Drop-in transports for Vercel AI SDK and TanStack AI - Yjs support for collaborative editing - HTTP proxy that makes existing SSE/token streams resumable with no code changes

1/Hosted durable streams is live on Electric Cloud! Persistent, resumable event streams over HTTP. Reads served from CDN, tested to 1M concurrent connections. 240K writes/second. 5M writes/month free.

2/Durable streams 0.2.0 ships with idempotent producers and exactly-once semantics. 400+ conformance tests. Client libraries in 10 languages: TypeScript, Python, Go, Rust, Java, Swift, PHP, Ruby, Elixir, .NET.

ElectricSQL reposted

In 11 days from now, join the #LocalFirst and #CRDT devroom at #fosdem26 #fosdem in Brussels! @electric-sql.com @tanstack.com

Open Local First@localfirst.bsky.social

Kevin de Porre from @electric-sql.com will be talking about Query-driven Sync in @tanstack.com DB, at @fosdem.org '26 #Local-First & #CRDTs devroom! Come listen to the founding engineer at ElectricSQL. Join the 25 speakers on 1st Feb, it is free! more details: openlocalfirst.org/schedules/#6...

Today we're open-sourcing Durable Streams: a persistent stream primitive and HTTP protocol for reliable, resumable, real-time data streaming to clients. We built it inside Electric. Now we're standardizing it as a standalone protocol.

ElectricSQL reposted

Replying to @tanstack.com

Designed for your existing REST, GraphQL, or tRPC APIs. No backend migration. Bonus: Works with sync engines (@electric-sql.com, Trailbase, PowerSync) for real-time updates with near-zero incremental network cost.

ElectricSQL reposted

🚀 TanStack DB 0.5 is here with Query-Driven Sync Your component's query IS the API call. No custom endpoints. No GraphQL resolvers. Just write your query and DB figures out exactly what to fetch. Details 🧵👇

ElectricSQL reposted

using bun and pglite from @electric-sql.com I'm able to create in memory or persisted postgres instances (one per bun process) available to use with Postgrex via `socket_dir` in theory I could have a "cheap read replica" or simpler testing #myelixirstatus

ElectricSQL reposted

One day boutique conference for the sync era of the web. Hear from the world's top builders about how to develop systems in the era of agentic software and real-time sync.

Sync Conf@syncconf.bsky.social

Announcing Sync Conf 2025. Join us in SF on Nov 12th.

ElectricSQL reposted

That's 168ms -> 1.6ms! and we have a lot of good ideas how to make it even faster.

ElectricSQL@electric.ax

We've just delivered a 100x write performance bump with our latest release of Electric. How? We threw away our storage engine and built a new one designed for sync 🧵 electric-sql.com/blog/2025/08...

We've been running Electric in production for a year so we knew exactly what we needed: fast append-only writes and no data processing on reads. The performance gains exceeded our expectations.

The lesson: by shipping a system that works into production early and learning from it, allowed us to design a much better solution based on real-world requirements.

We're already syncing data to millions of clients in real-time behind a CDN, but our write path was heavily under-optimized. The result: high CPU usage, accumulating WAL on Postgres, and high end-user p95 latencies.

ElectricSQL reposted

Replying to @thruflo.com

LangChain, vector databases, instruction routing, specialized memory stores. You'd be forgiven for thinking you need a whole new stack to build agentic systems. However, that isn't actually the case: electric-sql.com/blog/2025/08...

electric-sql.comBringing agents back down to earth | ElectricSQLAgentic AI, beneath all the hype, is actually just normal software. You can build agentic systems with a database, standard web tooling and real-time sync.

How to build agentic systems on real-time sync.

James Arthur@thruflo.com

Agentic AI, beneath all the hype, is actually just normal software. You can build agentic systems with a database, standard web tooling and real-time sync.

ElectricSQL recently completed a 120-day reliability sprint. Our one goal: make our sync engine so boring-reliable you stop thinking about it and just build. We chased every incident, fixed every user-reported bug, and made unglamorous work our priority. 🧵

View full thread

We fixed IPv6 fallbacks, WAL slot recovery, memory leaks, file handle exhaustion, replication races, and dozens more issues. The boring stuff that makes infrastructure work. Because when AWS launched S3, they didn't lead with features — they led with eleven nines. 🎯

ElectricSQL recently completed a 120-day reliability sprint. Our one goal: make our sync engine so boring-reliable you stop thinking about it and just build. We chased every incident, fixed every user-reported bug, and made unglamorous work our priority. 🧵

View full thread

The results? @triggerdotdev.bsky.social achieved 20,000 updates/sec with sub-100ms latency handling 500GB+ daily Postgres traffic using Electric. Our Cloud syncs data to devices in 100+ countries monthly. How? Postgres + HTTP foundation + serious reliability engineering.

Some highlights from our sprint: • Connection recovery: 18s → 1.2s median recovery time • Zero-downtime operations: clients stay connected through restarts • Live schema changes: Electric adapts as your database evolves • Better observability: see exactly what's happening

ElectricSQL recently completed a 120-day reliability sprint. Our one goal: make our sync engine so boring-reliable you stop thinking about it and just build. We chased every incident, fixed every user-reported bug, and made unglamorous work our priority. 🧵

Infrastructure software can't have bugs. Your sync layer is load-bearing infrastructure with database-level expectations. We looked to S3 (11 nines!) and Redis for inspiration. They're simple ideas made extraordinary through relentless reliability engineering.

Tanstack DB is a reactive client store for building super fast apps on sync. Based on a TypeScript implementation of differential dataflow, it's type-safe, declarative, incrementally adoptable and insanely fast.

Kyle Mathews@kyle.bricolage.io

TanStack DB is now in BETA! We’ve been working on TanStack DB, an embedded, reactive client database for TanStack Query, and are proud to announce today that with the 0.1 release that it's now in BETA! tanstack.com/blog/tanstac...

View full thread

We look forward to collaborating more to make TanStack DB the future of app development with Electric and the best way to build the new generation of AI apps and agentic systems.

Tanstack DB is a reactive client store for building super fast apps on sync. Based on a TypeScript implementation of differential dataflow, it's type-safe, declarative, incrementally adoptable and insanely fast.

Kyle Mathews@kyle.bricolage.io

TanStack DB is now in BETA! We’ve been working on TanStack DB, an embedded, reactive client database for TanStack Query, and are proud to announce today that with the 0.1 release that it's now in BETA! tanstack.com/blog/tanstac...

ElectricSQL reposted