Software Supernova: Bolt.new - The AI Web App Developer In Your Browser

The numbers we publicly disclosed, like in the first 8 weeks, we went from 0 to $20 million of ARR and we've just continued to grow since then. We actually wrote an operating system that runs natively inside of your browser that boots in like 100 milliseconds. There's zero latency. There's no cloud VMs that have to get spun up. It gives you a very reliable experience that actually can scale. If you force people to go download a thing to their computer and set all that up and then they get to use Eye, the drop-off is insane. Right. I mean, it's like 90% or something out of it, if not more, whereas when it's native in the browser, it's frictionless. And the actual AI augmentation then actually even picks up from there. Right. So there's an order of magnitude more complexity. You have to set up an environment locally for any of these things.

Hello and welcome back to The Cognitive Revolution. Today we're simultaneously releasing the first 2 parts of a series that we're calling Software Supernova. With the makers of new and stunningly fast-growing full-stack AI developer products, Bolt and Lovable. Both episodes explore in different ways how AI's rapidly improving coding capabilities are beginning to tangibly transform the software industry by expanding the space of what can be built, changing how professional software developers work, and making it possible for people to create software without ever learning to code. My guest in this episode is Eric Simons, founder and CEO at StackBlitz, makers of Bolt, online at bolt.new, which has suddenly gone vertical after adding an AI coding assistant to the web-based IDE that they'd spent the previous 7 years building. After announcing that they'd reached $20 million in annual recurring revenue after just a couple months in market, the company has gone on to raise and recently announced a $105 million funding round. In this conversation, Eric walks us through how the company's foundational web container technology works and how it's allowed them to scale so rapidly, explains the company's open source approach and shows where we can check out their prompts on GitHub, uses the agent to build a Spotify clone with just a few natural language interactions, showcases a few web apps that real customers have built, and describes how product managers are having especially notable success using Bolt to bypass design platforms like Figma and instead go directly to working prototypes. Video of the demo, by the way, is on YouTube, and the app design did come out looking really good. But you can take my word for that, and I think you'll be fine with the audio-only version if you prefer. We also discuss how the economics of AI development are creating unique opportunities for Bolt users. One freelancer, Eric says, spent $7 on Bolt inference to deliver a $9,000 project for a client. To be honest, I have no idea how much of that is really happening in the economy at large or how long it will last. But I can confirm that there is at least some real AI arbitrage going on right now. Businesses that are used to paying tens of thousands of dollars for projects are now effectively paying thousands of dollars per hour, in some cases without realizing it. In any case, I'm confident that the market, including the market for rapid response human help that Eric and team are planning to build on the Bolt platform, will rapidly bring prices down and send quantities soaring before we know it. And once again, I feel like the safest bet in the AI revolution is high consumer surplus. As always, if you're finding value in the show, please share it with friends, write a review, or reach out via our website, cognitiverevolution.ai. We always welcome your feedback and suggestions. For now, I hope you enjoy this unique perspective on AI-powered software development with Eric Simons, CEO of StackBlitz, makers of Bolt, online at bolt.new.

Eric Simons, founder and CEO at StackBlitz, makers of Bolt, online at bolt.new. Welcome to the Cognitive Revolution.

Awesome. Thanks for having me. Excited to be here.

You guys have made a splash, to say the least, in one of the hottest categories going right now, which is the full-stack AI software engineer. People are prompting their way to all sorts of creations on your product. And the revenue is popping off. You guys have raised a bunch of money. We're going to get into all of that. For starters, I would love to get just a kind of general sense of your AI worldview, because I feel like so many of these conversations are much more intelligible, much easier to sort of understand the details when you have the person's big picture in mind. How would you describe where we are right now in the AI moment? What is your expectation for like, AGI or transformative AI? Are you somebody who worries about risk? Do you maintain a P doom? Give me the Eric Simons AI worldview in a minute.

I guess to me what's been very interesting, if you kind of rewind a couple of years when ChatGPT came out, the first year after that, I mean, it's just people are like, AGI is going to be here within a year. Da da da da. I mean, there's a lot of hype, and understandably, because it was this obviously a pretty big zero to one moment sort of thing. And these models have gotten really good at certain things. But Software is one that makes sense. It's getting a lot faster because its code is text-based, and right, and so it's easy to train these things. And it's also you know code is deterministic. Like if you want to train an L11 to be good at law, you know you're looking at like the cases dating back to you know the 1700s and like how this judge felt at the time. It's not deterministic, but with code, it's you know you can write code and AI can write code, evaluate it. Did it do the thing or not? And then that's a new test case, right? So it makes sense that in the past year, that's where. Yeah, I think some of the biggest leaps have happened, and that's going to continue. So I guess my pragmatic AI worldview is just, you know, the world software order is getting rewritten. I think the world software is actually going to be maybe the first major tectonic shift that's going to happen where stuff is just getting replaced by AI. Like, software is, you know, one-to-one getting replaced by being generated new. And I think that's going to be huge because, you know, The bars can be lowered for creating software. So I think to me is the most interesting, very tangible what is happening right now versus kind of, okay, postulating like where a year from now, 5 years from now. Yeah, I mean, at least to me, it's like I like to take it more like what's the pragmatic on-the-ground view of what we actually see moving in a meaningful way. And obviously the stuff around reasoning is a pretty big breakthrough, I would say. But again, where's it going to have the most, where's it going to be a multiplier? You know, particularly it's like software. Apply reasoning into software development. Boom! That's huge. Anyway, so that's I think that's kind of my general worldview. I holistically, I think it's just going to be a good thing. I'm not. I you know I don't think that this is going to be you know like every other technology that's come before this. It tends to be a great enabler of like a different future, and it's things you know are reconfigured differently. But it doesn't strike me that what I see now is just people that couldn't code before being able to build real. Production products, you know, with software and like engineers that are fantastic today are, you know, can leverage themselves 5, 10x, right? So the world needs more software. We've just been, we've been constrained.

Yeah, it's definitely been pretty much universal, I would say, among businesses that create software at all, that if you had asked, you know, at any point in time and still to today, you know, is there more you would like to be creating if you could, then they're all like, yeah, we're totally constrained by how many developers we have. We're constantly making these trade-offs, constantly prioritising. I've certainly lived that life myself. But your comments about reasoning, obviously we're in the O1 to O3 transition period and also the R1 moment. It is crazy to think that we haven't seen it as the public yet, but the O3 results where they have the model in the top 200 coders in the world on competitive coding challenges is really a pretty crazy result, right? I mean, that's like beating almost everybody at OpenAI. I think they said there was like maybe one person left at OpenAI who has a higher score in competitive coding challenges than the latest model does, which is pretty wild to think about.

So how do you—

I mean, I sort of am a big believer in We need more software. I've also kind of started to be a big believer in the concept of luxury software, or I just saw the phrase for the first time yesterday, selfish software. And those are kind of similar ideas, but basically, like, potentially you don't need to create software for a mass market. Potentially you can just create it for yourself or for your team, or you can create AI apps that spend an unreasonable amount of tokens Because it's worth it to you, even if you couldn't necessarily take it to market in a scalable way. I would love to hear what your vision is in terms of how you think we'll be interacting with software, what the software landscape might look like in the future. Because I do also feel a tension where I'm like, to some degree, yes, I want these personal things that are just made exactly for what I want. But then I also am kind of like, But also I do really want to use like well-polished stuff with like good UIs. You know, it's sort of in today's world, it's easy to have that vision, but then it's also easy to get to a point where you're like, I tried making this thing for myself and it has a lot of bugs and it actually is not, you know, I'm not exactly living the dream yet. So, you know, give me a little, put a little more color on like what the future of the software development and user experience might be.

No, it's a good point. I mean, if I had to like rephrase this, but you're kind of pointing out there's kind of a long tail of like, okay, you can have this thing punch out software, right? But there's a long tail of like UX and even just support issues with it that are not, certainly today are not addressed. And it's like, even if you kind of look forward, it's like, okay, well, you know, if you're constantly having to have, you know, what, at least today are expensive models and maybe that price, you know, it's just going to keep going down. But like, I mean, so it's just really a question of how far out into the future is the long tail dealt with? Like, where does equilibrium hit basically? And I think you kind of hit the nail on the head is I think, you know, for certain use cases today, it already makes sense. Right? Like for people that are using Bolt, they're building internal tools for their company that are actually relied upon for critical business function or whatever. People are building real products that are like their startups and that sort of thing. So it's like, I think in both of those cases, you're kind of dealing with people that have a keen eye for product. And I think like the people that find the most success with Bolt, and I imagine other tools in a similar space, is like they tend to be like PMs. And And designers and that sort of, and of course engineers, but I'm going to kind of put them aside because they know how to like write software. But the people that don't know how to code, it's like entrepreneurs, PMs, they know how to build great products. They know what that experience looks like and feels like. They know how to actually sculpt the thing, you know? And previously they could only write that code through someone else's fingertips, you know? And so they, again, PMs, like their job is really interfacing with developers and like, Helping point them in the right direction, how to you know actually you know make the product experience great. Now with the AI, they're just saying basically the same words, but just getting an instant result. Be like no no no like no more of this, less of that or whatever, right? So anyways, I think for folks that fit that category, I think that they're already finding a lot of success today, and over the next year or two, it's going to be even more. For when you kind of get to like general end user, I think the point's extremely valid where it's like you know to reasonably expect you know someone who has not has not been in like the the business of building products to really be able to build something that's going to be bug-free and a great experience, da da da. I think there's going to need to be more, in short, under the hood, just more inference and more capabilities in these models and the agents to actually allow you to do that. Because right now it's just very rudimentary. It's very rudimentary. And there's a lot of the issues that people run into when they use Cursor or any other tool than when they're non-technical. It's like, You know, when stuff goes wrong, it's like, how do you fix it? So that's, I think, certainly trending that way. And it's like, you know, I think a lot of the folks in that category, PMs, entrepreneurs, designers, et cetera, you know, I think that's going to be the first big market unlock here. It's already happening. These folks are coming online writing software and like next few years that's going to explode.

That's quite interesting and sort of anticipated another question I had in terms of just like, who are your target customers today? So it sounds like they are people who are gaining leverage and doing things they probably otherwise just would never see bubble up to the top of their to-do list because they can now talk to a product like Bolt instead of having to talk to a human. And obviously the cost ratio there is massive.

It's nuts. Yeah. So our user base, like we see, you know, something like 40% developers, 30, 40% are traditional software developers. You know, 60, 70% is folks that are like PMs, entrepreneurs, that sort of category. They're not software developers. In the developer category, this is a 10x multiplier on their ability to go and like make prototypes or ship, you know, create UI or whatever have you. So they're coming to us to drop in stuff from Figma or prototype out an app they've been thinking. And instead of going and, you know, writing out a whole bunch of code or having to instrument stuff in Cursor or whatever, they just come to Bolt.new. They drop it in, hit enter, couple of prompts, they get something great, they pull it out to Git or locally or whatever, and then continue building on it. So that's like a very concrete use case. Like that's one of the ROI stories. There's this guy CJ on Twitter. I mean, I don't know what his handle is, but he's got like the most insane ROI that I've seen. But basically, so he's like a freelancer and his client had him build a, like a web app. It was like some dashboard or something. And he spent like, I think it was like $7 worth of inference on us. And someone asked, you know, the question I would've asked, You know, had they not, which was like, how much did you bill the client? And the answer is $9,000. It's just so if you like go to like Twitter and you search like Bolt arbitrage, like there's a lot of developers, like freelancers that are connecting the dots here, right? Because you have this, you know, the demand supply curve, it has not begun to normalize on that yet, right? So that's kind of that one category. And we have Fortune 500 using it to prototype instead of using Figma and that sort of thing. On the PMs entrepreneur side, folks are coming here where whether it's a side project, they want to launch a startup or a side business. They're using Bolt to build full-stack applications with payments and authentication and database and all that sort of stuff. And even if they're at a company, again, like, I mean, if you think about like the role of a PM, a lot of their job is like writing Jira tickets, explaining how to make the product better, assigning it to someone who's going to code it. They say they did it. The PM reviews the work. They give feedback. It's like, wouldn't it be great if they could just like, instead of writing the Jira ticket, they just Tell an AI to do it, get the immediate feedback. When it looks good, they just commit it, you know, and then the developer can pull it down and they had no idea if that was written by a coworker or an AI. It doesn't matter, you know. And so that's like we're seeing that use case a lot as well, you know, for both people that are starting their own stuff, starting their own projects, startups. But, you know, now we're seeing businesses start to come online where it's like, oh, okay, like this is, this is a huge multiplier. Like the devs, it's a better use of the devs' time. To work on really tough functionality that like the AI models are not great at or whatever, right? Zero shot at least. And the PMs can go ahead and make the, like the kind of the sort of like level of UX polish you're describing where it's like, make the buttons align, make the colors right. Like make sure that this goes to that page when you click submit, you know, simple stuff like that. It's like, you know, they can just do it and they can make sure it's perfect and then ship it. Right. So those are the kind of the 2 segments of the audience we see in the sort of use cases that they're finding a lot of success with.

Hey, we'll continue our interview in a moment after a word from our sponsors. Yeah, that's interesting. So if I imagine not too long into the future, it seems like everybody has this vision, and it seems like from your answer, we're not quite there yet to where people who have not been in the product creation business at all could start to get into the game. I imagine kind of a number of different stumbling points or barriers that they would have to get over, some of which would apply even to today's users, the developers, and even, or the PMs and even the developers, but others would be sort of easier for your current user profile, but harder for these, like my dad or my mom who's never done anything like this. But my dad has plenty of ideas. So maybe we can just run through a few and you can kind of tell me how you're thinking about it. One is like just drawing out of people what it is that they want. I think when my dad sits down at something like this, he greatly underspecifies what it is that he even wants. And doesn't even know that he's doing that, right? He just is like, he's so green in this area, and then he gets something back, probably from a lot of products where he's like, that's not what I wanted. And so I wonder to what degree there's a way to get over that. I also would flag, as you did, when things are not working, how do you fix them? That has been probably one of the trickiest pain points. I'm really interested to hear how you are addressing that and what you think the sort of trajectory is there. Another one is deployment. And that's also, I'm sure, like a really critical one for your business because, and I've lived this reality too at times. So it's like, it's one thing if people can come in, make something with your product, export it, and never have to come back. It's another thing if you become part of how they actually operate their business. So I'm sure that's something you think about a lot. And deployment is definitely a major pain point. You might also have your own taxonomy of other challenges, but sound off on those 3 at least.

So on the first one, right, like people that have not worked as entrepreneurs or product folks before, et cetera, we have folks that are coming to the product and using it that don't fit those categories exactly. And everyone has to learn, right, how to build great products. That's like, there's kind of a general skill set of kind of learning how to like really sculpt something, right? And what's cool about Bolt is, and again, like, you know, or just these AI generative tools, is it's lowering the barrier to entry to come and learn how to actually build great stuff instead of getting mired in— like, you know what, my co-founder and I, we grew up down the street from each other in Chicago when we were 13, and we learned how to code together. And we learned how to code together because we wanted to build products. That was the reason we got into building software. If this existed then, I don't know how deep we would have necessarily had to go or have gone on becoming software engineers. You know, because our end goal is to build great products. And so I think we have a ton of people that are coming today to Bolt and they're learning by actually working with the AI and how to best leverage it to build products and picking up the general, how do I build products or how do I build a business skillset, right? And like, so it's funny, like actually a couple of weeks before we launched, I had my mom who's 73 test this thing out because she's the— I love her, but she would admit this readily. She's probably the least technical person you'll ever meet. And she built and deployed her first website on this thing without any guidance because it's just, it's the simplest interface in the world. It's a text box that you type in what you want, you hit enter, and then there's a deploy button, you know, where you get a live URL of the thing. That's it. There's a lot of use cases too that we've seen of just people building this for personal, for weddings, you know, for one guy who had tweeted us, you know, his daughter needed medical donations or something like that. And he created a website to do that, which I, which to me was kind of like, I was, you know, it was But I was also like, you know, should I tell this guy that like Wix exists, right? Or Squarespace? Because we're not the first people that have allowed you to build a website. But then it hit me, like for my wedding website in 2021, I used Squarespace because my wife, I had originally wanted to build the site myself. I spent a week, like a day on a weekend on it, never came back to it because it's, you know, it just takes a lot longer than you want. So she, you know, made me use Squarespace and man, the interfaces for those things suck. These drag and drop builders are really complicated to use and they're supposed to be like targeting Less sophisticated computer users than than me. But but when you look at bold, it's this is it. So it's like that entire category is like gonna get it's gonna go away. I mean, like this, there's no reason for drag and drop wissies when you when you have this sort of stuff, right? So anyway, so yeah. So on how do you educate these folks though? How do you make them successful? So I think there's two direct ways that you can do, and then there's kind of a rising tide. Thing that's going on, but basically one education, like teaching folks instead of just the school of hard knocks of them prompting the AI and figuring it out. Create great resources. I think this is one of the things that's been very effective for us is like we've invested a lot in our community because if you look at Midjourney is probably one of the best examples. What made Midjourney really successful was the community of people prompting, but then sharing those prompts and et cetera. And so that's kind of the same thing we've got with Bolt, where we have a very vibrant community of folks that are sharing how they are doing it. And we're learning a ton from these people because like they've used the product more than our own core team has at this point, you know, like they're the kind of the domain experts on the thing. So we invest a lot in our community, our educational resources, that sort of thing. That's like a, you know, a long-running sort of how do you kind of ramp people? The second thing is just we're not at a point tangibly Depending on if you're trying to build something pretty complex, we're just not at a point where you can actually, without any technical knowledge, just rely on an AI to get all the way there. And really what you need is just someone like to grab who's reasonably technical or is just very good at debugging these things or whatever to grab like 30 minutes of their time and just kind of plug them into your codebase. And so we haven't announced this. I think we're going to announce it like next week. I don't know when this is coming out, but like if this scoops our announcement, it was, I guess it was heard here first. But so we're going to be, we're actually like rolling out a program where Within Bolt, like you can actually kind of raise your hand and go, hey, like I'm stuck on something and we can actually connect you with like an expert that we've like certified that can like punch in, help you get debugged real quick and then get you back on your way. So you can just keep using the AI and that sort of thing. So it's just like basically a way to just get quick on-demand help to get unblocked or get a professional opinion on it and then move on and that sort of thing. I'm not aware of anyone else that's done that model really well. So I think we will probably be one of the first. And I think the third thing is. These models just keep getting better and we're making our agent better and better, et cetera. And the quality of the models has, you just, a multiplier on the swing of, you know, everything that's leading up to that, like how much you have to learn, how many times you need to loop a human into the process to help debug you, right? So it's like, I think if you look forward over the next 3, 6, 12, 24 months, I mean, it's just, it's the better those get, the less you're gonna have to rely on the other things to actually keep, you know, proceed, right? But even today, it's like we've crossed this chasm where it's crazy valuable. You know, that wasn't true a year ago. Yeah. Yeah.

I think we've officially put to bed the no progress since GPT-4 narrative that popped up for a little while there. But even before, like the 0.1 sequence, I was like, guys, like there's been a lot of progress on just making GPT-4 class models, you know, do the things that we actually want them to do in a much more consistently useful way. So I totally agree that the progress has been Pretty amazing, especially in areas like code. So it's really, I think that the human in the loop thing is really interesting. You guys are literally exploding right now. I don't know what metrics you're tracking or how much time you have to even stay up to date on metrics, but do you have a sense for what your success rate is? If somebody sits down at the product and is like, I want to build X, how often do they actually get to X versus getting stuck somewhere that they can't get out of? And do you have a sense also for what has moved the needle on that success? I assume that getting the model to do a better job is core to that, but I'm kind of wondering, are you fine tuning? You did mention choosing integrations. That's another thing that I think people are very overwhelmed by, by default, right? Oh my God, I want to do payments, but What do I use? Yeah, it seems like you're being pretty prescriptive on sort of, this is the happy path that we think you, you know, we really think you should go this way. I imagine that's been a driver of the success rate. But yeah, what is the success rate? What's driving the success rate? And what do you think will drive it in the future?

Yeah, good question. I think we're seeing a good success rate. I think that, you know, at a high level, you measure this with just like revenue growth. And, you know, for us, like with the numbers we publicly disclosed, like in the first 8 weeks, We went from 0 to $20 million of ARR and we've just continued to grow since then. And so we haven't seen the ARR go down at all. Right. And so I think that when you dig into the usage metrics as well, it's just, we're kind of setting, you know, new, more and more folks coming to the platform. The retention is extremely good. With a lot of these products in the AI direct-to-consumer space, the churn on these things can be insane. I mean, they can be like 60, 70%. We're nowhere close to that. I think this acceptable is anywhere from like 20 to 50. You know, we're hanging out like the 25% range, which is like pretty good. So people are finding a lot of success in the product and finding a lot of value in it because they're sticking around, they're coming back every day, etc. And, you know, I think that's to— there's some, you can kind of like look this stuff up online, but as far as like AI code products globally, if you kind of exclude like Microsoft GitHub and et cetera, we look at the startups like from, you know, I think free markets are a good way to just measure how much value is being generated, right? For folks in startups, like Cursor is number 1 at $100 million. We're number 2. And then there's a whole category of folks that are kind of in the, you know, anywhere from like $5 to $15 ARR or something like that. And so there's really, there's only been at this point a couple of You know, there's really only 2 tools at this point that have kind of broken out for the rest of the pack, and that's us and Curse. I'm sure there's gonna be other folks that pop out and that sort of thing. But I kind of look at that and it's like, you know, clearly something here is working. And for our product, a lot of this comes down to this technology we made that enables this experience. I can show it in a second, but basically you think about, okay, well, if I'm gonna come to Bolt.new, And I'm going to type in words and get a full-stack web application back. That sounds great, right? But when you actually go to build these products, the question is, okay, well, where are you actually running the development environment for that? Like where that full-stack app is running that the AI is programming? How do you do that? And this is just, it just so happens, this is like what our company has been working on for the past 7 years. We started out as a web-based IDE. The traditional way that you solve this problem is you put it on a cloud VM. Like everyone gets their own cloud VM that's using the service, et cetera. And that's kind of been the model of cloud IDE since Cloud9 was like the first. And there's never been a breakthrough application that has been used by lots of people that has this model where every user gets a VM for a couple of reasons. One, the experience tends to not be great because you have latency. So every keystroke you're putting in has to be synced to a server. The result has to be synced back to you. Someone's got to pick up the cost of that cloud VM because these things are They cost money. If you want to scale to a billion people, that's a billion VMs. That's a good amount of capital. But the other problem is there's not a billion VMs that you can rent on the planet, but there are a billion devices. So there's a billion laptops, iPads, whatever. And so if you look at how Google Docs and Figma work, like they don't spin up a cloud VM for each user to actually render your designs or as you're typing the document, your keystrokes show up immediately. And that's because it's using your CPU, your memory, your GPU, through the browser as the interface to those parts of your device. And so what our company did is we actually wrote an operating system that runs natively inside of your browser that boots in like 100 milliseconds. There's zero latency. There's no cloud VMs that have to get spun up. It gives you a very reliable experience that actually can scale. And so when you kind of look at the other approaches in the space, a lot of the issues folks will run into is the cloud VM gets borked. It's extremely slow, the latency, da da da. There's tons of issues that can kind of happen with these things because they're just running in the cloud. Tends to be a lot more expensive. And whereas with Bolt, you come here in 100 milliseconds, you have a live environment, the AI is just punching code into it and you see the result like instantly. I think that's like under the hood, something that's like maybe not obvious to folks that are visiting, but from a technical perspective, that's like the crown jewel of our company. Like we spent, you know, 5 years building WebContainer, this technology. And it just so happened that, you know, what we've been building with Frontier AI Makes this magic experience that just kind of isn't possible with any other approach, right? So I think that in a nutshell is the key enabler for us. And then beyond that, it's yeah, certainly like we're doing a lot of stuff around our AI agent. Like a couple of folks in our team that actually built the Web Canary technology just so happens that before that they were working in ML and AI. And so when it came time to actually write our AI agent, they knew exactly what to do, you know, to go and build them, but also instrument it so we can actually like. leverage the data and the insights to fine-tune and make it really reliable and not run into tons of errors for the end user. Because again, we want it to be a smooth experience. So in a nutshell, there's kind of a lot there, but that's, I think that's the 360 of like, why is the experience this so different and kind of why has Bolt been a completely different trajectory comparatively to kind of the other stuff that's existed before us and after us, you know?

Hey, We'll continue our interview in a moment after a word from our sponsors. I've got like a growing collection of these stories of people who were building something hard and then AI came along and made it like, you know, 10x more valuable to sometimes the same user they originally envisioned and sometimes like an entirely new user base. And it sounds like you've had a bit of both, but it's really expanded who can use the product. I've lived, for what it's worth, a pretty similar story at my company, which is Waymark, where we do video creation for small businesses. We've been on this journey, I call it, from DIY to done for you by AI over the last few years. But similar thing where we spent a few years building an in-browser rendering engine for And because we had a couple, and one in particular major early partnership with a cable company, Spectrum Reach, we had to deliver TV quality specs. So we couldn't take any like shortcuts on the final thing. It had to be 30 frames a second and HD and so on and so forth. It was a little bit crazy to try to do that in the browser. And we ended up with a lot of work into that tech stack.

Yeah.

And then it was kind of like, I don't know if you've experienced something similar, but we did sort of have an in-between moment where we were like, okay, this thing's working pretty well. But then we sort of found like, huh, people that are pro video creators, they still want to use the pro tools. People that are not pro video creators were giving us feedback like, yeah, this is great. You know, it's easy to use. And we were like, so why don't you use it more? And they were like, I don't really know. I don't really have any ideas for videos. Or I did have an idea, but, you know, I sat down to try to write it and I kind of got frustrated and we're like, you know, could we make it, could we improve the product? A lot of times they're like, not really, you know, it's just, it's on me, but, you know, but it is what it is. And so the AI thing like totally changed that. And now the, you know, it's sort of accessibility in a web, you know, browser-based sense did not automatically translate for us to Actual end user value, but then layering on the AI, you know, totally transformed that. We haven't grown it certainly as fast as you've grown, but it has definitely changed the trajectory for us too.

Yeah, I imagine. I mean, that's the exact same story. And like, if you rewind 6 months, we were, you know, we had this awesome technology, developers loved it, but it's just like, we couldn't get them to leave their local tools and therefore build a meaningful revenue generating business out of the thing. And so we were looking at like, okay, well, it's, we might need to start figuring out how to wind this thing down. Because at some point after 7 years, it, you know, this is cool technology, but we're a venture-backed company. This has to make sense, right? And that what you just said is exactly what happened with us. And so hearing it's happened with you, I remember you mentioned this a little bit when we chatted like a couple weeks ago, but it makes me think there's going to be more of this, right? Because that's the idea of like, if you think about people that are non-technical, if you look at any profession, most professional tools, if you're going to be using a computer to do it, are local, right? Like video is something that's a graphic setting until Figma was local, right? And then Canva, I should say too, for that matter, development, video editing, video games. There's kind of this list of things that have not come to the browser yet. And for, because it's just really tough to get professionals out of the existing environments that they are in. Like Figma's like Figma and like the G Suite are kind of the only ones that have really broken through. But with AI actually making a, like lowering the barrier to entry, I actually think that this stuff being able to live in the browser is a key part because the hardest part, if you want to become a software engineer, and this is like when we started StackBlitz, like the company that builds Bolt, the key insight that we had is like setting up dev environments has always been the worst part of this from when we were 13 learning how to code. It's like, you're not even learning how to code. It's like, Week 1 and 2, learn how to just get stuff installed on your computer and like just get a dev server, right? So you're not even coding, you're just poking and prodding your machine to get it to work right. And this happens when you join like Meta or Netflix, the first month is onboarding to just run the stuff on your computer. Like it's crazy. And so, yeah, I mean, if the experience of your product as a video editing tool, right? If you force people to go download a thing to their computer and set all that up and then they get to use it, the drop-off is insane. Right. I mean, it's like 90% or something automated, if not more, you know, whereas when it's native in the browser, it's frictionless. And the actual AI augmentation then actually even picks up, you know, from there, right? So like there's an order of magnitude more complexity. You have to set up an environment locally for any of these things. And then there's an order of magnitude on top of that of actually knowing how to code or operate these things. And so like, if you can kind of collapse that full stack, that effectively, it seems like there's probably a good number of these plays. that could be run here where people that have been building stuff to be browser native by integrating really great agentic experiences into them can open up to a totally new market of people that'll find value in it. And even for the professionals, because they're like, oh wow, this is great. I can just punch in here, tell it to make me a video or make me a full stack web app to scaffold out, and then I'll pull it down locally. I mean, it's like, it's still valuable, but it just blows the lid off what you can do.

Yeah, it really helps that model is incredible for sharing as well. I mean, it's the amount of times in the past where I've experienced like, okay, it's done, but where can I use it? You know, that is just an absolute nightmare. You know, it's like, well, it's on my local computer. Okay, but how do I use it? You know, well, I've got to deploy to staging. Oh, God. You know, I felt that pain. Do you want to Do a little demo or sure.

Yeah, I was just thinking maybe I can show you how this thing works real quick. So it's pretty cool. So I'm gonna go and pull this up. So if you go to bolt.new, which I love the domain, it's just, it's like the simplest thing to remember, you know? So you go to bolt.new, we've got a free tier. And so one of the cool ones, this thing is probably one of the best tools in the world for actually building beautiful looking user interfaces. So hopefully the demo gods play nice with me here, but we can just kind of punch in anything that we would want to make. So like. If I say make me a music app that looks like Spotify, I'll just go ahead and hit enter. This is like a pretty unbounded request I'm giving this thing, right? What you see here, this kind of looks like ChatGPT or something like that until this happens. And so on the right, this is what I was talking about with the core technology we've been building. This is actually running a full operating system here inside of my browser. It's already booted. It's already installed the dependencies for this project. So right now the AI is just writing out the code for this thing. I can just type in commands like I would, you know, for those who are developers. I mean, you can, it's like a Unix compliant operating system we've built in WebAssembly that's booted inside the browser.

You made your own from the ground up? It's not like Ubuntu derived or anything like that?

No, we had to write it from the ground up. Right. And the reason being is if you want it to be, if you want it to be fast, if you want it to like boot in like 100 milliseconds, there are things that will let you take a Docker image and convert it to Wasm or whatever. But the image, the Wasm file ends up being like 100 megabytes or more. It runs 10 times slower.

What's WASM? Like, I guess how much do browsers sort of anticipate or how much were they built to enable this? I know like the video story of this, there's like, in our case, it's like there's WebGL. You can use that. It's not necessarily meant to do 30 frames a second, but it can do stuff.

Totally.

What was that like on the, on kind of creating a web container experience?

Hard. I mean, hard because yeah, like the thing with browsers is that they're very strange with like what APIs, as you know, from building on these things. It's not the sort of like really robust interfaces you typically got on your own computer if you were to build software there. And this is why you don't see a lot of these productivity tools that come to the web because you, if you want to do it right, you have to actually just start from scratch. And this is the same story of what happened with Figma. So back in like 2012, my co-founder and I actually had the good fortune of bumping into Dylan and becoming friends with him back then when he and Evan were starting Figma. And their first pitch for Figma was not a design tool. Like they were like, hey, we want to build a design tool. But what we have today is just this 3D ball dropping into water. Let me see if I can actually find that. It's like kind of iconic. Figma 3D ball demo. So this is the demo. So Evan Wallace is a co-founder of Figma. He made this demo of 3D, this ball you can bring into 3D water and see the actual ripples of it, right? This is back in 2012. And so this was, this is a game changer. Because you couldn't do this in browsers before, but WebGL just landed in browsers. WebAssembly or the predecessor had just landed in browsers. And that's what made this possible. And so their pitch was design could not have come to the browser before, but now it can. Because look at what you can do. We can certainly build a 2D rendering engine around this, around WebGL and WebAssembly, but we have to write it from scratch on top of these specific technologies. And that's what they spent the first year or 2 doing was just building a rendering engine That that Figma, the product could actually be built around, right? And so that for us was same deal when we went to build web container, which again, like you know, is this when you go to the code view here, this terminal, right? I mean, this is deceptively simple what you're looking at here, but we had to write something from scratch because if you want people expect a web page to load in a second. That means that the size of this operating system is going to have to be like two megabytes, maybe a megabyte, and it'll need to be it'll have to boot in like a hundred milliseconds. That is what we built here. And we had completely from the ground up, and it took us years. We've been working on this thing for like 5 years at this point. It'll be 6 this year, but just a classic, like deep technology play that enables this to boot so fast, right? So if I hit refresh, let's say there's something wrong with this. Like imagine if like Gmail breaks, how do you get, how do you like fix it? You hit the refresh button, right? That's the, again, the benefit of taking this sort of approach is if there was something wrong with that operating system, It just booted a brand new fresh one, installed dependencies, spun up the server, and boom, we're going to see the application in a second here that we just built. So that's like, if you compare this to anything else in the space, you're getting connected to a cloud VM. There's a lot of latency. If the thing gets broken, you have to go contact support and be like, hey, you better— you have to hope that they have good support, blah, blah, blah, all that sort of stuff.

Right.

That is fascinating. Now that we're here and we've got this thing generated, first of all, did it just generate these images on the fly as well? Are you including?

Yeah, it's smart. So it'll go grab images that it thinks are going to be relevant, right, for you. And so these are the ones it pulled to like go.

These are not like the real album covers, are they?

No, I don't think so. Everything that we're pulling is like, you know, royalty-free, da da da sort of stuff, or We have the applicable licenses, but yeah, it goes. It'll go and grab like good placeholders, and you can tell it to use other stuff if you want. But this is like zero shot, right? I mean, this is all I said was just make me a music app that looks like Spotify, and this is what it punched back, which is kind of incredible that it's this good just on the first shot of the thing. And so, like a lot of people, like I mentioned, like a lot of folks are you know in the Fortune 500, often they're not saying, "Hey, I want to build a full stack application from scratch." Da da da da. They're like working on specific UI, whether it's for like Chase's, you know, website for like checking your banking details, or it's like on Netflix, like the clicking the next, next in the series button or whatever. Right. And so this is like an incredible environment to just be like, hey, let me go hammer out some components that look gorgeous. But you can also continue to prompt on this thing. So like, what would be a good example? Maybe I guess doing an audio file, you wouldn't be able to hear it on the stream, but let's say, you know, I can just say like, make the play button work and the seek track bar. Let's see what it does. But you can just keep prompting it. You can just tell it like what you want it to do. And so you can, for example, like if we wanted to, you know, if we want to make an actual music streaming application or something with this, we could go and say, okay, here's the Spotify API, add OAuth and like, let me log in and You know, play it through my Spotify account. And it's smart enough to actually just go and be able to do that. And, you know, it's the sort of thing where you might get some errors back and you like, we have a fix error button you can click. Maybe they'll pop up if something here goes wrong. Or you can just go and debug it yourself if you're a developer or just Google it, et cetera. But it kind of, the sky's the limit with the sort of things that you can build with this thing. I can show some of the stuff folks have built that's like, you know, really sophisticated and full stack. So you can see here, the play button is working. It does say there's an error. It actually is using The HTML5 audio API to handle. So that's the error it throws. It says, you know, there's nothing to play. We need to give it an audio file. It kind of went beyond what I was expecting it to do here. So this is like, we actually have a tool that can actually play arbitrary audio files and this seek bar actually would work if we plugged it in and that sort of thing.

Yeah, I can imagine a Suno or a Udio. I don't know if those guys have APIs yet, but you're an API call away from generating your own music and kind of living a real hallucinated dream here.

I've seen people make stuff with— I think Suno might have one because there's a guy who made like a meditation app using Bolt and it goes to Suno and grabbed it. It says, you know, make me some music that's, you know, zen. And it has you like breathe in and breathe out with this. It's just crazy. I mean, it's like when he tweeted, I was like, you know, I looked at the market cap of Calm and it was like, I think it was like $3 billion or something. I was like, I have that, his app pinned on my phone now. I'm like, why? This is That's insane. Like, you know, he built that in like 10 minutes. It's wild.

Yeah, that is disruption might be coming sooner than some expect.

Totally. And just like I said, maybe some examples of stuff that folks have made. So this is actually made by a gal. She's a PM at a software banking company in Thailand. And so this is like her, she started this as her side project, but basically the idea with Viral Hooks, super cool idea. Is effectively you can come here and sign up and this product helps you. I don't know if you ever had the inclination to be like a viral TikToker or whatever. Yeah, I've never tried, but like, you gotta think about what it takes. Like you have to have like a good hook to keep people watching. Right. And so what she did with this is it actually like reverse engineers, you know, the scripts of what popular creators do to like make their hooks. And she made an AI agent that you kind of give it the content you want to talk about and then it'll actually like create viral hooks for your scripts. Right. And so like a week before Bolt came out, she actually listed this project on Upwork. And I think the quote she got was from like a Ukrainian developer. And it was, I want to say it was like $3K or $4K or something like that. And I think the timeline is it would take like 3 months or something in that range, which like is pretty reasonable, you know, kind of given the scope of the project we're talking here. And then the week after that, she, you know, Bolt came out and she signed up for our $50 a month plan. And she had the thing built and launched in 2 weeks, you know, with a full-time job. So like the ROI reduction there is crazy. I mean, it's like a 99% cost reduction. You know, it's a 10x faster delivery. And there's another case of this guy named Paul made this entire CRM using Bolt. And this has like an AI agent built into it. So I think I can zoom in here. So you can actually like, you know, I don't know if you ever use a CRM, these things suck. They're so boring to use. He has this AI agent built into this. So if you don't want to click through to, you know, do actions, hey, I met with this guy, can you log it? And it just does it, you know, like a pretty sophisticated application he made. And it was the same deal he spent. I think he spent like $200 or $300 on Bolt. The quote he got from an agency was $30 grand, was going to take 6 months. And he had this done, I think it was in a month for this one, which is, it's just like wild, you know? And so these are both like startups that have launched and are making money at this point, just like 2 tangible examples here. But yeah, I mean, I should mention both these folks are not technical. They're not coders. They made these things and completely without even having to tap developers to even help them finish it. Right. Which made incredible products here. This is the— I got kicked out. I'm on the free trial. I guess I'm logged in here, but I mean, this is real. It's like I should buy this. I should support Shield CRM. But anyways, this is kind of insane that you can actually That, you know, without any technical knowledge, you can build real products like this at this point, you know?

Yeah, it's pretty amazing. What does your pricing look like? Because you mentioned like a sort of monthly plan and then it sounded like there was sort of usage-based pricing as well.

Yeah, totally. So this is actually one of the interesting things that I think we were kind of the first to discover. A lot of people have followed suit because it makes sense and it works. So a lot of these like code gen tools, like GitHub Copilot or ChatGPT, they've had this thing where from the days of like, you know, where you pay like Netflix, you're like, oh, I should pay $20, kind of get like all you can eat access. But like, if you eat too much, like you have to like slow down, we're going to throttle you. And so what we ended up doing with Bolt is like, instead of like trying to cram it into $20, we're like, hey, you can just pay for as much inference as you need. And we gave people different plans. And so it starts at $20, it goes up to $200. Folks need even more than that. You can actually buy tokens or tokens, inference tokens. You can buy them as needed as well outside of your subscription. But you know, you can kind of pick what makes sense to you. And what we see people do is they come in, they try the free tier, they love it. They run out of tokens, they upgrade to the $20 tier. They're like, oh, this is good. This is, you know, building incredible stuff is totally worth $20. They burn through that. They keep upgrading, right? Because it's just, it, you know, provides so much value. I mean, just the, like, for an engineer, $7 to selling it for $9,000, like in that one example and like Yeah, these folks are saving 99% compared to going with a freelancer contracting firm or whatever. When people start doing that, they get to feel the math as they use the product. They just naturally upgrade to the higher tiers because like, this is totally worth the money, right? So that's for individuals. We also have team plans for organizations that are buying it for their employees and that sort of thing. But again, it's all based on the number of tokens that you're using per month.

I guess a couple of questions there. One is if I'm doing my math right, your per token price is lower than the Claude Sonnet 3.5 token price, which suggests you're probably not using either— you're counting on people to not use all their tokens in a significant way, or you're using different models.

It's just interesting.

When I was trying the product, I was like, I wonder what model they're using. So how are you thinking about whether— and in Cursor, for example, they do just— I can just choose my model, right?

Yeah.

So there's an interesting Kind of different approach there where you are not making it clear to the user what model, and you have sort of a pricing layer that is not fully transparent into, even though they can see their usage, but they don't know exactly where it's going. How are you thinking about that? And can you tell us anything about what models you in fact are using under the hood?

We're super open about it. So yeah, we use Claude 3.5 a lot. We're using other models too in various places. I appreciate the call out of like, hey, this is cheaper than Claude because people often are like, man, this is so expensive. Like, I'm just going to use Claude directly. We're like, go for it because it's going to be more expensive. It's like one of the benefits, you know, of, you know, I think top 3 or 4 or 5 or something customers, right, are upstream AI vendors is like we can negotiate volume discounting on this stuff. And so that's like one of the benefits of having a subscription-based model is that because we can project forward of like, hey, here's how much inference the user is effectively reserving, we can actually go and negotiate a They say, hey, we know that we certainly need this much inference, you know, in over the next months or whatever, right? So that's a huge advantage for us on a pricing perspective because we can, you know, price the thing aggressively. And one of the other kind of cool things about this is when people say, hey, like this, this is a lot of money or whatever. And some people are like, this is, this is so cheap. When you kind of understand the ROI, it's like, this is so cheap. For folks that are maybe just kind of learning how to build products, you're like, wow, this is a lot of money. It's like, yeah, Well, one, you probably need to kind of learn how to ramp up on how to best control these AI things. But 2 is you can actually run Bolt locally. So this is a pretty unique aspect of our product versus pretty much everything else out there in this space or whatever. When we launched Bolt, we actually launched an open source version of it. If you go to, I think it's bolt.diy, this kicks you to our official repo for this. And so you can actually run Bolt using any LLM. So you can, you know, choose the Gemini APIs, you can use OpenAI. This past week, DeepSeek landed in this. And so what's great is you can actually, this is kind of like our testing bed of, hey, what are the best models in the Bolt production application? What are the things that really show great promise, great results in our open source stuff? And then we pull that forward and build it into the product. You can just plug in your own API keys and use this locally, et cetera. You know, I think it's gotten pretty wildly popular because again, there's not a lot of products like good AI agents and certainly to the level of quality that we're talking here. Most of this stuff is kept closed source because I think what's your moat? I mean, like for us, we've been building the core technology of the dev environments for 7 years. So it's going to take time for anyone that wants to build something to the fidelity and speed and accuracy we've got. But you said from our point of view is like, there's only upside to put an open source version out there that people can build and fork on and improve. It's actually become a pretty popular thing that the AI labs use because they actually will go to bolt.diy to actually test out their new models to see, okay, well, how well does this perform in like an actually real world application? Because like a lot of these benchmarks for software engineering, the evals or whatever have you, it's like they're good to test against, but it's, you know, it's, you're kind of talking, you're not talking about a very dynamic test there, right? It's like a specific test case that it passes or fails or whatever have you. And so with our open source version of Bolt, they can actually come here and do things that are even like a bit more qualitative, like how good is the design that comes out of this stuff zero shot, right? And just how good is this an agentic experience of building a real application versus just You know, a to-do app that's not even styled, you know? So this is actually a very, like, I think one of the, you know, maybe counterintuitively, one of the big reasons that I think Bolt has kind of pulled away from a lot of the other stuff in the space is that there's a, and you see this with a lot of popular open source projects, like, you know, people end up kind of consolidating around the things that are open source that they can fork and use and modify their own needs. And that ends up being a tide that lifts all boats and especially like whatever products the company that's building the open source project are making. You know, we see a lot of people try Bolt DIY and then buy a Bolt subscription, still use Bolt DIY. Like, so, you know, it's just a very symbiotic and cool thing that we're doing here. Cause I don't see anyone else doing this.

I noticed the last commit was 9 minutes ago at the time that you loaded the page, which is— Couldn't have timed that better. So what exactly am I— I understand that when I go to the main web experience, all the code is loaded into my browser. I'm running this local container in the browser itself. What exactly am I downloading when I download DIY? And am I still ultimately using it in my browser or is it a different paradigm?

No, great question. Yeah. So what Bolt DIY does, it basically runs the open source First variant of Bolt.new just on your local machine. When Bolt.DIY is doing the code streaming and execution, it's still using web container inside of your browser to do that. Really, all you all Bolt DIY is is doing is letting you run that locally on your own device or on your own server or whatever have you, right? So and basically this is great if you want to have an offline experience running DeepSeek locally. You can actually use Bolt offline with Bolt DIY with DeepSeek locally. Connected directly in, et cetera. So we see a lot of like enterprises starting to pick up Bolt DIY to run behind their VPNs and use whatever inference they've got behind there, et cetera, et cetera. Right. But it's effectively just a way to host the web application of bolt.new. And it's designed to easily point at any inference provider.

Gotcha. Okay. Yeah, that's cool. It is. And I don't recall seeing anything quite like that. So that is, I guess Cursor in a way has something similar where you can sort of subscribe, or you can just use their fork thing with your own tokens or whatever. But it's also, it's always a local app. So it is definitely different too.

And it's closed source, which is, it's cool that they let you do that. But I think having it be open source, just kind of, a lot of people are interested in this stuff, but how do you actually contribute to something that actually has real adoption?

You know, like where you can actually see, hey, prompt templates and everything in there too. All the definitions of the happy paths. People can go study like how are you prompting it to make sure it's doing the Stripe integration correctly and all that kind of thing.

Yeah. We've got, let me see if I can find our, we have our entire system prompt and everything in this guy. And we have some stuff that's, you know, we're in the bolt.news side is, you know, we're not, we haven't backported and some stuff we just might not backport, but we actually do. We have been backporting a good amount of the stuff we are doing. Let me see. Where is that? It's been a while since I looked at this codebase. My job as CEO sadly keeps me out of our codebase for the most part. But I, somewhere in here we've got the entire system prompt in this thing. But yeah, which is, which is kind of cool. Oh, there we go. Get system prompt. Okay. So let's pull this thing up. So prompt/prompts. There we go. Yeah. So there it is. There's the whole shebang. This is like the main system prompt for us, you know, like how Bolt actually works under the hood. Right. It was pretty cool. I mean, and then there's others, there's other prompts that are kind of like chained and, you know, da da da and that sort of thing, but. This is crazy useful. I mean, this represented, you know, some months of work for us with really smart folks building that. And where else are you going to find that? You know, unless you like prompt leak one of the other providers or whatever, but it's like, this is forkable, runnable in the product. I imagine like, like people have made PRs to this prompt.

So you have, I'm seeing here you have, it looks like partial support for Python.

I didn't realize there was any support for Python. So it's like the Node side, I can download random dependencies. On the Python side, I have like a sort of limited Python. I can't download, I'm seeing here, I can't download third party, but I didn't realize there was any at all. So.

Yeah. Yeah.

Yeah.

We have some basic support for Python. So like the Node.js ecosystem has, you know, we've worked in that one for like half a decade to make pretty much all the major toolchains run in WebAssembly and that sort of thing. Python is not the beginning of the trailhead, but just, it's a couple steps down the trailhead of making everything work in Wasm. And so I believe if I actually go back here, I can probably in the terminal, let's see if we've got this enabled. If I like type Python, we should get back, I think the REPL or whatever. So we've got like, you know, a version of Python that's running in WebAssembly here that we can, you know, kind of execute Python code in. I think we have some basic, you know, standard libraries and stuff baked into this thing. Yeah, I know it's on our docket to like get pip added in. And I think for a lot of the use cases we're seeing though, it's when we were an IDE, it mattered a lot more to support like every language, you know? That was like our 10-year roadmap or whatever. Now that we're on, and we've always unabashedly been focused on web applications, like that's kind of been the point of, you know, it's like the key insight was like browsers don't have a way, you know, to build web apps, right? I mean, like the web should be able to build the web. That's like, you know, if you look at every other platform, like, you know, Mac has Xcode and Windows has Visual Studio. There's no tool like that built into browsers. And that was the impetus. And so we've always been focused on Node.js and the JavaScript-based ecosystem. But yeah, we've actually, so we got Python. I think it's a couple other ones too. Like, so the entire WordPress and PHP ecosystem now actually runs in WebAssembly too. So you can actually run WordPress in this thing. I think Laravel runs in it. And so I think that's like the number 2 ecosystem behind Node.js as far as compatibility is the PHP one in WebAssembly and web containers at this point. But I imagine, I think by the end of the decade, I think most of the major languages and ecosystems are going to be running in WebAssembly.

We'll just ask the superintelligence to handle that for us.

Totally, right? That's a lot of the issue right now is it's just, how do you get the engineering hours to kind of really drill in and make that happen? Yeah, agents.

Yeah. And as the market, I mean, it's another difference between developers and everybody else. Developers care what they use. My dad doesn't even want to know, you know, he just wants to see something work. And in the ideal state for him, he's never going to even consider the code or what language it's written in. Best product experience for him. He literally wouldn't be able to tell you at the end what language things were ultimately coded in.

Totally. Well, I think that's what's interesting about the intersection of where we're at versus, I think, you know, I, maybe Replit is somewhat-ish in this space. I think they lean a bit more developed, like heavy developing than we are, but we're kind of at this, like the perfect intersection of like providing a great service to developers and providing a great service to non-developers where, you know, especially because we made the core of this thing open source, people are contributing to it. People want to see more stuff working in it. Right. And developers, there's developers, they want Python to work in this. Like they want, there's Python developers like, I want Python. And we get this all the time. Like, I want Python apps. I want this. I want that. And so people are making pull requests and they're making this stuff work. And on the flip side of that upstream, and even what you see working in Bolt today is the result of the past 5 years of the toolchain that's running here is called Vite. That ecosystem said this running inside of WebAssembly and WebContainers is important to us because we want to be able to have these in browser environments. Let's make it a reality. And they commit to it. And that's what's making this possible. Right? Is like these, the developers care. And so it's kind of, it's this two-sided ecosystem where without developers caring, you can't enable all these people that you have never programmed before to actually leverage these tools. Right? And I think that's kind of cool is we're kind of right in the middle of both those where developers care and they love our product. So do non-developers. And so we're able to kind of make this magic happen where again, like you don't really see that happening in other products or tools or ecosystems, you know?

Yeah, that's cool. I'm learning a lot from that. I really had no idea how far the in-browser containerized world had come and just how many things you could do in it. Nor did I even realize that even from trying the app, which I definitely did, you know, spend some time trying to make something myself, but I didn't get that deep into the internals.

Good. Yes. I mean, that's the point. You know, anyone should be able to use this and be completely unaware. That means we did our job right.

What are some of the other kind of foundational technology pieces that you are tapping into? For example, you mentioned Stripe. You can see Supabase in the UI there. I saw a mention of Vercel AI SDK.

Oh, yeah.

Some of those are, I guess, fairly obvious choices at this point. Stripe has certainly emerged as a standard. But what would you, could you run down kind of the list of like the opinionated decisions that you've made and why?

Yeah. So we've got like, you know, if you're using, there's kind of one track that we're opinionated on. And this is really kind of more for people that are not developers. We want to have a smooth path where they're going to not run into a lot of errors. It's going to be really great. And even for developers that are just looking to quickly build a product or something, right? So kind of in that path, you know, it's like Vite and React, which we've been for the past 5, 6 years we've been supporting. And like I mentioned them before. So that's kind of your dev tooling and the framework or whatever. For auth and database and like webhooks and that sort of thing, Supabase provides us. You can click this connect to Supabase button. You can create a project or have you and spin up an actual database for this thing, et cetera. Hopefully, I don't know why this thing, maybe my internet's lagging. But so you can like have, you know, have a database with like auth, you know, a way to actually, you know, create rows, et cetera, with the Postgres database backing it. With that, you can actually plug in Stripe. You can accept billing, which you saw on the Chilled CRM site. So this is powered by Stripe, using it for the subscriptions there and that sort of thing. And the final thing that's kind of cool about Bolt, let me go refresh the page to get back to a fresh slate. This is the beautiful, wonderful thing is if something goes wrong, usually you can get back to a fresh slate. Maybe not. Maybe I might have Borked my dev account before we came on here. But kind of the cool thing about Bolt is that again, because we're running an operating system in the browser here, you know, like you mentioned this before, actually, I didn't actually answer your question. You're like, how do you actually deploy this somewhere? Right. Because that's like often a, you know, a challenge. Like, hey, you made something cool. Now, like, how do you actually get it onto a URL and, you know, do something useful with it and actually like have a domain? We actually have a built-in integration with Netlify. So you don't even have to sign into Netlify. To do this, you can. It's just in every Bolt project. You can just click this deploy button, and I'll flip back to the code view because this is cool. So this is actually running a production build again using my CPU. Normally, if like spin up some cloud, you know, CI box or whatever, built a production website, deployed it live on Netlify. That's the URL, and I can share this with you. And if I want to add my own domain right now, if I want to connect this to a Git repo or whatever. I can click on this link, which will actually take me to Netlify and attach to my account. So again, myspotifyclone.com, it points directly at this thing. And anytime I deploy here and out, so if I wanna make the backgrounds neon or something, we'll see what it does. As I make changes to this thing, it'll go ahead and update those. And once it's done making these changes and make sure it's good, I'm gonna actually be able to just hit the deploy button again. It'll run another build. It'll put it right back onto that URL. So if we had a production.com domain pointed at this thing, it would update live with that, right? So it completely removes the entire deployment part of the question for this experience, which again is like usually one that can be rather challenging to do.

So. Yeah, deployment is such a nightmare. I'm very excited about things that make deployment easy and Replit, which you mentioned, was One of the first things that I saw that kind of changed my paradigm there. But this is doing something similarly cool, which is—

And the Replit guys did a great job where like they've baked deployment into the product, right? Which is, I think for like certain types of apps is great. Like I think what's nice about us just having a partnership with an actual deployment platform, that's, that's kind of what they do as a business. It's really reliable. You can attach domains to it. You can actually build real products and teams around it, right? And so I think it's like, you know, and that's not to say that what, like having an in-house deployment solution, like what Replit's doing isn't useful. Because I think they've done a really good job there. But a lot of people want to actually host something that's got a real domain and that sort of thing. So I'm going to click kick off another deploy here. This is what it currently looks like for reference. We'll let this thing go ahead and do a production build again. So go ahead and do that. And if I go ahead and refresh, boom, you see our neon colors, right? So yeah, insanely simple to get this thing back live. But that's, I think that's probably like one of the most magic parts of the Bolt experience is just having a one-click way to get this thing live on a real prod URL.

Yeah, that's cool.

What's coming next?

I mean, candidate ideas that I would be interested in your takes on, obviously O3 Mini should be coming soon, allegedly going to be another significant jump in coding ability. Agents in general, of course, are like, you know, big buzzword. But when I've been doing this sort of AI accelerated app development, I've definitely noticed that a lot of my time is spent just copying and pasting stuff around. And even more is like testing the flow that I just had the thing code. So I'm starting to kind of wish for like, a cloud computer use to code it, or now we've got OpenAI Operator, which is obviously limited access at the moment, but I do pay the $200 a month, so I had the chance to use it. I kind of wonder, are you expecting to sort of create an AI user, an AI tester? Because that seems like it would be the next biggest chunk of time for me, probably, that would get taken out. If I could zoom out one level, And go from today, I go, okay, what is my feature that I want to do? I often take that to O1 Pro because again, I pay for everything and then have that do a sort of an analysis and kind of plan, make sure that my overall roadmap for a feature is good. I'll usually put my full codebase in there if it fits. And then it's like, okay, now I've got a step-by-step plan. Now I can take that to the coding agent. Most of my experience recently has been with Cursor. That usually works pretty well, but then I'm like, okay, did it work really well or not? I have to go find the edge cases. So I kind of wish I could zoom out one level up and be like, here's my thing, you go do it. And also you test it and bang on it 5 times and fix the errors that come up. I feel like I'm already often 5x faster to do things, maybe in some cases 10x faster than I used to be. And if I could do that, I feel like I would be like consistently more than 10x and maybe, you know, genuinely getting into like 20+ range for some scenarios.

Totally. I mean, I think the company that's kind of doing what you're describing is like Devin, right? Where I was talking with one of my buddies, Sean Wang, you might know him or you might have at least seen him on like Twitter or whatever. He's like really smart guy and he's currently, he's been doing a lot of stuff in the— yeah, Swix. Yeah. Yeah. Sorry. I should refer to him by the thing that people know him by. Yeah, yeah, I know. I like, I always call him Sean just because I met him in person first before online, I guess. Like everyone calls him Swyx, but awesome guy. And so he's like an angel in the company and a good friend of mine. And so, you know, sat down a couple of weeks ago and we were just kind of chatting about kind of this of like kind of the breakdown of different products in the AI software engineer space or how they're oriented. And I think at least my takeaway, and I think Sean would probably agree with it, I think was like. You know, I think the problem with things like Devin, which is not knocking their product, because I think for certain cases, I'm sure it's great. But I think the issue is when you kind of tell an agent to go and do something and it's going to do something that's like going to take a while, it's going to do a lot of things during that while, therefore it's going to spend a lot of inference and whatever during that while. A lot of things can just go wrong. And like, Depending on how, at what stage of the process things went wrong and kind of cascade. And then wrong can, doesn't necessarily mean, oh, an error happened, but it's like it got confused or it misinterpreted directions and da da da da da. And so I think that's kind of the challenge, candidly, for agents, I think is like, when you want to start baking stuff on and it's going to go and do a whole bunch of things, the odds of that collapsing increases the more steps you add into it. Because right now these things are just not, you know, they're just not the fidelity. They're just not the fidelity that you would need to really send the thing off into the woods to go and do a meaningfully sized set of tasks, right? It doesn't mean that it can't work in some capacity, but it's like, you know, on Bolt, right? Coming back to your earlier question, what's the success rate? And I think from what I understand from what the more longer running agentic things like Devin, The success rate is pretty low of like where people are like thumbs up. I'm super happy with what the result was, right? Whereas when you flip to something like Bolt, there's a lot more people, a lot more, which you get to the point where the ARR just continues to ramp because they're seeing immediate results. And if the thing does make a mistake, it didn't go off for 20 minutes burning inference to just make a chain of decisions that are from the root of not what you want or whatever, right? And so I think having kind of human in the loop where it's, you know, they're kind of guiding the thing and verifying that it's not screwing stuff up, et cetera, is right now I think where tangibly you can really squeeze an incredible amount of value out of it. And honestly, I'm a little hesitant. We're doing R&D on the kind of the longer running stuff, but it's like I'm a little hesitant to really try and pull off of that just because I think humans are just now and for the foreseeable are just going to be important part of the creation process, you know. So it's kind of longer answer your question. So as far as kind of adding some level of automated testing, there's certainly stuff that can be done around, hey, have the thing write unit tests up front, you know. So it's like as it's building, it's ensuring that it's aligning with that, right? But again, I think part of the trick is, okay, well, how do you write unit tests if the user's not technical? How do you ensure that those unit tests actually are like good, you know, that they're actually going to be representative of what the end user wanted? That's the big question I think around this stuff. That's kind of a longer answer, but that's kind of like my kind of current worldview on just, okay, how do you improve these things generally? And what are kind of the limitations that pragmatically and immediately we see? But we're investing kind of across the board in those areas, at least.

Yeah, I think that's really interesting. In preparing for this, I lined up 4 different products and basically tried to build the same app with all. And they were Bolt, Replit, which I've had the most experience with, Devin, and Lovable. And I would say Devin definitely stood out as being the most different experience from the others in terms of just the paradigm. And it is for the reason that we're just discussing, where it sort of just keeps going. And I feel like I do want that. But I don't want to watch it. And at least as it was at the time that I tried it, which was 10 days ago or whatever, so these things are changing fast. It was with the other 3 products, when I came back, literally just rotating through them and being like, what's the status of this one? What's my next instruction? Tab. And so I'm like the outer loop agent, and each one is kind of doing its inner loop. What I found was a little weird with the Devin experience was like, I didn't know where I was when I came back. So if I had watched it, I would have known where I was, but I didn't want to watch it. Of course, I want to do other things. That's one of the big promises of this. It does feel to me like there is a way to solve that. If you imagine a good intern or junior person who's helping you with a project like this, the piece that I feel is kind of missing— I do want them to take that initiative. I do want you to test it before you bring it to me. So that's definitely an expectation for a human developer I'm working with, right? Like, don't bring it back to me not even having tried the happy path. I can expect that there could be some edge cases that you haven't sanded down, but if you haven't been down the fairway and confirmed that it works, you're not doing your job. At the same time, you know, I want like a summary of that. I want to kind of know, not in a, like, I have to go back and read through your experiment logs, but I need you to tell me like, this is where I'm at. I did this, I tested it this way, confirmed this is working. working? Got a question here. And that sort of interaction layer, I don't think has been nailed. But I do think I want that several extra turns. But I haven't seen anything yet that sort of brings me that human-like experience of like, here's kind of the update, boss, on everything that happened since last time you were here. And they'd almost need to trigger that on refocusing of the browser tab, really, or some sort of signal that now is the time when the user's back for an update. Because I was coming in and it was just kind of midstream and it's working and I'm like, I don't know where you are, where you've been. But I do think that will get, with time, people will improve that. And I do think I'm definitely willing to wait longer and pay more inference tokens if I can get just bigger chunks of things done.

It's definitely going to happen, right? I mean, I think it's, and that's kind of the thing that we kicked off with the pricing model where it's like you can buy more. That was a result of, I mean, Sont 3.5 basically has gotten AI coding to the point where it's good enough where the more money you kind of put into it, you can actually have some realistic expectation of value that it's going to actually be able to give you back on it. Right. And that's, I mean, before that, I mean, it was, that was not the case, like with the previous kind of frontier models. Like we tried building Bolt a year ago, like in February of 24, with the frontier models at that time, and they just couldn't do it. Like it just the code was too unreliable. The output was you know the design output was ugly if it even worked. I think as these things just improve like 100%, like I mean I want that too. If I get where I if I can because I do this all the time with my own team where I'm like hey can you go ship da da da you know and they and and they're they're brilliant folks and they. And, you know, so I've worked with them for a while. So we have, you know, like they kind of have a sense of what I'm looking for or whatever. And they'll come back with a, hey, here's kind of where I'm at in it or whatever. But if you can deliver on that, oh my gosh. Yeah. I mean, that's worth every penny and way more actually. Right. And I think the trick is, is really just the accuracy and the user experience. I don't think we're far. I feel like we're probably a model or 2 release away where the fidelity is at a point where you can meaningfully start doing that for At least some types of workloads. You can have longer running agentic processes that you can actually trust to actually do what you want them to do. I don't think it's far, but it's an important part. I think it's definitely like, there's a lot of value, I think, that'll be created from that end of things, you know?

Yeah, it's a fine, it's a tricky balance for you and all these people taking different approaches to this because it's like, to varying degrees, and it sounds like there was a time when you really needed to turn up some business metrics. But everybody wants to deliver value to customers and grow today and have momentum. And you want that positive feedback that's going to make everything better, including hiring and just whatever. So you need to be sort of in the sweet spot, but you also need to be getting ahead because we know that the sweet spot is definitely moving. That's definitely been a challenge that I've experienced again firsthand. It's like, how do you do both? I don't know. That actually might be a Great closing question. That's about all the questions I had, but I would be interested to hear how you think about balancing the today versus tomorrow. And then you can throw in anything else you want to. If you want to put a bad signal out for hiring purposes or anything like that, welcome that too.

Yeah, it's a good question. I mean, I think we're pretty laser focused on just making our AI agent incredible today. And we've got irons in the fire on a handful of kind of R&D stuff, but I mean, I think it's, you know, there's a very clear line of sight for our product being able to like enabling folks to build incredible software. It's already happening today. And, you know, it just keeps getting better, right? Even with the current state of the models. And so I think that's like primarily where our focus is. And there's a part of this too where like there's kind of, there's just tsunami waves that keep hitting every 6 to 12 months with these models. And there were some products that were in this space. You know, I think there's a couple of them like, you know, like Replit and I mean, Replit v0 and Lovable. Lovable had like rebranded, relaunched or whatever. But like all these guys were kind of around before we, before Bolt existed 6 months ago or 9 months ago or whatever. And when Sonnet 3.5 came out, they had those product experiences. They had to completely reinvent them because all the work they were doing on those agents for previous models just didn't matter anymore. And in some cases, they just, I mean, they straight up pivoted their product offerings, right? So I kind of look at that and I look towards the future and it's like, how do you ride tsunami waves into the shore and then paddle back out and catch the next one versus getting wiped out by it, right? I think that's kind of, it's a delicate balance, just like pro surfers. I mean, there's, you know, you have to, it's not an easy thing to do. It kind of takes having a realistic perspective of, hey, what are the, what's the probabilities of how this is going to land and what the next one could be and aligning yourself to catch the thing. Right. And sometimes you just can't, of course. But so I think, I think that that's kind of, that's kind of how internally we kind of view that, how we hedge the bets here as we look towards the future, just because we've kind of seen the result of, you know, one or two of these things at this point and how that's kind of transformed how people's products were oriented. So we're pretty open-minded about what'll happen. So yeah, and to that end, yeah, like we're hiring. Yes, we just announced we raised a Series B like a week ago. So we just raised $105.5 million and we are looking to aggressively expand our team. We've scaled to tens of millions of dollars of revenue and we have like over 2 million registered users. We have a team of 20. Severely, severely understaffed for the demand we are seeing. I think last time I checked, we have, I don't know, like 50,000, 60,000 customers, something like that active. So we are hiring aggressively. So if you go to stackblitz.com/careers, we'd love to hear from you. I think we're working on some pretty cool stuff and anyone interested in AI and the web and just enabling both developers and people who've never coded in their life to build great software. We'd love to hear from you and work with you.

Cool. Well, this has been excellent. I really appreciate the time and the product demo and some of the deep tech stuff that I didn't know previously. And you guys are on an unbelievable trajectory. So definitely check out— what was the careers page again? It's bolt.new.

Yeah, if you go to bolt.new, there's a link at the top that says we're hiring, so you can click that. Or if you just go to stackblitz.com/careers, careers, that's like the direct link to the thing.

Alrighty, cool. Again, this has been amazing. Eric Simons, founder and CEO at StackBlitz, makers of Bolt.new, $20 million ARR in just the first 8 weeks, $100 million raised, and an exciting future in front of you guys.

Yeah, thanks for having me.

Thank you for being part of the Cognitive Revolution.

It is both energizing and enlightening to hear why people listen and learn what they value about the show. So please don't hesitate to reach out via email at tcr@turpentine.co Or you can DM me on the social media platform of your choice.