I've been thinking a lot about timing as we were preparing to have this conversation, because what you guys are doing with Reflection feels very apt to the moment we're in. I was looking and mentions of open models on earnings calls 6x'd in Q3, and open model tokens are now the majority of what's flowing through Vercel and OpenRouter. So there's this real shift that's been underway, and you guys have been in stealth and have big news that we're going to talk about on the open model front. But first, before we get there, I'd be curious to hear you both comment on what you think is driving this moment right now in terms of the surging interest in open tokens. There's multiple things here I think we can peel back at, but if you were to kind of look at it big picture, what do you make of the moment we're in? Misha, we could start with you.
You know, we decided to really push for building great open models at this company about a year ago. And at the time, I think that we just... there are some things that we saw that would be kind of happening that have happened faster than we expected. And maybe one way to think about why open models are so top-of-mind and so important right now is using a real estate analogy, which is we have to remember that in the AI market, this market commercially has only existed for maybe three years. The market effectively started as a rental market. Like, closed models are the equivalent in real estate to renting an apartment. You're renting your intelligence. And that makes a lot of sense, especially when you're, you know, when you're earlier in your life, you're a student or you just graduated college, you might go and rent an apartment. But as a consumer, you get older, you have a family, you have more finances, ownership starts mattering a lot more in the real estate market. And so that's why there's rental and ownership in real estate. AI timelines are compressed. And so we've been in this commercial market for three years where effectively in the West there's only been a rental alternative. And now what we're seeing is that as AI adoption has increased and the small startups that were tiny a few years ago are now giant enterprises and large enterprises have adopted AI, an ownership market is basically coming in. And the only way to own intelligence is by definition if it's open, because if it's open you can run it on your stuff, you can own it, you can control it, you can customize it. And what we're seeing is that the reason this has happened so quickly is because AI as a market has grown so quickly. And you're right, I think that 12 months ago not that many enterprises at all were using open models, and not even startups really were using open models all that much. Six months ago, a lot of startups that had grown at the application level started switching to open models and have continued growing very quickly. And I think that's where maybe six months ago there's 30% of token consumption on OpenRouter over SaaS was going to open models, 70% to closed, and now six months later it's flipped where it's maybe more 70% on open models and 30% to closed. And so we've just seen a very fast movement in the maturing of the AI market, and I think that is one thing, and obviously the geopolitical thing is the other thing.
Yes, which we'll get into. Giannis, though, I'm curious from your perspective, technically, the state of open models. Has the progress surprised you? Is it about where you expected if we were to have looked out a year ago to now? As you've been thinking about the research roadmap, have you been seeing this moment coming, or has this surprised you as well?
No, actually, I think that if you look back, you can see that the open models have kept pace with the closed models, and I think like maybe there's even a shorter distance between the open and the closed frontier currently with like the biggest Chinese models. And I think that this is something that will just become more prevalent in the future, in the sense that like I don't see why the open frontier should just stay behind the closed frontier. It's a matter of just having the talent and the compute, and you can definitely just build open models that punch at the same level as closed models. And you know, one thing to say here, I think like there are two main reasons why we've also seen this adoption of open models by enterprises and startups. Like in my mind at least, like one is the fact that the capabilities are there now. Like you know, we have like some really powerful Chinese models or like open models in general which can really be used in the place of like closed models. And the second thing is that the market has started to mature, like to Misha's point. And what we've seen in the software market is that like whenever something matures, there's like always a movement towards the open alternative. You know, once the market matures and the SaaS market matures, then there are open alternatives, and then enterprises and companies and individuals just like move to the open alternatives. And I think that like something similar will happen with the AI market as it matures further.
This episode is brought to you by Mercury, AI-native banking that's loved by more than 300,000 entrepreneurs, including me. Visit mercury.com to learn more. Mercury is a fintech, not a bank. Check the show notes for details. This episode is also brought to you by Jira by Atlassian, where teams and agents get the context, coordination, and control to move work forward. Try it free at jira.com. That's jira.com. Thanks also to Granola, the AI notepad for people in back-to-back meetings. It works everywhere you do and lets you focus on what matters. Try it at granola.ai/sources and use the code sources for three months off. You all are obviously an American company and you have your model coming out, which we're going to talk about, but I'd be curious to hear from you all. Why is it that China and Chinese labs have just dominated on open up until this point? I mean, Meta had its moment with Llama 3, but really the West has completely lost the frontier of open until you guys. And I'm curious, what is it about the Chinese labs, if you guys were to armchair it, that you think has led them to catapult the way they have?
You know, the thing that drives technological development in the West is ultimately, you know, it's capitalistically and commercially driven. And if you're in an early market that is a rental market that primarily supports, you know, closed model development, then that's the thing that develops first. And it's only once the market is ready for ownership that I think there's a kind of commercial and capitalistic market support for open models. So I think that, for example, I mean, America used to have the best open models, and indeed I think the highlight, the peak of that was Llama 3, but there was no real commercial incentive at the time for, you know, Meta to do that or for anyone else to be producing great open models in the West. I think that, again, armchair, that China has a different mindset that is more geopolitically motivated. And that I think that there was a bit of a sort of fluke moment, like an unpredict- a moment that was hard to predict, which is when DeepSeek V3 came out and was so good, and then made Chinese intelligence abroad so relevant in a way that it hadn't been before. And I think that there was a concentrated push to support an open-source ecosystem primarily driven for geopolitical reasons. And so these labs in China were not actually making that much money at all until recently, until their intelligence got good enough and the market matured that there's a commercial market for open intelligence, and now they're starting to make revenues. So I think that my view is that what happened there was primarily geopolitically motivated in trying to kickstart that ecosystem.
Well, I think that brings us to what you guys are doing. You guys are talking about Beam, your first model, which I think everyone in the AI community has been buzzing about. What is Reflection doing? When are they shipping? And the moment's coming now. So, you've got Beam, and it's around a 500 billion parameter model. On the open benchmarks, it seems state-of-the-art. But I'd be curious to hear from you all, and as we're talking, you're still kind of going through the final phases of validation and all this, but I'd be curious to hear from you all like what you expect the reaction to this model to be.
So, Beam is, yeah, it's our first model, it's our first open-weight model. We're very, very excited to release it. I think it's, you know, building a company is, I think there's a Reid Hoffman quote that it's building a plane while you're flying it, and the plane's been built. So I think we're very excited about that. It is indeed around a 500B total parameter model, 23B active, and it advances the frontier of Western open models in a meaningful way, which we're excited about. The things that we think we're proud of with this model is it's particularly strong in coding and agentic benchmarks. We believe that the form factor and the strength in these capabilities make it a really strong workhorse model for enterprises, public sector, right? It has this right kind of utility but also efficiency around it that I think will be appreciated. The kind of other thing that we're really excited about is that it's a model that is leading in its reasoning efficiency relative to other open models. And when we say reasoning efficiency, we mean how fast does it solve a task relative to the compute it has at inference time or relative to the tokens that it has at inference time. And you know, Giannis and team did some incredible work to get that state. Maybe you wanted to share that.
The form factor for the model is a 500 billion parameter model, 23 billion active. And if you actually like think of what you want from a model that's an open model and you want to ensure that it has like wide adoption, especially from like enterprises, you need something that is efficient, it is compact, and it actually like really produces the most intelligence that you can get out of your flops. And in order to do that, you need to have like a reasoner, like these are reasoning models, and the idea is to just like use tokens to actually solve tasks. The way that you measure whether a model is like more efficient or like equally efficient to another model in terms of like reasoning efficiency is by just like seeing how many tokens or like how much time, how much compute it actually takes to solve a task of like, you know, similar difficulty. And what we've actually seen is that we have a model, we've built a model that can be three or four times more token efficient, reasoning efficient than some of the open frontier models like GLM 5.3 or like some of the best closed models like GPT-6, Llama. So the question then is like how can you ensure that you can extract the most reasoning and the most intelligence out of like this small model? And the way to do it is by really scaling reinforcement learning. So reinforcement learning is something that, you know, I've been always like really passionate about. It's like, you know, I started like doing reinforcement learning back in the early days of reinforcement learning in 2012, 2013, and, you know, it's something that like both Misha and I have always like been really true believers in reinforcement learning, we've been RL-pilled. And you can actually see now that by scaling reinforcement learning, and what we've actually done at Reflection is that we scale reinforcement learning to the highest levels of compute in terms of like what we know publicly available in comparison to other like open labs. We've actually like, you know, released their research and we can just like compare apples to apples. So we've really kind of like doubled down on the compute we put into reinforcement learning with the goal of ensuring that we extract the most juice, the most intelligence out of the model. And this is ultimately what like enterprises and, you know, developers and everyone cares about, like a compact model that uses its tokens efficiently and intelligently to solve tasks.
And the enterprise use cases seem obvious when you describe it that way. Do you imagine broader consumer... I mean, these are all kind of nebulous terms, and enterprise adopting it can translate into consumer adoption based on how that company's relationship with customers, you know, functions, but do you see consumer applications of a lightweight, efficient reasoning model like this?
Definitely. Though the way we kind of think about it is that the purpose of an open model is to enable an ecosystem of builders to build on top of it. And so, right, it enables other companies that might be building consumer applications to control their own destiny and have an efficient workhorse that they can also customize against their data. And, you know, we're starting to see this new wave of new consumer experiences powered by agentic models. And so agentic capabilities are very important for doing, you know, certain, you know, they seem like basic tasks for a consumer, but they're actually hard for AI, they cost a lot of tokens. Yes, that's right. So if you have a workhorse model that is sort of doubly efficient, in that the size factor is efficient, but then because it's also very efficient in its reasoning, right, if it's say 4x more efficient in reasoning than other models and it has a smaller form factor, then those efficiency gains translate to faster response times to consumers, much lower cost of serving, and honestly, for consumer use cases specifically, the cost of serving matters a lot. And so I'm really excited to see what others build on top of these open models and how can we empower both enterprises and companies building consumer applications.
And you all trained this from scratch. You didn't do distillation or anything like that. Talk to me about that decision to do it from scratch, because in open, I think everyone just kind of assumes these days that everyone's distilling everything, even the closed, you know, players, there's like rumors of distillation happening and accusations. So why approach it that way?
Yeah, so this is a good question. I think that like there are two reasons. First of all, we wanted to ensure that like this is, you know, a Western frontier open model that's actually like fully built, you know, by our team in the United States. We also have like a team in the UK, but like built in our offices in the West. And the second thing is that especially when you want to really scale reinforcement learning, it is extremely important that you also like control your pre-training. Like pre-training, you know, now it's like more of a better understood science than reinforcement learning, but like in order to do it in the right way so that you can scale reinforcement learning, keep it extremely stable, ensure that like this is a mixture of experts model, but like ensure that the router and the experts remain balanced and stable during this like high-compute reinforcement learning regime. It's really important that you fully own it. There's a lot of work that went into the data that we put in our pre-training to ensure that like it seeds the right reasoning capabilities to the model that like then reinforcement learning picks up and just really accentuates. And also on the architecture and the learning dynamics and the optimization so that like once you've actually trained it, it's really stable. It has the right biases and priors so it can really like pick up with reinforcement learning. And only by just really optimizing the system end to end by innovating both on the pre-training and of course on the reinforcement learning side, it is possible to just like build something that again is like really capable for its model size and it really packs a lot of intelligence in a smaller form factor.
I'm curious how you all are thinking about safety and alignment. It's the maybe number one topic not just in AI but like in geopolitics right now is aligning these models. There's all the headlines recently of, you know, OpenAI and others having rogue agents going out there and hacking things, and I think people are concerned about the increasing capabilities of these models. How do you approach alignment, especially for an open-weight model?
You know, there are kind of two things to kind of think about. One is what are the benefits of doing safety research and protecting, you know, models in the open. And then the technical of how do you, you know, actually go and bake in safety into a model as it pertains to kind of open source traditionally. And let's not even think about models for now because there's a very similar thing that happened in software development. And, you know, with operating systems and the internet, the internet protocols are open, operating systems like Linux and Android are open, and a lot of the strong encryption protocols that gave rise to the whole field of cybersecurity are open. Like there's the way, right, you test software, you do penetration testing, there's both black and white box penetration testing. And so the notion of openness has been fundamental to securing software over the last decades to the point, right, there's Linus's Law, which is that with enough eyeballs all bugs become shallow. And that's why open source software is actually in many ways considered safer and more trustworthy than closed software because you can just iron out all the kinks. Now we have to think about artificial intelligence as, right, it's an evolution of software, it's a machine, it's a piece of software, so it's not a god. Not well, not that I'm aware of. Okay, good. I mean, and you know, it's no more than, you know, than Linux or Android is a god, so maybe there's a church. Yeah, maybe there's a church of Linux somewhere and all the power to them. But it's ultimately, it's a very sophisticated machine that has a long tail of vulnerabilities like any piece of software, and it is impossible to discover and patch up that long tail with high confidence when you have a small number of people who have access to it. So right, across the closed labs there might be 300 safety researchers, and that's great, and I think the intentions are great, but it's kind of like saying across my whole body I have 300 white blood cells. Do I trust those 300 white blood cells to, you know, find all the pathogens and get rid of, you know, the stuff that's, you know, attacking, you know, your body every day? No. I'd rather have as many white blood cells as possible. And I think that, you know, this notion of with enough eyeballs, right, all bugs become shallow. I think it's true to like if we think about mechanistically patching like all the vulnerabilities in these systems, of which there are many, you need to bring a community in, right? You need to bring, you know, from 300, 300,000, right, people who can investigate, inspect these systems. And so fundamentally I think that in the same way that open source software has actually been the safest way to develop software broadly previously, I think the same thing transfers here. There are some things that are new because the software is so powerful, but the broad strokes are still the same. And so at a high level, I'm excited for moving into a world where a large open source community protects us, you know, in a way that I think is going to be much more effective than, you know, having a very small handful of people who are protecting.
As you're saying that, I'm thinking about, you know, Hugging Face when it was getting hacked by OpenAI. What did they do? They turned to open models, Chinese models, because they needed to defend and they didn't have access to the best frontier closed thing, right? So that speaks to what you're saying. At the same time, I mean, I think there is a fear that, or a belief in a lot of the closed labs at least, that like this is different than Linux and maybe there should be a point at which this is held back. I mean, Giannis, maybe you can speak to this from the research perspective. Is there something on, I assume you guys are training your next model already, is there something on like larger trains where you would go, we would hold this back even though it's open, we're an open company, this is too capable? Do you all think that way at all? It sounds like no.
You know, I think like it is possible that like it gets to a level of capability that you want to just like be more careful with like how you deploy it. I think fundamentally sharing it with the research community at large has always been a net positive for like the development of AI. And we actually saw that with safety in particular, like once like powerful open models were available to the researchers, actually like so many insights and so many new safeguards were actually developed. So I think that like fundamentally it is a net positive. I think like maybe you want to just be more careful on like who has like access to the model, like you might want to just like restrict it more, but fundamentally sharing it with the research community and with, you know, the vast majority of developers out there who have like good intentions and actually want to help us and the world to just like make these systems more safe, it's a net positive and it's the right approach. Now this is actually true that we see that like models get more and more powerful, you know, they hack their sandboxes, they form communities online, they collude with each other, exactly, and this is something that we see more and more. At the same time, they also like become better at like policing themselves, or like you can actually use AI to control AI and to just like make it safer. You know, there's like research that goes into that. And you know, fundamentally, I think that it is important that we share many of those findings. I think the fact that even the closed labs went ahead and just like released the findings of how these different agents operated can only provide us more insight and more information so that we can protect ourselves and we develop the necessary defense mechanisms. So this is to say that like in general, being open, being transparent makes things safer and makes our society better prepared for like the advent of AI.
But is there a capability threshold you would hit where you'd go, we can't put these weights out? Like, have you guys thought about that?
We've definitely thought about that, and also obviously there's a lot of discussions now in DC around that notion, and that is very important. And independent whether a model is open or closed, right, if you hit a certain capability, then, you know, we should as a community of both, you know, industry and government, right, there are policies around what should be kind of released and not, and under what, you know, gated measures you'd allow that to happen. So that's really around kind of a capability of intelligence. I wouldn't describe us as, you know, hardliners of, you know, closed is not safe or open, you know, it's really around an ecosystem is safe, like having an ecosystem is safe and having, you know, closed models out there with their points of view, open models with their points of view, and this and that, right, that is the safer world. And of course there's a threshold of capability under which these things need to be regulated, but that is independent of whether they are open or not. And I think that when it comes to openness specifically, there are arguments that, well, look, you can release an open model and maybe we need to like that some bad actor, right, could use it to do this and that, which by the way, that's exactly what people do with software and why there's cybersecurity, right? So, but there's this other thing that I don't think people talk about as often, which is there's the bad actor issue and then there's the unintended consequences issue. And what happened with the OpenAI Hugging Face hack that you just described is that was an unintended consequences issue that again, because you have to like, when we do these runs, right, these large RL runs, there can be like a billion agents over the life of a run, right, doing stuff, and it is impossible to imagine that, you know, your like 100 researchers, 300 researchers or whatever will be able to, you know, to really track each of those agents, right? So there will be, when there are a small number of blood cells, right, there's a large surface area of things to protect against and there are unintended consequences. And so what happened there was that, right, these agents hacked out. I think Hugging Face tried to use closed models to protect them, but because the safety guardrails prevented them from being used for cyber, they were not able to protect themselves. So they had to turn to an open model. And that actually shows you an ecosystem working because, okay, there's some, you know, there's some principles on one side that say, no, we can't use it for that. Then principles on the other side is like, no, you can use it for it. And ultimately because the ecosystem existed, that enabled Hugging Face to protect itself. And so it's just this technology has a lot of unintended consequences and the only way to really deal with it safely is to have a community and an ecosystem around it.
I totally get that ecosystem approach makes sense. I'm curious though, technically, how do you approach this technically? Does that differ when you're building an open model, how you do safety alignment at all, or is it the same?
So actually, like in terms of the technology that we're building, it's quite similar to the technology and the recipes that are used in the closed labs. The way that you actually do it is that there are two parts to it. Like you need to first ensure that you have like all the right evaluations across like all the different risk profiles so that you can measure the performance for the model, also the response of the model, and ensure that like it's not either a model that just like refuses everything, because like a model that refuses to do anything is like super safe. It's the safest model, but it's not useful. So there's like, you have like these two things. On one hand you have usefulness, on the other hand you have like safety, and it's like a trade-off that you need to ensure that like you're measuring it right by having the right evaluations and you also like hill climbing it in the right way. Once you have your evaluations and you've actually collected the data and you've defined what is the behavior that you want your model to have, and the way to do that is by collecting examples of like, you know, what good behavior and bad behavior looks like, then you can actually apply the usual methods of, you know, imitation learning or SFT as it's called, or reinforcement learning to ensure that the model always behaves, is aligned and behaves in the way that you want it to behave. This is, you know, a field of study that like, you know, has been developed in the past five years. These are like methods that, you know, they've actually been developed in the closed labs and, you know, in the open research community. And we're also like really putting a lot of effort. We have a team of like researchers who are only focusing on like safety and ensuring that like the models that we put out there are like really evaluated correctly and they are like safe and they're really at the frontier of like safety and usefulness.
Even if you buy the argument that model capability will create intelligence we cannot fathom, we cannot comprehend what it will do in the world if it's fully diffused. And therefore, it's not fair to compare to an operating system. It's actually something much more, almost like a being in the sense of we don't know how to control it, we don't know its parameters. I feel like that's starting to seep into the consciousness of the public with how some AI leaders talk about things. And I'm curious where you guys sit there.
I think that like the other thing that is important, and it goes back to the diffusion of power that like Misha was talking about, is that every time you have like only one or two institutions controlling something that's like so powerful, even if they have the best intentions, it's like a single node of failure. So you want to ensure that you have like a redundancy even in the system to ensure that like it's not, you know, if this system just like fails, then all systems have failed. And the Hugging Face example is a prime example of that, that if you could actually use AI to protect against like a bad-behaving AI, then the world ends up being safer. And if other people are actually like enabled and other institutions are enabled to use like powerful models for cybersecurity and for protecting, I think, yeah, for protecting everyone, then that's a net positive.
One of the biggest pains I've had running Sources has been managing my books. I'm not an accountant, and all of the software out there is unintuitive, clunky, and detached from where my transactions actually live, until now. Mercury recently launched Mercury Books. It's AI-powered accounting that works with your Mercury banking and credit card transactions, plus external cards and payroll systems as well. You can choose between cash and accrual accounting and quickly generate reports for your cash flow, P&L, and balance sheet. Like everything Mercury does, the design of Mercury Books is super approachable and clean. I finally don't feel overwhelmed when I'm trying to understand the big picture of my business. I love that AI does most of the heavy lifting, including for things like autocategorizing transactions, and that Mercury's Command AI agent can handle tasks end to end. You don't need to be paying for separate accounting software anymore. And you can even invite your accountant or CPA to work alongside your Mercury Books with you. This doesn't cost extra, and Mercury will even help you find a human accountant if you need one. Visit mercury.com/books to learn more and apply online in minutes. Mercury is a fintech company, not an FDIC-insured bank. Banking services provided through Choice Financial Group and Column N.A., members FDIC. AI is only as useful as the context it has. But when that context is scattered across tools, threads, and DMs, your team and your AI agents are flying blind. That's the problem Jira by Atlassian solves. What's the goal tied to your project? What got decided last week in Slack DMs? Atlassian's Teamwork Graph pulls all of the valuable pieces together from Jira, Confluence, GitHub, Slack, and more, so nothing falls through the cracks. You get 44% more accurate results with 48% less token usage. With Jira, you can easily share your work context with the AI agents you already love, like Claude, Cursor, and GitHub Copilot. Assign them work directly or connect your tools through MCP. All of this lets you spend less time digging through endless links and messages, chasing down what got decided and by who, and spend more time actually shipping. Learn more at jira.com. That's jira.com.
I spend a lot of time context switching between meetings, often with no time to process one before the next starts. Thankfully, Granola runs in the background the whole time. It's an easy-to-use AI notepad for meetings that works everywhere, even on phone calls. I use Granola to recall what was said in meetings and create helpful summaries. I use it every day to stay on top of what I need to get done with my team. It connects to my email and suggests follow-ups for me to quickly review and send, saving me valuable time. Granola isn't just a core part of my workflow. It's basically my second brain. Try Granola at granola.ai/sources and use the promo code sources for 3 months off.
Framer is the AI website builder that powers the Sources podcast website at podcast.sources.news. Framer brings AI agents into the same canvas where your website is designed, managed, and published so you can move faster without giving up your taste or control. I use Framer to make the Sources podcast website be the destination for everywhere you can find the show. Plus, you can also see recent issues of my newsletter. Start building with agents for free today at framer.com/sources for 30% off a Framer Pro annual plan. framer.com/sources. Rules and restrictions may apply.
I have other questions about the business. But before we get into that, for people who don't know, what's the origin story of Reflection? You guys worked together at DeepMind. I actually heard that you reported to Giannis at one point.
Uh, yeah, Giannis was basically my boss.
And now you're the CEO. So that's a fun twist.
Well, we're actually equal partners like the way...
That was going to be my question. How do you run the company? You started it together leaving DeepMind. Maybe there first, like you bet on open in what, this 2024? Is that right?
Well, I guess it was a year ago. So, you know, we... well actually when we started the company, we had two bets. And I would kind of bring it back to the origin story. At the time, Giannis and I had worked on Gemini 1, 1.5. Giannis was the RLHF lead and, you know, one of the most storied reinforcement learning researchers at DeepMind. I actually switched from physics to AI when I saw AlphaGo come out and then I later learned, you know, well I knew that Giannis was an author but that was kind of a, you know, sort of a dare I say it a celebrity crush moment [laughter] when I joined DeepMind and had the pleasure to work under Giannis on his RL team. But at the time we shipped, you know, Gemini 1, 1.5 and those models were really good at chat. You have to remember when ChatGPT came out these models were not good at coding. They were not good at agentic. They were really good at chat. And we started the company with kind of two bets in mind. A scientific bet and kind of a market bet. One was that reinforcement learning was the way to get these models to have agentic coding capabilities. And the other one was that there'd be powerful Western open models we can build on top of so that we can just do this research a lot more cost effectively. And the reinforcement learning within the first kind of year of the company became right across the industry. We were able to show some, you know, really strong reinforcement learning results at small scale and obviously the reasoning models started coming out at that time from other labs but at the same time the Western kind of open frontier receded with the DeepSeek V3 moment and we actually waited around for a few months for something to come out that was as good and then saw that wasn't happening and so that's kind of how the company changed course but there I think even a better, you know, a better story in terms of how we actually started it. And when we were building Gemini, there would be these sprints where teams from different offices would come together and I was in the New York office, Giannis was in the London office and kind of an SF, New York and London team descended on New York for, you know, one of these sprints. And at the time, you know, it turned out that Giannis and I were thinking these ideas kind of independently. I'd wanted to broach a subject with Giannis, but he's an intense guy and like it's, you know, like telling your boss like, 'Hey, do you want to [laughter] like start something?' was, you know, was a bit intimidating. So there was an evening when we, you know, Giannis came to New York and I was kind of showing people around, right? And so we went to take a group to the Comedy Cellar and it was like an outlier raunchy set. It was the raunchiest set I've ever been to. So it was a little awkward.
I've been there a lot. I've seen some raunchy sets. Yeah.
Is this like, you know, do people find us funny or am I... you know, we went to that and then we took a long walk and went and grabbed this dinner on, there's this kind of boat in New York by, you know, by the Google office that serves lobster rolls and actually Giannis broached the subject of hey, you know, maybe we start something in this shape. And honestly that for me at that time it was really, you know, whatever it is if it's kind of with Giannis we're starting it. But we ended up, you know, we're both reinforcement learning pilled, both AGI pilled. I think had a very similar view of where we thought the world was going and then decided to start something together.
I heard a rumor, I don't know if it's true. Was it Jensen? Nvidia is one of your large investors. Was it Jensen who pushed you guys to go the open route when you were focusing on coding? Is that accurate?