Databricks said on August 13, 2026 that it closed a $5 billion strategic funding round at a $190 billion valuation. The close advances the company’s July term-sheet announcement and establishes a completed financing event. It does not establish that $5 billion entered Databricks’ bank accounts or became unrestricted cash available to treasury.
The announcement does not disclose the split between new capital issued by the company and any secondary liquidity for employees or existing investors. It also omits transaction deductions, settlement evidence, restrictions on proceeds, the post-close cash balance and a forward cash-use basis. Treasury should therefore keep the $190 billion valuation, the $5 billion gross round and usable company cash as separate measures. Actual runway remains unverified.
What changed and what it means
Treating the $190bn valuation or the full $5bn round as company cash could materially overstate unrestricted liquidity and runway.
- Decision affected
- Decide what amount, if any, may enter unrestricted liquidity and runway scenarios before primary proceeds, secondary liquidity, deductions and settled cash are evidenced.
- Evidence in brief
- Databricks says the round closed at $5bn and a $190bn valuation; the July release establishes the previous term-sheet state, while Reuters corroborates the financing.
- What remains unresolved
- The primary-versus-secondary allocation, transaction costs, restrictions, cash received at closing, post-close cash balance and forward cash-use basis are not disclosed.
- Next verification
- Require a closing sources-and-uses schedule, capitalization reconciliation and bank-settlement evidence before changing base liquidity or runway.
Key takeaways
- Databricks closed a $5 billion strategic funding round at a $190 billion valuation on August 13, 2026.
- The valuation is a financing-pricing reference, not cash, liquidity or runway.
- The full round cannot be treated as issuer cash until the primary-versus-secondary allocation, deductions and settlement are evidenced.
- No disclosed post-close cash balance or forward cash-use basis supports an actual runway calculation.
What changed from the $188bn term sheet
The July 16 term-sheet announcement said Databricks had signed a term sheet for strategic funding at a $188 billion valuation and expected the round to close later in the summer. It did not state a funding amount. The August release changes two verified fields: the status moved from signed term sheet to closed, and the company disclosed a $5 billion round at a $190 billion valuation.
Reuters corroborated the $5 billion financing and $190 billion valuation, along with the named lead investors and Databricks’ stated product-investment plans. Neither the company release nor Reuters provides a closing sources-and-uses schedule. “Closed” is therefore the correct transaction status, but it is not a substitute for a proceeds reconciliation.
Earlier Databricks financing terms should not be carried into this round. The company’s February 2026 financing announcement separately described approximately $5 billion of equity financing, approximately $2 billion of additional debt capacity and expected employee liquidity. The August announcement does not repeat that structure. Treasury cannot assume the same debt, employee-liquidity or primary-capital treatment applies.
The $190bn valuation is not cash
A financing valuation is a pricing reference for the company or securities in the transaction. It is not a cash balance, a committed facility or an amount available for spending. The release also does not define the valuation basis in enough detail for treasury to turn it into a cash measure.
The $5 billion round size is closer to the funds flow, but it is still a gross transaction figure. A private round can include newly issued company securities, purchases from existing holders, employee liquidity or other transaction components. Cash paid for secondary shares goes to selling holders, not automatically to the company. Even the primary portion may differ from net cash after fees, expenses, reimbursements and other documented deductions.
A six-stage test from round size to usable treasury cash
| Stage | Minimum evidence | Treasury treatment |
|---|---|---|
| Valuation | Financing terms and the defined valuation basis | Transaction-pricing context only; never record as cash |
| Gross round size | Executed closing schedule confirming the total transaction amount | Record as the reported round, not issuer proceeds |
| Primary-versus-secondary allocation | Share or security schedule identifying company issuance and holder sales | Exclude secondary liquidity from company cash |
| Issuer gross proceeds | Sources-and-uses schedule identifying the amount payable to the company | Use as a controlled financing input, subject to deductions and settlement |
| Issuer net proceeds | Closing statement with fees, expenses and other deductions | Forecast the expected receipt by amount and date; do not yet call it cash received |
| Settled unrestricted cash | Bank receipt, account ownership, restriction review and ledger reconciliation | Enter base liquidity only to the evidenced usable amount and settlement date |
The public record currently stops at the gross-round stage. The financing is closed, but the information needed to bridge from $5 billion to issuer net proceeds and settled unrestricted cash is not disclosed.
Why a closed round still does not establish runway
Runway needs a defined opening cash amount and a defined forward cash-use assumption. A simple scenario may divide unrestricted cash available for operations by forecast net monthly cash use. Neither input appears in the August financing release. The announcement therefore cannot support a public estimate of how many months the round adds.
Databricks says it delivered positive adjusted free cash flow over the preceding 12 months and surpassed a $7 billion revenue run-rate. Those are company-stated performance measures. They are not the post-close cash balance, and they do not establish future cash generation under a product, acquisition or infrastructure plan. Revenue run-rate is also not cash on hand. Treasury would need the company’s own liquidity forecast, committed uses and scenario assumptions before changing runway.
What Databricks has not disclosed
- The amount of the round attributable to newly issued company securities.
- Any secondary sales, employee liquidity or existing-investor liquidity.
- The security types, pricing schedule or capitalization reconciliation.
- Fees, expenses, reimbursements or other deductions from issuer proceeds.
- The settlement date, amount credited to controlled accounts or bank evidence.
- Restrictions, earmarks or board-approved allocations attached to the cash.
- The post-close cash and cash-equivalents balance.
- A forward operating cash-use or free-cash-flow forecast suitable for runway.
Databricks says the investment will support Lakebase, Genie and Unity AI Gateway. That identifies intended strategic areas, not an allocation schedule or proof that all issuer proceeds are unrestricted. The absence of public detail does not imply that the company lacks internal closing records; it limits what an outside treasury analysis can count.
What treasury should verify next
- Obtain the executed closing package and reconcile the announced $5 billion to each security and selling party.
- Separate primary company capital from employee, founder or investor secondary liquidity.
- Reconcile issuer gross proceeds to net proceeds through fees, expenses and any other deductions.
- Confirm settlement in controlled bank accounts and document restrictions, earmarks and approved uses.
- Update the liquidity model only for the evidenced usable amount and settlement date.
- Recalculate runway from a controlled post-close cash balance and a forward cash-use scenario, not from valuation or revenue run-rate.
Until those records are available, the defensible public classification is narrow: Databricks closed a $5 billion round at a $190 billion valuation; the amount of unrestricted company cash added and the resulting runway are unverified.