@danprimack And/or it’s classic and prudent book building strategy to build momentum and increase both pricing and size later on. Little downsize to start conservatively.
I don't think we should fight. The two companies are complementary. Since you're not doing this AI stuff, I really think Snowflake should consider getting its AI tokens through Databricks. You can get both cheap OSS models as well as frontier (OAI/Ant/Gemini/Grok) models from our platform. It all goes through Unity Gateway which has Smart Routing, Budgets, and Access Control. You can even use Omnigent with any harness, including CoCo. Most of our customers used this to reduce token spend ~30% last few months while token count went up. Genie lets you then track, control, manage that spend, all your financials, marketing, etc. Quick POC?
I got this question so many times today. "How can you grow 80% at $7B?"
The true answer is that we're finally seeing a breakthrough with AI agents starting to work in the enterprise.
The AIs have been super smart for a while, but have lacked basic context that's in people's heads, or in some SaaS system-or-record. A lot of organizations are deploying FDEs to capture this context, or Ontology, and feed it to the AI. This is labor intensive and expensive. We just automated that with Genie Ontology.
Once you have that enterprise context graph, an AI agent like Genie becomes magical. I find myself no longer waiting for answers from my CRO, CFO, CMO, CHRO etc, I just keep queuing up questions on the phone while sitting in meetings. It'd frankly addictive.
Our customers are starting to do the same, over 70% of all queries on the platform are now generated by Genie agents. This fuels more questions to the platform, which drives consumption, which drives revenue. That's the simple answer.
We disclosed today as part of our Series L that our 4-yr old data warehousing business is now >$1B revenue run rate. This is to the best of my knowledge the fastest to $1B DW product in the industry. How did we do it, and what’s next?
The conventional wisdom is that it would take 5+ years to build a new database (just to release one).
Four years ago, the linked blog announced that Databricks had won the official TPC-DS 100TB benchmark with DBSQL, which was in preview back then. It had the best perf and the best price/perf, and notably beating Snowflake by 12x in price/perf in that benchmark. (Note: we are still the top place on the official TPC-DS benchmark today.)
That blog post launched a contentious "benchmarking war" with a lot of back and forth between vendors, but more importantly it marked the very beginning of our data warehousing business.
To build this business, we assembled the best engineering team and established a new infrastructure product category called Lakehouse that inherits the flexibility and openness of data lakes and performance of data warehouses. Lakehouse is now the standard for data infrastructure, and organizations are migrating from legacy data warehouses to the Lakehouse.
The result so far is a testament to the team and their execution. We have a lot of ideas on how to take performance and usability to the next level, and the team is working hard to make that happen. Expect some big announcements next year. We want to lay the foundation for growing the data warehousing product to a $10B business.
Databricks had operated largely in the “analytics” side of data in the past, and we believe the “operational” side of data (aka “OLTP”) is also ready for a “Lakehouse” style disruption. A huge chunk of the founding team’s time is now focusing on “Lakebase”, a new category of OLTP databases that separates storage (in the lake) from compute. That architecture enables features that have been virtually impossible for databases in the past: instant provisioning, elastic scaling (down to zero), branching, high throughput scan directly from Spark, …
I won’t go into too much detail about Lakebase here, but we expect a similar trend to happen in the next few years: Lakebase will transform the industry and other OLTP systems will re-architect or position towards it.
The best data warehouse is a lakehouse, and the best database is a lakebase!
https://t.co/BHrOE18Gtt