# Daytona's Pivot to AI Agent Infrastructure

**Podcast:** Latent Space: The AI Engineer Podcast
**Published:** 2026-05-21

## Transcript

Okay, we're in the studio with Ivan Bourazin, CEO of Daytona.
Welcome.
Thanks for having me, man.
Ivan, you and I go back.
Way back.
I don't even know how you found, like, did you reach out for shift?
I reached out to you.
The reason was you, we were just, we were thinking about, I was one of the co-founders of Code Anywhere, the first browser-based idea.
And so we were thinking a long time of like local hosts should die.
Oh, yeah.
And you had this article.
And the local hosts.
And then I reached out.
to you because of that.
And then we talked and I was actually at a different job and learning about, I was a head of like developer experience and you were quite well versed in that and actually reached out to you among other people.
Like, how do we, how do we go about that?
What are the key things and whatnot at this point in time?
And you were nice enough to take the call.
And I remember I was late on your call with you.
I don't remember.
I remember because I was with my then, I was thinking of a girlfriend or wife at that point in time.
I'm not sure.
It's the same person.
So that's great.
And I was late because we were in Italy on vacation and then I was late for something.
I felt so bad and you were so nice to be good about that.
The reason I'm nice is because I'm also late to other people.
So it's like, you know, who's without sin here?
Yeah, so I have to, you know, for those who don't know Infobip Shift, there's this whole thing that you did in the past.
And that was basically one of the inspirations for me starting an AI engineer.
which is like, you know, I have to thank you for giving me that push to be like, oh, you can build and sell conferences.
Yeah.
And I remember you asked me at the beginning to give me advisory shares.
I was so focused on what we're doing.
I said no, and I should have took the advisory shares.
But anyway.
We're not venture-backed, you know.
Anyway, so I think what's impressive about you is that Code Anywhere is the thing that you've been trying to build.
And, you know, you kind of put it on hold and came back after Infobip.
Just give us the story, the story and the origin story going into Daytona.
Sure, like really way back, me and my co-founder have been together.
I've said this multiple times.
It's like we were married and divorced and married.
Some people actually ask me, is my co-founder my partner?
Like they thought it literally.
It's not literally.
But we have done multiple companies together.
And to your point, we had this shift where we went from.
the code anywhere to the conference called Shift and then back to Daytona.
We originally started stacking servers, doing like virtualization in the early 2000s and, you know, routers and doing basically all these things at a foundational level.
And that was a services company, which we sold to focus on what my co-founder actually invented, which was the very first browser-based IDE, right?
I say the first before us was actually Heroku.
They did it for a very, very short time until they became Heroku.
But outside of them, we were the only one.
There was Cloud9.
There was Cloud9 that came out slightly after us.
There was Replit, which came out.
When we stopped doing it, Replit came out, and they have been successful since then, which is great.
There was Nitrous I.O.
There was quite a few that existed in time, but it was like too early.
But the interesting part is that we, at that point in time, because there was no VS Code.
for those that still remember me as code.
There was no Kubernetes and Docker had just started when we, or I'm not sure if it was even public at that point in time.
And so we had to build everything into the whole stack ourselves.
And that was the key learning that we brought into and that we've been using in Daytona today.
So it was super early.
There's about 3 million people used Code Anywhere.
It was slightly, it was angel backed, more than venture backed.
We ended up paying everyone back because it didn't have that sort of scale.
But, you know, three years ago, we started something similar with Daytona, which is not what we were, what we are today, but it was automating dev environments for human engineers.
Basically, the underlining stack of CodeAnywhere.
And then we did a hard pivot last January to sandboxes.
And so here we are.
Historic pivot.
And, you know, it's one of those things where, like, I had independently invested in CodeAnywhere, but also in E2B.
And then both of you pivoted into the same thing.
I'm like, fuck.
You invested in Daytona.
You invested in Daytona.
But you were the first.
If we had knocked out your check, we wouldn't have done it.
No way.
No, it was like, we have to get him on board first.
And you were the kicker that we did that got us.
No, because you were putting me on your pitch deck, man.
I was like, man, this is like a good trip if I don't invest.
Well, that's because it was your quote.
We did a bunch of research about end of local hosts and who was interested in that.
Yeah, no, that's like, I put, I wrote that blog post and every single company in that field reached out to me.
And then every VC.
who was receiving those pitches then also had to call me and talk through it with me.
It's finally happening.
It's finally happening.
It's finally happening.
It's finally happening.
With maybe sort of non-human users.
Yeah.
So what is Daytona today?
Let's get like a quick description.
I'm wearing this shirt.
You're wearing a shirt.
Yes.
It says, I think your branding is very good.
Like it's very consistent.
It runs AI code.
Like it cannot be simpler.
Exactly.
But we're going to probably have to change that because it's also a subset of what we do.
Unfortunately, we really love this.
A run-out code is super simple.
People interpret it different ways.
I think we've given out five, six thousand of these shirts.
People wear them with pride because it doesn't really market to.
about us in the back-end markets to the person, about the person itself.
So I think we did a really good job on that one.
But it's also a subset of what we do because people, when they think about running AI code, they just think about these small, let's call it isolates, code execution boxes that, you know, you send some code, you get an output.
Whereas what Daytona is today is essentially composable computers for AI agents.
It is, the market calls them sandboxes, which can be misleading.
All these things on the...
Yeah, exactly.
It can be misleading because people usually think about sandboxes as a demo or a test environment versus a production grade environment.
But what Daytona does, if you think of the laptop that you have in front of you or the computer that's over there, or, you know, my wife is an architect, so she has like a Windows with 3D graphics card inside to do 3D rendering, like computers or different compositions of computers.
And our belief is strongly that agents today and going forward will need all these different compositions of computers to do different types of tasks.
And so we offer that.
basically through an api yeah to give people i'm trying to sort of front load all the aha moments of the wow moments so that people can uh stay engaged and click like and subscribe uh the market is is exploding right like uh you have been reporting 74 month-to-month growth and it also it's just been going for a while like it's been going like this and every single It's not just you guys.
It's every single sort of compute provider.
I don't know if you agree with me saying compute provider or not.
But yeah, so it's like organically PLG driven growth, but also enterprise is doing super well.
I think I want to rewind to January last year when you did the pivot.
So you obviously called this market early and you were positioned for it and you are now one of the market leaders.
But what was the insight that made you do the pivot?
The insight that made us do this pivot is the the quarter before that, so end of 2024, when we had, basically we did a demo with, I think we discussed this as well.
Devin was not public.
You actually gave me access to Devin at that time.
So Devin.
I did.
I don't think I was supposed to.
Yeah, exactly.
So it doesn't matter.
I gave like three friends access.
Or it was a call and you showed it to me.
It doesn't matter.
But OpenDevin was available, which is now called Open Hands.
And so we're like, oh, this seems to be a thing.
This is not public.
Let's take our for human automation of dev environments and take OpenDevIn and launch that as a SaaS.
And we did that.
Not very many people signed up and used it, but a lot of people reached out that were building agents and they're like, hey, my agent needs a compute sandbox runtime, whatever you want to call it.
I forgot what it was called at that point.
And then we were like, oh, amazing.
This is a new market.
Here is our infrastructure.
Here's our product and go.
And what we found really, really fast soon was that people did not like what we had built.
It didn't work.
And I remember talking to people at the beginning when we're doing this, you know, the sandbox we're building for agents, people are like, oh, why is it different?
It's the same thing.
We have like EC2, we have VMs, we have all these things.
But we saw that everyone we gave it to was like 20, 30 people.
They all said, no, like this is not what we need.
This sort of breaks.
And basically me and my co-founder not knowing.
a lot about because we're infra people.
We're not AI people.
So I basically took upon myself to like watch every single podcast that exists, including all of these and all that and sort of get up to date, read all the blogs, like get, understand what's going on.
Do you want to shout out who else was useful?
Just in case people are also looking.
So generally we, I looked at, there's a few of podcasts, different segments in different types.
So there's You Guys, No Priors.
Bill Gurley's was great while it was around.
So there's a few 20VCs interesting from a different dynamic and some are different dynamics, but there was But we're not really about the compute market.
It was also ready.
Sorry?
I guess you're looking at the agent inframarket.
I was looking at the agent market, the AI market in general, and sort of understanding who are the players, what's the perception and how that goes.
And like, obviously, you complement this with like going to conferences, going to events, going to meetups, reading white papers, like doing all the things that you have to do to understand what's happening.
And so when we figured, when we sort of had an idea of what we had to build, literally over the New Year's Eve, literally on New Year's Eve, I...
half vibe coded the first MC first minimal viable product of what Daytona is today.
And I went to sleep at like 3am or something like that I was doing I just put my like baby daughter and wife to sleep and you know, Happy New Year's and go back to just doing this.
And I sent it to my co founder my CTO and he saw it in the morning.
He's like, This is absolute garbage.
I show this to anybody at all.
But the idea is good.
And so he took two weeks and he did it look like that.
It was my it was way worse, but it was like a very it was a simplistic view of what it should be like.
It worked, but it was not ideal.
And so he went we went down the hole, which is his job as CTO to go.
And he came back with this version.
We then called all the people that said, like, this is garbage, you know, a quarter ago.
And we set up these calls and we gave it to we just sent it to everyone.
And.
all the calls went long, every single one.
They were 15 minute calls and they all went like 25, 30 minutes or whatnot.
And everyone said, we need, we want access.
There was no login, just an API key because it was just a beta or an alpha.
And they said, oh, we want access.
And we're like, sure.
Yeah.
Okay.
Thank you very much.
But after like the next day, if we'd not send it, every single one, like every call that we did, everyone came back.
Where's my API key?
Like everyone wanted it.
We're like, shit.
Like this is it.
Like I've never felt.
So one, the understanding to your point was like, most people thought it was the same infrastructure for humans and agents.
We understood a quarter ago it's not.
We just didn't know what was the right primitive.
And then when we came and we can talk about what that is and we gave it to these people, I've never experienced, I've done multiple companies in my life, I've never experienced this that people literally call you if you do not give them access.
Like they want access right now.
And so it's like, okay, they don't want this.
The thing that they want doesn't seem to exist or they have not found it.
And they really, really want what we want.
And then when we understood that we're onto something, and then when you think about the size of the market, like the market for human engineers and enterprise is a very large market.
So think GitLab or whatnot.
But the market for every single agent that will exist ever in the future is just like, what is that market?
How big is that?
And we're like, we are all in on this.
And so that is where we made sort of the cut between the old products and the new ones.
Yeah, but it wasn't composable at the time.
So it was very, it was basically just a Linux box that you could change, that you could define number of CPUs, disk and RAM.
Like that, that is what you could do, but you couldn't have multiple operating systems.
You couldn't resize it on the fly.
You couldn't add a GPU.
You couldn't do like all the things.
It was just the first sort of variation of that.
Yeah.
And was it bare metal from the start?
It was bare metal from the start.
And so the interesting thing that we thought about.
right away.
Which, you know, gives people the background.
What is the normal path?
Yeah, so basically most providers run this on top of VMs.
Yeah, Firecracker.
Yeah, they run a Firecracker on VMs.
We have multiple isolation layers and we can do that.
But the common way to do it is that they, one, that the state of the machine or the hard disk is not part of the sandbox itself.
And the other thing is they're not meant to last forever.
So most of them are preemptible.
Like they can, there's a time that they can live.
And so our thought was when we're going into this is agents will be like humans in the sense of you don't want your laptop to be shut down until you're done with work.
Like, and you want to close the lid and open the lid.
It's the same state.
So agents would want that, like the pause and come back.
They want those two things.
But also agents really, really want speed, right?
Can they get it?
So when we thought about it, it's like we need something insanely fast, how to make it fast, how to make it long running.
and stateful.
And so those two things, it's like combining a Lambda and an EC2, right?
Those two things together.
And so we didn't have an idea how others did it because we didn't know too much that there was a market around this.
It was more like, okay, this is what we need, what they need.
And we looked at Kubernetes.
It wasn't good enough for that.
We look at Nomad.
It didn't enable that.
And so our history in rewriting our own scheduler at CodeAnywhere is basically what my CTO came up with.
Like, he's like, oh, the learnings from there, and he brought it.
And the funny thing is, our third co-founder, when he saw it, he's like, dude, what is this?
This is like 2008.
Like, we went back in time.
And he's like, exactly.
And so, the reason why Daytona is like super, super fast, and you see this on benchmarks, is we essentially, we run on bare metal, we have our own scheduler, we use the underlining disk, CPU, and RAM.
of the underlining machine, which means your IOPS are insanely fast because there's no, you know, there's no network between an EBS or something like that.
But also the snapshot, the point in time, the templates are also preloaded on the bare metal machines.
So when you fire off a sandbox from a template or a snapshot, you you're essentially directed to the bare metal machine where that snapshot is based on that NVMe drive.
And then it literally just turns on that machine and it's local.
There's no network latency, anything on there.
And so that is sort of the specificities that we, when we're thinking from first principles, what a computer would look like for an agent, that is what we came up with.
And that's what we created.
Yeah, I should maybe, I don't know if you endorse this, but there's someone that does compute SDK.
You guys do very well on there with like the TTI, right?
I guess.
Is this a relevant metaphor for you guys?
I don't know.
And it changes every day.
So today, Arquil.
I don't know what Arquil is.
Never heard of it.
Yeah.
So it is.
But you are, you know, at least a third of the next tier of performance.
And then, you know, there's a lot of other better known names that are very slow to start.
Yeah, we've been the number one by far for a long time.
And now there's different, there's different definitions also of sandboxes, different isolation patterns, different other things.
So Arquil runs it literally on the S3.
The data is very different and they spin up a container for that.
So it's a different type of thing.
The definition of a sandbox is something that we can all need to get along with.
But yeah, we're insanely fast on getting these things up and running.
And so you can see even there that it's 0.10 to 0.11.
Close enough.
Yeah.
I mean, what else do you need, right?
So the benchmarks itself, I don't think the benchmarks equate to...
market ownership or revenue or anything like that.
And I've seen this with multiple benchmarks, not just in sandboxes, but in general benchmarks around.
It's table stakes.
It's just like that.
But you definitely have to be...
up there and you have to be competing so that people know that, oh, this is definitely one of the top, because this is only one dimension of what customers look for.
There's other things like how many can you spin up consecutively.
There's a feature set, there's support, there's like all different things that people look at, but you definitely have to be there on the benchmark.
How many people do people spin up consecutively?
So we have currently, I guess, is the concurrency.
So there's three metrics that we look at.
And so one is like time to spin up one.
And so our time to spin up one is 60 milliseconds with network latency.
So requests, spin up, reply, the whole thing, 60 milliseconds.
That is one.
But if you want to spin up 50,000 at once, we are now at about 75 seconds.
So it takes about 75 seconds to spin up concurrently 50,000.
Some others, there's public data around this, like take 2,000 seconds, which is 30 minutes.
Like there's different variations of that.
And then there is, so it is speed of one, speed of like.
multiple and then how many can you consistently have up and running.
And so we basically have right now no limit to how much we can add because we basically own our own metal.
But the biggest customer of ours does like about 850,000 every single day is sort of where they're just shy of a million every single day that they're running.
We do have a request for half a million concurrent, which is literally half a million.
CPUs somewhere running.
So that's interesting.
And they pay by vCPU seconds.
The other thing is, I guess, the sleeping and the resuming, because it's all the stateful resumption of all these things.
What kind of workload are people putting?
through this, right?
Like, do we measure by gigabytes in memory, gigabytes in storage?
I don't, like, you know, network attacks, storage.
You know, what are the costly ones out of all these features?
The most expensive thing are CPU.
Then it's RAM, then it's disk.
We actually don't charge.
Which is snapshotting, right?
So, you know, it's actually, snapshotting is part of it, but basically the size of your hard disk of your machine.
So do you have 10 gigabytes, do you have 20, do you have 50, do you have whatever?
And then the transference of that.
Right now, currently, we don't charge for network at all.
Oh, yeah, you got to fix that.
Yeah, it is very much, it's a larger and larger part of our bill.
So we're working around that part there.
Obviously, that is the least expensive.
So the hardest is the least expensive.
So it's basically CPU, RAM for us network because we don't charge the customer.
And then hard disk is how it's spun up.
But there's also different types of workloads.
So we basically split it up into two types of workloads in Daytona.
One is what we call background agents or long running agents.
And the other is basically RLs and evals, which I put sort of together.
And so they have very different patterns of usage.
And if you look at the usage of a background, and I'll just...
Name names of companies, not specifically.
Yeah, open, all hands.
Yeah, so like a background agent, a cognition, a lovable, like all these things are Harvey.
These are all long running background agents.
And so if you look at their usage patterns, their usage patterns are similar to human, which is like follow the sun.
Basically, the usage patterns of that is like noon is probably the highest and midnight is the lowest.
And then weekends are lower.
You know, weekdays are higher.
That's a fun question.
How global is it?
You know, is it very US centric or?
So the US is a large part, but we have.
Currently, we have Asia, Europe, and the U.S.
It's quite global.
Yeah, it's quite global.
We have it all.
It's interesting that our number, I talked to you about this, our number one city by user is Singapore.
Oh, wow.
Which is an interesting one, right?
Not by revenue, just by individual headcount.
Just like an interesting, interesting.
Singapore is weirdly high in the adoption charts of AI for the...
population.
It's like a 7-8 million population.
And it keeps showing up.
No, it's quite interesting.
We were quite shocked.
I was like, oh, this is interesting.
And also one that's out there.
There's a reason I'm doing AI using it for it.
Exactly.
So we're there.
We're going to be there.
And it's interesting that Japan is in the top or Tokyo is in the top, which is in all the tech cycles, it has never been.
Yeah.
It has never been.
So it's quite interesting that.
I think the Japanese just love AI.
Yeah.
It's that and then it's Brazil.
Yeah, but Brazil has always been in the, even when I look, if you look at like GitHub's data and us historically with CodeAnywhere, it was always like US, Western Europe, and then you'd have like India, Brazil, China, like that would be there.
But like Singapore was not in specifically, Japan was never in the sort of top.
Yeah, weird pockets.
Yeah, so it's very global.
So actually, but that helps you to distribute your load through.
all time, you know?
Yeah, so the interesting thing is we have those kinds of loads, but if you look at the researcher loads, they're quite different.
So what they are is like, if you give them concurrency of 10,000 or 50,000 or 100,000 CPUs, whatever it may be, when they fire off a run, it's just 100%.
And then it just runs, runs, runs, and then it stops.
So it's very, the usage pattern is squares, basically, right?
And it's also not follow the sun because people will fire it off at midnight before they go to sleep, but then they wake up.
So it's very...
unpredictable.
So you don't know where that is.
So the shapes of the usage are quite different than we have had before.
And also what's interesting is when it's sort of a fall of the sun, even if you have a high growth company, you can sort of predict your usage patterns and have enough capacity for that because it's sort of, it grows in a way you can project.
When you have companies doing sort of like evals and RL, they're super spiky.
So they're going to come in.
It's like, we're going to use nothing.
Then can we have a hundred thousand, right?
And then go back down and then have thousands and get back down.
So it's very, very different.
Right.
And so, so do you want to lock them into commits?
So yeah, we do.
So we have to lock them into some sort of commits to have that capacity because we have to have, basically we have to have the capacity for peak.
Yeah.
Right.
And so right now, Daytona's mean utilization is 15%, 1.5%.
Oh my God.
So it's very low.
Because it's very spiky.
But it's very spiky, but we get up to 90%.
Yeah, yeah.
So we have these things.
And so what we're looking at right now as a company is similar to Cloudflare where you can like geo move things around, but that works really well for basically the background agent towards the sun.
But this, it's not, like it's a very different shape.
Obviously with scale, you figure these things out, but that's an interesting new problem that we have as a compute provider in the...
agent space.
And when we were doing the conference recently, and so we talked to like Nikita from Neon and the...
I should bring it up.
Parag from Parallel and whatnot.
Everyone has the same problem, whereas the usage is super spiky.
And this is something that has not happened before, that you have these types of...
Like it was always...
The amplitudes were not this high, right?
So it's quite interesting use case and problem solve.
Yeah.
I don't know if we're going to bring this up again, but let's just talk about the conference.
You had like a thousand something people at the Warriors game at the...
Sorry, where is it?
What's the?
Chase Center.
Chase Center.
Chase Center.
I went, it was very impressive.
Obviously, you know how to throw a conference.
What did you learn?
You know, you pulled together all these impressive names.
Yeah.
And what were you looking for?
My thesis behind the Compute Conference was, let's bring together people that are building infrastructure for AI agents.
Because when I think of what we're building, it is the agent is the primary user.
What are the ergonomics and usage patterns of agents?
And so we can do that.
What I found, this was a theory, it wasn't proven, is that we all have these problems, as I touched on too.
And as I was talking on stage, it was like, we all have the same underlining infra problems, which is this spiky workloads, unpredictable workloads that we've never had before in human computer or human infrastructure.
And it's, again, it's the same when I was talking to Parag or when I was talking to...
Lynn, Nikita, Lynn, especially I was talking to her the other day as well.
Like the, it is a very interesting type of problem solve because I can touch on Cloudflare because there's a lot of like talk about that recently and how they solve that, which is they have a bunch of geos and basically as users work in different places and depending on your tier, they can move you around the geos.
And so that's how they get to the higher utilization.
But you can sort of predict these.
And if it's something, you'll rarely get, a spike that is 10 orders of magnitude.
Like you'll get a spike, like you say, one of your customers has like an exponential curve.
What is that to, I'm using cloud for example, 10%, 20%, whatever it means.
I don't, I don't have this data.
I'm just assessing.
It's surely not 10x, right?
It's really not something there.
And so how do you go out and solve this problem?
And we're all solving this in different ways.
So she also has the same thing.
So yeah, I know specifically that like Neon had that issue as well.
Like how are we solving these spiky loads and things like that?
Because we talked about it.
And so the interesting thing for me to actually internalize was, yes, everyone that's building for agents first is going through this and we're all solving similar problems.
Let me double click on this.
Okay, so for example, Neon, I happen to know that they're very sort of S3 oriented, right?
So they're just like fully bet on S3.
And you get to benefit from S3's distribution and infrastructure.
So I would imagine that Neon doesn't have to care.
Whereas Lin maybe has to care a bit more because obviously she's doing GPU inference.
And for listeners, we did an episode with her one and a half years ago.
And you have to care.
Yeah.
Right.
So Parag cares for sure.
And Parag is CEO of Parallel, former CTO of Twitter.
They are the search.
Yeah, they're search.
You and I know.
The listeners don't know.
We can put it down in the screen.
And so, because we were talking.
I mean, I put it all on the screen so people can look it up if they need to.
And yes, but they still have CPU and RAM.
allocation that you have to have in running.
And so CPU RAM, you have to allocate that and have that ready.
And so there's basically two ways to do it.
One is you either over-provision and you can handle the bursts.
Or two, you basically have, I don't know if it's a term, just-in-time compute, which is like, as your usage comes in, you can fire off requests for VMs or bare metals at other cloud providers.
And then...
get them up and running.
So this is if you go above 100%, right?
Yeah, this is your overflow.
If your overflow, like spillage or whatever, you probably lose money on it, but it doesn't matter.
Well, you might not.
That is a more cost-effective way to do it, but it's a slower way to do it.
Because basically what you have to do is you have to queue your requests, spin up these just-in-time compute, get it all ready, provision it, and then get your workload there.
And so if the time isn't important that much, that's fine.
And you can do that.
But if your customer, and especially for, let's say, the RL training runs, the reason why a lot of people come to us is because GPUs are more expensive than CPUs, right?
So you want your GPU running at, what, 100% the entire time.
And so when you're running runs on CPUs, when the CPU cycle is down and spinning up the next one, you want that to be instantaneous so that your GPU doesn't go down, right?
And if you then have to go out and provision...
machines, you're essentially telling the GPU that it has to wait and that's incurring our cost.
So there's things that you have to try to solve further.
Yeah.
Let's talk about the different workload, right?
You said that, was it a few months ago you had zero RL workload and now it's 50%?
It will be this one, 50%.
Yeah.
Let's talk about how different it is, right?
Like I imagine, for example, a lot less dynamic code generation of like arbitrary code.
Like here is probably all the same code.
You're just doing parallel runs or something.
Yeah.
So you'll have multiple depends on the like for each run, you'll have a snapshot.
And for the most part, they actually do use our declarative image builder, which is like, oh, the agent wants these dependencies, these end bars.
Yeah.
Yeah.
The declarative image builder.
Which is a very modal like thing.
Yeah.
And so we build it on the fly and then we propagate that snapshot and then you can spin up as many sandboxes as you want to gain that snapshot.
And then if you have to do changes, the model can.
Or like it could be automated.
It's like, oh, now for the next run, we need to install these things or remove these things or whatever to get a task done.
And then it goes off and runs that.
So yes, that is something that it seems that they prefer.
The number one reason I found, or should I say, let's take a step back.
What we are competing against in that environment is essentially managed Kubernetes.
So EKS, GKS, whatever.
That is what the vast majority run on.
Anyone that has tried Daytona versus GKS, EKS is like, I'm never going back.
That has always been.
There's a few reasons.
One is the ergonomics.
So if you have, if you're using Kubernetes to spin that up, you have to essentially manage the interface interactions with that.
Daytona, although as a compute provider, it's more akin to a Twilio and Stripe from a consumption perspective than it is an AWS.
Like you have an API and SDK, it's quite like easy and seamless to get these things up and running.
That's one.
The other is the speed to which we spin up, which we mentioned earlier, which is much, much faster, and the scale to which we can go to.
We haven't got into features, but an interesting feature is that it's very hard to OOM or out of memory our sandboxes because we can dynamically on the flyer resize, which is like impossible on almost any other thing.
There are some technologies that enable you to use that, but it's like a very hard thing.
And so we actually saw this when the terminal bench team is...
brought us actually, so thank you, Alex and the team, they brought us into this whole space.
It's just very, very, very rare that, you know, a framework would just say, guys, just use Daytona.
Yeah, I think it says it somewhere.
Yeah.
Yeah.
I was like, what is this?
There's all, there's multiple there, but they also mentioned a few other places.
Yeah.
And so Daytona specifically.
We have, just jumping on themes here, we, I don't know where it says Daytona.
I don't know.
There's a very, very strong recommendation, which is like very unusual.
We do not pay them for this.
I know.
They just like you.
Yeah, they like us.
Yeah.
And also a thing, so Daytona has multiple isolation sets underneath.
The customer doesn't have to know what they are.
But basically we have Docker, which is a container that's hardened with SysBox.
So it's Docker's.
isolation that is a security equivalent to a VM, but it's still a container.
And that is the default.
And they, especially in these training workloads, really like that as an interface to be able to use just a basic Docker container.
And we enable Docker and Docker, which for these RL runs, if you need to do a Docker compose or Kubernetes, you can spin up a K3S inside of these things, which unlocks a huge amount.
of workloads that you can do that you cannot do on other providers.
So just on that part is much more interesting.
And so we went through that, we showed them that we could do that and they enjoyed that quite a bit.
They being the people and the Harvard people.
Do you know, are they a company yet?
I do not know.
It's super obvious that there's a lot of excitement and success around these things.
Tell us more, right?
This is an exploding workload.
Harbor adopted you, which helped speed things along.
But what are you learning as this new workload comes online?
Sure, there's a couple of things that we learned, which we should chat about in the beginning.
And this has led our story, as we mentioned, we talked to a lot of customers along the way and we add more features and more tool sets as we talk to customers.
And I think it's that the ecosystem is so small and or the models get smarter where when we see one user come with a request, we know.
it goes on a roadmap if like three to five customers come with the same request in that week.
It's like very bizarre.
And it happens so many times, which is like- Because they're all friends.
Sorry?
They're all friends.
They're all in the same group chat.
Yeah, probably.
Yeah.
And they're like, oh, can you do this?
I'm like, okay, this is interesting.
We'll put it on a feature request.
And then the next one's like, oh, can you do this?
Okay.
It's all the same.
So it's the same.
And so what we try to do, and I personally try to do, I try to be on as many quote unquote sales calls I can.
I'm in every Slack channel.
We literally have about a thousand Slack Connect channels, something like that.
It's an interesting, there's so many interesting things you find out when you have all the Slack channels.
You can also see where people transfer between companies.
You see leave Slack channel and Slack channel.
It's an interesting thing.
Also, just I digress, I feel that Slack Connect is literally LinkedIn what it should be.
Yeah.
You have a list.
LinkedIn charges you to, you know, use your own connections, but Slack doesn't, right?
Slack is like, do it for free.
It's more lock-in.
It's great.
Yeah, it's easy.
You're going to pay Slack for life.
Exactly.
You're there for life.
So that's interesting.
And so one of the things, the newer things we were talking about earlier is we made a big bet and put a lot of investment on computer use.
That is not seen publicly in the light of day.
We haven't GA'd that yet.
But we have...
Is there a thing I can pull up?
There is computer use there.
It's right up a bit.
Oh, yeah.
Okay.
Yeah.
Cool.
And what we have, what we talked about and what we've seen publicly is there's this theme now about like the human emulator where, and Elon from XAI has talked about this publicly.
And if you think about the models today, they're actually quite sophisticated and they can do a lot of work, but they still don't have access to all the tools.
Like I'm a strong believer that the most efficient way for an agent to work is essentially headless or through, you know, terminal or whatnot.
But.
If we look at knowledge work in general, there's about 100 million knowledge workers in the U.S., about a billion in the world, and knowledge workers.
And the salaries of them aggregate to 10 trillion in the U.S., 50 trillion worldwide, something like that.
And if we look at the five most important sectors of that, so like healthcare and government and financial services and whatnot, that's about 56% of that.
So let's say it's about half.
of that so in the us it's about 25 trillion and most of them most of that work is actually still locked into legacy apps inside of windows which is not going anywhere for a very very long time like people just won't invest in that how much of it our assumption is the following if like in the rpa market which is similar market but not the same 25 of like these white collar workers um work is automated If an agent is more sophisticated, can go through more runs, figure stuff out, let's say it's like 40%, right?
And so if you take 40% of that, you get to essentially like $10 trillion a year.
That's a 10.
That is a 10.
So that's the 10 of the models, right?
That's not essentially ours, but you get to that size.
And to be able to do that, you essentially have to give agents.
these computers with the legacy.
So a computer use, either Mac or Windows or Linux.
Linux, we also obviously have and others have, but Windows specifically is something very, very new.
And the only option right now is an EC2 with Windows or on Azure.
Both of them take anywhere from three to five minutes to spin up.
We've created an actual sandbox.
So it's a second instead of milliseconds, but you have like point in time snapshots, you have like forking, you have all the things that you have from.
a sandbox, but essentially enables you to hopefully unlock all this value.
And so that's been our big push.
And what we've sort of like kept our ear to the ground, what is sort of the next things in the market?
Yeah, knowledge work and building and sort of RPA, the next wave of RPA.
I got very excited about RPA kind of during COVID times.
The UI path was IPO-ing and it was like a very hard, isn't it Eastern European?
It is Romanian.
Romanian?
Yeah, it might be the only Romanian.
big unicorn.
Okay, yeah.
I don't have like a, I think there's a stage being set for the resurgence of RPA because everyone understands that, yeah, no one wants to deal with these shitty apps and no one's going to rewrite them.
You just have to do like a remote operation and programmatic operation of them.
But if you want to unlock it, like my own setup was basically the following.
So I was doing a board deck.
Yeah.
Recently, last month, whatever.
And I'm like, okay, let's just, let's just do automated.
So like all our data is in like ClickHouse and PostHog and QuickBooks, like where everyone else's is.
And I'm basically like connected that all to like my cloud code, like go off and go cloud code, whatever.
Go off and like, here's integrations, go do that.
It pulled out the first report, which was great.
It connects to Brex and all these things, which was great.
And I say, okay, now pull out this, this, this, this.
And I kept getting like.
really well McKinsey style design reports, but the data said partial data, missing data, partial data, like it can't access all the things.
And I got so frustrated.
And so I got, I got, you know, my Mac mini virtual sandbox with OpenClaw.
I gave it its own account in our company.
And then I went to all these services and created a read only account.
So literally like an intern in your company.
And so I would say now go and do this report and it'll get the same or like I can't via the MCB or the API or whatever.
I can't get all the information.
I'm like, go log in.
And it will log in to the website, then go in, export the data, it'll export the data and do the thing end to end.
So even for things that have today APIs, not all of it is exposed.
And to get value, like I get immense value right now, but it has to be a computer usage, unfortunately.
And so I spend a bunch of tokens just on that, but I get the job done.
And so if even a startup like ours and using all the hottest tools still needs a computer agent, what hope does, you know, Goldman have to have a headless, right?
Yeah, yeah.
Why isn't Microsoft doing this?
Well, I'm pretty sure like Satya had a post yesterday.
Oh, it's like every agent needs a computer.
I see, I see.
So they have launched something.
Yeah, they have Microsoft Power Automate.
I'm sure, I'm sure like, you know, they're going to have their version.
Version of that, yeah.
And you're going to try to do yours.
And I always know there's always demand for Mac, but I know it's like tricky to host Mac OS sandboxes.
So we will have Mac OS sandboxes.
fairly soon.
The problem with macOS sandboxes is, I'm deep in this, I don't know how much interesting is this.
macOS has this problem.
It's a licensing thing.
Licensing thing.
So one, you're allowed to run only two parallel VMs per machine.
So that's one.
Two, you can only license to a different user every 24 hours.
So if you come in, and theoretically, if I want to charge you per second, I charge you one second, I have to have it idle for the rest of the day.
I can't have anyone else doing that.
So the pricing will be different in the sense that...
we would have to charge for 24 hours.
And that's not even the most difficult thing.
But the thing above that is, from a security perspective, they enable you to do memory snapshots, pause, resume, but only on the same physical machine.
And so what you can do in like Windows world or Linux world is that I can move in the background your snapshot from one to the other and manage load, right?
Here, if you want to do that, you essentially have to have your.
Yeah, step shots.
Your physical machine.
You can't break it up.
You can't move things around that.
And all of that is, that part is like from a security standpoint, if it is, like I understand the security aspect of that, but it disables you from doing these agentic, like really scalable agentic workloads.
You need to do a vibe-coded cleanroom implementation of macOS that you can then, it's like cleanOS or something, I don't know.
I guess so.
You know, because Linux was originally a cleanroom rewrite of Unix.
Something like that, right?
Same thing to Mac OS.
Someone needs to do it.
Someone will do that.
We'll have some long-running agents for a few days to figure this stuff out.
But yeah, so definitely we're really close to offering something because people do want it, but the pricing will be different and the feature set will be kind of stringent.
Yeah, nobody's going to use this.
I mean, the labs will because they want to automate Mac OS.
They have to do URL again.
The point is with the RL part, if you do RL on macOS, then the next iteration of the model comes out, it will be able to use these tools significantly.
Then you actually need to run that somewhere.
So you're going to have to have that later on.
And from if anyone at Apple is listening, I very much feel that they are shooting itself in the foot of the scale of the revenue of compute or licensing they could get if it would just enable.
a concurrency model similar to what you can get on a Windows and Linux.
Yeah, and I'm sure they've heard this before.
They just don't care.
Yeah.
And maybe they will change their mind with the new CEO.
Yeah, we'll see.
High hopes.
High hopes.
Okay, but I mean, it's very clear the market opportunity is huge in Windows and you can go for a long time on just Windows, but your customers are going to want both.
It is interesting to me that...
This is the sort of god application of agents, right?
How big was OpenClaw for you guys?
Was there like a significant bump?
Not for us.
So we're kind of positioned differently.
Whereas, although it's completely PLG and we have individual developers that use it, most of the users that use Daytona are sort of a B2B2C.
It's either B2B or B2B2C.
In the researcher world, it's B2B, so you're selling to labs and neolabs and things like that.
But on the long-running agents, it's mostly, from a scale revenue perspective, it's mostly B2B2C where you have a app layer agent.
that uses you at the scale.
Like a Manus.
Yeah.
Like a Manus lovable type.
Yeah.
Yeah.
B2B2C is basically to me what I've been calling an agent lab, which is kind of like you're not in a model lab, but you're making a very, very good wrapper that is a platform that other people can sign up so they don't have to code those things.
Yeah.
It sounds like a much better market than the direct open claw market.
So I've like, we, I've done multiple things.
So the code anywhere.
part of our career path, R on the calendar, was very much an end user developer product.
And so that is great.
You can get a lot of developer love.
And I feel that we do as a company have a bunch of developer love, but it's a different type where it's people building these things.
Again, it's more akin to a Twilio because you don't really run, as a person, you wouldn't run Twilio.
I don't know how many people remember it was like, ask your developer, billboard and whatnot.
And people really love Twilio, but they only use it inside of like.
oh, I'm building this app or service for thing.
And so we're very much directionally to that.
And you also know that I used to work for a competitor for Twilio, so it's kind of ingrained, I guess, in my DNA.
People don't know Infobip is that big.
Yeah, it's like...
Because they're all American.
They're like, whatever's in Europe doesn't matter to me.
But like, it's the same size or bigger?
No, no, it's about half the size.
Half the size?
It's about half the size.
But it's still huge.
Multiple billions a year.
Yeah, it's crazy.
Exactly.
These are like really...
interesting and large revenue generating, very sticky businesses.
Whereas when you're selling to the, when your focus is the end developer, it is a very hard sell because they're very price sensitive, very price conscience, very, you know, around that.
And there's very hard, it's very hard to scale.
Your cap is the number of people that are willing to spin up.
First, I want to spin that up and then spin up multiple of these.
Whereas if you're in the enterprise one, like we know everyone's talking about like how many tokens they're spending, I'm spending like, like a lot of companies today are like, this is our company, spend as much as you can.
Like basically that is where we're going.
And so if you think about that paradigm where you're selling to companies that say, spend as much as you can to generate, you know, productivity versus, oh, I'm a single person.
I have this much budget and I'm doing this thing because it's fun or it's helping me out or whatever.
Like it is a different, it's a different go to market, I think strategy.
Yeah.
There's a lot of discussion.
I'm just kind of going through like the mental list of things that are in your favor, which is, for example, MCP versus CLI.
Like, obviously you want CLI.
It's been very good for you.
I feel like it's maybe a drop in the bucket or maybe it's huge.
I'm just checking.
whether it's like these are big trends.
I mean, those things work well in our favor, to your point, just because...
But they're kind of dropping the bucket, right?
I guess, I think it's like sort of all the things come together.
So there's so many things that impact that.
To your point, like OpenClaw wasn't huge for us, but like having the agent SDK from Anthropic, so or CloudCode was very interesting.
The reason why it was interesting is that a lot of, let's call them, I don't know what to call them, app layer agent companies, essentially, they are like, oh, I can create this new app, this new agent.
All I need, I just use Cloud Code and I throw it into a sandbox and then I have my interface to the human to that.
And so that enabled so many more companies to actually offer this and then they would pull on sandbox.
That was interesting.
And to your point, like MCP versus the CLI, I mean, the MCP is an interface against an API, whereas the CLI is like, you can actually go do things.
Like, this is the difference between integrations and actually, running script or data or analysis against the thing.
So being able to use CLI very, very well enables the agent to do more things.
And it's because people will invoke a sandbox, they'll run in the CLI, but it'll do analysis on that data and then give you an actual result versus just, you know, pulling data from an APS.
Yeah, it's a layer of indirection, basically.
It's the same thing as agentic search versus RAG, which...
Exactly, exactly, yeah.
Just like...
You just win whenever people put more agents into the workflow.
Exactly.
So like, it doesn't really matter, but I'm just kind of teasing out like, what else have people heard about that?
Like it's sort of, oh yeah, this is another sandbox use case.
Oh yeah, that's another one.
Yeah.
Am I missing any big ones?
So the thing that people, which is the computer use stuff, which I think is probably the most interesting one is, and to your point, we've talked to so many people over the last year, it's like, oh.
Like, why do you need a sandbox?
Why do you need this?
Why this?
And to your point, it's like, oh, I need sandbox for this.
I need sandbox for that.
And so, oh, I need it for every single thing.
And so basically what I, and it sounds like a broken record, is like you use a laptop every single day, right?
And you are, end of one.
It's just you.
But now imagine how many, and by the way, the laptop, the computer PC market, the PC market is about equal to the cloud market.
So it's about 150, 180.
billion a year, something like that.
It's about roughly, the three cloud hyperscalers is about equal to like Apple, HP, Lenovo, whatever.
It's a little bit less, but it's sort of like that.
And now imagine, and that's just like, so how big is the international market?
How many people are there in the world now?
What's the last day?
And it's called 8 billion.
8 billion.
And so let's say you can have two computers.
Like you have one personal and one business, whatever.
It's double that.
And so that's 16 billion.
How many agents are going to be running in two years, in 10 years, in 100 years?
And for every single task, they will need one of these.
And so how big sound that market is essentially quote unquote infinite.
You will get to the point, and Dylan Patel was at the conference talking about from Semi Analysis that talks usually about GPUs, was also talking about how CPUs will now be a bottleneck because it will be the constraint.
You won't be able to grow or we won't be able to have enough of these because there won't be enough CPUs to basically do that.
Yeah, well, I actually had a really good podcast with Doug Oloffin, which was his president at Semi Analysis, where they've basically been like, yeah, It's been a GPU shortage first, but then it's cascaded down to memory and now to CPUs.
And I mean, what's next?
Networking.
Networking actually has been a shortage for a while if you're looking at like just GPU networking.
But yeah, I mean, it's really crazy the amount of computer use that's going on.
Yeah, cool.
I guess other questions are just the one very big part is the open sourceness, which you didn't have to do.
Your competitors don't do.
I guess a lot of people are worried about keeping their projects open source because some competitor can just slot fork it.
Yeah.
I don't know if there's any reflections on just being an open source company.
Yeah, there's a bunch.
So the original product that we did was open source.
Yeah.
Doing that was actually very good for us.
There's basically a saying of, what's the saying?
companies that are doing really well measure themselves against, you know, free cash flow that are kind of okay, it's EBITDA.
The worst is like GitHub Stars.
GitHub Stars, yeah.
So you go all the way down to GitHub Stars.
And so our original one was GitHub Stars.
That's what we talked about.
We're at the point where we talk about revenue.
So we've gone off the stack on that.
And so we started- Profit, profit.
Yeah, we haven't, we'll get there.
But basically, at that point, we did stars and GitHub and WANA, and it was useful.
And the original variation that we did, we split the core into its own repo, and it was Apache 2.0, so very permissive.
And then we basically would bundle that on the enterprise side with a proprietary repo.
So it was like open core, but it didn't fill out the repository.
The repository was very clean.
When we did the pivot, we didn't have time to rethink this, and we wanted to, we had this open source community.
It felt a shame.
not to do that.
And so, but we still did want to add some restrictions.
So in the new Sandbox product, we did add an AGPL 3, which is, you know, it's a kind of a shortcut way to do that where you are open source.
And it is true open source in the sense of that enterprise can use it if it wants, but you essentially can't make a competitor without open sourcing your stuff.
It's one of like three approaches.
Like there's a BSL and some of the other sort of elastic license.
Yeah, there's some others there.
So pure open source believers.
agree that this is not full open source.
And I totally respect that.
That is absolutely true.
But we did leave that.
And Daytona, in its essence, everything outside of what's under a feature flag today, which is like the Windows stuff, GPU stuff, whatever, it is in this open source.
It is there.
So everything is there.
Like our own scheduler, everything is there.
So we are, I've had some competitors say like, you guys are actually open source, open source.
Like you, you're really, like you can actually see that.
And I mean, people do like that.
And it has.
helped a bit, but it's actually more helped in the consumption of our cloud product than actually transferring people over.
The reason is you can actually, you send the repository to your agent when you're integrating Daytona and it just has more context.
It's like, oh, okay, this is why this is happening.
This is why this is not there.
You could equivalently just have docs that you can, yeah.
I agree, but to be fair, and so it actually doesn't really help the growth significantly today?
We've had this kind of conversation with like investors and other people.
It's like, how do you convert people from open source?
The open source business conversation is so all over the place, right?
Okay.
I was just like, for listeners who maybe they haven't thought this through, a lot of people say, oh, it's a free tier, right?
Like, oh, if you run it yourself, but when you get serious, call us, right?
And then other, and then me personally, because of my temporal experience, it actually is the way that, it's GTM into some of the largest companies where we wouldn't pass their review process, maybe because we're too young of a company or like there's like parts of the stack that we haven't, like that just doesn't work with them.
But because it's open source, then they adopt it and then later on we figure it out.
That's the low end and the high end.
I don't know if it.
No, no, absolutely.
And that has been historically.
The thing that we have found in this AI transition is, and so we haven't talked about this, Daytona's customers are everything from you know, the single developer, the YC startup to people say Fortune 500, I'll say Fortune 5, like the biggest companies in the world.
And big Neolabs.
You told me about, yeah, we're going to keep them anonymous.
Enormous companies, right?
And because the market pull is so strong, we're able to circumvent these.
process.
I'm not saying we go, we pass security audits, we pass all these things.
But as you know, it's your mention, like Temporal way back in the day in our old version of Daytona, like it took us months.
And usually at the end, they would churn off because just like, oh, you're too small of a company.
Like we don't trust you enough.
Whereas today we've had these large companies push us, like they would push us through.
Like usually when you would go through procurement to become a vendor of large companies, it would take you like two, three months.
We could have done five days now.
And this is not saying that maybe we're great.
but it's more, I think, a sign of the market where it is today.
And so when you think about that, the open source is something that we, from a go-to-market perspective, don't think about that much because everything that we've created right now has been PLG through the cloud product, people signing up and just pulling us inwards.
This is a personal interest, and I don't know if you have an answer, but do you have problems with GitHub?
I do, a little bit, a little bit.
Yeah, tell me, tell me.
Because, you know, I'm thinking about like, okay, what would it take to replace GitHub?
So there's a lot of things.
I've thought about this and I've tweeted about this and I looked at some.
I've actually invested personally in some.
Is it entire?
No.
No?
Okay.
Yeah, so I've met Thomas virtually and we've talked.
So I really think, and this was my reason for that, because we have a bunch of background long-run agents and for our time, most of them are coding agents.
Like everyone was building up a competitor to Lovable or...
or Devon or whatnot, what we saw from our customers was that they were all trying to figure out how to do versioning.
Everyone is doing it in different ways.
There were some really weird ways where people were doing that.
And the reason was that GitHub as is was an overhead.
Like it wasn't fast enough what they needed.
It didn't solve the problem that they needed.
And to be fair, like GitHub is for post your, the inner loop.
right?
It is post your laptop.
Yeah, GitHub is the point at which the auto loop starts.
Exactly.
People started using that for sandboxes, which is inner loop, which is usually, you know, it's on your laptop, right?
And so that is not what it's made for.
And then we had everything from people, actually, the most interesting one is we had one customer that will literally take the entire code base inside the sandbox and every, I forgot what the time sequence was, they would just dump it all into a JSON and then push that to S3.
Yeah.
And that's it.
Make your own Git.
There's not even diffs.
It's just a whole thing every single time.
It's just every, because it was super fast.
And then they would go back and search and find, you know, sort of what the file was and whatnot.
Because there's text file, there's JSON, they're very small.
So then the network cost is very low and they didn't care and they just did it that way.
And I'm like, if people are doing this, that means there needs to be a new solution to this problem, right?
And so for me, it's quite interesting to look at.
who is building these types of new things.
Agent first.
I think Git as is still exists in the future.
Maybe even GitHub exists, but there will be a whole new.
Yeah, exactly.
Git is like the deploy artifact to kick off CI, CD.
Yeah.
But then there's a layer before that that is like the agent collaboration layer.
And so I think something's to be said there.
But on the other side, like there's issues with another interesting thing is just like CI right now.
So the amount of PRs being created is insane right now, right?
In general.
Even for you guys, right?
Everyone's creating a bunch of PR, like everyone.
And then all that has to go through CI.
And then that's the bottleneck.
Like everyone's bottleneck.
Like not just actions, but like go to any CI provider.
You will not be able to, if you have a high throughput of PRs, there's one company we're talking to, they do a thousand PRs a day, which means like, and they're just waiting.
They have just a queue on that, right?
What do they use?
Like build kite or circle?
I don't know.
You know, technically your tech can be used for CI.
That was the conversation.
Oh, okay.
Is that a serious conversation?
So we'll see how that goes.
We've had quite a few conversations around that.
We are not a CI provider by any means.
But what is, I mean, what's missing?
Essentially, you could use a Daytona sandbox instead of whatever you use for, you know, your GitHub runners.
Yeah.
The only thing I would say is like, maybe CI machines are supposed to be very cheap.
Maybe it's like the low end because it's supposed to be like, you know, non-blocking or...
something like a background job.
Like it's the urgency is not that important for CI.
Performances though.
Yeah.
Performances.
Yeah.
Yeah.
Okay.
That's interesting.
Before we leave Daytona and go into like sort of broader like founder takes and what have you, when startups evaluate you, like, so you have, you have all these like names and you have more that you can't, you can't even name.
They see all your wall of competitors.
Yeah.
And yeah, you have differentiation versus many of these, but like what sells them?
The thing that we found that sells people the most, this is more maybe a day two thing instead of a day one thing.
And we've seen this again and again.
So we have a bunch of case studies and a bunch of them still coming out.
They're all done by third parties.
We don't do the case studies.
And it's actually interesting to watch those cases.
I watched their recorded.
And because it's a third party, people are actually more open and they will tell you, oh, we use this competitor or we like this competitor more or this thing or whatever.
And the number one thing that people come back to us for is that we have an insane responsiveness.
In terms of your team?
In terms of the team.
Okay.
Insane responsiveness has been by far than...
Now, we can talk about like features and breadth of product and concurrency and CPUs and all those things.
But I feel that that would probably...
So if all other things are equal, that is very much a differentiator I've found.
And I did not...
And is that entirely Slack or Slack plus email?
There's email there as well.
There's calls, but the vast majority is like on site.
So it's Slack.
Like we have had...
customers like, hey, we have a problem.
Can you get on huddle?
Like we will get on that huddle like five minutes, literally.
I've done this multiple times.
So yeah.
Okay.
So how big are you?
25 today.
How do you do this kind of support?
We're insane.
We don't sleep.
007.
Have you heard the new thing?
007.
I mean, I've met your team.
They're very impressive.
They're very dedicated.
But also, how do you get a team to do that?
I have Slack exhaustion, you know?
Yeah, we all have Slack exhaustion.
We're very, very tired.
The thing that's unique, I don't know, unique about us, but I would say unique about any successful serial founder is that you're able to pull in people that you've worked with before.
And so you can't do that as a first-time founder.
Like, I couldn't have done that.
But of the 25 people in Daytona, I think about 13 of them, we have worked with seven years plus.
Yeah.
So it's like high trust, high throughput, high, we know what we're signing off to do.
And especially these people worked with us when we were starting and we were actually hustling, you know, hungry for food hustling type level.
And so those are the people that work with us.
The now, the new segment that has come is almost everyone is sort of, you know, one degree of separation.
So it's like someone that someone has known.
And so they sort of.
come into this org.
And we've had people that have like not fit into org as well.
It's just like, it's that type of culture where there is a high expectation of like being online, replying for these things.
And I do that first.
You will, if you ask any engineer, they're like, you never sleep like about me.
And so then I do that as an example.
I don't do it as an example.
That's just how I'm wired.
My wife doesn't appreciate that.
I tell you, my wife doesn't appreciate that.
I told her about 996.
She said, I wish.
It's like these Chinese people are slacking.
Yeah.
So like that is something there.
And so I think every company has their own culture and that's something very, very deep.
And it's something that's come up again and again.
And every single day we're reminded about that.
And I didn't go out thinking that that is how I'm going to build it.
It's just how I built these things.
I'll transition a little bit on the founder side.
Like I'm very impressed by you in general of like your sort of balance.
You have a young family.
Two kids.
Yeah.
Two kids now.
Yeah.
Two kids now.
I think a lot of people I meet, they're like, well, I'm starting a family.
I can't be a founder and all that.
What's your advice to those people?
Every single day.
So my family, they're here right now, but they're usually, I fly between Croatia and here.
Like a lot of our team is in Croatia.
A part of our team and a growing is here now in San Francisco.
And so I spend a lot of time away from my family.
And that is hard.
Like that is a sacrifice that you have to.
But going in, like people say like on your deathbed, you're going to miss some of those things.
The thing that, and probably might be true.
But I think that going into this, I already said, like, I know that this is going to hurt and everything has to hurt.
By the way, I'm very much of a feeling that everything has to hurt.
Going to the gym hurts.
Losing weight hurts.
Like everything has to hurt, right?
It does.
No pain, no gain.
It is literally, but you actually have to enjoy the pain and just like, if you don't enjoy the pain, it's not for you.
And so you get accustomed to that pain.
And so a lot of kids, especially, I'm a daughter and a son, daughter is the oldest, like love.
her and do miss her when she's not here.
But it's like, that's what I signed up for.
And there is a plan and target of what I'm trying to achieve.
And now hopefully with my wife, which does support me, we can get ourselves together more.
So it doesn't there, but she takes a large portion of that.
And so if you have a partner on the other side that is okay with that, then you can do that.
But even if they do, you have to be okay with not being there.
Yeah.
This is my, uh, my vision for you.
this meme.
Yeah, yeah, yeah.
So that's your kids in the future.
Yeah, I think so.
We have to teach them that they're not rich.
Because dad, you know, built the compute sandboxes.
Dad made sandboxes.
Dad made sandboxes.
And built the spiritual successor to serverless and Kubernetes and for agents.
Any other sort of hot topics, trends?
You have a lot of hot takes.
Actually, you are best known for, you were sort of in sort of hustle culture mode, right?
And someone quoted you and said, I haven't even heard of you, bro.
Just log off and take the Christmas off.
And then your response was?
My response was like, that's why I can't.
Yeah.
So, I mean, I think that's very typical of you.
I don't have it here.
I can't bring it up.
But I think that's very typical of that culture.
But I think you have a lot of interesting hot takes like that.
Any other sort of takes on the startup ecosystem?
Oh, the startup ecosystem.
And this was the recent one, which is I think that and this is general-like business, I feel that the, it didn't come off, I think, well on Twitter, something that has misread it, which is the market is adding premium to SaaS vendors that are reselling tokens.
Yes.
And I think that's incorrect.
Why?
Why I think that's incorrect is that if you look at, one, your pricing depends on what the price is, if it's a public market or if it's private or whatever, you're saying, the person that's reading that, that the reacceleration of revenue is equal to the old revenue, which it's not, not even close.
Because one, you had on SaaS, you had typical SaaS margins, whatever it was, right?
Stickiness and all these things.
Now what you're doing is you are saying, here is my agent and I have whatever the margin is, it's way worse, right?
And now you're using Anthropic or, you know, or OpenAI or whatever through me, the SaaS model.
And then we as a community are saying now that is reacceleration.
And so one, I think that's wrong because first it's not the same.
The makeup is not the same.
The other thing is, and go back to like what I mentioned earlier is like the Kua and how I set up OpenClaw and whatever.
I don't want your agent essentially because what happens right now we have a problem that, and this historically been, you have data siloed in, again, ClickHouse.
QuickBooks, it's all siloed.
And now you're giving me an agent that'll give me the data, but it's still siloed.
Right?
And so now I have to like take that data and then get another agent.
Just expose the data to my agent.
Just expose the data.
And one thing I have to say, and so I'm like, just expose everything and charge me for that.
So charge me for consumption of API.
So you'll have your old seed-based pricing for humans.
Yeah, yeah.
Charge me for this.
The number of agents will skyrocket and essentially you'll have more usage and charge for more if you're product has value.
So like there's arguments, some of them do have value, which have database, not database.
We can get into that, but some of them really do.
And I was actually shocked that the first person to do this was Benioff.
Salesforce.
There was a tweet, I think three days ago, where she said every product in Salesforce has been exposed via API.
Wow.
Everything.
And I'm like, now I understand why this person has built this insane.
Kudos to him.
amazing.
It's like, thank you.
I don't know if you listen to me or someone else, but like, thank you for someone.
This is the direction of the world.
And so if you can get real acceleration against that, against consumption of API, that is actual revenue and that is actual real acceleration and that is where value will come from.
And I think that there will be a cold shower when people understand like no one's actually going to use and pay for these agents and tokens and that wasn't actually real acceleration, but it'll drop back down.
Yeah, I mean, look, like, obviously, I think generally correct.
And I agree, I think, but people are going to try to become an AI company.
No, no, absolutely.
And nothing against that.
And this is no, to be very clear, this is not a downer on anyone that's building this thing.
Everyone has to get to like, get to the revenues, get to multiples, get to valuations, do what you have to get to the next step.
Absolutely agree.
But we as a community are now like saying, oh, this is like the magical way to get out.
This is not like, that is not what's happening, right?
No, I think there was like this kitchen appliance company that put out some AI nonsense recently.
But it was also the sneakers, what was called Allbirds.
Allbirds.
Allbirds is pivoting to GPU.
That's fine.
It's like, you know, I have some money left.
I'm just going to do some lottery tickets.
Would you go into offering GPUs?
Oh, yeah, we will.
But not for inference.
Like essentially what we think about is like the GPU sandbox.
So if you think of like, if you have a GPU in your computer.
that is what you have a GPU in the sandbox.
So there are workloads that do need GPUs.
Again, I always go back to 3D rendering because it's the easiest one to comprehend.
But like, if you want to do any type of RL on like CAD or something like that, you will need a GPU in the sandbox.
And so that's coming now as well.
How about own data centers?
Own data centers.
So we run on co-location providers, bare middle machines.
Data centers, we technically can run on that or our own data center.
Like that's how we architected it.
Today from a gross...
profit margin perspective doesn't make sense for us to get in that.
You have to raise a large amount of capital, a large amount of risk for like single digit percentage points.
So today that doesn't make sense, but we are fundamentally architected so that we can do that if we want.
Yeah.
I mean, you're a large customer of these guys now.
Do you see any opportunity?
We will see.
Yeah.
We will see.
Yeah.
Yeah.
I see a lot of people like.
trying to do the bare metal thing.
We talked to Railway the other day and they're also doing a very similar strategy.
They think, I think they're building out something or they have their own sort of data centers now.
Yeah, their majority, their own data centers.
But I do think, I mean, they still use Equinix and all those things.
So I think it's just interesting that, you know, this model basically hasn't changed.
It's basically a real estate model.
They manage the facilities and then you do everything else.
I wonder how it can be changed for the future.
Because I mean, you know, the AI wave is an opportunity to reinvent everything.
Yeah.
Anything else?
Cool.
I think that's about it.
I didn't have any other topics.
I think this is like as best and comprehensive, like if you have like any questions about the compute market and sandboxing in Daytona, like this is the best place to start.
Where does this go, man?
Like, you know, we're here in April.
Things are going 75% month a month.
What are we going to be by end of year?
It's an insane number.
I'm sort of scared to say it out loud.
So it's very big.
Just the sandbox market, and we talked about this in general, the entire infrastructure market is growing 40% plus or minus month or month.
Everyone is growing 40% month or month.
And that's also a hot tag.
It's like if you're not growing 40%-ish, it's not that.
It's just the market.
You might as well, you don't have to come to work.
You'll grow that amount, basically.
I'm half kidding, but that's where it's going.
And so where does it end?
We will see.
the thing that I think about from from at least a CPU perspective, GPU is even crazier, but a CPU perspective is like there is a high probability that actually owning the CPUs beforehand will be a a go to market tactic.
And it will probably because as you do probably talk to a lot of GPU providers, their growth is hindered by the amount of GPUs that you have.
Right.
Yeah, it's just like it's whatever Nvidia decides to bless that day.
Yeah, that's how much they're going to grow, right?
And so the CPU market in general, be it like something like Railway, for example, or Vercel or whatnot, or deployment, or like the sandboxes, they're still CPUs.
So like each is growing at the pace of the market and what they're, you know, plus or minus of that market, but it's still not constrained by that.
And so my thought is like, for all of us in this market, and databases fall into that as well, because databases also run on CPUs.
And it's like, We all have to grow as fast as we can so we can get enough of, you know, CPUs tomorrow from Intel or from NVIDIA because they have now CPUs and everyone else later on.
So it'll be interesting when we get to that.
Maybe one version of I'll phrase this is like, are you, you know, is the potential new Heroku, new AWS or new Stripe?
Like what's the analogy that is most appropriate?
It's interesting.
There's like analogies of like...
So, you know, there's new Cloudflare, but new Cloudflare is new Cloudflare.
Like, they're actually doing a really good job about, like...
And Cloudflare owns networking.
No one can fight.
Yeah, yeah, yeah.
Come on.
They're doing really well.
No, what I was going to say is in the sense of their whole agent portfolio is actually really good.
And I should say, there are some technical limitations, I think, personally, around, like, everything's under, constrained under workers.
Like, workers is their thing.
But from a go-to-market vision perspective, I think they're actually really, really good.
I think they actually get it, unlike some other companies.
And to your question is like, what is going to be, there will be an equivalent, everyone says like an AWS for AI agents, but your answer, like it might look more like Stripe than AWS in a sense.
So there will be a cloud built out specifically for agents.
And so that cloud will have sandboxes and it will have web search and it'll have databases like.
SQLite or Neon or whatever specifically for agent and other things.
We are not at the end of the new infrastructure primitives for agents.
There are more coming.
So people think like, oh, there's nothing else.
There are more.
Like we have some ideas about the next ones.
We don't have time to do them.
But there are definitely more primitives that are being built out for agents.
And there will be, I think, a cloud that runs all that.
Yeah.
OpenAI has said AI cloud.
Vercel has said AI cloud.
And you are potentially also one of the other perspective AI clouds.
I think it's a Very big prize to win.
Well, thanks for coming on.
Thank you for having me.
It's been amazing.