Apply

Podcast guests

Yakko Majuri

Yakko Majuri is the founder of Railcode and a guest on the Solo Founders Podcast.

Episode 24

Everyone Has Claude Code. Now What?

Published · 30 min

Companies are handing every employee AI coding tools and calling themselves AI-native — then blocking everything those employees build. Yakko Majuri, early PostHog engineer and infrastructure lead at Doublepoint through its acquisition by Oura, just launched Railcode: a secure home for internal apps and AI agents where you build with your own tools and deploy in seconds. He gives a live demo — Railcode's first on camera — and explains why most software going forward will be internal.

Transcript

Transcribed automatically, so names and words may be wrong. Each time opens the video at that moment.

0:00Are you holding your team back? There are companies out there. We're talking about being AI

0:04native, and they are holding employees back without realizing that they're doing so. They're

0:07like, hey, we've given everybody cloud code. We've given everybody codecs. But what's the next step?

0:11How are they being held back? They had to wait a week or more to get something that they've built

0:16live, because it needed to be approved by DevOps. Most of the software going forward is going to be

0:21internal software. The week that we close actually spent ten hours this week supporting this. And now

0:26the CEO can build everything himself. I just fired off a clod code and I just said add dark mode

0:30support, wait like five seconds and then the deploy is live. What's the advice for us all our

0:35founders? Get in touch with yourself and the things you want to build. It's fun for me to build

0:41real code and fun is useful. Welcome to Solo and Prod. This is a new experiment that we're

0:47running where we highlight startups in the Solo Founders Program just as they launch. So you can

0:52get a sense of why the founder is working on the company in the first place, the insight they have

0:57and the inspiration that caused them to start it. This first episode is featuring Yakko, who is

1:01building Railcode. Yakko has particularly interesting insights into internal tooling at

1:07companies, and he actually built the first version of Session Replay with the team at PostHog, where

1:13he was one of the first employees. Yakko believes that most of the software that's built in the

1:18future will actually be internal. Facing versus external and Railcode is his solution to help

1:24these teams build much more effectively. Also, if you're building solo or you're thinking about it,

1:29you should apply for the Solo Founders Program and join other people like Yakko who are building

1:33solo together. You can check that out at solofounders.com. Yakko, this is really exciting. What

1:39is Railcode? Yeah, so Railcode is a platform for building internal apps and agents in like a

1:45secure environment. So what we're seeing is that people get access to cloud code these days, and

1:50they want to build software that, like, works well for them. So we're providing a secure place for

1:55them to both experiment and actually build serious apps that obstacle kind of in production

2:00internally and that help other people and that can be shared around the company. And I think that,

2:05like historically, people have used tools like retool to, to essentially build like different

2:11interfaces and things like that for people to use it internally at companies, you know, internal

2:15tooling, right. And historically, also that meant that, like all of the code was kind of like on

2:22retool and like all of it was sort of like in their walled garden type situation. In this case,

2:28though, you essentially had an insight that there was something that was fundamentally at odds

2:35with, like the way people are building these apps, these internal apps, these many products. Can you

2:41share a little bit more about sort of how you came to that insight, like what you were working

2:45on, the types of conversations you had that led to that? So the best harness is my harness, right? So

2:52everyone is building their own harness and their product. You go into every product and there's

2:55like an AI box there that you can talk to. But I use cloud code every day. Some people use cloud

3:00desktop. People use these different things. I use codecs as well. All my skills are there. All my

3:05workflows are there. It can browser test for me. It has all kind of my testing setup. So what

3:11I'm building is basically enabling people to stay within that workflow and just have a secure place

3:19to put this software that they're building. This came from speaking to a lot of people where they

3:25were either moving off of retool or they had retool, but like people were spinning things up in

3:31other, other places, like they were putting things like on Vercel. But then someone puts it on Vercel,

3:35someone puts it on Cloudflare, it has no idea what's going on. So I'm going the difficult

3:42route, which is, hey, build on your own harness. I don't have control over that, so it's really hard

3:48to build, but that's where I think the future is going. I don't want to lock people in. The code is

3:53their code. Put it on GitHub, run ci, CD, um, but still have a place to kind of deploy this and

3:59share it with your team really fast and govern everything that's going around there. So like, I'm

4:03curious, you know, if you were to have a hypothetical question that you would ask someone

4:08to really help them understand, like, and help you understand whether or not railroad actually

4:13solves a real problem for them, what would that question be? It would be, are you unable to keep up

4:19with your team's development with AI today? Basically, people are moving fast. People are

4:25experimenting. They've figured out that they can do a lot that helps them in their day to day job,

4:30and the company is unable to support that. So that would be my question. Are you holding your team

4:35back? How are they being held back right now? So the customers that I have, most of them,

4:42they had to wait a week or more to get something that they've built live because it needed to be

4:49approved by DevOps. It needed to go through kind of a specific process to make sure that it

4:54follows the standards that it has, the right authentication, that it can connect to a database,

4:58that it can use these API keys. So somebody that builds something that is really

5:05useful and they want to share with the team, they get discouraged. I don't want to go through this

5:08whole process. Um, some of the companies that I've spoken to, some people have just given up. They

5:12just they're just like, okay, I just run it locally. It's fine. Like people don't. I teach people how to

5:17prompt their own thing into existence, and it's not multiplayer. So there are companies out there

5:23where we're talking about being AI native, and they are holding employees back without realizing

5:28that they're doing so. They're like, hey, we've given everybody cloud code. We've given everybody

5:31codecs. Like, you know, we're we're, you know, AI forward. But you know, what's the next

5:38step? It's really interesting because, you know, when you talk about just like, hey, it's a week

5:43delay from somebody's vibe coding some internal tool to it going live. That's actually the least

5:48painful part, right? Because the painful part is the thing that doesn't happen because people are,

5:53as you said, discouraged or, you know, I think another thing that's really interesting about

5:57this is like, if somebody doesn't even know that something is possible or permissioned, they just

6:02won't even think to necessarily do it. So it's like until people had access to all these great

6:09tools to, you know, build things. And like a lot of people just weren't building things because they

6:14didn't know how to code. Right. But now we have this new thing which is like, you don't even know

6:18that you could actually build, like, the types of internal tools that are possible, or you wouldn't

6:23even just try because you don't think that there is this way to actually get them into other

6:27people's hands or to even easily use them yourself. So I think there's something really

6:31important about this, which is not just it's sort of saving people time or making it easier. I think

6:37by introducing something like what you're doing with real code, it might actually help encourage

6:43companies and individuals at companies to start to build a lot more that will actually help them

6:48and help the team, you know, do the things that really matter for a company, which means, you know,

6:52serve customers, right? Um, you know, get new customers and, and also like, coordinate internally.

6:59It's these are important things. And once you give people the ability to do that with the tool, um, by,

7:05by essentially enabling more people to build and deploy stuff internally, that seems like a really

7:10big opportunity. It's it's two sides of the same coin. There's people that are discouraged, and then

7:16there are the people that aren't encouraged. And it's really hard to measure the second one. It's

7:21like, what are the potential gains you can have when people see what everyone else is doing? Um,

7:27this is something that I actually lived at my previous company where basically we didn't have a

7:31customer facing product. We were developing algorithms for gesture detection for wearables.

7:36And so basically everything that we did was internal. Um, and I came in to kind of basically

7:41build that whole internal platform, like both the data platform, but it ended up being a lot of

7:44internal tools. Um, and there wasn't a place for this stuff. And once I set up the infrastructure

7:51in a way that, hey, this is a place where we can build these things. So much stuff came out of it

7:56that made model training faster. We collected more data. We were able to get better models. Leadership

8:02had a sense of what was going on and could direct the company better. It was like it made things

8:07exponentially better. Um, and company was acquired by order. Now, um, and, uh,

8:14having that internal engine moving was something that was really important in that case. And in

8:20that case, you know, when we talk about internal tools, sometimes we think about an external facing

8:23product and then internal tools as well as like a separate thing. But for some companies the

8:28internal tooling is the product. Like we didn't have a customer facing product. Well, not an open

8:34one that people can kind of sign up self-serve to. We were selling algorithms to, to, to um, companies

8:40that, um, that were manufacturing these devices. Most people think that starting a company without

8:45a co-founder is a bad idea. We believe the opposite, that solo founding will become the

8:50default way great companies get started. And that's why we built the Solo Founders program,

8:55where solo founders spend three months in San Francisco building solo together. Our alumni say

9:00it's like having co-founders, but getting to make their own decisions. And four cohorts in, we're

9:05starting to see just how much solo founders can accomplish. One secured a formal partnership with

9:11a major US government institution just five months after incorporation. Another hit 20,000

9:16GitHub stars and 3 million downloads, and a third got millionaire before making a single hire. The

9:23demand for the program continues to grow. Our first cohort got 1000 applications for six spots.

9:29Our fourth cohort got 4500 for ten. And today we're officially opening applications for cohort

9:36five. We'll select about dozen founders. I'll work closely with each of them and will invest

9:41$100,000 in every company. We kick off September 10th. If you're building solo or you're ready to

9:47start, apply at solofounders.com. It seems extremely

9:54interesting to realize, and I didn't really realize this until we met and we started talking

9:59about this. And also we should talk about sort of the history of kind of what you were working on

10:03before this and what led you to to work on this specifically. But, you know, it does feel like in

10:08many ways, a lot of things. Um, there's sometimes, you know, we build things that are customer facing

10:14and like a lot of, a lot of the abilities of, you know, models and code gen

10:21have really gone to us building new features and new products for customers. But in a way, it feels

10:28like in some in some ways we've kind of like, um, not spent as much time in giving the, uh, the

10:33abilities for people to do things internally. Um, and it feels like this is something that's

10:38lagging behind the customer facing, and it feels like a really big opportunity and one that

10:43seemingly the people who are using Railcode seem to really be lighting up on. Can you share a

10:47little bit more about, you know, you don't have to speak about the specific customers by name, but in

10:54the abstract. You know, there was this there's a customer who is working with, you know, CEO, CTO.

11:01It's a relatively small company. What was that like when they were using the product? Yeah. So

11:05just to tie back to what you were saying, I mean, I think most of the software. Going forward is going

11:09to be internal software. So we want to enable that. Um, as far as the company that you're speaking

11:14about, the CEO is versed and well versed in like using cloud code.

11:20But the CTO was not confident with the CEO deploying things. You know, you can tell a coding

11:27agent to deploy something on Vercel and it will do it. The CTO was not confident that it was going

11:32to follow the right security practices, that it was going to have the right authentication and

11:36wasn't confident, like handing the CEO like, hey, here are some like database keys that you can

11:41build on top of. And like maybe you're going to put them out there and like, we never know if this

11:45thing is actually secure. So what would happen is the CEO would go to the CTO and it would say, hey,

11:52I need this build. Um, and they're a small company. You know, you're taking time from the CTO that

11:56should be spending time on product. And sometimes the CTO was spending, you know, it's like, oh, it's

12:00going to be a two hour thing, and then it becomes a four hour thing. And the CTO, the week that we

12:05close, he was like, I actually spent like ten hours this week supporting this. And now the CEO can

12:09build everything himself. And the CTO is fine because he knows that Railcode is like a secure

12:14environment for this. Um, there's all the permissions are there, all the connectors. He's

12:19kind of audited all of that. And he's happy with the CEO being able to build things on top of

12:24there. Um, and actually he's been looking at what the CEO was building and said, well, actually I can

12:28build things here too, and it's going to be faster even than even me as an engineer. It's going to be

12:33faster than me trying to set it all up the right way to deploy it elsewhere. Um, so they've been

12:37building a lot. They're kind of making Railcode that the place where work gets done in a lot of

12:43ways, um, particularly now that we have agents and they can interact with, um, the data that they've

12:48brought in and the apps that we've built on slack, for example. So they're doing some really

12:53interesting stuff with real code. It's really cool because in a lot of ways, when you think about

12:57permissions and things like that, you think, oh, this has got to be mostly used by larger

13:02companies that really need to like tamp down on things, right? Make sure that everything is secure.

13:08But at the same time, small teams, small companies, as soon as you have customer data, you need to be

13:13really, really mindful of, like who's getting access to things, how they're getting access to it.

13:18And ultimately, it's really great to see that this example, you're helping the CEO get

13:24unblocked and you're also helping the CTO not have to spend as much time on building things

13:31that are important but aren't core product. I think that that was another thing you've told me

13:36is that, you know, all this stuff is important, but it's not core product. So sometimes the people who,

13:42you know, who might have to like, deal with the requests and the work associated with getting

13:47these non-core products, these internal important internal tools out there are, you know, essentially

13:52getting pulled away from core product work and customer work, which, you know, is not great. I'd be

13:58really curious to hear, um, and for you to share a little bit about, kind of, you know, what you were

14:03doing when you and I met and you joined Solo Founders Program and a little bit of the

14:08backstory before the company that you were working on most recently that that you joined and

14:13then was acquired by aura. Um, can you share a little bit more about the backstory and then sort

14:17of like the context in which you joined Solo Founders Program? Yeah. So I'm a I'm an engineer.

14:23I've always been an engineer full stack, but always had a focus on backend and infrastructure.

14:29Um, I found that dealing with complex infrastructure is really motivating, and

14:34particularly because if you do a great job, like people don't see what's done, um, but you're

14:39simplifying something really complex into something that just works. Was one of the early

14:43employees at PostHog owned a lot of the infrastructure there. Um, and also built internal

14:49tooling there. Um, joined this company. Finnish company called Double Point where I was owning

14:55infrastructure and and again, it was building this whole kind of internal product. Um, and when we met,

15:02I was early in my founder journey. Um, I had pivoted off of another product,

15:08and I was validating an idea that, um, I invalidated, um,

15:15for a few kind of different reasons. And I was doing a little bit

15:22of, uh, soul searching, and I was looking back at all the notes that I had from people that I had

15:29spoken to about the previous ideas that I had and products that I'd worked on, and correlating that

15:35with my experience and things that I've done in the past. And this was like a clear

15:41fit. It's, um, it's enabling people to do things that they weren't able to do before and making it

15:47really simple for them to do so. There are really complex infrastructure problems that I have to

15:52solve in the background that hopefully you don't even see them or you never feel them, they're just

15:56solved for you. And that that's really motivating. And it ties back to things that I did at PostHog

16:01and things I did at double point, so it was quite a natural fit. I looked back at my notes. I had

16:07people mentioning this problem in relation to other things that I was working on. Um, so then I

16:13decided to jump on this and uh, coincidentally, actually, or maybe not, some of the stuff that I

16:20was working on in the past actually builds up to what I'm building now. So I think in some ways

16:24it's actually an evolution. Um, the previous product was also a security infrastructure minded

16:29product, and I've actually reused some of the code in real code. It's really cool. And I think that

16:34there's something, uh, something really important to note there, which is it's that through line.

16:39Right? You talk to a lot of people who build companies, and oftentimes maybe they're skating

16:45around various ideas, but usually the thing that they end up working on is some sort of

16:50continuation, some sort of thing where we call it like pulling the thread, right? You continue to

16:54pull the thread, you continue to sort of explore in an area and see where it takes you. It's really

16:59cool to see where this has taken you. And I remember sort of the the time when you were sort

17:03of going from the last idea to this one and sort of that that journey of like reflection and

17:08trying to look through your notes and think about things that you enjoyed. And I think that's

17:13another thing that's really important. It's like, I remember we were talking, you really enjoy the

17:17stuff that you're working on now. And I think that it's very easy when you're sort of in the idea

17:22search space, you can kind of sometimes get sucked into something that maybe sounds like an

17:27attractive business idea, but if you're being honest, it's maybe not the thing that actually

17:30causes you to light up. And I think that some people really need to not just have an attractive

17:35business idea. Even if it starts to get momentum, they really want to have something that they have

17:39some like passion and or some experience and and it really feels like real code. Is that for you? Oh

17:44yeah. I mean, that's why like, everyone's talking about my website, and my website has like a little

17:49bit of a playground in it, and it has like a roller coaster and everything, and, and what that

17:53website shows is like, it's fun. And the thing is, it's fun for me to build real code. It's actually

17:59I'm having a lot of fun building with rails code. And actually, as I was iterating on the website, I

18:05actually, um, I was having a conversation with a customer and I asked him, is real code fun? Like we

18:11were talking about, like how useful it is and all these different things. But I stopped it and I

18:15said, it's real code fun. And he was like, yeah, it's fun because building things is fun, and you're

18:21allowing me to build things fast and without having to deal with the stuff that I don't like

18:25taking care of, which is like the permissions and the security and the infrastructure. And you're

18:29not taking me out of my workflow either, because I'm using, well, in their case, open code. So you're

18:33not kind of forcing me into something else. So it's fun. And I think the website shows that

18:38because I'm having fun building it and I'm having fun using it, that's awesome. And I feel like if I,

18:43if I were to think of like a sort of a big company that's like high growth company right now

18:48that that I feel like really exemplifies fun, at least in the way it presents itself to the world.

18:52Its post hoc. So can you share a little bit more about like how? I think that a lot of people are

18:58like, wow, you super early at Post talk. Like, how did that happen? Like how how did you find the

19:02opportunity? How did they find you? Uh, because I think that would be informative for people who

19:06are maybe looking to join something that becomes, you know, the next post. Org. Um, which, which is rare,

19:12but it's like it's possible. So I'd love to hear that. And then it also love to hear sort of what

19:16your thinking is around fun and like what the team over there does that makes it fun. Um, sort of

19:22what you took from inspiration from them. Yeah. So I got to them because of the handbook. I think a

19:27lot of people did. And this was, what, 5 or 6 months into the company and they

19:34had a whole handbook written out about how the company's going to operate. I think it wasn't even

19:38about just how the company operates, but about how it's going to operate, because there weren't that

19:42many employees to be operating in the first place. Um, so the handbook was what caught my eye. Um, and

19:50back then we were doing work trials, like three day work trials. And you could see from the work

19:54trial that the culture was what was told in the handbook. It wasn't like wishy washy stuff. Um, so

19:58that's what really got me interested. And I think it matched really well with my personality. Um, and

20:04I feel like I came in because I related to the culture, but consequently I added to the culture

20:11as well. Um, and I think what they do. Right. I mean, they do a lot of things, right. Um, but a lot of

20:16autonomy to people that they hire great people. Um, people that are aligned with their values. Um, the

20:21values are for real. And then people that work hard and, and, uh, do great work. Um, and they give

20:28them a lot of autonomy. No teams. There are larger than six people. Um, people have the freedom to

20:35move around, build new products, start initiatives. I think most of the products, some of the core

20:41products have come out of hackathons. Session replay is one of the massive things they do today.

20:46I was part of the hackathon team that built that kind of V0 of that. Um, I won't get most of the

20:52credit. It was Tim and Carl, but like I was, I was I was there and it was built at a hackathon and so

20:56were a lot of products. So yeah, I think there's a lot of stuff that they do. Right. But the autonomy

21:01is kind of like one of the top ones. And the transparency, which is reflected in the handbook.

21:05Two quick questions on that before we go to the demo, which is like, I think something would be

21:09really fun for people to see, even just the website we could scroll through. Um, okay. So what

21:15is, uh, what is something that you feel like you've applied from either that post hoc or, or the

21:20company after? Um, and, and then like also mascots like what's like, how important is the

21:27mascot? Um, where where's the Railcode mascot? Yeah. I don't have a mascot yet. I need to figure one

21:33out. Yeah. Do you think it's important, though? Like, is there aren't that many mascots, if you think

21:38about it. Is it important? I don't know if it's important, but it is. It is. I. I'm sure it's useful.

21:44Certainly fun. It's fun and fun. It's useful. Yeah. Um, yeah. I don't know if I can say it's it's

21:50necessarily important, but it's something for me to potentially think about. Um, and, um, what was it,

21:57what was it? I mean, in terms is there something that you've already applied in terms of how

22:00you're building Railcode that you either took away from postdoc or other work experiences? I

22:06think a lot of how I do engineering is very related to how to do it there. Um, move fast,

22:10iterate really fast, respond to customers, learn from customers actively. I think there's a lot of

22:16stuff about how I want to build a company that has a lot of synergy with how they build a

22:21company. As far as, um, when employees do come in and things of that nature. But right now, I think

22:27just basically a lot of how I am as an engineer aligns with how they do engineering. And that goes

22:33both ways. It's not like, I mean, the culture influenced me, but also I joined because the

22:38culture was a certain way. Um, so as a solo founder right now. That's kind of how I apply it. It's a

22:43really fast iteration and learning from customers really actively. That's awesome. Why don't you? Why

22:48do you share a little bit about kind of what railroad looks like today? Yeah. And uh, and we'll

22:52wrap up. But I think this has been amazing. Thank you for doing this. Let's let's hop into it. Cool.

22:57So yeah, this is my website. I'm pretty excited about it. I mean, it's, uh. Of course I built it. And

23:02so it's, uh, it's a reflection of you. And I think that's I think that's honestly like, what the most

23:07important thing is when you're getting started is you want somebody to represent who you are. Yeah.

23:10And I want people to see that, you know, this is something that I care about. Um, so this is the

23:14website, but this is the app, right? This is the more interesting part. Um, so this is like a demo

23:18organization and like we talked about real code is this secure environment where you can put

23:22these tools, tools, meaning apps and agents, and they weave pretty magically inside of real code,

23:29like apps are immediately accessible to agents without any extra work. So you build something

23:33custom and an agent can already operate on top of that data. So because I think that's the future

23:37where we're going right now, it's a lot of UIs that have agents. And I think we're going towards

23:42a place where it's maybe agents that have UIs. So so we're kind of going towards that. But I was

23:47preparing this demo here and, and I noticed that this Kanban app is actually on like light mode,

23:53and it doesn't seem to have dark mode. This is like a demo organization. So I spent I just I just

23:58fired off a colored code and I just said add dark mode support. Um, and this is like, you know, a small

24:04thing. It's not like an actual. But I just wanted to show, like, what the development looks like with

24:09real code, where I'm building in cloud code, and then I'm going to deploy. I could tell the agent

24:13to do this, but just for the sake of of the demo, I'm going to go ahead and say real code deploy. Um,

24:18and then we're going to just wait like five seconds and then the deploy is live and now it

24:24has dark mode. That's cool. And essentially what's happening here is you're using cloud code, which

24:29is the thing that you're used to if you have any skills set up. I mean, maybe you're using

24:33impeccable, which uh, which Paul was on the podcast, uh, for your design stuff like there are different

24:40skills and things that you have set up the way you do it, you're not having to use some other

24:43interface, and then also you're able to pull in your own data sources that have been permissioned

24:49across Railcode. Exactly. So that's exactly right. So basically you're building locally and we're

24:55governing all the data connectors with granular permissions. So you connect your Postgres and you

24:59say, hey Julian can access this on our Postgres instance and Yakko can access this. Or hey, we

25:06connect Google Calendar and these people can access it or these people can access it. So we do

25:11have another demo app here which actually has some data, which is this. Oh, we just went to

25:15combine and I just clicked it again, which is the CRM. So this CRM here kind of showcased a little

25:22bit of like all that real code can do. Building this didn't require explaining any

25:29technical details around, hey, get a database. Hey, get file storage. It just works. So you just say,

25:34hey, I need a CRM. I want to store files on my customers. I want to store data on my customers,

25:39and it just has the primitives to build on top of. So that's kind of the magic part that we do

25:44building with cloud code. But we do have this magic SDK that connects to these provided

25:48services, which are like database file storage APIs, for example. So the CRM, I can manage it from

25:55this chat, right? I can I can ask things and I can create deals right from this AI feature. And a

26:01non-technical person could have built this because they just need to say what they wanted,

26:05and it just has all the primitives to build it. But at the same time, an engineer that wants to

26:10own the code and have it own version control, they have it too. So it serves both purposes. And we

26:16were talking about connectors. This CRM specifically connects to granola for example, so I

26:21can connect my granola account and import data from there. And all of these connectors are

26:25governed within this Railcode space. It's super cool. I mean, like you can just imagine this is not

26:32this is you know, this is real, like where people go and they just vibe code stuff and then they're

26:37like, put a little password line in there. You know what I mean? Like a password input. It's not like

26:42actual secure stuff. And then they deploy it somewhere. I'm like vercel or something. And you

26:46have this, you have all these issues with like people, you know, in these companies like building

26:51their own little apps and then trying to deploy and like, this is the this is the thing, you're

26:55making it so that people can do it. Login is already handled for them. Right. All of the all the

27:00access to the right things is handled. So you make it super easy for people. It's it's really cool. Um,

27:06this is awesome. Like, you just launched like two days ago. Um, or if you're, if you're watching this,

27:10maybe it's maybe it's about a week ago, but this is like the the official demo. Uh, anything else

27:15you want to say is like words of wisdom, uh, or or comments like, where should people check this out?

27:21What's the URL? It's going to be in the show notes, of course. And then also like any advice for solo

27:25founders? Yeah. So basically there are a lot of teams out there that are doing what you're saying,

27:30like where they have like these tools where it's just like a password input and there's a shared

27:34password that they share around on slack. And it's like single player. Like everyone acts as the same

27:38user. Like Railcode. By default, it's like multiplayer. Like it already knows. Like who the

27:43users are. So you can find it@railroad.dev. Um, so that's. Yeah. Rail

27:50code. Pretty self-explanatory. How to spell that and advice for solo founders. I think it would

27:56have to be to just get in touch with yourself and the things you want to build. Um, because that's

28:02the way you're going to build, um, something that means something to you, that means you're going to

28:07work harder. That means you're going to stay at it longer. That means you're going to enjoy it more,

28:11and consequently, you're going to serve your customers better. Um, it's clearly been like that

28:15for me, um, early in my journey, very, very clearly. Right. But it's

28:22working on something that I'm excited about and that's like an extension of me. It's it makes

28:26things a lot easier. Amazing. Well, thanks for doing this demo for the audience, please. If you like it,

28:31tell your friends about, uh, Railcode. And, um, we'll put Yakko's Twitter and the show notes, so you can

28:37please give him a shout out as well. And Yakko, congrats on, uh, on the launch and so glad you're a

28:43part of SFP. Yeah, thanks. Appreciate it. If you enjoyed this conversation, we would love it. If you

28:48can share solo founders with everyone you know, particularly people who are considering starting

28:53companies solo or who are already doing it, you know, the entire goal of what we do is to

28:57normalize solo founder and encourage more people to solo founded, instead of to end up with

29:01co-founders of convenience, if you'd like. And we really appreciate it. You can go. Leave a review on

29:06Apple. You can go give us a thumbs up. You can subscribe on the YouTube channel. Anything helps.

29:10And of course, if you are starting a company or considering starting a company, you should go look

29:15at the Solo Founders Program. We work together with you in San Francisco alongside a bunch of

29:20other solo founders. The idea is it's much better to be solo together than to be solo alone. I'll

29:26spend a lot of time helping you, and we also invest $100,000 in your company. So if you're

29:31excited to learn more about that, go check out solofounders.com/program.

If you're already solo, you're early.

Whether you're solo founding now or still exploring, stay in the loop.

© 2026 Solo Founders. All rights reserved.

Privacy PolicyTermsSan Francisco, California