Loading…
Databricks
161 posts about Databricks. Every summary links to the original.
Stripe data now available on Databricks via Databricks Marketplace
Stripe Data Pipeline is now available on Databricks Marketplace through Delta Sharing, allowing payment and business data to be analyzed in a Databricks workspace without ETL. Stripe data—including transaction records, customer histories, subscriptions, refunds, and payouts—remains in Stripe’s infrastructure and is queried directly through Unity Catalog, where it can be joined with other tables. The approach replaces polling integrations and custom jobs, avoiding per-call charges, connector licensing fees, data duplication, and maintenance code while providing row- and column-level access controls, audit trails, and compliance features. The shared data is positioned for AI-native uses such as continuous transaction monitoring, churn scoring, LLM-powered retention workflows, Genie queries, and finance analytics apps. Getting started involves visiting the Stripe Data Pipeline listing on Databricks Marketplace.
Justin Fenton, Harish Gaur, Matt NapoliDatabricks and Stripe projects: Infrastructure built for agents
The post announces Databricks as a launch partner for Stripe Projects, an agent-first CLI that lets AI agents discover, provision, and pay for Neon databases without human interaction. It addresses the manual work still required to provision services, navigate interfaces, configure accounts, and enter payment details, which can slow autonomous app development. With Lakebase architecture, Neon can provide production-ready Postgres in under 350ms, while decoupled compute and storage support rapid creation and teardown of OLTP databases. Serverless scaling adjusts compute to traffic and can scale to zero, while zero-copy branching creates isolated production-data branches for testing, migrations, and prompt experiments without risking the primary environment. The post also notes Databricks’ Stripe Data Pipeline is available in the Databricks Marketplace for analyzing Stripe data without ETL.
Brad Van Vugt, Guillaume RivalsBuilt in, not bolted on: What AI-native actually means in cybersecurity
The discussion defines AI-native cybersecurity applications as systems architected with intelligence at their core, rather than traditional products with AI added later. It links tool sprawl to slower threat detection and response and argues that proprietary, context-rich security telemetry is the foundation for adaptive defense. Barracuda uses Databricks to consolidate fragmented data, normalize schemas, support real-time streaming detection, run ML operations through MLflow, and power natural-language log search across billions of security events with strict data isolation. The work began by defining customer outcomes, then progressed through incremental delivery; normalized data enabled models and agents to use cross-domain context. This approach extended across WAF-as-a-service, automated configuration, API security, and bot protection while shared outcomes aligned product, data science, engineering, and business teams.
Aly McGueFrom months to minutes: Building real-time clinical data pipelines with natural language
Healthcare data teams often spend months integrating EHR systems, normalizing HL7, CCD, and X12, and routing data through intermediary storage before analytics, creating latency and maintenance burden. Databricks and Redox describe a pipeline model that combines Redox MCP Server, natural-language prompts, and Databricks Zerobus Ingest to build integrations inside Databricks and stream clinical data directly into Unity Catalog managed tables. The post says Zerobus provides subsecond latency, while the MCP Server identifies environments, suggests workflow steps, executes integration tasks, and surfaces validation signals such as logs and performance summaries. A demonstrated workflow retrieved a recent patient admission as structured data with a plain-language summary, and Redox writeback can return AI outputs to EHRs for point-of-care action. The same foundation is presented as enabling real-time use cases and Redox Agents built with Databricks Genie Spaces.
Matthew Giglia, Tim Kessler, Assunta Carey-SaylorHow leading tech companies are killing the builder's tax with Lakebase
The post argues that AI-native applications face a “builder’s tax” because operational databases and lakehouse analytics are separated by CDC, ETL/ELT, and reverse ETL pipelines. This architecture can leave AI systems with stale data while duplicating governance and shifting engineering effort toward orchestration and failure management. It presents Lakebase, a fully managed serverless Postgres engine integrated with the Databricks Data + AI Platform, as a shared operational foundation where applications, agents, analytics, and governance use the same data. The proposed pattern combines a lakehouse intelligence layer, a low-latency Lakebase execution layer, and a continuous learning loop, with pgvector supporting agent memory and semantic search. Reported customer examples include faster feature onboarding, reduced on-call disruption, higher agent throughput, and consolidated data estates, though the results vary by organization.
Amey Banarse, Madelyn MullenModel risk management in 2026: A banker's guide to the revised interagency guidance
The post presents the April 17, 2026 revision to model risk management guidance as a shift toward risk-based, principles-driven oversight, replacing several earlier issuances from the Federal Reserve, FDIC, and OCC. It identifies five operational changes: materiality tiering, end-to-end lifecycle governance, reproducible effective challenge, continuous drift and performance monitoring, and application of MRM principles to GenAI and agentic systems. Its proposed response is a Databricks reference architecture built on Unity Catalog, Delta Lake, Lakeflow Declarative Pipelines, Feature Store, MLflow, Model Registry, Model Serving, and assurance tools. The design makes tiering metadata-driven and turns lineage, validation, approvals, monitoring, documentation, and retirement records into evidence generated during normal model work. The stated conclusion is that a unified substrate can reduce integration and manual evidence work, allowing regulatory changes to become configuration exercises rather than multi-quarter programs.
Pavithra Rao, Jennifer Miller, Chaitanya Varanasi, Kim HattonOpenAI GPT-5.5 + Codex, now available and fully governed on Databricks
Databricks announces native support for OpenAI’s GPT-5.5, making it available for coding workflows with Codex, enterprise agents, document pipelines, and data-driven employee workflows. Access is governed through Unity AI Gateway, which provides permissions and rate limits, configurable guardrails for PII, prompt injection, and content safety, MCP tool-call auditing, failover, and request-level observability for model and Codex interactions. The announcement describes GPT-5.5 use with Genie for natural-language analytics, Agent Bricks Custom Agents for multi-step workflows, and Lakeflow Spark Declarative Pipelines for document-focused GenAI ETL involving summarization, extraction, and classification. GPT-5.5 is available on Databricks across AWS, Azure, and GCP, with entry points including AI Playground, governed Codex endpoints, Agent Bricks, and the Foundation Model API.
Patrick Wendell, Hanlin Tang, Ahmed Bilal, Arnav Singhvi, Ivan Zhou, Harish GaurOperational databases: How they work and when to use them
Operational databases, or online transaction processing (OLTP) databases, support day-to-day operations by processing real-time CRUD transactions with low latency, high concurrency, and ACID guarantees. The guide contrasts them with data warehouses and OLAP systems, which favor historical analysis, complex aggregations, and read-heavy workloads, while describing ETL, CDC, and operational data stores in the OLTP-to-OLAP pipeline. It argues that traditional OLTP systems can struggle with real-time analytics and AI because of siloed data, structured-data constraints, rigid schemas, scaling limits, and missing governance features. Databricks Lakebase is presented as a hybrid solution using separate storage and compute, serverless Postgres, elastic scaling, branching, shared lakehouse storage, and open formats. The proposed workflow connects existing OLTP systems through CDC or streaming into Delta Lake for fresh SQL, BI, ML, and AI access.
Databricks StaffDatabricks partners with OpenAI on GPT-5.5
Databricks announces a partnership with OpenAI around GPT-5.5, described as OpenAI’s strongest frontier model for enterprise agentic work, complex document reasoning, and long-horizon coding agents. The model powers Codex and is presented as able to research, analyze data, create documents and spreadsheets, operate software, use tools, check outputs, recover from ambiguity, and continue through multi-part tasks. Databricks evaluated it on OfficeQA, a benchmark built from 89,000 pages of U.S. Treasury Bulletins that tests document retrieval, table interpretation, and precise calculation. With retrieval handled, GPT-5.5 scored 64.66% versus GPT-5.4’s 57.14%; in the full-agent OfficeQA Pro Agent Harness, it scored 52.63% versus 36.10%, representing reported improvements of roughly 13% and a 46% reduction in errors.
Hanlin Tang, Ahmed Bilal, Arnav Singhvi, Ivan Zhou, Harish GaurAnnouncing the Public Preview of Lakeflow Designer
Databricks announces the Public Preview of Lakeflow Designer, a visual, no-code, AI-native experience for data preparation and analytics built directly into the Databricks platform. It targets analysts, domain experts, and other less technical users with drag-and-drop workflows and natural-language authoring, while representing each transformation as an operator with previews. Genie Code can use Unity Catalog metadata, descriptions, lineage, popularity, and example queries to generate or modify workflows, inspect transformation results, and iterate when needed. Every visual transformation produces production-ready Python code that can be reviewed, versioned in Git, and scheduled through Lakeflow Jobs, while users pay for compute rather than per-user licenses. The preview is available in all workspaces, although an administrator may need to enable Visual data prep in the preview portal.
Jason Messer, Emanuel Zgraggen, V Maharajh, Matt Jones, Tracy YangBeyond the spreadsheet: How Databricks is delivering the modern CFO in financial services
Financial-services CFOs are being asked to act as Strategists and Catalysts, but fragmented legacy systems, T+1 batch processing, opaque reporting logic, and mismatched business semantics keep them focused on stewardship and retrospective operations. The proposed answer is Databricks as a unified, governed platform combining real-time streaming, centralized lineage, data and AI, with Unity Catalog, Lakeflow, Genie, and Agent Bricks addressing trust, latency, access, and model reproducibility. Unity Catalog can connect semantic definitions and end-to-end lineage from transactions through regulatory reports and models, while Lakeflow supports continuous ledger and liquidity processing. The post cites a global bank reducing liquidity-reporting processing from 10 hours to 8 minutes and Nationwide Insurance reporting a 5-point combined-ratio improvement and 3-point expense-ratio improvement. It presents a Lakehouse-based CFO stack as a shift from reporting historical results toward real-time capital management and previews AI-driven deposit and PPNR modeling.
Jennifer Miller, Marcela Granados, Andrea DeSosa, Alex Oberlander, Kim Hatton, Pavithra Rao, Naeem Rehman, Pravin Varma, Olga Deriy, Prasanna SelvarajAI App Development: Guide To Building AI-Powered Apps
Production-grade AI app development combines model orchestration, transactional state, governance, security, and live-data integration rather than only interface construction. The guide recommends defining users, outcomes, success metrics, timelines, and AI-relevant journeys, then shipping must-have features before enhancements. It evaluates builders by end-to-end support, technical audience, platform integration, code export, CI/CD, data connections, pricing, and deployment limits. For Databricks teams, it describes Databricks Apps, Declarative Automation Bundles, and Lakebase: serverless app compute, version-controlled deployment, and managed PostgreSQL with synced Unity Catalog Delta tables. It also recommends monitoring outputs, collecting correction feedback, refining prompts with automated evaluations, and governing models through MLflow, concluding that integrated infrastructure can leave teams focused on production AI workflows.
Databricks StaffPersonalization Strategies for Media Companies
Media companies are expected to tailor content and messaging across channels, with personalization programs typically targeting lower churn, deeper sessions, and higher subscription revenue. The proposed foundation starts with an audit of CRM, email, warehouse, and customer data platform sources, followed by required-field definitions, ownership mapping, consent tagging, and ingestion-quality checks. Teams then map segment behaviors and conversion or retention paths, including negative signals, before selecting a CDP with real-time ingestion, identity resolution, unified profiles, segmentation, activation, and governance. Identity rules should connect anonymous and authenticated activity across web, mobile, and connected TV, while event-level streaming delivers messages through email, push, in-app, and advertising channels with minimal latency. The roadmap recommends an MVP comprising unified ingestion, a homepage recommendation surface, and triggered re-engagement email, with performance, churn, revenue lift, and model drift monitored through iteration.
Databricks StaffIntroducing the Databricks Excel add-in for business users
Databricks has introduced the Excel Add-in, now in public preview, to let business users import and analyze lakehouse data directly in Excel without writing SQL or configuring ODBC drivers. Built on Databricks SQL and Unity Catalog, it provides point-and-click access to tables and metric views, native Excel pivot tables, refreshable results, reusable Workspace queries, and optional saved SQL. Metric views let data teams define business semantics once while Unity Catalog centrally manages permissions and controls, helping avoid duplicated logic and metric drift. The preview supports selecting tables and metric views, parameterized custom functions, manual refreshes, pivot-table filtering, query reuse, and workspace changes; scheduled refresh, AI integrations, and other usability improvements are planned next.
Toussaint Webb, Kaitlin BaumgardnerFrom Static Policies to Autonomous Insurance: How AI enables Real-Time Coverage
Insurance products often rely on annual pricing, periodic risk assessment, and coverage changes tied to major life events, even though driving behavior, digital fraud exposure, and travel risk can change in seconds. The post presents embedded insurance and usage-based insurance as a shift toward contextual, just-in-time coverage delivered through apps, checkout flows, vehicle purchases, and partner platforms. Its automotive example combines telematics, geospatial data, and real-time weather signals to update risk scores and premiums from trip behavior such as braking, following distance, mileage, location, and environmental conditions. A Databricks Lakehouse architecture registers devices, ingests telemetry through Zerobus, curates data in a governed Medallion architecture, and exposes features through Lakebase and Databricks One, with Unity Catalog supporting access controls, lineage, explainability, and audit trails. The proposed trajectory leads from embedded coverage toward autonomous insurance whose policies continuously adapt to risk.
Amee Vora, Anindita Mahapatra, Marcela GranadosBanks don't have an AI problem — they have a data platform problem
The post argues that banks’ difficulty scaling AI stems less from model capability than from fragmented data, weak governance, and limited real-time access. Examples from CBA Live 2026 include model drift in credit scoring, fragmented customer signals, and a collections model that predicted, with 85% accuracy, how many days newly delinquent accounts would take to cure using governed data. It also presents Erica’s 3.2 billion interactions since 2018 as evidence that production AI requires continuous tuning, monitoring, and edge-case management, while generic models decay in frontline settings. The proposed Databricks architecture combines Lakehouse, Unity Catalog, Lakeflow, Lakebase, MLflow, Model Monitoring, Online Feature Store, Genie, and Agent Bricks to support governed analytics, low-latency decisions, auditable models, and constrained agent actions. Its conclusion is that a shared data platform should precede additional AI use cases because it improves deployment speed, trust, explainability, and regulatory defensibility.
Naeem Rehman, Jennifer MillerOpen Platform, Unified Pipelines: Why dbt on Databricks is Accelerating
dbt provides structure for transforming raw data into curated datasets, but the post argues that its effectiveness depends on the underlying platform. Databricks is presented as an open lakehouse combining storage, compute, governance, orchestration, and monitoring to reduce duplicated data, fragmented permissions, and operational overhead. Lakeflow Jobs runs dbt alongside ingestion, downstream actions, retries, and dependencies, while Unity Catalog supplies persistent permissions, documentation, lineage, and fine-grained controls. The integration also supports Delta Lake and Apache Iceberg, query tags for cost tracking, Photon, Predictive Optimization, Liquid Clustering, and dbt materialized views. The post concludes these capabilities provide openness, integrated operations, governance, and price-performance for dbt workflows, citing one customer’s consolidation of notebooks and 7+ source systems and more than 2,900 customers already running dbt on Databricks.
Srilekha Dornadula, Ramiz BozaiDatabricks on Google Cloud: Innovate faster. Smarter. Together.
Databricks and Google Cloud are presenting their partnership at Google Cloud Next ’26 as a route from governed enterprise data to production AI, including autonomous agents and modernized workloads. In 2025, Databricks became a first-party provider of Gemini models, giving users direct API access to build, customize, and deploy agentic AI on governed data across all three Databricks clouds without moving data or managing infrastructure. The post reports more than 55% quarter-over-quarter growth in Gemini adoption, 85% year-over-year growth in Google Cloud consumption, and 4,000-plus Marketplace sign-ups, alongside support for Google Axion processors. Customer examples include Databricks SQL Serverless savings for Digital Turbine, faster Marketplace procurement for Dun & Bradstreet, regional compliance in Saudi Arabia and Brazil, and 30% faster analytics delivery through Lakeflow-powered pipelines. At the event, Databricks is offering demos, talks, expert sessions, and a free $400 trial through Google Cloud Marketplace.
Taylor Hoss, Sarah JackIntroducing the Databricks Connector for Google Sheets: Real-Time, Governed Lakehouse Data in the Sheets Users Love
Databricks has introduced a Google Sheets connector that brings live, governed lakehouse data into a familiar spreadsheet environment. The connector addresses reliance on CSV exports, snapshots, and custom pipelines, which left business teams with siloed copies, inconsistent metrics, and slower decisions. Built on Databricks SQL and Unity Catalog, it lets users query governed datasets, including Unity Catalog Metric Views, through a no-code GUI or SQL, while Unity Catalog manages permissions. Users can refresh results manually or schedule refreshes, keeping Sheets data current without exporting snapshots. The connector is Generally Available to all Databricks customers, and Nubank reports that it has enabled non-technical users to explore data in Sheets while preserving control.
Toussaint WebbLovable + Databricks: Build Data-Driven Apps at the Speed of Thought
Databricks users outside data teams often depend on requests to access business data because they may not write SQL or have a Databricks license. The official Lovable connector lets teams connect Lovable to a Databricks environment and build custom internal applications with plain English. Lovable's AI-powered agent examines accessible data and builds and deploys an application, while Databricks remains the source of truth and data stays within its security perimeter. Data is queried from Databricks at runtime, avoiding ETL, data replication, and sync jobs. Examples include live revenue and pipeline dashboards, spreadsheet-replacing operational tools, internal Slack chatbots, and other business applications that teams can build without engineering or data-team support.
Evan Pandya
