blog: announcement post.

website/.vitepress/theme/Layout.vue

@@ -101,11 +101,17 @@ onMounted(() => {
     { immediate: true }
   )
 })
-const shouldShowReleasebanner = frontmatter.hideReleaseBanner || !hasSidebar
+
+// Show the release banner on all non-sidebar pages, unless the
+// page opts out with `hideReleaseBanner: true` frontmatter.
+const shouldShowReleaseBanner = computed(
+  () => !hasSidebar.value && !frontmatter.value?.hideReleaseBanner
+)
 
 const layoutClass = computed(() => {
   const classes = []
   if (!hasSidebar.value) classes.push('nav-relative')
+  if (shouldShowReleaseBanner.value) classes.push('has-release-banner')
   if (frontmatter.value?.pageClass) classes.push(frontmatter.value.pageClass)
   return classes.join(' ')
 })
@@ -114,7 +120,7 @@ const layoutClass = computed(() => {
 <template>
   <Layout :class="layoutClass">
     <template #layout-top>
-      <template v-if="shouldShowReleasebanner">
+      <template v-if="shouldShowReleaseBanner">
         <ReleaseBanner />
       </template>
     </template>

website/.vitepress/theme/custom.css

@@ -351,6 +351,16 @@
   display: none !important;
 }
 
+/* The release banner adds ~66px of in-flow height above the relative
+   nav. The doc aside ("On this page", e.g. on blog posts) is
+   viewport-fixed and offsets itself by --vp-layout-top-height, which
+   nothing else sets — without this it starts under the nav. Scoped to
+   the aside because VPNav / VPNavScreen also read the variable and
+   must not shift. */
+.has-release-banner .VPDoc .aside {
+  --vp-layout-top-height: 66px;
+}
+
 .og-page .VPPage {
   padding: 0 !important;
   margin: 0 !important;

website/blog/posts/2026-07-17-electric-circuits.md

@@ -2,11 +2,7 @@
 title: "Electric Circuits: turn any database query live"
 description: "Electric Circuits turn static database queries into live ones: registered on shared incremental circuits, maintained as the data changes, and delivered over Durable Streams."
 excerpt: >-
-  Electric Circuits is a new primitive that turns any static database query
-  into a live one. Register a query and a circuit — an incremental
-  computation graph shared across queries with the same statement — keeps
-  its result updated as the database changes, with memory that scales with
-  your live queries, not your data.
+  Electric Circuits is a new primitive that turns any static database query into a live one. Register a query and a circuit keeps its result updated as the database changes.
 authors: [balegas]
 tags: [electric, circuits, dbsp, ivm, durable-streams]
 image: /img/blog/electric-circuits/header.png

website/blog/posts/2026-08-11-electric-joining-databricks.md

@@ -0,0 +1,81 @@
+---
+title: 'Electric is joining Databricks'
+description: >-
+  Electric is now part of Databricks. We're joining Neon to make Lakebase the best platform for building apps and agents. Everything we've open sourced stays open source.
+excerpt: >-
+  Electric is now part of Databricks. We're joining Neon to make Lakebase the best platform for building apps and agents. Everything we've open sourced stays open source.
+authors: [thruflo, balegas]
+image: /img/blog/electric-joining-databricks/header2.jpg
+tags: [electric, neon, databricks, sync, announcement]
+outline: [2, 3]
+post: true
+published: true
+---
+
+[Electric is joining Databricks](https://www.databricks.com/blog/electric-joins-databricks-bring-wasm-postgres-ai-agent-sandboxes) to add our data primitives and reactivity to [Lakebase](https://www.databricks.com/product/lakebase) and help make it the best platform for building
+<span class="no-wrap">apps and agents</span>.
+
+It's a big change for Electric. There are [implications for Cloud users](#what-this-means-for-electric-users) but everything we've previously [open sourced](https://github.com/electric-sql) stays open source. Ultimately, by joining [Neon](https://neon.com) at Databricks, we'll have the platform to [take sync to the next level](#electrifying-neon).
+
+> [!Warning] ✨ Key links
+> See the [Databricks announcement](https://www.databricks.com/blog/electric-joins-databricks-bring-wasm-postgres-ai-agent-sandboxes) and [what this means for Electric users](#what-this-means-for-electric-users).
+
+## Aligned from day one
+
+The first time that we came to San Francisco to raise funding for Electric, we were introduced to [Nikita Shamgunov](https://www.linkedin.com/in/nikitashamgunov), Co-founder and CEO of Neon.
+
+We were building Postgres to SQLite sync at the time. Nikita was fairly fresh from building his previous company, SingleStore, which was a distributed-SQL database that was wire-compatible with MySQL.
+
+His advice was stark. Stop syncing from Postgres to SQLite. The type-impedance is going to be a massive pain. Why not sync Postgres to Postgres instead?
+
+The next day, he shared an experimental repo that his co-founder, [Stas Kelvich](https://www.linkedin.com/in/kelvich/) has been working on, that cracked running Postgres locally in WASM.
+
+There had been previous WASM postgres projects, but they had all been VM-based, with overhead and a large build. What Stas' project gave us was a pure WASM build that was radically smaller and faster.
+
+Suddenly [the idea of running Postgres in the client](https://youtu.be/ZlHWSpIYixk) actually become viable:
+
+<div class="embed-container">
+  <YoutubeEmbed video-id="ZlHWSpIYixk" title="Little elephants everywhere" />
+</div>
+
+That repo became the basis of [PGlite](https://pglite.dev). Now Electric's most [widely-used project](/blog/2026/06/25/pglite-reaches-10-million-weekly-downloads) at 13M downloads a week.
+
+Since then, Neon has been our most popular Postgres integration and powered the majority of Electric Cloud sync services. So, in a real sense, Neon seeded both the strategy and technology behind Electric.
+
+## Electrifying Neon
+
+So why join Neon at Databricks now? It's because [Lakebase Postgres](https://docs.databricks.com/aws/en/oltp/projects) is now a core primitive shared across Neon and Databricks and Neon is expanding to become a [complete backend platform](https://neon.com/blog/were-building-backends).
+
+That takes more than raw database engineering. It takes world-class DX and AX (agent experience) wrapped up into the right data primitives.
+
+Apps and agents run on live data. Users expect interfaces that update instantly. Agents need [realtime state](https://electric.ax/blog/2026/04/08/data-primitive-agent-loop) and [coordination through the data layer](https://electric.ax/blog/2026/04/29/introducing-electric-agents).
+
+That's what we do at Electric. That's what Databricks is building around Lakebase.
+
+## The stack of the future
+
+[Lakebase](https://www.databricks.com/product/lakebase) is serverless Postgres for apps and agents. With [scale-to-zero](https://docs.databricks.com/aws/en/oltp/projects/scale-to-zero), [native&nbsp;branching](https://docs.databricks.com/aws/en/oltp/projects/branches) and support for both OLTP and OLAP.
+
+By combining Electric’s sync and local execution with the scalability and capabilities of Lakebase, apps and agents get a supercharged Postgres stack for optimal fast, reactive development, local query execution at machine speed and deployment at scale, for workloads of any scale.
+
+This is the stack of the future. We were always aligned with Neon but the opportunity to execute on this is now.
+
+## What this means for you
+
+Everything Electric has previously open sourced stays open source: [Postgres&nbsp;Sync](https://electric.ax/sync/postgres-sync), [PGlite](https://pglite.dev), [TanStack&nbsp;DB](https://tanstack.com/db), [Durable&nbsp;Streams](https://durablestreams.com).
+
+[Electric Cloud](/cloud/) is winding down. Cloud users will need to self-host or move to another provider. We've contacted every existing cloud user directly. If you're affected, we'll support you through the transition and there are a number of options available for seamless continuity of hosting with professional support.
+
+Moving forward, Electric will be building with Neon inside Databricks. You can see how a [Neon backend fits together](https://neon.com/docs/get-started/backend-overview) and [how the platform is evolving](https://neon.com/blog).
+
+## What's next
+
+To everyone who has adopted and contributed to Electric, we want to say a huge thank&nbsp;you. Together, we proved that sync is the future. Not just [for&nbsp;apps](/blog/2025/07/29/super-fast-apps-on-sync-with-tanstack-db) but also [for&nbsp;agents](/blog/2026/04/29/introducing-electric-agents). We couldn't have done this without you.
+
+Now, as part of Databricks, we have the platform to take sync to the next level.
+
+For more on this news, read the [Databricks announcement](https://www.databricks.com/blog/electric-joins-databricks-bring-wasm-postgres-ai-agent-sandboxes). If you haven't already, now is a great time to [start something on Neon](https://neon.com) and follow along as we ship:
+
+```sh
+npx neon@latest init
+```

website/cloud/index.md

@@ -6,7 +6,7 @@ description: >-
   Scalable data infrastructure platform for building fast, modern apps and collaborative multi-agent, multi-user AI apps and agentic systems.
 image: /img/meta/electric-cloud.jpg
 sidebar: false
-hideReleaseBanner: true
+hideReleaseBanner: false
 pageClass: cloud-overview-page
 mdExport:
   mode: parse-html

website/src/components/home/ReleaseBanner.vue

@@ -1,18 +1,27 @@
 <template>
-  <div class="banner">
+  <div class="release-banner">
     <div class="container">
       <div>
-        <a href="/blog/2026/01/22/announcing-hosted-durable-streams"
-          >✨ Durable Streams <span class="hidden-xs">are</span> now
-          <span class="hidden-sm">available</span> on Electric&nbsp;Cloud</a
-        >
+        <a href="/blog/2026/08/11/electric-joining-databricks"
+          >⚡&nbsp; Electric is joining
+          <span class="hidden-xs"> Neon at </span>
+          Databricks &raquo;
+        </a>
       </div>
     </div>
   </div>
 </template>
 
 <style scoped>
-.banner {
+.release-banner {
+  /* At ≤860px the homepage hero scene bleeds up to the viewport top
+     at `z-index: 2` (see HomeHero.vue), covering static content.
+     Layer the banner above it but below the navbar's 30, matching
+     how the navbar stays visible/tappable over the bleed. */
+  position: relative;
+  z-index: 10;
+  background: var(--vp-c-bg);
+
   color: var(--vp-c-text-1);
   border-bottom: 1px solid var(--vp-c-brand-2);
   font-weight: 500;
@@ -23,25 +32,25 @@
   font-size: 15px;
   text-align: center;
 }
-.banner a {
+.release-banner a {
   padding: 18px 24px;
 }
-.banner a:hover {
+.release-banner a:hover {
   color: var(--vp-c-brand-1);
 }
 @media (max-width: 559px) {
-  .banner {
+  .release-banner {
     font-size: 14.75px;
   }
-  .banner a {
+  .release-banner a {
     padding: 18px;
   }
 }
 @media (max-width: 449px) {
-  .banner {
+  .release-banner {
     font-size: 14px;
   }
-  .banner a {
+  .release-banner a {
     padding: 18px 0px;
   }
 }