Jay V is the founder and CEO of Opencode, an open-source alternative to Claude Code that works with any model you want. It's one of the fastest-growing products in AI: 13 million monthly active users, 20X growth this year, and more tokens processed daily than all of OpenRouter. But the overnight success took 16 years, one legal entity, and nine YC applications.
In this episode of the Lightcone, Jay explains how Anthropic's attempt to block Opencode accidentally fueled its rise, how 16 years of near-misses prepared him to catch lightning in a bottle, and why most of the world still hasn't experienced the magic of a coding agent. Chapters:
00:44 — OpenCode's Explosive Growth 01:16 — 20x Growth, 13M Users, and 7 Trillion Tokens 03:39 — The Anthropic Controversy That Changed Everything 05:43 — Bringing AI Coding Agents to the World 06:39 — When Open Source Models Became Good Enough 08:56 — What Millions of Developers Are Actually Using 13:31 — Why OpenCode Is Huge Outside the US 15:27 — Why Fortune 500 Companies Choose OpenCode 16:36 — The Economics of AI Tokens 20:02 — How Enterprises Are Using Coding Agents 22:58 — AI's New Unit Economics 24:56 — Why Model Choice Matters 29:55 — The Product Decisions Behind OpenCode 34:21 — A 16-Year Overnight Success 41:16 — Why Jay Never Gave Up
AI Generated·May contain errors
Video Summary
AI Generated
OpenCode is a rapidly growing AI coding agent platform that offers a model-neutral alternative to closed-source tools. By supporting a wide array of open-weight models and providing flexible pricing, it has achieved massive global adoption among individual developers and Fortune 500 companies, particularly in regions where premium subscriptions are cost-prohibitive.
Most people in the world still haven't experienced the magic of a coding agent.
This is just an unprecedented market, like the market for intelligence has not existed before.
Everybody should be thinking in a positive, some very high mentality.
It's huge in developing countries, like Indonesia is 4% of your traffic, Brazil is 5% of your
traffic. Places like Vietnam, you know, like places where a $200 a month cloud code subscription is
like very expensive. You really know you have product market fit when like enterprises are
bugging you to sign the security agreement so they can use your product.
Please do this because I don't know who you guys are, but a bunch of us are using this.
We want, you know, everybody in the world to have that aha moment with a coding agent.
Welcome back to another episode of the Lycome. Gary's out traveling today and we'll be back next
episode. Our guest today is JV, founder and CEO of OpenCode, an open source alternative to cloud
code that works with any model you want. OpenCode has been growing at an astounding rate this year.
They're now at 4.6 million weekly active users, which is actually pretty close to Codex's numbers.
Today, we're going to talk about what's driving their wild growth and also Jay's winding road
to get here since the company went through YC back in 2021. Jay, thanks so much for being here.
Thank you. Thank you for having me.
Why don't we just start with kind of like the crazy scale you guys are at. Maybe tell us about
any stats you can share with us.
Yeah. Yeah. I mean, you mentioned the weekly actives are monthly actives.
I think we ended June with around 13 million or so.
And that's around a 20x increase since the beginning of the year.
We also recently started processing around 7 trillion tokens per day.
For context, the open router does a total of around 6 trillion.
I think, again, sort of beginning of the year, we're probably at around 300 billion or so.
And then in terms of sort of our revenue off of our subscription product,
and if you were to pay per token with our inference and you took, let's say,
June's data and extrapolated for the year, that would be around 31 to 33 million or so.
And if you took last week's data and extrapolated for the year, that's around
38 to almost 40 million. And that's the inference part of our business.
So the way we sort of make money, we had launched that, call it,
end of September, early October last year. So about eight months
to get into around 40 million or so. I guess to sort of round out the numbers,
our subscribers, so these are people that pay for a monthly subscription with open code.
We launched that product early March, I think end of February,
and that's grown to around 160,000 monthly subscribers.
Yeah. And around that, that accounts for about 18 million of sort of the annualized revenue.
I saw a tweet from, I think he is Thibaut, I think he's a lead engineer,
at least one of the main engineers on Codex, saying that something like, I guess, 5%
of all Codex subscribers choose OpenCode as the main harness to actually use the underlying API.
Yeah. So Codex officially supported OpenCode. What that basically means is that you can use
Codex's subscription in OpenCode and a bunch of their users use OpenCode directly
to take advantage of their subscription plan.
And I think they did that right after some of the back and forth you had,
maybe with Anthropic and Cloud Code. Tell us about what happened and how that seemed
like it really fueled your growth as an inflection point for you guys.
Again, to sort of contextualize this, we were at around 650,000 monthly active users to begin the
year. And the first week of January, we started to sort of hear some rumblings around Anthropic
trying to clamp down on people using OpenCode, but using Cloud Code subscriptions on there.
And this was a very sort of common way to kind of use the Cloud Code subscription. And the way I
think that sort of blocked it, or they were trying to block it, was if the system prompt mentioned
literally the word OpenCode, they would sort of reject the request. From our perspective,
that sort of makes sense. They're sort of subsidizing usage. That's kind of what they
want to do. But of course, a lot of users weren't happy. And when they had kind of done that,
what it inadvertently did was it put OpenCode and Cloud Code on the same sort of pedestal.
It like equated the two products in some ways. And even for the people that weren't using OpenCode
at the time, you know, they sort of took notice of the fact that Cloud Code is taking that kind
of an action against OpenCode. You got new users because people
heard about you for the first time, and they're like, oh, Cloud Code's banning this thing,
or clamping down on this thing. Yeah, or that it is worth looking into,
that it's not just one of the other dozen or so coding agents out there.
It's funny how often this happens in startups. Same thing happened with Instacart. When Amazon
bought Whole Foods, it was like, oh, this is the death of Instacart. And the death of Instacart
became this meme. But the meme actually just drove all the grocers to check out what Instacart was.
And they just went through this explosive growth of signing up every grocer in America.
So it seems like actually a lot of your growth is global, across the world. Tell us a bit about that.
Yeah, so the premise of the product is that most people in the world still haven't experienced the
magic of a coding agent. And it's been almost a year, and I'm sure it's sort of hard to remember
maybe for you guys as well. But the first time you had this experience, it's a magical experience.
And when we had felt that for ourselves, we sort of recognized that, you know, how important that
moment is in sort of tech history, I guess. It comes along once every sort of generation or so.
And the way we sort of looked at that was, let's take that, let's take that to as many people in
the world as possible, you know, have them sort of experience something similar. Because
the frontier models and the frontier labs charge so much per token that it's going to be hard for
a lot of people across the globe to have that experience. And we wanted to make sure
they had that with us in some ways.
I guess it was at a point where literally, like, early on, there was sort of like seemed
like there was a big gap between the open source models and the frontier models.
Is that true? Kind of when you were first launching the product?
Yeah, for sure. I think when we had first launched, it was mostly, hey, you're using
your cloud code subscription with cloud code, come try that with with open code.
And then and so this was back in June of last year, and by about August, September or so we
started to see the first crop of open source models. And you had the sense that like, oh,
there may be six months behind, you know, and of course, there's always been sort of a gap between
them. But that was sort of the first point when people are like, there's the GLMs of the world,
the Kimi's of the world, the minimaxes of the world, and it seems like there is now an
alternative. And, and as that started to happen, that would trigger a wave of users coming in
trying out open code, because that was probably the only way you could try out these multiple
models. And, and as that gap started to shrink, or the fact that the open weight models became
good enough for real work, is when it sort of became viable to use open code with them.
Yeah, I think I remember you, maybe a few months back, you were saying that,
let me get this right, that even, even though the open source models are obviously
cheaper to use through open code, you still saw more usage from the leading frontier
model, except was it when Kimi 2.5 came out? Yeah, that was the first time that it was equivalent,
or it flipped. Yeah, that's exactly it. I think it was like, probably 2.4. I forget the sort of
model. But, but yeah, this was, this was February of this year, where for a four week span, and
said never happened in our data before. And I think we're sort of fortunate to be able to
see this global usage. And so a lot of times we see the comparison of, you know, these open source
models versus some of the frontier ones. And we had noticed for the first time that a bunch of
users were just using Kimi way more than they were using the Anthropic models. It was sort of
Sonnet plus Opus at the time together. And that's the point when we were like, oh, I think we should
launch a subscription product, because now maybe these models actually do make sense for real work.
So speaking of that, like you guys have this incredibly unique insight, like probably the only,
you're the most, you have the best data on just how these models are being used by engineers across
the whole world. And you released a bunch of this data. So maybe we could just like,
look through some of it and pluck out some more interesting insights.
Yeah. So this is, you know, you can go to opencode.ai slash data. I think we started to
publish this about a month ago or so. This is basically taking all of the usage on OpenCodeGo,
which is our subscription plan, where you pay $10 to be able to use any of these open source models.
And this breakdown specifically is by token volume per day across the different models. So
what we sort of see here is that DeepSeek Flash is the one that is used a lot. And there's some
sort of details here. I can kind of go into why that is sort of the case. But if you just sort of
look at the top three, we're seeing sort of the two DeepSeeks plus GLM. And you can kind of see
all the hype that GLM has been getting sort of lately being sort of reflected here in these
charts. Which the data says otherwise, as opposed to all the Twitter chatter about the
GLM taking over DeepSeek. This is telling a different story.
Yeah. Yeah, it is. I can show you a different breakdown here. So this is by unique users. And
this was the thing that I heard you were sort of alluding to. We get to see actual usage data for
each of the users, as opposed to with maybe like an open router where you're seeing it aggregated
across a bunch of services or other products even that are sort of internally using it. In this case,
it's an, you know, each one of these is sort of an actual user. But yeah, what's sort of
fascinating is if we look at the market share graph, so this is breaking down for each of these
labs, the amount of token volume they're doing per day, you know, comparing that sort of across
them, you can kind of see the DeepSeek one dip around the time GLM sort of comes out. But it
seems to sort of bounce back up after. And we have sort of some theories around why that's
sort of the case, but that's sort of an interesting fact. And then if I go back up to the
users one, this is also kind of fascinating in that it might be a little bit hard to see here,
but if you look at the sort of top three unique users per model, you've got Flash at sort of
38k and then there is DeepSeek Pro at 31k and GLM 5.2 at close to, you know, 30k as well.
And that's interesting because GLM is sort of on par with one of the DeepSeek models,
but the fact that there are two of them makes it a little bit different. I'll sort of caveat
this by saying that DeepSeek Flash, being as cheap as it is, allows a lot of users to
extend how much they can use a coding agent, because as they get closer to, let's say,
their daily or weekly limits, they can switch over to one of these very cheap models, in this case,
DeepSeek Flash, so to get the rest of their work done. Again, this is very different from the way
we sort of think about coding agents and LLMs here in the Valley and SF in the West in general.
What are you seeing? Yes, I mean, we definitely are at the other extreme end of where it's sort of
like token maxing. But for the users you see, which to be fair, it does seem like there's
a general vibe shift, especially in the enterprise world towards like more token budgeting. What do
you see? Is it as simple as people, once they approach their usage limits, they switch over
to one of these models or is there more going on? Yeah, there's a few different things. I think
people do try and optimize for things. One of the reasons why originally Kimi had sort of taken off
was it was being hosted in a way that the tokens per second was a lot higher than what you would
get out of even an Opus. And so it was just a drastically faster model. It felt like you were
working almost in real time. And some of these models tend to exhibit those qualities, which
makes it, you know, characteristically a little bit different from using some of the frontier ones,
for example. So there's a little bit of that, but yeah, cost is obviously a big driver.
And then the other one that pops up every once in a while is, you know, people sort of get a feel
that GLM 5.0, for example, is better at front end design as compared to some of the other models.
And so that ends up sort of driving some usage as well. You also have a really interesting breakdown
by Jio to show like where the users are. Yeah. So who are your users? Where are they coming from?
Yeah. So again, some sort of context here is that, you know, we had launched the OpenCode Go
plan to be able to serve the sort of global audience. And you can kind of see that with
sort of China being kind of number one at 17%. That's crazy. I feel like you're probably the
only YC company in history that has meaningful usage in China. It's also fascinating because a
lot of these models are Chinese. So, you know, in their situation, they're trying to use the
ones that are being built in their country. And OpenCode kind of gives them the choice to be able
to do that. So that's sort of interesting as well. I think the US one is actually interesting to us
because when we had built this plan originally, we weren't thinking about the US. We weren't
thinking about the States because, you know, as we're sort of saying, you know, people here just
throw money at it. But then, no, it turns out it's growing really well in the States as well.
And maybe, yeah, that speaks to the sort of vibe shift of like, maybe you should be a little bit
more conscious with the tokens. But then there's the other side of this where people want to use
some of these. So when GLM 512 was getting popular, a lot of people are trying out our subscription
plan because it's one of the options to sort of do that. So because it's so much cheaper, it's huge
in developing countries like Indonesia is 4% of your traffic, Brazil is 5% of your traffic,
places like Vietnam, you know, like places where a $200 a month cloud code subscription is like
very expensive. So that makes sense that, you know, sure. But what you were telling me earlier
was that in addition to that, there's a lot of like large US companies that have basically
unlimited budgets for tokens that are also using OpenCode. Can you talk about that and why,
like who's using you and how come those people are using you? Yeah, this is what we had seen
early on before some of these open source models even sort of took off is that a lot of companies
would start using OpenCode because they didn't want to be locked into using a specific model
or a specific harness. So, you know, some users just wanted more choice and this was a good
neutral option for them that allowed them the flexibility in the future to switch to whatever
they sort of wanted to. And I think you had a crazy stat, it was something like a dozen of the
top very forward fortune 500 companies are using you and have a significant footprint.
Yeah, it's funny, we get DMs, we get emails sort of internally about, hey, you know, XYZ company
here, we're got a few thousand people using OpenCode now, please don't share this publicly.
But I think most of it what's sort of going on is like, yeah, there's a bunch of choice there.
And we can probably talk about this later. But we're very intentional with our product design,
we want something that everybody uses every single day, and we hold that bar fairly high.
And in those instances, I think that's what's sort of resonating with people,
as opposed to the cheaper tokens. I'm very curious on a slightly different topic.
There's been a shift for all these companies like you in terms of the AI token economics.
Because in the old world of companies, other B2C or B2B companies, there was a lot of a
CAC that used to be based on ads. And now the equation is different is based on token to acquire
users. They're also even more weird. There's this thing that you're describing where there's some
whales that pay for a lot of it at some point. And there might be a lot of churn, but it doesn't
matter. Because as long as you have the power users and experts really using it, they convert
these large orgs. And I think the big labs can subsidize that, right? Which is what effectively
ClockGoat and Codex have done, they can subsidize it. But you have a magic formula to skip all this.
The broader context here is that for you to use AI, and especially these coding agents,
because of the amount of tokens they use, to use them well, you have to really sort of understand
them. And this is the experts thing you're sort of talking about. And to get there is fairly
expensive from a per token perspective. Token maxing is expensive.
Right. It's very expensive. And that is a chasm that is very hard for a lot of people, a lot of
companies to cross. And so what the anthropics and the open AIs of the world do is they subsidize it
so that people are able to cross that. And then yes, like the whale's idea here, a certain
percentage of them cross it, get to that point, are spending the crazy amounts that you sort of see.
And then it makes sense. The entire sort of funnel then sort of makes sense.
But when we had sort of approached this, we had thought about it from a product perspective,
where it was, you know, we sort of talked about, we want, you know, everybody in the world to have
that aha moment with a coding agent. So that's sort of our free tier. And then because the open
source models were now cheap enough and good enough for real work, you want a subscription
plan that allows them to do real work with it. And that is sort of the thing that allows somebody to
buy into, OK, now I can justify spending so much more to potentially redo some of the processes
within my company to take advantage of these coding agents. And that's when hopefully, you
sort of turn into whales. And that's what you're seeing, like you're seeing people come in through
the free tier to try it out and then become advocates to be like, oh, yeah, like we should
adopt this at our like 1,400, 500 company. Yeah. I mean, it's to the point that we'll,
you know, in sort of the older sort of SaaS enterprise world, you would have this procurement
process that a lot of them sort of go through where, you know, somebody sort of rejoin, you
have this whole dance that they do. In our case, the inbounds that we get are typically just like,
hey, there are a bunch of people at this company, at our company using you guys. Can you fill out
the security questionnaire? And we're just like, oh, first off, I didn't know. I didn't know we had
users there. But secondarily, give us a second. You really know you have product market fit when
like enterprises are bugging you to sign the security agreement so they can use your product.
Please do this because I don't know who you guys are, but a bunch of us are using this. And so
it is a little bit different now. Yeah. Once you're through the procurement and admin side
of things, what are the enterprises asking you for? Are they trying to pull the product in a
different direction? Because that often tends to be something that open source companies have to
think through and be careful about. What's interesting here, I think, is
these coding agents are at the core of how an LLM does work. And so a lot of times when we
get these enterprises sort of reaching out to us, it's because they're trying to figure out
where else they can use it. There's the obvious one. Yes, we've got a bunch of developers at our
company that are using open code. Let's just figure out how we can officially use it. And
then on the flip side, it is, oh, there's some non-technical people that would want to be able
to use this as well. And then, you know, secondarily, there's this. Our product is
probably going to be using a coding agent as a part of its core loop. Can we sort of use it there?
So we get some sort of pull there. The other bit of pull that we see is mostly around just
managing tokens a little bit, but being like, hey, there's certain organizations within our company
that don't need the frontier models. Can we sort of limit access there or have some more creative
ways of managing token spend? And we see pull there. And so there's some sort of questions
around that. The strange one we had gotten recently was somebody wanted to be able to,
you know, mostly just have really good visibility of exactly what everybody is doing at the company.
And then that sort of gets into questions of like, you know, is that something we want to build?
Didn't RAMP use you in sort of an interesting way?
Yeah, I think RAMP was very sort of forward thinking. They had published a blog post,
I think this was in December of last year, but they had reached out prior to that where a team
within RAMP had kind of built this Slack bot that was essentially running OpenCode behind the scenes.
And it was just sort of incredible to see. It was mind-blowing partly because we hadn't even
done that yet internally. And they were showing off a use case that was definitely pointing
towards the future. What does that mean exactly? I think it can be hard for people to get their
head around because they think of you as like an open source flawed code. So what does that mean
that their Slack bot was running on OpenCode? Yeah, so you can think of OpenCode as a
two-part product. There is the UI and the application part that you sort of see and that
you interact with. But then there is the agent loop, the thing that's actually doing work while
calling the LLM. And that is sort of behind the scenes. That's a little bit of like, we call it
the server. That server can be embedded separately from the UI. And so in this case,
they were embedding that and running their Slack bot off of that.
YC's next batch is now taking applications. Got a startup in you? Apply at ycombinator.com
slash apply. It's never too early and filling out the app will level up your idea. Okay,
back to the video. Can you tell us a bit about sort of these numbers and how the
unit economics work? Because there was a shocking stat that was mentioned in Dylan Patel's podcast
that Anthropic is profitable and by huge margin. In Q2, they are on track to be doing 50 billion
annualized revenue and around 70% margin. But they got there before the previous year was
not profitable and way less. And they crossed this chasm, which sounds like where you're heading,
but you don't have to subsidize it, which is... Yeah, I mean, we do subsidize a little bit,
the subscription plan that we kind of have. And you have a free tier too.
And we have a free tier, yeah. And I think that's the CAC part that you were sort of talking about
early on where... The new ads is rather than ads, the CAC is rather than paying for ads,
is paying for tokens. Yeah, it's because that's how people sort of experience that kind of magic
moment. And that's the way we sort of get them into using the product, understanding what a
for a lot of people. And I think the part here in terms of the unit economics that kind of works
out is if you're actually paying per token there in the case of Anthropic and in the case of how
we sort of operate as well, we're able to get, at least in our scenario, we're able to get volume
discounts because of the amount of tokens that we sort of serve. And so when you pay per token,
that effectively turns into our margin. Whereas when you're subsidizing, yeah, obviously you're
sort of eating the cost there or in the case of the free tier, yeah, you're eating the cost as well.
But you were talking about this before, as you start to get more and more of these whales,
those whales are paying per token and directly feeding into your margins.
Yeah, the discounts you're able to get by sort of aggregating the tokens is interesting because
I mean, it's something we've talked a lot about over the last year in particular. It's where's,
I mean, everybody in the valley is at this point. So where's the value going to accrue? Will it be
the frontier models are going to make all of the money and everything at the app player is left for
dust or will it go the other way? How have you thought about that? Because yeah, you're in an
interesting spot because you actually really do own the relationship with your end user and you're
sort of effectively making it easy for them to pick and choose the models that they want to run
with. So just what are your thoughts on where this all plays out and how it will hopefully play
out in a good way for OpenCode? Yeah, it feels like a little bit like a marketplace where a user
is able to sort of make the choice of the model that they kind of want to use and different models,
different attributes, different cost characteristics. And our claim here is, look,
we want to showcase that diversity as well as sort of possible. And that also creates an
environment where the labs are aware of each other and that competition ends up being good
for the consumer in this case. Whereas the flip side is if you're locked into a specific vendor,
then you don't benefit from the sort of competition that would otherwise sort of come
with it. And you're likely helping their, maybe their margins in some ways. Yeah, I kind of feel
like your growth is a pretty decent proxy for the fact that the choices only improved over time,
right? That's exactly it. Yeah. Yeah. I think every, we could probably track back to sort of
our bump in monthly active users down to some sort of bump in the open source model market. And
the way we sort of think about this is that it's not that we're picking a winner in terms of a
model lab. We're just betting the field. We just think the rest of the field is going to do well.
The next logical conclusion of this is that models are becoming commoditized utilities.
Yeah. Yeah. I think, I think what's sort of interesting here is that the market is so large
that it is hard to imagine people not, or model labs not picking off niches and chunks of their
own in that they're specializing for specific areas or specific characteristics. Like in our
case, when we sort of see some of the data that we were looking at before, you've got obviously
the frontier labs, you know, we sort of know them well, but when we see the success of DeepSeek,
it's very clear that they have picked the cost part of the quality cost performance sort of
axes. And then they're basically saying, look, we want to be very, very good at that part.
And, you know, it's hard not to imagine that happening across the board, across all these
characteristics. Yeah. It feels like if you truly believe the sales pitch of the labs themselves
make, which is, this is just an unprecedented market, like the market for intelligence has
not existed before. Everybody should be thinking in a positive, some very high mentality, in which
case they should really want you to grow and succeed because you'll end up just being like
a huge customer for all of them. Yeah. I think that that's sort of true now with these open
source models. We're the largest customer for most of them. You're the largest customer for
most of the open source models. Yeah. Yeah. Just in terms of the token volume, I think the amount
that we do. Yeah. Wow. So that means that you guys must be sort of like locked in this like
symbiotic relationship now where like you both need each other for this machine to work. Yeah.
The other half for us is the ecosystem, right? So we look at the open source ecosystem as a
whole and we're going, look, we need to make this entire thing sort of work. And again,
with all the talk of sort of open source models lately, that's essentially our pitch.
Since you're the largest driver of most of the open source model companies, you must
have this incredible like insight into like the GPU market and where all this inference is
actually happening because you're the ones driving the inference. Are you seeing anything
interesting in the GPU market? Where's all this open code power compute happening?
Yeah. So we rent GPUs. We work with providers that provide just straight inference. We work
with the model labs themselves. But one thing that we started to notice that was sort of
interesting at some point because of our global usage was that the peaks and troughs over the
course of a day for GPU utilization wasn't that far off for us. Again, given the fact that like,
you know, when sort of the East is sort of working, you know, maybe the West is sort of asleep,
but when the West is working, the East is sort of, and so as a result, we have a reasonably
stable 24 hour GPU cycle, which allows for pretty good utilization. And it helps sort of the unit
economics for us in running these models a little bit more efficiently. And that ends up being a
competitive advantage when we think about some of our counterparts that maybe just serve one part
of the world. Do you think it's just such an interesting spot to be in? Like, do you think
there are like specific product choices or design decisions you made when you were first launching
the product that have led to just like quite like this sort of like, the fact that you're
growing and winning so much? Yeah, it's funny, you know, the name OpenCode like literally comes
from that. I think we've done a similar project in the past. It was called OpenNext. And the idea
was, when you've got a dominant or in this case, two dominant players in the market,
the rest of the market coalesces around an open alternative. And picking that position ends up
being really valuable. Because if you pick it, it's very hard for somebody else to displace you.
And if it's open, you should try and become the default as quickly as possible. So when we had
launched, you know, the name was was was a very deliberate choice. The fact that we wanted to
support even even at the time of launch, we said we we claimed that we supported 70 plus models and
providers. Just to make that happen, we had to create a separate open source project called
models.dev that built up this entire database that didn't exist at the time. And now obviously,
now you can you can contribute to it. And this is probably the best data set of all the models and
providers out there in the world. But again, just to sort of make that happen and to, you know,
occupy that position. It was a very deliberate choice. Can you think of any other examples of
like intentional product design choices you made that you think have really sort of
helped you hit this inflection point? Yeah, I think the name came a little bit later. It's
happened within a span of a few weeks. But yeah, the first thing I think that had happened was
with our past product, we had just hit sort of being break even. And around that time,
this was February or so of 2025, Cloud Code comes out. We look at Cloud Code and we go,
this is fundamentally different from using autocomplete, using AI in that form. And this
is something that actually does make sense for us as a kind of a core developer. You know, we were
sort of NeoVim users at the time. And so Cursor didn't necessarily resonate with us as much.
But watching sort of Cloud Code and sort of using it a little bit, we kind of realized that
it wasn't up to the standard of some of these other terminal UIs like the NeoVims of the world.
And we wanted to build something like that. And that was really the first sort of bit was that,
you know, when you open this up, this should feel like a modern terminal experience to a lot of the
core developer audience, the ones that we were going after very early on. It should feel like
one of these other things. That's so interesting, because I feel like a lot of Cloud Code users,
because you have such low expectations for what you can get out of a terminal UI. People are like,
wow, this is kind of crazy how much you can get done. And these graphics and effects are really
cute and cool. And that's awesome. But the fact that you were sort of like terminal UI connoisseurs,
it sounds like, you were looking at it thinking of, oh, you would actually do so much more in
the terminal. Yeah. And we had built a couple of terminal UIs in the past, one as a part of
our core product with SST. The other, Dax had sort of built on the side with a couple of his friends.
You could buy coffee online. It's a terminal UI. It's a complete storefront.
It was sort of a fun pet project, but it showed off what we could actually do.
Wait, wait. So your product was a terminal UI for buying coffee in case you wanted to
buy coffee without leaving your terminal. Because the idea was, you know, you're a
hardcore developer. You're in the terminal all day. You can't be bothered to open a browser.
So you go ssh-terminal.shop and you order coffee over SSH.
It makes sense way easier.
I feel like this is an example of that PG essay, where if you're a developer and you
build things that you want yourself, even if it seems really goofy to other people,
and a VC would turn up their noses like, well, that's a horrible business. What are you talking
about? A terminal UI for buying coffee? It has this tendency to pull you in an interesting direction.
Yeah, it just generalizes to having eccentric tastes. Not always leads to something interesting,
but it's kind of how you get to these outlying things.
Because we were so embedded in the open source community,
and because most of the people that sort of surrounded that community
were people that looked up to products that were really good in the terminal,
we knew that if we built one of those, it would resonate with them almost right away.
It's pretty easy to think that you guys sort of just came out of nowhere and have just
exploded and this overnight success story. But the company's actually been around for
a little bit longer than six months. And so tell us a bit about that backstory,
because you went through YC over five years ago now, but even before that.
Yeah, but the story starts way before even that.
So it was second year university, and I was just in a co-op term at Waterloo. And I was like, wow,
I don't want to do this. And so I sort of come back, being very naive, find the smartest people
I can get a hold of. It ends up being Frank, my college roommate. And the two of us were like,
yeah, let's just start a company. Again, I'm a 21 year old. And so I picked the name Anomaly
as the name of the company, because I'm like, I'm special. But yeah, it literally starts off
with me reading PG's essays. How long ago is this?
2006, 2007. And I think I started reading PG's essays, because I was like, yeah, I want to start
a company. I would want to do a startup. And this was effectively the best thing you sort of find on
it at the time. I think the first YC application was probably around that time. But the first
interview and what brought me the first time to Silicon Valley, I forget the exact batch,
but I think this was the Mixpanel batch, because I know the day that I interviewed was literally
after Mixpanel, like Soyella sort of interviewed. And I think this was right after Airbnb's batch.
And so one of the Airbnb founders was hanging out in the sort of room when we were sort of
waiting to be interviewed. And this was obviously with PG back then. And yeah, that was one. And
I think the first of many interviews and applications to YC.
It took more than a decade to get in, let's just put it that way.
And you told me something crazy, which is, I assumed that during those years,
these were different startups. But apparently, it was literally the same startup,
like the same legal entity all of those years. Yeah, yeah.
So this legal entity is almost 20?
Yeah. So we incorporated in 2010.
So it's a 16-year-old legal entity. And you've had successful products before,
but OpenCode is the most successful. And so it took 16 years since you started the company to
have like a truly runaway success product. Yeah, yeah. I think part of it is also to do with
just sort of like your level of maturity, your level of, I guess, like ability, I guess.
We were maybe too young for some of these other waves, like the mobile wave,
the cloud wave, whatever, you know. And we did build things that did reasonably well.
But this time around, it feels a little bit different in that it is a sum total of our
experiences. And that's maybe made things a lot more easier to navigate, especially given the
chaos in the space that we operate and the competition. I looked at the numbers, and
you did nine applications from 2016 up to 2021 when you got accepted. And you did four interviews.
And for all of these, they were all different ideas, but it was the same legal entity.
It was the same legal entity, yeah. And the same founders.
And the same co-founders. It was just you and Frank doing it the whole time.
Yeah, doing the whole time. And then after we did YC, then our third co-founder sort of joined,
and then it was the three of us for the last four years.
Another chunk of time. It's just, you know, it's like fly away.
What was the idea you applied to YC with for 2021 that you got in with?
Yeah, so we were building a serverless platform at the time. It was like Heroku, but for AWS and
serverless. And we wanted to do a better job in that space and maybe grow the market. And we built
basically a serverless framework. That was our first big open source project. And it was our
first move into building open source products, building in public, you know, doing the whole
thing. And eventually, obviously, all of that sort of ties into OpenCode.
Where does the building in public come from? Because you're clearly doing it now. You're
like quite transparent with your metrics and growth, which is awesome. But yeah,
where does that come from?
A little bit of that came from Dalton. I think he was sort of
pushing us just in general, just talking about like, yeah, you should probably do things in
public because you're sort of an open source company. Then I think it sort of dawned on us.
This was maybe 2022 or so where it was like, it was actually Dax, one of our other co-founders,
where the idea was just look, you know, all your code is public. You work basically in public.
If you don't talk about it publicly, you're probably doing yourself a disservice and your
product disservice. And, you know, ever since then, it's just been a part of our identity that,
you know, for a lot of our community, the people that sort of follow us on Twitter,
to them, it feels, it sounds funny, but to them, it feels like watching a reality TV show
of this team and the company and the sort of journey that they're on.
I think the thing that's fascinating is that even though it sounds like
such a windy road, and if people just heard the beginning of the podcast,
the company sounds like a lightning in the bottle moment is that you just
got caught by strike and got so lucky. But the reality is you've been grinding for a good
10 years and never gave up, which is so impressive. All those windy destinations
that ended up being dead ends actually did teach you different things because
you also ran a consumer company. So you got really good at really all consumer acquisition,
tracking numbers and all of that, which really plays right now. And the level of detail you have
for open code and of course, open source and all of these, they were not all like wasted,
quote unquote. It was really more a journey that took 10 years to get to zero to 30 million in
eight months. Yeah. Yeah. Yeah. It's crazy when you put it that way. I think what's fun is that
with open code, we feel like we can go out and address the entire market. And that includes
consumers, individual users to small teams, obviously the open source community,
mid market, all the way to the enterprise. And in our past iterations of all the different
products we've worked on, we've probably done one of each. And so now it feels like,
oh, we get to do all of them together in one product. And it's a lot more fun because you
can think about the customer journey through that entire thing. And it makes a lot more sense because
you're not hyper-optimizing for specific parts, right? I'm not trying to build a very specific
enterprise company or a very specific consumer company. We're trying to just do the whole thing.
What got you to not give up? Partly maybe being a little stubborn.
It's funny. Maybe we should put a little warning that don't try this at home.
Because I think the prudent thing would have been, yeah, shut down your company,
go join a high growth startup, learn a bunch of things. But I think there was something in the
back of my mind, and Frank is probably the same, in that we felt like we were learning these
different things along the way. And in our heads, we were figuring out, okay, here's what it takes
to build not just a product, but do the marketing, to understand the positioning of things,
to do the whole thing. And that journey felt like just progress and positive progress.
And I think a part of that was obviously us being fortunate to have the ability to do that,
which was basically just living with parents for a bunch of time and we ran out of money.
But yeah, maybe a combination of being a little thick-headed and seeing positive progress.
So I'll admit, I've been kind of a diehard Cloud Code user since Gary Tan became addicted to Cloud
Code. But recently, I've been using OpenCode, and I dropped a bunch of PRs from OpenCode this
week. And I've been really impressed with how well it works with open source models on our
existing code base, which is a very large, very complex code base. For folks who are watching,
who possibly have only used Cloud Code or Codex or Cursor, how should they think about trying
OpenCode and potentially switching to it? When you hear about a new model that comes out,
especially an open source one, and you sort of want to try it out, you could kind of hack your
way into using it with Cloud Code or one of the closed source alternatives. But OpenCode is really
good for this. You sort of go in, you look at the model picker and GLM 5.2 or whatever the new open
source model is, is probably up there. And you can pick it and start sort of using it right away.
Okay, well, Jay, I think that's all we have time for today. I actually learned lots of really
interesting stuff about your backstory that I didn't know in this episode. I mean, I think
it's a pretty inspiring story, honestly, for anyone that wants to start a company.
Or at least entertaining.
Entertaining and inspiring, it can be. I know it just hits on so many of the classic startup
wisdom, right? It's like, you should pursue your interests, have eccentric tastes, be like,
live in the future a little bit. I would argue that trying to order coffee through the terminal
is... So I'm not sure if that's living in the future or the past, but it's not living in the
current times. Maybe there's something in there. But yeah, I know also just the fact that you kept
building your taste and to keep building things over a long period of time. And then when lightning
strikes, you're actually in a position to capture it. I think that's the thing that doesn't get
mentioned actually, is to catch lightning in the bottle, you actually have to sort of position the
bottle correctly and be ready for it and know what to do with it. Yeah, and you guys are well
positioned to do that. So congrats on all your success. I know it's gonna only get more explosive
from here.
Thank you. Thank you for having me.