So it was kind of out of despair that we started Databricks because no one else is listening to it. At that time there is zero interest in AI. Now I think we have all the intelligence we need to completely transform the planet.
It's not possible to have a thousand agents doing stuff realistically. Am I correct?
They're just using AI in very rudimentary ways. They're just using it as a glorified Google search. We're actually getting into like management moneyball, aren't we?
So if the token cost is going up exponentially, is your revenue at your company going up exponentially? But I actually think GDP will move very slowly and it's going to take decades.
Are they a little drunk on their own success?
Just because 98% of the code is being written by AI, we don't have RSI. If it automates the last 2%, who cares?
When are you going public?
If you were building a global financial system from first principles today, you wouldn't build it on 50-year-old legacy rails. You'd build Airwallex, one AI-native platform for global accounts, cards, and payments, designed to make the entire world feel like a local market. Others are bolting AI onto broken infrastructure, but Airwallex was built for the intelligent era from day one. Stop paying the legacy tax and start building the future at airwallex.com/allin. Airwallex, built for the future.
All right, everybody. Welcome back to the All-In interview. We're so lucky because all of these amazing leaders in the world — CEOs, politicians, scientists — they watch the show. They're part of the community. And Ali Ghodsi is one of those individuals. He, of course, is the CEO of Databricks, a private company that has been doing incredible. I don't know why it's not public yet. I think a lot of people are asking that question. We'll talk about it today. In 2015, they were doing 1.5 million in revenue. It's August — or the rumor I heard, August 2026 — Ali, $7 billion run rate, growing 80% year over year. And obviously you got a lot of competition, the Snowflakes of the world, etc. But this is a tremendous business, and we're going to talk a lot about how you're using AI to run this incredible business. We're going to talk about recursive self-improvement, but welcome to the program, and then maybe you could tell the audience a little bit about what you do at Databricks and how it became so successful.
Yeah, happy to do that. Thanks for having me on. Excited for this. Yeah, so we started the business in 2013, but if you rewind a little bit before that, we were all at UC Berkeley. There were about 20 of us, and we were actually part of a lab called AMPLab, which was, I think, the largest AI research lab in the world at that time. And you know, we were trying to figure out how can we combine data processing with AI, and you know, we came up with really interesting things, but the industry was just not ready for it. So we were trying to get the industry to adopt this technology, and they weren't. So it was kind of out of despair that we started Databricks because we thought, you know, if we don't start a company around this, no one else is listening to it. At that time there was zero interest in AI. Actually, it was called machine learning at the time, and AI was just robotics. So that's kind of like the beginning of the story.
And for people who don't use the product day in and day out, who aren't in the industry, what's the goal of the Databricks product suite? What do you do? I know you released some new products today. So happy to talk about those as well. But conceptually, you got there so early, obviously machine learning. Google was built on that, Facebook and their ad network, a lot of interesting services, Uber and their routing algorithms. Maybe you could talk a little bit about where Databricks started and what it's become and how it's generating billions of dollars in revenue.
Yeah. So the first use case actually — the first use case ever was at UC Berkeley when we wanted to help Netflix recommend better movies so that people would watch more movies. So it was like a, you know, recommendation algorithm AI use case that started the whole thing. And then we thought, you know, more organizations — probably every organization will need a data science team that can do this kind of AI stuff, and it was kind of bold at the time. There's a lot of people that said, no, no, no, AI is just for ad tech, the ad companies need it, but we thought, no, no, this is going to be a bigger market. And actually, we had a lot of debates internally. We weren't sure it was going to explode. So we got into it, and then we realized when we started the company, we realized why they're not doing it, why it's so hard, because basically all the organizations out there in the world are like bogged down. They have legacy software that they've had for 30, 40, 50 years, and some of them, you know, companies have been around for 100 years. You know, things are moving slow. They have a lot of processes. There's, you know, a lot of compliance, a lot of regulatory, a lot of security, but all these things have gone worse with generative AI in the recent years. So basically what was missing from our research at UC Berkeley was that we didn't think about the security, the governance. So what we did the first bunch of years is that we figured out how do we take this technology that lets you process all your data in an enterprise. So you know, organizations have a lot of data. The most important data they have — actually people don't talk about it — the most important data any company has is the data on the core product that they have. Like for you here, it's this podcast, you know, the data on that. Someone else might be selling insurance, someone else might have, you know, a drug. It's the data that comes out of that. That data doesn't sit in CRM. It doesn't sit in human resource management. In fact, it probably wasn't even tracked.
I remember in the early days of the internet, they'd be like, hey, would you like this log file? And I'd say, okay, yeah, keep everything. And they'd say, okay, well, you got an $8,000 storage bill a month. And I'd be like, okay, delete it. And they're like, well, we could roll it up and keep some of it. I'm like, well, who's ever using the open rate on our emails? Who cares about that? You know, we send the emails, that's it. But then that changed. And was storage and compute and cloud computing a major accelerant to this big data movement and then eventually machine learning? Those were kind of the waypoints in this movement.
Yeah. Before we started in 2013, basically people were running their own data centers. And when they're running their own data centers, you had to buy machines, and the machines came with storage and compute combined. So if you ran out of storage, you had to buy more machines. And the IT departments of every organization were busy with this. What the cloud enabled was to just completely decentralize this and separate compute and storage. So that you could just imagine you have infinite storage. You just dump everything there. Okay? And if it's gone cold, so the data is old, it knows how to archive it. So it becomes almost free to store it. And then you could get the illusion of as much compute as you wanted, and then of course you could start running machine learning on it, and then eventually GPUs showed up. So it kind of transformed everything. We bet everything, the whole farm, on just being a cloud company. We bet everything on AI, the use cases of AI, and we bet on open and open source. And at the time, actually, all three of these bets were controversial. People were — I had a standing bet with one of the most important analyst firms out there where they said it's a strategic blunder, you're going to go under because you're betting on the cloud. And it turned out actually the only reason we succeeded was because of these bets, because they were contrarian, because other people did not agree with them. So we got a head start for many, many years. And then eventually when we, you know, happened to be right, then we had, you know, we were so far along and we got too big that, you know, there's too much momentum to stop it.
It's so funny you mentioned this Netflix algorithm. Netflix started, obviously, in the Bay Area as DVDs that were mailed to you in an envelope, and then you had this queue, and it was critically important. For people who don't know, the Netflix Prize. This was in the 2008-2009 time period. They put a million-dollar prize out to any computer science team that can make the algorithm, I think, 10% better at predicting what movie you would give four or five stars to. So they just took all their data, they released it, and then they got probably $50 million worth of work from computer scientists around the world. It was the first time an X Prize — and I think X Prize and this were around the same time, and they were all inspired by those old prizes. So like who could circumnavigate the globe, who could solo fly over Amelia Earhart, who could solo fly over the Atlantic or the Pacific. It was like a very interesting moment in time. And that hit AMP, right? And AMP, the group was algorithms, machine learning. I don't know what the P stands for.
It was for people, actually, because we thought that, you know, the AI is not good enough yet.
So it needs a little bit of human nudging.
So it's nice, actually, this kind of, you know, human feedback was already there. We were like, we do need the human feedback because this last mile is just too hard for AI to figure out itself. So we had people there as well.
Putting the people in there makes sense because Berkeley's a little hippie-dippie. Friedberg's alma mater, obviously, they were like, we need some people in the middle of this. You know, we had Ben Horowitz on the other week, and he was like, the best explanation I've ever heard for why we are going to be able to control the rollout of superintelligence and this jump between artificial intelligence or artificial general intelligence and superintelligence that gets recursive and runs off with it and dooms us all and we're all going to die sentiment by some people came from you. So, please explain your thesis here. And then I'd like you to go even one step further and talk specifically about maybe the culture in the Bay Area, perhaps even the East Bay, and this group of people.
I mean, happy to get into it. You know, I think there's sort of two different things happening at the same time. On the one hand, I actually think we already have artificial general intelligence. I've been saying it since last year, and I base that on the kind of consensus we had in that AMPLab where it was, I think, the largest AI lab at the time in 2009-2010, and that definition of AI that most of us had — AGI — we already achieved that last year. And I wasn't actually sure about this, so I actually went and checked with some of the people that were in the lab, like, hey, is it just me, am I hallucinating? And they said, no, no, no, that definition for sure, but we've moved the goalpost, you know. So I actually think we have all the intelligence we need, and actually, if you happen to stop all progress right now, I think we have all the intelligence we need to completely transform the planet.
Okay, but that's — we do all intelligence work by humans, right? I mean, if it solves this latest cohort of math problems and we're just starting to build harnesses and build out the infrastructure, I guess your statement would be correct. And I kind of am in line with you. We've hit artificial general intelligence. It just hasn't been equally distributed yet.
Yeah. So the labs and a lot of researchers, they're kind of obsessed with superintelligence. Okay. So when I say superintelligence, I mean it the way it was defined by Bostrom in 2014 in his book called Superintelligence. And there he's talking about something completely different. He's talking about something that can do a millennia worth of thought. So like a thousand years of human thought, it can do it like in a minute. Okay? All of mankind in a minute. It thinks in 11 dimensions. It's so much faster. Just a single agent is just, you know, many orders of magnitude — imagine a thousand times faster than any of us, okay? And that's just a different thing. Like, it can write a novel PhD thesis instantaneously and so on. So I think the labs are on the quest of that, and in that, by the way —
So just to summarize that, there's the ability to write an entire unique PhD thesis instantly. Which do we even have the amount of compute in your mind to do something like that today? If everybody got together and said, hey, today we're going to give all our compute, or for the next hour, just as a thought experiment, to this incredible mega prompt. Do you think it would actually happen? Is it a computer issue or is it a model issue?
Well, actually, the AIs are kind of slow. What we have to do is we have to parallelize them and have many of them, and we have to have them, you know, collaborate with each other. So it's actually not the way that he wrote it down. He had also intelligence in the book of how it can be, you know, communities of intelligence. But I'm just saying the labs and many of the other companies are focused on this, and that's why they're so obsessed with the math, the Clay problems, the seven, you know, millennial problems and so on. But I argue that the biggest challenge that's facing us is how do we actually just make this AI applicable inside organizations? That's what Databricks is focused on. We just want to help all these organizations. And when I go talk to organizations out there, enterprises, I see that they're just using AI in very rudimentary ways. They're just using it as a glorified Google search. They're using chatbots all day. And instead of typing in Google search and getting 10 blue links and then looking at the 10 blue links, the AI just does that for them.
The second thing that they're doing is they're doing coding. Okay? And with the coding, actually, they're not seeing enough speedups. They're seeing maybe like 20-30%. I ask them this question every day. I'm in meetings every day with customers and I ask them these questions. That's kind of what reality looks like. I always ask them, how many of you have, you know, thousands of agents running around automating all of work and doing core work for you and so on. It's just not happened yet.
Now, they might be running a half dozen agents, a dozen agents. Like somebody who's at the forefront might actually be coordinating against that many, but the human still needs to be in the loop. Just like AMP, like there's a person who still needs to be in there because it will return slop, it will return weirdness, it can go drift off course. It's not possible to have a thousand agents doing stuff realistically. Am I correct?
Yeah. Well, some are further along. I mean, I'm actually using this all throughout Databricks, and I'm happy to show you, but, you know, the reality is that they're not. And you have to ask the question, why is that? Like, if it can solve Navier-Stokes, very difficult math problems, how come enterprises and organizations out there are so far behind?
And I think — yeah.
Well, there's many reasons, but the main reason is — or maybe one way to look at it: if we could gather all the information that you have inside a large organization with 200,000 employees, record all the meetings, which, by the way, that itself — one of the big bank CEOs told me the other day, no way, we're never recording the meetings. Like, not in a million years. But assume you have —
Liability. I mean, by the way, which I already — I was already kind of shocked because if you can't do that, how can the AI ever help you? Like, the AI is simply not in the meeting. If it's not in the meeting, it's useless. It doesn't matter if you have Terence Tao or you have the greatest mathematician in the world. If they're in the cold and they don't know what decisions or what you're doing, and you're meeting with hundreds of thousands of employees, there's no way it can help you. So, if you capture all that context and you could feed it to the AI, they would nail the problems. They could help us right now already. So that's really the context problem. Now, you might say, okay, well, let's figure that out and do that, and we were doing that at Databricks, but that's not enough. Even if you do that, you have a second problem, which is, you know, you could unleash something like OpenClaw and just have it access all your data everywhere. Well, then you get into this problem that you're going to get hacked. Cyber is a real thing, and all the big organizations that have successful businesses, they're really terrified right now of getting attacked, right? This is like a big concern. The top —
It certainly creates a lot of surface area when you embrace this. I mean, if a CEO or in a small company you want to connect everything, it's a certain amount of surface area, but for a 200,000-person organization, 10,000 — my lord, the surface area has now gone 1,000x.
Yes. Exactly. So that's like the second problem you bump into, which is like, okay, we can access all the data. Well, wait, we don't want to maybe access all of it to the agents because, you know, now we have an insider threat and we might get hacked. So what do we do about that? Well, let's say we solve that too. So now we've solved the cyber problem, which, by the way, we have actually ways to do that at Databricks. Happy to show you. Then you still have another problem, which is, okay, now the token cost is going up exponentially. So if the token cost is going up exponentially, is your revenue at your company going up exponentially? And I don't know any company who started using AI and as of their use of AI the revenue started accelerating exponentially matching their cost curve. So then eventually, first of all, CEOs are like, go get the AI, get more AI, get it in there, you know, we need to move faster. Yeah.
Exactly. But then at some point the CFO shows up and says, hey, our opex is going up significantly here, and even the cogs, what are we doing about it? And we have an earnings call soon, and then they freak out. So then how do we fix that? So you need to also do this efficiently, which we also have ways to do that at Databricks. Now you've done all of these three, then there's a strategic last question that still remains, which is like, okay, fine, we figured it out, we accessed all the data, we secured it, and, you know, we figured out the cost situation. How do we avoid getting locked in, and how do we own our own IP? Because, you know, otherwise, you know, there's no business to be made in the future, because —
Data sovereignty is what you're kind of referring to, intelligent sovereignty. And if you use Anthropic, OpenAI, or any of these platforms, there is this risk that it will leak, that it will get incorporated into their next version. And as we've seen, a company called Anthropic seems to be releasing every two weeks a half dozen products that just now they're competing against Microsoft — one of their, I think Microsoft is like one of their giant partners — and they just came out with basically an Excel killer. They're killing Photoshop, and they're just going after everybody wholesale.
Yeah. For free. For free. Yeah. Yeah. So, by the way, these companies are amazing. They're doing amazing work, and without them, we wouldn't even have this intelligence probably. So, you know, I'm thankful. This is awesome. I'm just pointing out why when you look around you, all these, you know, successful organizations, all the Global 2000, all the Fortune 500s, NASDAQ, and so on, how come it's just glorified chatbot and a little bit of coding? This is the reason. So, you need to really tackle all four of those, and only then can you start getting something out of it.
And one of those issues as well, I believe, is the autonomy in an organization to come up with a groundbreaking idea. You know, you may have captured a large portion of your market. You may be getting incremental benefits. So if I tell you like, hey, we can put another 500 horsepower into your Ford Taurus, it's like, okay, my Ford Explorer now has 500 extra horsepower. It's going to rip the chassis off. This thing is not capable of going 500 miles an hour. So then it's, well, who decides we're launching three more product lines? Well, at Anthropic, somebody is deciding, why don't we just go after every single business in the world? And they started doing dashboards. That's a little close to your business, is it not?
Little dashboards over here.
So dashboards, you know, we don't have a product where we charge for dashboards. Dashboards are usually backed by data, and you typically want that data to be governed. So, you know, you don't want just numbers and then, you know, those numbers are incorrect. This is a big problem in organizations. So that gets back to the second thing I said, the governance security aspect. Okay. So like, yeah, maybe we can get access to all the data and get all the context, but we got to make it secure. So yeah, it's great. You can actually connect all of these agents from outside to Databricks, but then we are the governed data repository, and then when you access that data and, you know, the governance, we charge consumption rates on that. So actually that's one of the reasons you see acceleration of our business because all these companies, whenever they have agents and they're using it — and I think we're just in the beginning, as I said, I still think it's mostly Google search and coding — but the agents, when they start using that, they just, you know, send us more queries.
How does the behavior change when people actually embrace agentic technology and they start working with agents, let's say every hour, every other hour of the day, like you and I do?
I think that the organization — the org charts are built this way, you know, it's like a tree structure, the CEO at the top, and all decision-making goes kind of up and down in these org charts, and you have all these old processes, and getting agreement across this org chart is very, very hard inside of an enterprise or inside of any organization that's sizable. It's somewhat easy up until Dunbar's number, which is 150. You can know everyone. So small startups, it's a different story. But above 150, this becomes a coordination problem. But if you look at how actually any organization actually, you know, sells a product or a service to its customers, it's actually not this kind of hierarchical thing. It actually cuts across that org chart. You know, like here at Databricks we have customers. They give us feedback. The feedback goes to product management organization. Product management hands it to engineering organization. Engineering builds products that goes to marketing, that markets it, you know, and then marketing gives it to sales, that sells it to customers again. So you kind of want to go across. So you want to cut out that latency so that you can be really, really fast. But that requires that you have an AI that actually understands your whole business, your IP. It needs to understand your org chart. It needs to know who's who, who's —
What percentage of companies actually understand what you just described? Would you say 10% of organizations understand this? 5%?
At scale? I don't know how many — I don't know the answer to that. At scale, I know that Databricks is doing it. I'm doing it.
I haven't seen anyone else, to be honest, do it at this kind of —
You know, I think probably Block and Square with Jack Dorsey, since he's pushing — he's calling it the company world model. He calls the same thing I kind of described, I think, you know, different way of viewing it. He's calling it the company world model. So I think that they're probably pretty far ahead in general. I think digital natives are probably further ahead. Digital natives being companies that have only existed 10, 15 years. You know, if you've been around 20, 30, 40, 50 years, which means you're an amazing company, maybe you're a Fortune 500, the best companies in the United States, you have maybe 100,000 employees. You know, they're loyal. You know, they love your products. And you know what? You're the best in the world on that. You just — you have so much software, you know, you have so much regulation, and you have so many processes around security and so on, that it's very hard for you to adopt this. But that is the very problem Databricks wants to solve for them. So we want them to adopt the technologies, so that the AI, so that they can do what I do at Databricks, basically.
Yeah, let's see it. You said you would be willing to show us like how you run Databricks with agents and with AI, and I've been looking forward to this all day because I literally am taking the entire — while you queue it up — my entire life on podcasting and on early-stage investing. And I'm looking at each of the components of those things as services, as agents, and defining the goal, working backwards to what are the signs of success that you're heading towards the goal. Not that you've achieved the goal. The achieving the goal is kind of binary. Yes or no, you made the sale, you didn't. But what are the precursor signals? And then trying to have each of these bots hand off things back and forth. It's —
You have to be a real systems thinker. It's like kind of playing five chess games at once while riding a horse. I mean, you're —
It's really like intellectually, I find it super stimulating. I can tell you do too. So hey, you can share your screen.
So let's jump in. So okay, so the key thing here is that — so we have a product called Genie. But the key thing that Genie has, because, you know, there's so many chatbots out there and there's so many assistants and there's so many cowork products out there and agents in the background. The key thing is that it has an ontology. The ontology is a graph that it constantly is constructing for your company. That graph understands all of the people, who reports to who, what are they working on, what are the emails that are coming in, what meetings have happened, and what's the transcripts of all those meetings and all the decisions that are being made there, what's on Slack, what's being communicated. So it has access to all of these things, and then also all of the docs that you're creating, all the Excel sheets, all the PowerPoint presentations. So it has access to all of those. That's what we call Genie here. So you can see here.
So I wake up, it, you know, I have an — it has an inbox. In the morning when I come in, it basically has done a bunch of background work for me. It's running 24/7. As you can see, it has access to my, you know, calendar. In fact, I could just ask it like, you know, —
Which I tell Jason on All-In today. Here it goes.
Yeah. So see what this is going to say. But let's look at some of the stuff that I've done. So like actually the other day, one of the interesting things is I was looking at our HR department came back and they were saying, hey, we've done a survey on all of Databricks. You know, so we had over 10,000 people, employees that responded to this survey, and you know, I looked at the results and she was going through it, and you know, I said, hey, make me a dashboard of the results. You know, did nothing magical here yet. So it told me like, look, here's how you're doing. You're doing great on some things, but —
Executive leadership 88%, you're doing okay.
Work-life blend —
60%. That you're working people pretty hard over there. But maybe everybody says that, right?
Yeah. No, but we want to know. But this has been — so we wanted to improve these two. And this action one really bothers me because, you know, action — by the way, it means that when we ask them for feedback, they give us feedback, improve this and that, and they feel like you're not listening to us. So two out of three feel you are. One out of three feels you're not. Just to —
You're doing okay. It's not terrible, by the way. This could be like 30%.
60% is not great. So, but — and especially not great if you actually take into account that every year it's low, and every year I promise the company we're going to fix this, and every year it doesn't happen.
So, you know, we're going through the results, and, you know, we're discussing it with these staff, and while they're discussing it, they're speculating. You know, my CFO says, you know, hey, I think it's because of work-life blend. Work-life blend is bad, you know, and that's causing action to go down. So it's causing — work-life blend is causing low action. And I was like, that doesn't make any sense. But I just entered here immediately as we were discussing, and it immediately pulled up, okay, this is the correlation between these two, and this is how it's looking. But then I was like, wow, maybe he's right. But then it says, no, actually it's not causal. It's not causing it. And here's the exact proof points. We probably have to anonymize these folks, but here's a manager that has work-life blend 44. That's pretty bad. Action is 77%. So, you know —
They're working hard, and he's recognizing and taking action on their concerns. So —
That's kind of — that's your guy right there. He's pushing people hard, and he's listening to them. I like that.
Exactly. So, okay. So now I'm learning stuff about the organization. This is amazing. It would have taken me like a week to get the data team to do this analysis for me, but that's just me getting information. That's useful. So, like, we're cutting this, you know, latencies up and down the org chart a little bit. But then I'm like, okay, why is it low? And look through all of the comments, and it gives me some reasons. I didn't like the reasons. So then I actually clarified the question. I say, hey, can you slice it by department for me?
And, you know, and then actually figured it out. It said, look, product management has low action because they don't like decision-making — there's too many stakeholders. Engineering, they don't like the tools and systems. There's too much — you know, sales operations, it's career growth, and so on and so forth. So —
That makes sense because salespeople always think they should get a promotion because they're salespeople and they should get their commissions right, and product people think you should just listen to them.
Instead of, you know, six people trying to design a piece of art. This all starts to track now with the data and the AI. I love it.
Yeah. So how did it do this? It has access to its ontology. So it's not going and searching live only. It actually found that there's already — it already had in its graph these people, you know, already five people had already contributed to this, and there's 19 pieces of information here that you can see that it's actually leveraging that already had — it didn't search for them live. These are in the ontology. So we can look at, for instance, this particular one. If we click on it, it has a definition, it's a metric, and there's a graph. And this graph, you can see it here, you know, so there's a favorability, and it comes from, you know, this is the author. You can click on the author, and because it understands the org charts, it understands who this person is. This person actually has 29 snippets, you know, they have lots of different assets, you know, that they've — you know, that it's learned from them. So this constantly is learning the intelligence or ontology of your organization. So that's a typical thing. Here's another one that, you know, is maybe interesting. I wanted to know — actually, there's new results here in the last 59 minutes. I haven't actually looked at all of those, but I wanted to understand the org chart and what's going on with the org chart and, you know, span of control, and I asked it —
And already out of the box it was actually — I was shocked by this. It immediately told me like, hey, there is an org inside Databricks which is very deep. You know, this person reports to this person, reports to this person, reports to this person, but they have three people reporting to them, five people reporting to him, four people reporting to him, five people reporting to them. So that's not a flat organization, you know. So then you can look at, okay, what can we do about that? Again, it understands — since it understands all the people, it can immediately out of the box understand that engineering, you know, cost is, you know, something that we look at at — and, you know, so that's another thing we wanted to see if we could understand.
And what's great about this too is instead of you as the leader saying, hey, listen, if we're going to have an opinion, let's go with mine, you've now created a forum where people can be data-first, test theories, and you don't have to be dogmatic about who came up with the theory. You just have to be intellectually curious and open to possibilities. And eventually, if this is where we are today, can you imagine like in a year or two? It's going to just be giving you these — instead of through a culture report, it's going to be like a temperature gauge in your company. It's just like you're going to be looking at the nest in your company. It's like, oh, wow, looks a little hot today. What's going on? And it's like, oh yeah, we made people come in this weekend, and yeah, maybe we should buy some pizzas or give people a comp day during Thanksgiving. Yeah.