Lakebase
Recent items mentioning Lakebase across the Databricks ecosystem — releases, news, videos, and community Q&A. Updated hourly.
What is Lakebase?
Lakebase Postgres is a fully managed Postgres database built into the Databricks platform. It's real Postgres, so standard drivers and clients work, and instead of a fixed server you provision a project with branches and databases inside it.
Analytics tables in the lakehouse are a poor fit for application backends that need low latency reads and writes, and that's the gap Lakebase fills without leaving the platform. You can sync Unity Catalog tables into Lakebase so applications query them quickly, and store Postgres changes back as Delta tables for pipelines and audit (that direction is in Public Preview). Autoscaling, scale-to-zero, and instant branching keep development and test environments cheap to create.
Lakebase reached general availability on January 22, 2026, with automated backups and point-in-time recovery; read replicas and high availability with automatic failover are also available, the latter added in March 2026. As of September 2026 it tracks current Postgres releases, with major versions 16, 17, and 18 supported.
Is Lakebase generally available?
Yes. Lakebase reached GA on January 22, 2026, including autoscaling, scale-to-zero, instant branching, automated backups, and point-in-time recovery. One notable exception is storing Postgres changes as Delta tables with full change history, which is in Public Preview.
Is Lakebase real Postgres or just Postgres compatible?
It's actual managed Postgres, and standard Postgres drivers and clients work against it. As of September 2026 it supports Postgres major versions 16, 17, and 18.
How much does Lakebase cost?
Billing is usage based and began in January 2026, with snapshot storage billed separately since June 1, 2026. Scale-to-zero and autoscaling are the main levers for keeping idle branches and quiet databases cheap; Databricks publishes current rates per cloud and region on its pricing page.
Do I need Lakebase if I already have the lakehouse?
The lakehouse handles analytics, while Lakebase is for transactional application workloads that need low latency reads and writes. The two connect: you can sync Unity Catalog tables into Lakebase for fast serving, and capture Postgres changes back as Delta tables for downstream pipelines and audit.
Sources: Lakebase Postgres (Databricks docs) · Lakebase release notes (Databricks docs)
Built directly on Delta and Iceberg storage rather than external replication pipelines 9, Lakebase Postgres delivers an LTAP architecture that serves 99.46% of reads without leaving the compute node 4. Databricks also launched Lakebase Insights, an autonomous telemetry agent that flags deadlocks and missing indexes for Genie-assisted remediation 56, while teams increasingly leverage copy-on-write database branching to safely evaluate AI agents against production data 310.
Generated daily from the 10 most recent items mentioning Lakebase. Click any [N] to jump to the source.
Predictive Optimization keeps running on system.lakebase after disabling it at account level
NewsHow Jio Platforms move insights into production with Databricks | Data + AI Executive Series: Fast 5
Jio Platforms relies on Databricks Lakehouse to unify data and AI governance and achieve end to end lineage across its businesses including telecom, retail, media, and finance. The company uses Databricks Genie and Lakehouse to accelerate insights to production and allow business users to define their own KPIs and metrics.
Branch, sync, serve: What our Lakebase Hackathon taught us about building on Lakebase
Operational Postgres is becoming an integrated part of the lakehouse rather than a standalone system running alongside it. Customer hackathon projects demonstrate this shift by using Databricks Lakebase to safely test applications and AI agents via database branching, while syncing directly with the lakehouse to serve real-time data and ML features.
Built on object storage, served from cache
Lakebase Postgres combines durable object storage with a caching architecture that serves 99.99999% of production page reads from fast local cache. With 99.46% of reads never leaving the compute node, fetches to object storage are limited to rare one-offs like cold restores or waking idle databases.
ReleasesIntroducing Lakebase Insights
Lakebase Insights is a new agent that reviews Lakebase Postgres telemetry in the background and surfaces issues like slow queries, deadlocks, and missing indexes. It provides severity rankings, evidence, plain-language explanations, and recommended fixes, which users can apply themselves or have the Genie AI assistant handle.
TutorialsLakebase Insights: Find and Fix Postgres Issues Before Your Users Do
Lakebase Insights is an agent that analyzes your Lakebase Postgres telemetry in the background to flag issues like slow queries, deadlocks, and missing indexes. It automatically ranks findings by severity, provides plain-language explanations and evidence, and integrates with Genie to help you fix problems.
Databricks is a Leader and positioned highest in execution in the 2026 Gartner® Magic Quadrant™ for Data Lakehouse Platforms
Databricks has been named a Leader positioned highest in execution in the 2026 Gartner Magic Quadrant for Data Lakehouse Platforms and the sole Visionary for Cloud Operational Database Management Systems. Complementing this recognition, Databricks Lakebase Postgres delivers an open-format transactional database on the lake to serve as the system of record for agentic workloads, modern applications, and traditional systems.
Transactional apps on Databricks: Lakebase owns the decision, Delta gets the copy
Dispelling LTAP myths
Lakebase's LTAP design makes the data lake the database's primary storage rather than an expensive replica maintained through logical replication pipelines. By pairing a single Delta or Iceberg table with Postgres caches and pageservers, point lookups read heap pages while scans read Parquet, ensuring analytical queries always see consistent snapshots that include commits not yet in the lake.
How H6.ai builds AI-powered financial automation with Lakebase Postgres
H6.ai isolates customer data on its multi-tenant AP automation platform by provisioning a dedicated Lakebase Postgres database for every account. By leveraging copy-on-write, schema-migrated branches and AI judges, the team safely replays exact invoice issues and validates new models against real cases without touching live production or ERP systems.
NewsCompare Amazon RDS for Postgres with Databricks Lakebase
Lakebase provisions databases much faster, scales and idles automatically, branches instantly, and integrates with Unity Catalog seamlessly compared to Amazon RDS. Lakebase also enables zero-pipeline reverse ETL through continuous synced tables, whereas Amazon RDS requires separate standalone services and manual configuration.
Lakebase in production: what surprised you?
NewsS2 Ep4: All About the Rise of Genie | Falek Miah
Genie is a natural language interface that has evolved into a comprehensive suite of AI tools including Genie Agents, Genie Code, Genie App Builder, and Genie Ontology. These tools integrate with platforms like Lakebase to streamline data access, automate app building, and improve data governance.
Lakebase Data API
NewsRun Postgres Across Availability Zones with Databricks Lakebase
Lakebase high availability allows a database to run on multiple availability zones using one primary compute and up to three secondary computes. This configuration keeps replicas warm and ready to take over queries when a primary compute fails.
Announcement | Lakebase branching for CI/CD: lessons from 100 PR databases
DQX Studio - Data Quality App
Saw this app available on the marketplace: https://marketplace.databricks.com/details/99214a23-5dc6-48c4-968d-c1f0a6ed8c37/Databricks\_DQX-Studio-Data-Quality-App Do Databricks Apps like the above have any dependencies e.g. Lakebase that I need to pre provision? Or is that all taken care of after hitting the "get access" button? Also, are all these apps free? Is the DQX app free? submitted by /u/RazzmatazzLiving1323 [link] [comments]
TutorialsDatabricks Genie App Builder: From Prompt to App
Databricks Genie App Builder turns plain-English prompts into actual applications with logic, queries, and UIs using the AppKit framework. The deployment command commits code to Git, checks it, and starts the deployment, allowing users to build apps without spreadsheets.
NewsDQX Studio Demo: No-Code Data Quality on Databricks
DQX Studio is a native Databricks application that enables business users to define, manage, and monitor data quality rules with AI assistance. It features a rules registry, table mapping, rule marketplaces, and drill-down reporting, and is available for installation through the Databricks Marketplace.
Zerobus to lakebase
NewsServe Lakehouse Data to Your App with Lakebase Synced Tables
Lakebase synced tables allow you to effortlessly bring Delta tables from your lakehouse into your app's PostgreSQL database. The video demonstrates how to create a continuous sync pipeline and shows that data updates propagate from the lakehouse to the application within seconds.
NewsScale Postgres Up, Down and to Zero with Databricks Lakebase
Lakebase separates compute from storage to automatically scale database resources up and down based on real-time workload demands. It can also automatically scale down to zero when idle and instantly wake up upon receiving a new query.
Databricks Asset Bundles now deploy registered model aliases to Unity Catalog and resolve bugs that repeatedly reapplied permissions and grants to recreated resources. The CLI also restores Databricks-specific pip magic execution in Jupyter notebooks over SSH and removes the CRITICAL compute priority class from AI Runtime.
Lakebase streaming sync is now GA
Hey Reddit, I’m happy to share one more new feature. The Lakebase streaming sync is now officially GA. Lots of customers are already using this feature to write streaming data with latency in 10s of milliseconds to Lakebase. It's much simpler to use than foreachBatch and you don't have to worry about connection pools, rate limits, error handling, etc. Here's what's new since we announced the Public Preview earlier this year: Declarative merge strategies*: Choose, per column, how an incoming row is reconciled with the existing row on a primary-key conflict. For example, you can keep the latest non-null value, keep the first value written, or take the value from the row with the latest event time. No custom SQL is required. External PostgreSQL via UC connections (Public Preview)*: Write to Postgres databases outside Lakebase, authenticated through a Unity Catalog connection so no credentials live in code. INTERVAL types*: DayTimeInterval and YearMonthInterval columns map to Postgres interval on DBR 19 and above. Serverless support: The sink now runs on serverless compute for notebooks and jobs, using the AvailableNow trigger. \ Merge strategies, external Postgres, and interval types require DBR 19.* Example: df.writeStream .format("postgresql") .outputMode("update") // optional; can be append mode as well .option("upsertkey", "primaryKey") // optional .option("upsert.columnStrategies", "last_updated_at:greatest,status:latestBy(last_updated_at)") .toTable("catalog.schema.table") SDP support remains in Private Preview. Public Preview, which adds support for native Lakebase streaming tables, is slated for later this year. submitted by /u/inkypinky [link] [comments]
TutorialsMulti-Part Series: App Developer - Introduction to Databricks Development
This video introduces the Databricks App Developer skill builder series, which covers application architecture, identity and governance, data and compute choices, AI integration, deployment, and operations through a series of hands-on labs. It highlights Databricks Apps, AppKit, Lakebase, and Unity Gateway as key tools for building and managing secure, scalable data and AI applications.
Real-time fraud detection with Feature Views
Feature Views let you define fraud features once and reuse them for both point-in-time training and online scoring, which reduces data leakage and training-serving skew. The example pairs rolling windows for payment bursts with a 30-day Sawtooth baseline and an on-demand feature that scores each payment against it, and a single materialize_features() call sets up managed streaming pipelines into the Online Feature Store on Lakebase with sub-200ms feature freshness.
A builder’s guide to scaling Databricks Apps
Scaling Databricks Apps starts with agreeing on target response times and peak user counts, then routing heavy work to the right service while app compute handles the UI and coordinates calls. Keep code responsive and state recoverable by caching per user and storing hard state in Lakebase or Unity Catalog tables, then size instances, workers and Lakebase connections from load tests and telemetry.
NewsWhy the Creator of Delta Lake Says: Stop Writing ETL
Spark declarative pipelines, or SDP, allow engineers to define what data tables and transformations should exist rather than manually scripting how to execute them, letting the system handle the underlying orchestration, incremental updates, and error handling. Michael Armbrust and Alexandra Chashchina explain how SDP simplifies data pipelines across various workloads, improves cost efficiency, and reduces manual intervention compared to traditional Spark and Delta Live Tables approaches.
Building on Lakebase | Episode 3: Branch, Test, and Ship: Release Changes Safely using Branching
NewsLakebase Search Explained
Lakebase search introduces two new Postgres extensions, lakebase_text and lakebase_vector, to optimize text and vector search. These extensions allow developers to run search operations directly alongside operational data in a single SQL query.
TutorialsHow To Detect Telecom Fraud in Real Time with an AI Fraud Analyst Coworker | Databricks Demo
The video demonstrates a real-time telecom fraud detection platform built on Databricks that unifies data infrastructure, governance, and AI agents. It showcases executive, management, and analyst views to monitor fraud metrics, forecast case volume, and investigate high-risk transactions.
NewsBuilding on Lakebase | Episode 3: Branch, Test, and Ship: Release Changes Safely using Branching
Lakebase branching allows developers to test database schema and code changes on isolated, production-like data branches without affecting production. The demonstration shows how automated GitHub Actions workflow uses pull requests to create branches, run migrations and tests, review schema diffs, and merge changes.
Databricks Apps vs AKS + Lakebase for Business Applications
We’re currently evaluating two architecture options for an enterprise business application: Azure AKS/K8S + Databricks Lakebase: Host the application on AKS and use Lakebase as the transactional database. Databricks Apps + Lakebase: Host both the application and database within the Databricks ecosystem. The application itself is less analytics-focused and more geared toward supporting business operations, including workflows, CRUD operations, user management, RBAC, APIs, and integrations with other systems. I’m leaning toward AKS given its flexibility and maturity, but Databricks Apps seems appealing from an infrastructure management and deployment perspective. Curious if anyone has experience running business applications on Databricks Apps in production. A few things I’m particularly interested in: - Any limitations with scalability, performance, or concurrent users? - How does Databricks Apps handle complex backend logic and external integrations? - Any challenges with CI/CD, monitoring, authentication, or environment management? - How do the costs compare once you factor in infrastructure and operational overhead? - Is Databricks Apps mature enough for business-critical applications, or is AKS still the safer choice? Would appreciate any real-world experience or lessons learned, especially from those who have worked with both approaches. submitted by /u/Conscious_Awareness6 [link] [comments]
Lakebase Change Data Feed exports whole schemas: feed it one event table instead
Lakebase synced tables: how can a database owner/admin configure default SELECT privileges for the m
Lakebase Postgres is now generally available on Google Cloud
Lakebase Postgres, Databricks' fully managed serverless Postgres database, is now generally available on Google Cloud, with autoscaling, scale to zero, instant branching, and point-in-time recovery built in. Because operational and analytical data share the same storage foundation, analytics, apps, and agents run on one platform without fragile pipelines to maintain.
TutorialsHow to Use Database Branching in Databricks Lakebase
Databricks Lakebase provides serverless PostgreSQL database branching for fast schema testing, allowing users to run migrations on branches and apply them to production while avoiding data merges. Lakebase also offers point-in-time database restoration to recover data safely without overwriting the production environment.
Lakebase branching for CI/CD: lessons from 100 PR databases
Snorkel AI's CI/CD pipeline now gives every open pull request its own Lakebase Postgres branch, a full read/write copy of production data that's ready in under a minute rather than the 30+ minutes that previously made per-PR copies impractical. Because branches are copy-on-write, 100 concurrent PR databases on a ~2.5 TB production dataset add storage only for what each one changes, with TTL expiration cleaning up automatically and private connectivity plus Okta SSO keeping the setup governed.
Built my AngelHack Quest 4 App with Databricks Apps + Lakebase
Databricks and SAP unleash end-to-end data & AI capabilities to level up enterprise AI transformation
Databricks and SAP are expanding their partnership to give customers broader access to SAP application data across cloud and on-premises, speeding time to value for analytics and AI. Genie, Lakeflow, Unity Gateway, and Lakebase now come to SAP Databricks fully integrated with SAP Business Data Cloud, so teams can use the full Data + AI Platform on all their SAP data.
Serving the Lakebase Data API Through Azure API Management
NewsCreating a Digital Twin with Spark Real-Time Mode and Lakebase
This video demonstrates how to create a real-time digital twin for a manufacturing cell using Databricks tools such as Spark Real-Time Mode, Lakebase, Databricks Apps, and Unity Catalog. It explains how processing sensor readings instantly allows operators to detect and act on equipment faults, such as a hot spindle, before they negatively impact production quality and efficiency.
Migrating Europe from RDS Postgres to Lakebase
submitted by /u/Limp-Park7849 [link] [comments]
How to teach with Databricks Free Edition
Databricks Free Edition can anchor a full data and AI curriculum, from intro data science and statistics through data engineering, BI, machine learning, AI, and capstone projects. Students work with the same tools used in industry, including Apache Spark, Delta Lake, MLflow, Lakebase, Genie, and Databricks Apps, while instructors can hand out assignments through an existing LMS or GitHub and share datasets via cloud storage, Open Sharing, or Marketplace.
TutorialsLakebase Search: Build AI Retrieval for Agents with Lakebase Postgres
Lakebase Postgres introduces lakebase vector and lakebase text extensions to support hybrid search for AI agents. It leverages the Databricks Lakehouse architecture to synchronize and index data for efficient vector and full text search without requiring external databases.
The media industry is becoming a prediction economy
Media and advertising are shifting from counting attention to predicting and proving outcomes, which makes performance a leading indicator rather than a lagging one. Agents and measurement stall on fragmented data (only 3% of CMOs can tie half their marketing to a business outcome), so the post argues for one governed data and AI foundation built on context (CustomerLake, Genie, Lakebase), control, cost, and choice (Unity Gateway), and cites a pet specialty retailer that saw a 12% lift in transactions after activating loyalty data with agents.
How to add a resource to an app space?
Hi, I was testing out the Genie App Builder today and wanted to created an app which connects to a Lakebase postgres table. However, Genie told me the resource postgres is missing in the app (space) and I should add it. In the app settings I can't add the resource because the app is managed/restricted by the app space. But in the app space I cannot find the option to add the postgres resource either (according to the documentation only "User authorization", "Serverless usage policy", and "Permissions" can be configured https://learn.microsoft.com/en-us/azure/databricks/dev-tools/databricks-apps/app-spaces#configure ). Is it possible to add resources to app spaces? Or am I limited with them? submitted by /u/IIDraxII [link] [comments]
Test on a Branch, Not on Patients: Agentic Drug Substitution with Lakebase
AI Agent Memory
Databricks supports agent memory storage. The amazing part is that Lakebase stores the memory, so we can also inspect the saved record. We can save "User prefers Mexican recipes" and recall it through a client with the question "What should I cook for dinner?" more news https://medium.com/databrickscommunity/databricks-news-genie-cli-app-builder-agent-memory-dabs-41820427fcc2 submitted by /u/hubert-dudek [link] [comments]
Real-time energy trading and analytics on Databricks
Energy trading teams can run live trading and analytics on one Databricks platform instead of separate systems that leave risk data stale and governance duplicated. Spark Structured Streaming Real-Time Mode streams market data into Lakebase (serverless Postgres), which feeds the trading app, ML models, dashboards and Genie One, while Unity Catalog handles permissions, lineage and audit once for all of it.
Quest 4 Completed – Building and Deploying My First Databricks App with Lakebase
Databricks Apps/Jobs Deployment Issue on New Workspace: Due to Quota?
My company sells a data analytics application to professional sports teams. The application is built as a Databricks App, deployed into a customer's workspace. The underlying data model is seeded by ETL that lives in my own company's workspace, with the gold tables shared as pinned version views into the customer's workspace, where a daily job syncs the views into Lakebase on the customer side. I built this on Databricks partially because the customers typically don't have robust IT teams in-house. Rather than requiring them to self-manage a bunch of infrastructure or host my own costly SaaS backend, I figured I could save a lot of complexity by setting up a Databricks workspace for them and deploying the application code into it via DAB from a central repo. I'm having an issue with a new customer that I onboarded yesterday. They created a new Azure subscription for the purpose of deploying the Databricks workspace + our application. Everything deployed successfully, but the Databricks App stops itself after approximately two hours. At first I thought it was a transient issue and restarted the app, but it keeps recurring. Troubleshooting has been challenging, because App logs are not visible when an App is stopped. I was able to get the following from the CLI ( databricks apps get -o json ): "app_status": { "message": "App status is unavailable.", "state": "UNAVAILABLE" }, "compute_size": "MEDIUM", "compute_status": { "message": "App compute was stopped due to workspace or account status.", "state": "STOPPED" }, Both the Azure subscription (Azure Plan) and the Databricks workspace (Premium + RBAC) do not appear to be in a trial state. Both were set up in the past 48 hours. I suspect this is some kind of new workspace restriction on the Databricks side, but I'm not sure what can be done about it. The App is deployed into a few different workspaces and runs without issue, but all of the workspaces have existed for a while. This is the first Workspace that was deployed specifically for the App. I found this thread on Databricks Community that describes a similar issue, but it appears to have died without a resolution. Has anyone run into a similar issue, and is there anything that can be done about this? It's likely that many of our customers will need a new Databricks workspace to deploy our application, so if this is a recurring issue, we may need to rethink our entire architecture. submitted by /u/Minute_Visual_3423 [link] [comments]
The Fraud Analyst AI Coworker: Detecting Telecom Fraud in Real-Time on One Platform
Databricks Lakebase, Databricks Apps, and Genie combine into a single fraud detection stack for telecom, with Lakebase removing the analytical/transactional split for faster data sync, Apps powering a custom case-management workbench, and Genie acting as an AI coworker that answers natural-language questions over governed fraud data. The post argues that real-time network telemetry strengthens fraud models as attackers use agentic AI at machine speed, and the Telecom Fraud Prevention Solution Accelerator deploys the risk engine, workbench, and investigation agent via Databricks Asset Bundles, adaptable to other industries.
LTAP without lakebase?
Is there any world where an LTAP architecture can be created that does NOT include lakebase, or databricks for that matter? It seems to me that it isn't much more than a marketing term for selling lakebase. Every public doc about LTAP has references to lakebase sprinkled all over it. Lakebase is mentioned from the beginning to the very end. As I understand LTAP is essentially defined as a shared storage layer for OLTP and analytics workloads. And that sort of storage is an implementation detail that is ONLY found in the deepest and most proprietary parts of lakebase. (IMO, Microsoft has had their own flavor of LTAP for many years, in the form of Fabric DW. That engine looks and acts similar to a TSQL database, yet emits lakehouse files in storage. Yet I suppose it lacks some very particular features, or performs badly on certain disqualifying OLTP workloads. The disqualifications will always allow a databricks salesman to refuse to call it LTAP. If these disqualifications aren't purely subjective, then maybe we also need to define LTAP in terms of a certain TPS threshold and a certain set of minimal DBMS capabilities. I haven't seen anything like that.) submitted by /u/SmallAd3697 [link] [comments]
Performance Test - Batch-Loaded Unique Constraint Validation in Lakebase
The vendors that create big-data engines keep saying it is so challenging and costly to enforce uniqueness constraints in their managed catalogs (eg. in technologies like UC managed tables, that live on top of lakehouse blobs). They say it "doesn't scale". And that it gets more challenging at large volumes. But this is like anything else - customers should still be empowered to use features that may not always scale well. Would this problem get easier if they offered it only for certain data types like 32 bit unsigned integers? Lets consider Lakebase. Lets say I'm a user of Lakebase, and I'm running sequential batch transactions to insert a consecutive series of 1000 integers at a time that are validated by the database to be unique. How long would it take until those transactions to become slower than 100ms? Should I expect to to insert all 4 billion integers and never see any transaction take longer than 100ms? Now lets do a similar thing in a UC managed table , where we insert the same sequentially increasing 1000 integers at a time, and I check for the uniqueness of these myself in my serializable insert transactions. (Because the UC managed table won't help me with that.) Obviously my uniqueness validations would start to slow down over time. As I approach the limit of 4 billion integers I would expect the insert operations to take longer than lakebase , but possibly never more than one second per transaction. Does that sound about right? (If necessary I might use cheats, like break apart the integer into four columns of one byte each, then use partitioning). TLDR, validating uniqueness with 32 bit integers may be harder in a UC managed-table than for lakebase. But IMO that does NOT mean customers should be doing the heavy lifting ourselves. These lakehouse-based technologies should give us a mechanism for it, even if there are restrictions (ie. certain data types, tables of no more than 4 billion rows, etc). submitted by /u/SmallAd3697 [link] [comments]
Lakebase: Postgres That Actually Likes Your Lakehouse
Introducing Agent Memory on Databricks
Agent Memory is now in Beta on Agent Bricks, giving agents a Lakebase-backed store for facts, preferences, and workflows, built on Databricks Research's MemCurrent architecture, which combines plugins, on-demand tools, and an offline "dreaming" pipeline. In Databricks' internal benchmarks on enterprise tasks, it tripled agent pass rate while using 31% fewer tokens, and the Agent Bricks CLI can deploy an agent with memory and sessions in minutes.
How Hamlet uses Databricks Lakebase Postgres to test changes against production data
Hamlet gives every pull request its own Lakebase Postgres branch of production data, so engineers can reproduce and test fixes against the exact data that caused a bug without touching production. AI coding agents run the pipelines and check their work on each branch before a person approves the merge, and Hamlet is now exploring Lakebase Search, branching for object storage, and a home for longer agentic jobs.
ReleasesIntroducing Agent Memory on Databricks
Databricks announced Agent Memory, a new tool for Agent Bricks that allows AI agents to store and recall past conversations and user data using lakebase architecture. By connecting session stores and memory stores through automated memory pipelines, agents can retain context across multiple sessions to improve task performance and reduce token usage.
How to Sync Lakebase Tables to Delta with Lakehouse Sync
Get Tuesday's version of this
Tracking Lakebase? The Tuesday email carries what moved across the whole ecosystem, not just this topic. Free, one-click unsubscribe.