{"slug": "electric-joins-databricks-to-bring-wasm-postgres-to-ai-agent-sandboxes", "title": "Electric joins Databricks to bring WASM Postgres to AI agent sandboxes", "summary": "Databricks has acquired Electric, the company behind PGlite and a real-time sync engine, to bring WASM Postgres to AI agent sandboxes and extend its Postgres capabilities from the lakehouse to the edge. PGlite, a WASM Postgres database that runs inside agents, has grown from 1 million to 13 million weekly downloads in twelve months. The acquisition reunites the team with Stas Kelvich, who co-founded Neon and created the foundational WASM Postgres work, and will combine PGlite with Databricks' Lakebase to provide agents with local, low-latency databases synchronized to central infrastructure.", "body_md": "Together, Lakebase and Electric extend Databricks' Postgres capabilities from the lakehouse to the edge\n\nby [Stas Kelvich](/blog/author/Stas-Kelvich), [Yan Leshinsky](/blog/author/yan-leshinsky), [Nikita Shamgunov](/blog/author/nikita-shamgunov) and [Reynold Xin](/blog/author/reynold-xin)\n\nToday, we’re excited to welcome Electric to Databricks. The world is building a new era of agentic applications which require distributed state and real-time data synchronization between teams of agents working in sandboxes. Electric is leading the way in pioneering data primitives purpose-built for agents: PGlite gives every agent its own lightweight Postgres right where it runs, providing ultra-low latency access to local context, and Electric’s real-time sync engine synchronizes distributed state back to a central Lakebase, enabling teams of agents to collaborate without losing track of shared context. That vision now continues at Databricks as we bring WASM Postgres to AI agent sandboxes, extending Databricks’ Postgres capabilities from the lakehouse to the edge.\n\n**Agents don’t behave like traditional applications**\n\nDevelopers are moving from building traditional apps to building agentic applications, and the assumptions underlying traditional infrastructure are shifting with them. A traditional application has a known shape: its queries are written in advance, its data access patterns are predictable, and it runs in a place its architects chose. One managed Postgres database serves it well.\n\nThe agents in agentic applications add a second surface. Alongside the durable, governed state every application needs, an agent generates a fast-moving context set. Agents differ in three ways that matter for a database:\n\n**Introducing Electric**\n\nThe Electric team built data primitives for the era of agentic applications.\n\nThey created PGlite to push Postgres to the edge, creating a WASM Postgres database small enough to run inside the application or agent itself - in an agent sandbox, browser tab, or user’s device - rather than on a separate server. PGlite has grown from 1M to 13M weekly downloads in just twelve months, enabling developers to build a new class of distributed Postgres applications and agents.\n\nBut local execution is just part of the challenge. Agents also need a shared, up-to-date view of changing information. Electric’s real-time sync engine continuously synchronizes data between distributed agents and centralized Lakebase infrastructure, enabling agents to securely share information with the definitive record in the cloud while keeping fast local context. The real-time sync architecture powers collaborative apps like Google Docs, Figma and Notion, and it turns out to be exactly what a fleet of agents needs to stay current while working in parallel.\n\n**Shared Postgres DNA**\n\nBoth Electric and Lakebase are built on Postgres, the open-source database technology that has become the default foundation for AI agents. In fact, PGlite was built on the foundational WASM Postgres work of Stas Kelvich, who co-founded Neon. Electric took that proof of concept and turned it into the embeddable Postgres that millions of projects run every week. Bringing these teams together reunites two halves of the same idea and strengthens Databricks’ leadership at the center of innovation for modern databases as demand for agents accelerates.\n\n**Databricks + Electric**\n\nLakebase delivers Postgres at production scale. PGlite brings WASM Postgres into the agent's own sandbox. Sync keeps the two consistent. By combining the power of Lakebase Postgres with the local execution of PGlite, agents get the lightweight databases they need to move fast and the infrastructure required to deploy at any scale.\n\nFor developers, this means:\n\nWe’re thrilled to have the Electric team join Databricks, and can’t wait to see what our customers build.\n\nCheck out the [Neon blog](https://neon.com/blog/electric-joins-neon), and [hear directly from Electric’s founders](https://electric.ax/blog/2026/08/11/electric-joining-databricks) about why they’re excited to join forces.\n\nSubscribe to our blog and get the latest posts delivered to your inbox.", "url": "https://wpnews.pro/news/electric-joins-databricks-to-bring-wasm-postgres-to-ai-agent-sandboxes", "canonical_source": "https://www.databricks.com/blog/electric-joins-databricks-bring-wasm-postgres-ai-agent-sandboxes", "published_at": "2026-08-11 07:00:00+00:00", "updated_at": "2026-08-11 14:25:12.200763+00:00", "lang": "en", "topics": ["ai-agents", "ai-infrastructure", "developer-tools", "artificial-intelligence"], "entities": ["Databricks", "Electric", "PGlite", "Lakebase", "Stas Kelvich", "Neon", "Postgres", "WASM"], "alternates": {"html": "https://wpnews.pro/news/electric-joins-databricks-to-bring-wasm-postgres-to-ai-agent-sandboxes", "markdown": "https://wpnews.pro/news/electric-joins-databricks-to-bring-wasm-postgres-to-ai-agent-sandboxes.md", "text": "https://wpnews.pro/news/electric-joins-databricks-to-bring-wasm-postgres-to-ai-agent-sandboxes.txt", "jsonld": "https://wpnews.pro/news/electric-joins-databricks-to-bring-wasm-postgres-to-ai-agent-sandboxes.jsonld"}}