Databricks Buys Row Zero for Planned Genie Spreadsheet

Databricks acquired Row Zero, a cloud spreadsheet its finance team had already used with Genie; TechCrunch’s September 24, 2026, deal report says the price was not disclosed and notes that Row Zero raised $10 million in May 2025. Databricks’ acquisition announcement says Row Zero will become a native spreadsheet interface for Genie, its AI coworker, drawing on live data, permission-aware queries, export controls, write-back and auditable activity. The acquisition is complete; the native Genie interface remains a planned product experience.

The appeal is a familiar way to work with enterprise data after Genie answers a question. Finance teams can build formulas and scenarios in a grid while the underlying data remains connected to its source. Whether the future interface preserves the controls of an existing Row Zero workbook will depend on integration details that have yet to be specified.

Why a spreadsheet matters to Genie

Exporting a query result to a conventional spreadsheet creates a snapshot. If the source data changes, the downloaded file does not update unless someone refreshes or replaces it. Sharing that file can also create copies beyond the system that checked permission for the original query. A data platform may govern access to a table while having less control over the exported values used in a forecast.

Row Zero offers a connected grid for the work that follows a query: calculations, pivots and scenario modeling. Genie can supply a way to ask about a business metric; the spreadsheet can hold the assumptions and formulas used to explore what that answer means. The proposed integration would bring those activities closer to the same governed data, rather than requiring every analysis to become a detached file.

That does not make a spreadsheet calculation automatically trustworthy. A reviewer still needs to know which source values fed a model, who changed an assumption and whether an agent produced or revised a formula. The distinction matters most when a workbook moves from exploration toward a decision or a result written back to another system.

What the existing Row Zero connection does

The Row Zero Databricks connection guide documents an existing route into Genie: Row Zero can discover Genie Spaces available to a connection and use a selected space to generate SQL. With individual OAuth credentials, queries respect the database permissions of the person running them. A shared connection using a service-account token instead operates through that account’s access, making the choice of connection identity consequential.

The identity also needs access to the Genie Space, its underlying data and the selected SQL warehouse. Those requirements describe how a Row Zero user reaches Databricks today. The acquisition points toward the reverse journey, from Genie into spreadsheet modeling, but the connector does not establish how the eventual native interface will handle workbook sharing, collaboration or existing connections.

This distinction limits what customers can infer from a working integration. The products can already exchange queries, yet a query connection is only part of a spreadsheet experience. Keeping a live workbook governed also requires decisions about what happens after data appears in cells: who may export it, who may change it and whether a change may be sent back to a source system.

Where governance must follow people and agents

The acquired spreadsheet’s controls address different stages of that work. Permission-aware queries govern which data a connection can retrieve; automatic refresh reduces dependence on stale snapshots; export restrictions limit the creation of separate copies. Write-back needs its own authority because changing a result in a workbook is different from changing data in another system. An audit trail is useful when it identifies the actor, action and resulting state.

Shared work between a person and an agent makes those distinctions sharper. If an agent creates a formula and a person later changes it, a reviewer would need to distinguish the two actions and see which version produced a decision. The public acquisition details do not specify whether agents in the native Genie spreadsheet will act under a user’s identity, a service identity or a separate approval process. They also do not describe which write-backs, if any, will require human sign-off.

The existing connection shows why identity cannot be treated as a minor setup choice. Individual OAuth access and a shared service account can expose different data to the same spreadsheet workflow. How that difference will appear to users and reviewers inside Genie remains an implementation question, as does the treatment of audit history when work moves between the current product and a native interface.

What remains open after the acquisition

In TechTarget’s interview about the integration, Databricks product manager Ken Wong said work on the native version had begun but gave no target release date or pricing for its integrated features; he also described plans to continue the separate Row Zero product and Databricks’ Excel add-in. The add-in provides access to Databricks data in Excel, while the proposed native spreadsheet would put modeling inside the Genie experience.

Continued support for the separate product offers existing Row Zero users some continuity, but it is not a migration timetable. There is no published account of whether their workbooks will move into Genie automatically, how connection identities and sharing rights will carry over, or whether earlier audit records will remain visible there. Those questions will determine how much of the promised governance extends through an entire modeling workflow.

Databricks now owns the spreadsheet product and has begun building its native Genie integration. The deal price remains undisclosed. Customers are still waiting for a release date, commercial terms and a precise description of how permissions, agent actions and write-back will work together.