Click any tag below to further narrow down your results
Links
Genie One is a free iOS app from Databricks that lets business users ask plain-language questions and get answers drawn from their company's governed data and dashboards. It's in public preview and aimed at checking numbers on the go or tracing why a metric suddenly moved.
- Answers are grounded in the organization's governed data, curated business logic, and dashboards, not general web knowledge.
- Users can ask follow-up questions to drill down toward root cause, and browse mobile-optimized dashboards.
- The app also launches Databricks Apps from one place, and the latest update adds deeplinks into AWS and GCP workspaces.
Databricks has updated Genie, its AI agent, to handle multistep business tasks without supervision. CEO Ali Ghodsi shows how he uses it to surface bad news his 12,000-person company's managers won't tell him directly.
- Genie now runs multistep jobs unsupervised, using an ontology Databricks built from customer data on its platform.
- Ghodsi uses it to analyze a poorly scoring employee survey, rate executive fixes, and summarize a failed sales pitch, including the features the prospect wanted.
- He argues that past about 150 employees (Dunbar's number), leaders stop hearing negative news, and cost controls come through Databricks' Unity Gateway, which sets usage limits and swaps in cheaper open-weight models.
Databricks, Snowflake, Google, Amazon, and Microsoft have all built AI-facing products on PostgreSQL, and this piece explains why the open license, extension model, and developer familiarity made it the shared choice. It also warns that "Postgres" now covers four different levels of compatibility, so buyers need to check which one they're getting.
- Databricks paid around $1 billion for Neon and Snowflake paid around $165 million for Crunchy Data, showing the premium the market puts on real Postgres compatibility plus modern architecture.
- Extensions like pgvector, pg_lake, and pg_duckdb turned Postgres into a single engine for state, vector retrieval, and analytics, which suits most AI workloads below very large scale.
- "Postgres compatible" ranges from the real engine to a wire protocol over a different database, and the extensions you rely on determine which layer you need and what leaving will cost.
This a16z piece argues Databricks is quietly building the data infrastructure that agentic AI will need to run inside real companies, tracing its path from Spark to the lakehouse to Lakebase. It ties that infrastructure to a bigger claim: that front-line workers will regain decision-making power from the managerial hierarchy that dominated the 20th century.
- Databricks grew from Spark, an open-source engine Matei Zaharia wrote at Berkeley that kept data in memory and ran iterative workloads up to ten times faster than Hadoop.
- The "lakehouse" merged cheap data lake storage with warehouse reliability, and the company says its Lakehouse runs at a more than $1.5 billion revenue run-rate, growing over 100% year over year.
- Databricks bought Neon in 2025 to build Lakebase, which separates storage from compute and removes the pipelines between operational databases and analytics, a setup the author says agents will depend on.
Databricks is buying Panther to bolster its security lakehouse platform as an alternative to legacy SIEM systems. Panther’s AI-driven SOC tools and over 100 pre-built integrations will automate threat detection, alert investigation, and response at scale.
- Databricks is acquiring Panther (price undisclosed, pending regulatory approval) to fold into its Lakewatch security lakehouse, positioning it against legacy SIEM tools that are costly, partial, and slow.
- Panther adds 100+ prebuilt integrations and AI-driven automation for threat detection, alert triage, and response, aiming to help defenders keep pace with AI-powered attacks.
- This is Databricks' third security acquisition (after Antimatter and SiftD.ai), signaling a deliberate push into AI-native security infrastructure.
- With 70% of the Fortune 500 already using Databricks, the deal extends its reach into cloud/SaaS-focused enterprise security operations.
Databricks is launching a Software-Defined Storage ecosystem that uses the open-source OpenSharing protocol to link on-premises, edge, and private-cloud systems directly into its Data Intelligence Platform. This zero-copy approach lets teams run serverless compute and train models on local datasets under Unity Catalog governance without migrating any data.
- Databricks now lets you query on-prem/edge/private-cloud data (via MinIO, Everpure, Qumulo, VAST Data) directly through Unity Catalog with zero-copy access and no egress fees, using the open-source OpenSharing protocol
- MinIO's AIStor integration is already GA, letting users run live queries on on-prem Iceberg and Delta tables; Everpure and Qumulo are in private preview, VAST Data joins in August
- Targeted at regulated/data-sovereignty-heavy industries (banks, healthcare, semiconductors, trading firms) facing GDPR/HIPAA/NIS2 rules and untenable cloud egress costs at exabyte scale
- Connections must pass Databricks's Partner Well-Architected Framework for security/certification before going live, preserving full lineage, access controls, and audit logs across hybrid environments
This article breaks down how Databricks’ ai_parse_document and ai_query functions simplify PDF extraction in a proof-of-concept but introduce hidden challenges—ongoing costs, duplicate processing, non-deterministic outputs, and input noise—when you scale to a reliable production pipeline. It walks through the core issues and why you need additional system design for checkpointing, deduplication, deterministic validation, and PII handling before using it on real healthcare data.
- Reprocessing a 30,000-page corpus costs ~$120–$137 every time you iterate, at ~$4.20–$4.55 per 1,000 pages.
- No built-in checkpointing means any small prompt fix forces a full reparse of everything.
- Even at temperature zero, non-determinism (LLM rounding, parallel GPU execution) can flip extracted fields like follow_up_required, breaking audit trails.
- Duplicate documents (corrected/resent notes) slip through unnoticed, skewing patient cohort and diagnosis counts.