Podcasts about Kudos

24,958 minutes of Ask Iliza later, we're celebrating staying fresh for 400 episodes! Join us for new questions and old memories, and you can get 40% off your first month or year of the Ask Iliza Anything Patreon with the code MAYNIP. Episodes we revisited: May Nip (10/10/2018) Hot Lettuce Is Never A Bop (9/2/2020) Power Fluting (12/14/21) An Italian Greyhound Named Susan (7/19/2022) Learn more about your ad choices. Visit megaphone.fm/adchoices

"The next episode of my Club Mixes was live streamed at the Ibizastardust radiostation on Saturday May30, with title ‘Sunrise'! Inspired by the Komm Schon Alter festival I have recently attended, this mix of 14 stunning tracks is a nice range of melodic and progressive house to start with and transitioning nicely into other uptempo house beats As always Kudos

Kudo er en død lejemorder. Fumika er en helt almindelig ung kvinde. Der er ingen grund til at deres veje skulle krydse, men det er lige præcist dét, der sker i denne japanske action-komedie. Som den eneste kan Fumika se den døde Kudo og Kudo kan oven i købet kontrollere Fumikas krop! Sammen tager de kampen op mod de gangstere, der står bag Kudos død. https://www.ikassenshow.dk/2026/06/i-kassen-1273-ghost-killer-2024.html

Mike and Eli put the Bearshark uniforms on again and start playing for real; Mike plays a tournament; a quick minute with Dr. Bob Rotella. Want bonus content? Join the Velcro: patreon.com/chasingscratch  Kudos to Titleist - Titleist.com Kudos to Footjoy - Footjoy.com MUSIC CREDITS: "Dangerous" by Kevin MacLeod is licensed under a Creative Commons Attribution license (creativecommons.org/licenses/by/4.0/) Source: incompetech.com/music/royalty-fre…isrc=USUAN1100414 Artist: incompetech.com/ "Summer Noir" purchased via PremiumBeat.com "Meaningful Change" purchased via PremiumBeat.com "Amazing World Time Lapse" purchased via PremiumBeat.com The Lincoln Commercial: https://www.youtube.com/watch?v=bPLFqtV7dGY  "Epic Battle Speech" is by Wayne Jones "C Major Prelude" is by Bach "Air to the Throne" is by Doug Maxwell "Connect The Dots" purchased via PremiumBeat.com "The Latest Scandal" purchased via PremiumBeat.com "The Old Tale" purchased via PremiumBeat.com "Philosophy" by Eskimotion purchased via PremiumBeat.com Mixed by Lenny Sterner Copyright © Drupelets Media LLC

Brett, Joel and Tess brave a thunderstorm in the Brunswick studio to bring you episode #196. The team debriefs the stellar results from our Australian professionals racing across the globe before jumping into training weeks. The crew put together strong training weeks and discuss (not scientifically) how Sauna hats are supposed to work. FTK "Friend Of The Show" Sean Gambier-Ross writes in with a question regarding key marathon workouts than can be used to predict race-day performance. Give Some Kudos sees three non-running-related (at least not directly) submissions, while TWHSOITWTWATSA brings it back to the realm of running. SIGN UP TO OUR PATREON TODAY: www.patreon.com/forthekudos Instagram: https://www.instagram.com/forthekudos Facebook: https://www.facebook.com/forthekudos TikTok: https://www.tiktok.com/@forthekudos Brett: https://www.instagram.com/brett_robinson23 Joel: https://www.instagram.com/joeltobinblack Tess: https://www.instagram.com/tesssicaa_/  

(Disclaimer: Click 'more' to see ad disclosure) Geobreeze Travel is part of an affiliate sales network and receives compensation for sending traffic to partner sites, such as MileValue.com. This compensation may impact how and where links appear on this site. This site does not include all financial companies or all available financial offers. Terms apply to American Express benefits and offers. Enrollment may be required for select American Express benefits and offers. Visit americanexpress.com to learn more.  ➤ Free points 101 course (includes hotel upgrade email template)https://geobreezetravel.com/freecourse  ➤ Free credit card consultations https://airtable.com/apparEqFGYkas0LHl/shrYFpUr2zutt5515 ➤ Seats.Aero: https://geobreezetravel.com/seatsaero ➤ Request a free personalized award search tutorial: https://go.geobreezetravel.com/ast-form If you are interested in supporting this show when you apply for your next card, check out https://geobreezetravel.com/cards and if you're not sure what card is right for you, I offer free credit card consultations athttps://geobreezetravel.com/consultations!Timestamps:00:00 Meet Tikue and Kudos01:53 From First Card to Points Pro03:33 Kudos Platform Overview04:41 Onboarding and Data Linking07:37 Valuing Rewards and Benefits10:31 Credits Overspending Trap12:50 Card Discovery by Spend16:56 Lounge Access Valuation22:57 Annual Fee Worth Calculator24:55 Portfolio View and Nuance31:06 Lounge Crowds and Certainty35:33 Extension and Bill Negotiation38:10 Pricing and Free vs Premium39:20 Wrap UpYou can find Julia at: ➤ Free course: https://julia-s-school-9209.thinkific.com/courses/your-first-points-redemption➤ Website: https://geobreezetravel.com/➤ Instagram: https://www.instagram.com/geobreezetravel/➤ Credit card links: https://www.geobreezetravel.com/cards➤ Patreon: https://www.patreon.com/geobreezetravelYou can find Tikue at:➤ Website: https://www.joinkudos.com/ Opinions expressed here are the author's alone, not those of any bank, credit card issuer, hotel, airline, or other entity. This content has not been reviewed, approved or otherwise endorsed by any of the entities included within the post. The content of this video is accurate as of the posting date. Some of the offers mentioned may no longer be available.

Eli returns to the scene of the crime to face an old foe; Mike takes on an 8th grader; Josh Nichols comes by to lay out the full details of our individual practice plans.  Want bonus content? Join the Velcro: patreon.com/chasingscratch  Kudos to Titleist - Titleist.com Kudos to Vuori - vuoriclothing.com/chasingscratch 20% off your first purchase Kudos to LMNT - drinkLMNT.com/chasingscratch  MUSIC CREDITS: "Dangerous" by Kevin MacLeod is licensed under a Creative Commons Attribution license (creativecommons.org/licenses/by/4.0/) Source: incompetech.com/music/royalty-fre…isrc=USUAN1100414 Artist: incompetech.com/ "Summer Noir" purchased via PremiumBeat.com "Meaningful Change" purchased via PremiumBeat.com "Amazing World Time Lapse" purchased via PremiumBeat.com The Lincoln Commercial: https://www.youtube.com/watch?v=bPLFqtV7dGY  "Epic Battle Speech" is by Wayne Jones "C Major Prelude" is by Bach "Air to the Throne" is by Doug Maxwell "Connect The Dots" purchased via PremiumBeat.com "The Latest Scandal" purchased via PremiumBeat.com "The Old Tale" purchased via PremiumBeat.com "Philosophy" by Eskimotion purchased via PremiumBeat.com Mixed by Lenny Sterner Copyright © Drupelets Media LLC

Take the 2026 AI Engineering Survey and get >$2k in credits and AIE WF tickets!On the product side, everyone is getting Computer - Perplexity, Manus, Cursor, and so on. Meanwhile on the research side, agentic evals like TerminalBench and GDPVal are also assuming computer (Harbor). On both ends, the consolidating LLM OS stack has become a standard toolkit, and Daytona is one of a small set of AI Infra companies that are booming because of it.“The end of localhost” has been Ivan Burazin's obsession for more than a decade.Something that is all too familiar…Long before agents became the default way people talked about software development, Ivan was already chasing the idea that development should not depend on a fragile local machine. CodeAnywhere, one of the first browser-based IDEs, was an early attempt at that future: move the development environment into the cloud, make setup reproducible, and free developers from the endless “works on my machine” tax.The thesis was directionally right, but the market wasn't ready yet.However, agents changed that. They do not care about a laptop, desk setup, or favorite editor. They need a computer they can access through an API: something stateful enough to keep working, fast enough to spin up instantly, flexible enough to resize, isolated enough to be safe, and composable enough to run the messy real-world workflows that real software engineering actually requires.Daytona isn't just selling “sandboxes” in the narrow code-execution sense. It is the latest version of Ivan's original localhost thesis.In this episode, Daytona's CEO joins swyx to explain why AI agents need more than code execution boxes: they need composable computers, stateful sandboxes, instant startup, dynamic resources, and infrastructure that can survive workloads going from zero to 100,000 CPUs.We go deep on the new agent compute market: Daytona's hard pivot from human dev environments to AI sandboxes, the New Year's Eve MVP that customers begged for, why Daytona runs on bare metal with its own scheduler, how one customer runs almost 850,000 sandboxes a day, and why RL/eval workloads went from 0% to roughly 50% of usage in just months. Ivan also explains why agents need Windows and macOS machines, why CLI may matter more than MCP, why Kubernetes is painful for this workload, and why the future AI cloud may look more like Stripe than AWS.We discuss:* How Daytona grew out of CodeAnywhere, Shift, and the “end of localhost” thesis* Why Daytona pivoted from human dev environments to AI sandboxes* Why agents need composable computers instead of disposable code execution boxes* The New Year's Eve MVP that customers chased API keys for* Why Daytona chose bare metal, stateful snapshots, and its own scheduler* How Daytona spins up one sandbox in ~60ms and 50,000 sandboxes in ~75 seconds* Why Daytona's biggest customer runs ~850,000 sandboxes a day* How RL/eval workloads create zero-to-100,000 CPU spikes* Why RL workloads went from 0% to roughly 50% of Daytona usage* Why customers compare Daytona against EKS/GKS and say they're “never going back”* Why every AI agent may need a computer, including Windows and macOS environments* The Apple licensing constraints that make macOS sandboxes hard* Why CLI gives agents more power than MCP* How open source helps agents integrate Daytona* Why agent-generated PRs may break today's CI/CD assumptions* Why AI SaaS companies reselling tokens may face a cold shower* Why the AI cloud may look more like Stripe than AWSIvan Burazin* LinkedIn: https://www.linkedin.com/in/ivanburazin* X: https://x.com/ivanburazinDaytona* Website: https://www.daytona.io* X: https://x.com/daytonaioTimestamps* 00:00:00 Hook* 00:01:12 Introduction* 00:03:15 CodeAnywhere, Shift, and the end of localhost* 00:05:58 What Daytona is: composable computers for AI agents* 00:08:07 The pivot from dev environments to AI sandboxes* 00:10:17 The New Year's Eve MVP and customers begging for API keys* 00:12:56 Bare metal, stateful sandboxes, and Daytona's scheduler* 00:17:28 60ms startup, 50,000 sandboxes, and 850K daily runs* 00:21:53 Spiky RL/eval workloads and the new agent infra problem* 00:28:12 RL workloads, Kubernetes pain, and dynamic resizing* 00:33:31 Why every AI agent needs a computer* 00:38:48 macOS sandboxes and Apple's licensing problem* 00:44:28 Why CLI may matter more than MCP* 00:48:11 Open source, GitHub stars, and agent integration* 00:53:11 Git, CI/CD, and agent collaboration bottlenecks* 00:58:15 Founder life and building a 25-person infra company* 01:02:44 AI SaaS, token resale, and API-first business models* 01:06:10 GPU sandboxes, data centers, and compute growth* 01:09:48 Why the AI cloud may look more like Stripe than AWS* 01:11:26 Closing thoughtsTranscriptIntroduction: Daytona, CodeAnywhere, and the End of LocalhostSwyx [00:00:02]: Okay, we're in the studio with Ivan Burazin, CEO of Daytona. Welcome.Ivan [00:00:07]: Thanks for having me, man.Swyx [00:00:08]: Ivan, you and I go back.Ivan [00:00:10]: Way back.Swyx [00:00:11]: How I don't even know how, you found, did you reach out or, for Shift.Ivan [00:00:17]: I reached out to you. The reason was you - we were just - we were thinking about I was one of the co-founders of CodeAnywhere, the first browser-based IDE, and so we were thinking a long time of, localhost should die. And you had this article.Swyx [00:00:29]: End of localhost.Ivan [00:00:30]: Then I reached out to you because of that, and then we talked, and I was actually at a different job and learning about I was the head of, developer experience, and you were quite well-versed in that, and I actually reached out to you, among other people, how do we go about that? What are the key things and whatnot at this point in time? And you were nice enough to take the call, and I remember I was late on your call with you.Swyx [00:00:51]: I don't remember.Ivan [00:00:52]: I remember because I was with my then I'm thinking of a girlfriend or wife at that point in time, I'm not sure. It's the same person, so that's great, and I was late ‘cause we were, in, Italy on, vacation, and then I was late for something. I felt so bad, and you were so nice to be, good about.Swyx [00:01:10]: The reason I'm nice is because I'm also late to other people, so it's like, who's, who's without sin here, yeah, so I have to, for those who don't know, InfoBip Shift, there's this whole thing that, you did in the past, and, and that was basically one of the inspirations for me starting AI Engineer, which is like, I have to thank you for giving me that push to be like, “Oh, you can, you can build and sell conferences?”Ivan [00:01:34]: I remember you asked you asked me at the beginning to give me advisory shares, and I was so focused on what we were doing, I said no, and I should've took the advisory shares. So I'm sorry, dude. But anyway.Swyx [00:01:43]: We're not, we're not venture backed.Ivan [00:01:44]: No, it doesn't matter.Swyx [00:01:45]: It's Yeah, anyway, so I think what's impressive about you is that CodeAnywhere is the thing that you've been trying to build, and, you kind of put it on hold and then came back after InfoBip. Just give us the story, do you - the story and the origin story, going into Daytona.From CodeAnywhere and Shift to DaytonaIvan [00:02:05]: Sure. Like, really way back, me and my co-founder have been together. I say this, I've said this multiple times, it's like we were married and divorced and married. Some people actually ask me is my co-founder my partner. they thought it literally. It's not literally, but we have done multiple companies together, and to your point, we had this shift where we went from the CodeAnywhere to the conference called Shift, and then back to, Daytona. We originally started stacking servers, doing like virtualization in the early 2000s and, routers and doing basically all these things, at a foundational level, and that was a services company which we sold to focus on what my co-founder actually invented, which was the very first browser-based IDE, right, I say the first. Before us was actually Heroku. They did it for a very short time until they became Heroku. But outside of them, we were the only one, and it was called.Swyx [00:02:55]: There was Cloud9.Ivan [00:02:57]: Cloud9 came out slightly after us. There was Replit, which came out when we stopped doing it, Replit came out, and they have been successful since then, which is great. There was Nitrous.io. There was quite a few that existed at the time, but it was like too early. But the interesting part is that we, at that point in time, because there was no VS Code, there was no Kubernetes, and Docker had just started when we Or I'm not sure if it was even public at that point in time. And so we had to build everything to the whole stack ourselves and that was the key learning that we brought into and that we've been using in Daytona today. So it was super early. There's about 3 million people used CodeAnywhere. It was slightly, it was angel-backed more than venture-backed. We ended up paying everyone back because it didn't have that sort of scale. But, three years ago, we started something similar with Daytona, which is not what we are today, but it was automating dev environments for human engineers, the basically the underlying stack of CodeAnywhere. And then we did a hard pivot last January to sandboxes. And so here we are.Swyx [00:04:01]: Historic pivot, yeah, and, it's one of those things where, I had independently invested in CodeAnywhere, but also in E2B, and then both of you pivoted into the same thing, and I'm like, “F**k.”Ivan [00:04:12]: You invested, you invested in Daytona. You invested in Daytona. But you were the first If we had not got your check, we wouldn't have done it.Swyx [00:04:18]: No way.Ivan [00:04:19]: No, it was like, “We have to get him on board first,” and you were that kicker that we, that got us off the ground.Swyx [00:04:23]: No, because you were putting me on your pitch deck, man. I was like, “Man, this is like a good trip if I don't invest.”Ivan [00:04:29]: That's because it was your quote. It's like we.Swyx [00:04:30]: Yeah. It's the end of localhost.Ivan [00:04:31]: Did a bunch of research about end of localhost and who was interested in that,.Swyx [00:04:34]: No, that's like, I put, I wrote that blog post, and every single company in that field reached out to me, and then every VC who was receiving those pitches then also had to call me and, talk it, talk through it with me.Ivan [00:04:47]: It's finally happening though.Swyx [00:04:48]: It was really super interesting.Ivan [00:04:48]: It's finally happening.Swyx [00:04:49]: It's finally happening.Ivan [00:04:49]: Yeah, it's finally.Swyx [00:04:49]: It's finally happening, with maybe sort of non-human users. Yeah, so what is Daytona today? Let's get like a quick description. I'm wearing the shirt.What Daytona Is Today: Composable Computers for AI AgentsIvan [00:04:58]: You're wearing the shirt. Yes,.Swyx [00:04:59]: It says, I think your branding is very good. Like, it's very consistent. It runs AI code. Like, it cannot be simpler.Ivan [00:05:05]: Exactly, but we're gonna probably have to change that.Swyx [00:05:07]: Oh, s**t.Ivan [00:05:07]: It's also a subset of what we do. Unfortunately, we really love this, Run AI Code is super simple. People interpret it different ways. I think we've given out 5,000, 6,000 of these shirts. People wear them with pride because it doesn't really market about us.Swyx [00:05:21]: Yeah, Daytona's on the back.Ivan [00:05:22]: It markets the back. It markets to the person itself, so I think we did a really good job on that one. But it is also a subset of what we do, because people, when they think about Run AI Code, they just think about these small, let's call it isolates, code execution boxes that, you send some code, you get an output. Whereas what Daytona is today is essentially composable computers for AI agents. It is, the market calls them sandboxes which can be misleading.Swyx [00:05:44]: All these things. All these things on.Ivan [00:05:45]: Yeah, exactly, ‘cause it can be misleading ‘cause people usually think about sandboxes as a demo or a test environment versus a production-grade environment. But what Daytona does, if you think of the laptop that you have in front of you or the computer that's over there, or, my wife is an architect, so she has like a Windows with a 3D graphics card inside to do 3D rendering. Like, as humans, we have different computers or different compositions of computers. And our belief is strongly that agents today and going forward will need all these different compositions of computers to do different types of tasks. And so we offer that basically through an API.Swyx [00:06:19]: Yeah, to give people - I'm trying to sort of front-load all the aha moments or the wow moments so that people can, stay engaged and click like and subscribe. the market is exploding, right? Like, you have been reporting 74% month-on-month growth, and it also, it's just been growing for a while. Like, it's been going like this. And every single - It's not just you guys. It's every single.Ivan [00:06:41]: Everyone, yeah.Swyx [00:06:42]: Sort of, compute provider. I don't know if you agree with me saying compute provider or not.Ivan [00:06:48]: It's fine.Swyx [00:06:48]: Yeah. So like organically PLG-driven growth, but also enterprise is doing super well, I think I wanna rewind to January of last year when you did the pivot. Like, so you obviously called this market early, and you were positioned for it, and you are now one of the market leaders. But what was the insight that made you do the pivot?The Pivot: From Human Dev Environments to Agent SandboxesIvan [00:07:06]: The insight that made us do this pivot is the quarter before that, so end of 2024, when we had - Basically, we did a demo with - I don't I think we discussed this as well, Devin was not public. You actually gave me access to Devin at that time. So Devin.Swyx [00:07:25]: I did?Ivan [00:07:26]: Yeah, you gave me access.Swyx [00:07:26]: I don't think I was supposed.Ivan [00:07:27]: Yeah, exactly.Swyx [00:07:28]: Yeah, I.Ivan [00:07:28]: So it doesn't matter. You.Swyx [00:07:29]: Yeah. I gave like three friends access.Ivan [00:07:31]: Yeah, or it was a call and you showed it to me. It doesn't matter. but OpenDevin was available, which is now called OpenHands. And so we're like, “Oh, this seems to be a thing. This is not public. Let's take our for human automation of dev environments and take, OpenDevin and launch that as a SaaS.” And we did that. Not very many people signed up and used it, but a lot of people reached out that were building agents, and they were like, “Hey, my agent needs a compute sandbox runtime,” whatever you wanna call it. I forgot what it was called at that point. And then we were like, “Oh, amazing. This is a new market. Here is our infrastructure. Here's our product, and go.” And what we found really fast, soon, was that people did not like what we had built. It didn't work. And I remember talking to people at the beginning when we're doing this, the sandbox we're building for agents. People were like, “Oh, why is it different? It's the same thing. We have like EC2, we have VMs, we have all these things.” But we saw that everyone we gave it to, it was like 20, 30 people, they all said, “No.” Like, “This is not what we need. This sort of breaks.” And basically, me and my co-founder not knowing a lot about - ‘cause we're infra people. We're not AI people. So I basically took it upon myself to like watch every single podcast that exists, including all of, all of these and all that, and sort of get up to date, read all the blogs, like get, understand what's going on.Swyx [00:08:45]: Do you wanna shout out who else was useful, just in case people are also looking.Ivan [00:08:49]: Generally we -, I looked at There's a few of podcast, different segments and different types. So there's you guys, No Priors, Bill Gurley's was great while.Swyx [00:09:04]: VG2, yeah.Ivan [00:09:05]: Yeah, while it was around. So there's a few. 20VC is interesting from a different dynamic, and some are different dynamic. But there was, also Red Points.Swyx [00:09:14]: We're not really about the compute market.Ivan [00:09:15]: It was also already - Sorry?Swyx [00:09:16]: You're, you want - You're looking at the agent infra market.Ivan [00:09:19]: I was looking at the agent market and the AI market in general and sort of understanding who are the players, what the perception, and how that goes. And like obviously you complement this with like going to conferences, going to events, going to meetups, reading white papers, like doing all the things that you have to do to understand what's happening. And so when we figured, when we sort of had an idea of what we had to build, literally over the New Year's Eve, literally on New Year's Eve, I half vibe coded the first MVP, first minimal viable product of what Daytona is today. And I went to sleep at like 3:00 AM or something like that. I was doing - I just put my like baby daughter and wife to sleep and, Happy New Year's, and go back to just, doing this. And I sent it to my co-founder, my CTO, and he saw it in the morning. He's like, “This is absolute garbage.” “Do not show this to anybody at all, but the idea is good.” And so he took two weeks, and he rebuilt it.Swyx [00:10:09]: Did it like look like that? Listen, I - It was rough idea.Ivan [00:10:12]: Oh, not even, not even close. Like it was it was way worse. But it was like a very - It was a simplistic view of what it should be. Like, it worked, but it was not ideal. And so he went, we went down the whole, which is his job as CTO, to go, and he came back with this version. We then called all the people that had said like, “This is garbage,” a quarter ago. And we set up these calls, and we gave it to - We just demoed it to everyone. And all the calls went long, every single one. They were 15-minute calls, and they all went to like 25, 30 minutes or whatnot. And everyone said, “We need, we want access.” There was no login, just an API key, ‘cause it was just a beta or an alpha. And they said, “Oh, we want access.” And we're like, “Sure, yeah. Okay, thank you very much.” But after like the next day, if we'd not send it, every single one, like every call that we did, everyone came back, “Where is my API key?” Like everyone wanted it. We're like, “S**t.” Like this is it. Like I've never felt So one, the understanding to your point was like most people thought it was the same infrastructure for humans and agents. We understood a quarter ago it's not. We just didn't know what was the right primitive. And then when we came, and we can talk about what that is, and we gave it to these people, I've never seen, I've never experienced - I've done multiple companies in my life. I've never experienced this, that people literally call you if you do not give them access. Like they want access right now. And so it's like, okay, they don't want this. the thing that they want doesn't seem to exist, or they have not found it, and they really want what we want. And then when we understood that we're onto something, and then when you think about the size of the market, like the market for human engineers and enterprise is a very large market, so think GitLab or whatnot. But the market for every single agent that will exist ever in the future is just like, what is that market? How big is that? And we're like, “We are all in on this.” And so that is where we made sort of the cut between the old product and the new one.Bare Metal, Stateful Sandboxes, and the Lambda + EC2 ModelSwyx [00:12:02]: Yeah. But it wasn't composable at the time?Ivan [00:12:05]: It was very - It was basically just a Linux box that you could change, that you could define number of CPUs, disk, and RAM. Like that is what you could do, but you couldn't have multiple operating systems, you couldn't resize it on the fly, you couldn't add a GPU, you couldn't do like all the things. It was just the, just the first sort of variation of that, yeah.Swyx [00:12:22]: Was it bare metal from the start?Ivan [00:12:24]: It was bare metal from the start. And so the interesting thing that we thought about right away, so our.Swyx [00:12:29]: Which, give people the background, what is the normal path?Ivan [00:12:32]: Yeah, so, basically most providers run this on top of VMs. And also.Swyx [00:12:37]: Firecracker.Ivan [00:12:38]: Yeah, they run on Firecracker and VM. And so we also fire - We can get - We have multiple isolation layers and we can do that. But the common way to do it is that they, one, that the state of the machine, or the hard disk is not part of the sandbox itself. And the other thing is they're not meant to last forever. So most of them are preemptible, like they can There's a time that they can live. And so our thought was when we were going into this is, agents will be like humans in the sense of you don't want your laptop to be shut down until you're done with work. Like, and you want to close the lid and open the lid, it's the same state. So you - Agents would want that, like the pause and come back. They want those two things. But also agents really want speed, right? Can they get it? So when we thought about it's like we need something insanely fast, how to make it fast, how to make it long-running, and stateful. And so those two things, it's like combining a Lambda and an EC2, right? Those two things together. And so we didn't have an idea how others did it, ‘cause we didn't know too that there was a market around this. It was more like, okay, this is what we need, what they need. And we looked at Kubernetes, it wasn't wasn't good enough for that. We looked at Nomad, it didn't enable that. And so our history in rewriting our own scheduler at CodeAnywhere is basically what my CTO came up with. Like, he's like, “Oh, the learnings from there,” and he brought it. And the funny thing is, our third co-founder, when he saw it, he's like, “Dude, what is this? This is like 2008.” Like, we went back in time, and he's like, “Exactly.” And so the reason why Daytona is like super fast, and you see this on benchmarks, is we essentially, we run on bare metal. We have our own scheduler, we use the underlying, disk, CPU, and RAM of the underlying machine, which means your IOPS are insanely fast because there's no, there's no network between an EBS or something like that. But also the snapshot, the point in time, the templates, are also preloaded on the bare metal machines. So when you fire off a sandbox from a template or a snapshot, you're essentially directed to the bare metal machine where that snapshot is based on that NVMe drive, and then it literally just turns on that machine, and it's local. There's no network latency, anything on there. And so that is sort of the specificities that we, when we're thinking from first principles, what a computer would look like for an agent, that is what we came up with, and that's what we created.Benchmarks, 60ms Startup, and 50,000 SandboxesSwyx [00:15:02]: Yeah. I should maybe, I don't know if you endorse this, but there's someone that does compute SDK, you guys do very well on there, with like the TTI, right? I. is this a, is this a is this a relevant benchmark for you guys? I don't know.Ivan [00:15:16]: I don't know, and it changes every day. So today RKL is.Swyx [00:15:18]: I don't know what RKL is. Never heard of it.Ivan [00:15:20]: Yeah. RK, yeah, so it is there.Swyx [00:15:22]: You are, at least a third of the next tier of performance, and then, there's a lot of other better-known names that are very slow to start.Ivan [00:15:31]: Yeah. We've been the number one by far for a long time, and now there's different, there's different definitions also of sandboxes, different isolation patterns, different other things. So RKL runs it literally on the S3, the data, so it's very different, and they spin up a sandbox, spin up a container for that, so it's a different type of thing. So the definition of a sandbox is something that we can all, we all need to get along with. But yeah, we're insanely fast on getting these things, up and running. And so you can see even there that it's a zero point 0.10 to 0.11, so.Swyx [00:16:03]: Close enough. Yeah. what else do you need, right?Ivan [00:16:05]: Yeah. So the benchmarks itself, so, in this, in I don't think the benchmarks equate to market ownership or revenue or anything like that. and I've seen this with multiple benchmarks, not just in sandboxes, but in general benchmarks around.Swyx [00:16:20]: It's table stakes. It's just like.Ivan [00:16:21]: Exactly. But it doesn't hurt.Swyx [00:16:22]: Just roughly check.Ivan [00:16:22]: Like you definitely have to be up there and you have to be competing so that people know that, oh, this is definitely one of the top. Because this is only one dimension of what customers look for. There's other things like how many can you spin up consecutively? There's a feature set, there's support, there's like all different things that people look at, but you definitely have to be there, on the benchmarks.Swyx [00:16:40]: How many people do people spin up consecutively?Ivan [00:16:43]: So we have.Swyx [00:16:43]: Or concurrently, is the Concurrency, right?Ivan [00:16:45]: There's three metrics that we look at. And so one is like time to spin up one, and so our time to spin up one is 60 milliseconds with network latency. So request, spin up, reply, 60, the whole thing, 60 milliseconds. That is one. But if you wanna spin up 50,000 at once, we are now at about 75 seconds. So it takes about 75 seconds to spin up concurrently 50,000. Some others, there's public data around this, like take 2,000 seconds, which is 30 minutes. Like there's different variations of that. And then there is the so it is speed of one, speed of like multiple, and then how many can you consistently have up and running. And so we basically have right now no limit to how much we can add because we basically own our own metal. But the biggest customer of ours does like about 850,000 every single day is sort of where they're, where they're just shy of a million every single day that they're running, we do have a request for half a million concurrent, which is literally half a million CPUs somewhere running. So that's an interesting.Swyx [00:17:44]: They pay by like vCPU seconds.Ivan [00:17:47]: By seconds, yeah.Swyx [00:17:47]: Or whatever. Yeah. Okay, and so and then, and the other thing is, the sleeping and the resuming, ‘cause it's all the stateful resumption of all these things, how, what kind of workload are people putting through this, right? Like how is it Do we measure by gigabytes in memory, gigabytes in storage? I don't In like network attached storage. I, what are the costly ones of, out of all these features?Workload Economics: CPU, RAM, Network, and StorageIvan [00:18:15]: The most expensive thing are CPU.Swyx [00:18:18]: Okay. Yeah, of course.Ivan [00:18:18]: The second one, yeah Then it's RAM, then it's disk. We actually don't charge.Swyx [00:18:22]: Which is snapshotting, right?Ivan [00:18:23]: No, it's actually the, snapshotting's part of it, but basically the size of your hard disk, of your machine. So do you have 10 gigabytes, do you have 20, do you have 50, do you have whatever? And then the transference of that. Right now, currently we don't charge for, network at all at Polychron.Swyx [00:18:37]: Oh, you gotta, yeah, you gotta fix.Ivan [00:18:38]: Yeah. It is very much a it's a larger and larger part of our bill, so we're working around, that part there. Obviously, that is the least, expensive, so the hard disk is the least expensive, so it's basically CPU, RAM, for us network, ‘cause we don't charge the customer, and then hard disk, is how it's split up. But there's also different types of workloads, so we basically split it up into two types of workloads in Daytona. One is what we call background agents or long-running agents. and the other is, basically RLs and evals, which I put sort of together. And so they have very different patterns of usage, and if you look at the usage of a background And I'll just name names of companies, not specifically.Background Agents vs. RL/Evals: Two Usage ShapesSwyx [00:19:21]: Yeah, open, all hands.Ivan [00:19:23]: Yeah. So like a background agent's a Cognition, a Lovable, a like all these things are Harvey. These are all long-running, background agents. And so if you look at their usage patterns, their usage patterns are similar to human, which is like follow the sun. Basically, the usage patterns of that is like noon is probably the highest, and the midnight is the lowest, and then weekends are lower. weekday is higher.Swyx [00:19:42]: Yeah, that's a fun question. How global is it? Is it very US-centric or?Ivan [00:19:46]: The US is a large part, but we have currently, we have Asia, Europe, and the US regions.Swyx [00:19:52]: So it's quite global.Ivan [00:19:53]: Yeah, it's quite global. We have it all over. It's interesting that our I talked to you a bit about this. Our number one city by user.Swyx [00:20:01]: Hmm.Ivan [00:20:02]: Is Singapore.Swyx [00:20:04]: Oh, wow. Amazing.Ivan [00:20:05]: Which is an interesting one, right? Not by revenue, just by just like by individual head count.Swyx [00:20:09]: Really?Ivan [00:20:09]: Just like an interesting thing.Swyx [00:20:10]: Singapore is, Singapore is weirdly high in the adoption charts of AI for the population. It's like an, seven, eight million population. And it's like keeps showing up.Ivan [00:20:20]: No, it's quite interesting. We were quite shocked, and I was like, “Oh, this is interesting.” And also one that's up there.Swyx [00:20:24]: There's a reason I'm doing AI using Singapore. it's because I'm from there.Ivan [00:20:27]: We're there. We're gonna, we're gonna be there as well. and it's interesting that Japan is in the top or like Tokyo's in the top, which is in all the tech cycles it has never been. It has never been, so it's quite interesting that they're.Swyx [00:20:39]: I think the Japanese just love AI. Yeah. It's that, and then it's Brazil. That's it.Ivan [00:20:44]: Brazil has always been in.Swyx [00:20:45]: I think.Ivan [00:20:46]: Even when I look, if you look at like GitHub's data and ask historically with CodeAnywhere, it was always like US, Western Europe, and then you'd have like India, Brazil, China, like that would be there. But like Singapore was not in, specifically Japan was never in sort of that top, that top.Swyx [00:21:01]: Yeah. Weird pockets.Ivan [00:21:01]: Weird. Yeah, so it's very global.Swyx [00:21:02]: Okay, so actually that, but that's helps you to distribute your load through, all time?Ivan [00:21:08]: The interesting thing is like we have those kind of loads, but if you look at the researcher loads, they're quite different. So what they are is like if you give them concurrency of 10,000 or 50,000 or 100,000 CPUs at ARMb, when they fire off a run, it's just 100%. And then it just runs, and then it stops. So it's very, the usage pattern is squares basically, right? And it's also not follow the sun, because people will fire it off at midnight before they go to sleep but then wake up and so it's very unpredictable, so you don't know where that is. So the shapes of the usage are quite different than we have had before. And also what's interesting is when it's sort of a follow the sun, even if you have a high growth company, you can sort of predict your usage patterns and have enough capacity for that, because it's sort of, it grows in a, in a way you can project. When you have companies doing sort of like evals and RL, they're super spiky. So they're gonna come in, it's like, “We're gonna use nothing, then can we have 100,000?” Right? And then go back down. And then 100,000, go back down. So it's very different, right? And.Swyx [00:22:09]: Do you want to lock them into commits so.Ivan [00:22:11]: Yeah, we do.Swyx [00:22:12]: Yeah, okay.Ivan [00:22:12]: We so we have to lock them into some sort of commits to have that capacity, because we have to have, basically we have to have the capacity for peak. Right? And so right now, Daytona's mean utilization is 15%, 1-5.Swyx [00:22:25]: Oh my God.Ivan [00:22:26]: So it's very low.Swyx [00:22:27]: Because it's very spiky.Ivan [00:22:27]: It's very spiky, but we get up to 90%. so we have these things. And so what we're, what we're looking at right now as a company is similar to Cloudflare where you can like geo move things around, but that works really well for basically the background agent where it's follow the sun. But this, it's not. Like it's a very different shape. Obviously with scale you figure these things out, but that's an interesting new problem that we have, as a compute provider in the agent space. And when we were doing the conference recently, and so we talked to like Nikita from Neon and.Swyx [00:22:57]: I should bring it up.Ivan [00:22:58]: Parag from Parallel and whatnot, everyone has the same problem. Whereas the usage is super spiky, and this is something that has not happened before, that you have these types of like it was always, it the amplitudes were not this high, right? So it's quite interesting use case and problem solve.Compute Conference and Spiky Agent InfrastructureSwyx [00:23:12]: Yeah, I don't know if we're gonna bring this up again, but let's just talk about the conference, you had like 1,000 something people at the Warriors game, at the Sorry, where is it? What's.Ivan [00:23:22]: Chase Center.Swyx [00:23:23]: Chase Center.Ivan [00:23:23]: Chase Center.Swyx [00:23:24]: I went. It was, it was very impressive. Obviously, you can, how to throw a conference, what did you learn? you put, you pulled together all these impressive names.Ivan [00:23:33]: What I.Swyx [00:23:34]: What were you looking for?Ivan [00:23:35]: My thesis behind the Compute Conference was let's bring together people that are building infrastructure for AI agents. Because when I think of what we're building, it is the agent is the primary user, what are the ergonomics and usage patterns of agents, and so we can do that. And what I found, this was a theory, it wasn't proven, is that we all have these problems, as I touched onto. And I was, as I was talking on stage, it was like we all have the same underlying infra problems, which is this spiky workloads, unpredictable workloads that we've never had before, in human, compute or human infrastructure. And it's, again, it's the same when I was talking to Parag or when I was talking.Swyx [00:24:20]: Lynn. Nikita.Ivan [00:24:21]: Lynn, Nikita. Lynn especially, I was talking to her the other day as well. Like the It is a very interesting type of problem to solve because I can touch on Cloudflare because there's a lot of like talk about that recently as to how they solve that, which is they have a bunch of geos, and basically, as users work in different places, and depending on your tier, they can move you around the geos. And so that how, that's how they get the higher utilization. But you can sort of predict these, and it's If it's something in You'll rarely get a spike that is 10 orders of magnitude. Like you'll get a like let's say one of your customers has some like an exponential curve. What is that to I'm using Cloudflare as an example. 10%, 20%, whatever it is. I don't, I don't have this data, I'm just assessing. It's surely not 10x, right? It's surely not something there. And so how do you go out and solve this problem? And we're all solving this in different ways. So we have.Swyx [00:25:11]: She also has the same thing.Ivan [00:25:12]: Yeah, I know specifically that like Neon had that issue as well. Like how are we solving these spiky loads and things like that ‘cause we talked about it. And so the interesting thing for me to actually internalize was, yes, everyone that's building for agents first is going through this, and we're all solving similar problems, which is quite.Swyx [00:25:28]: Let me let me double-click on this. Okay. So for example, Neon, I happen to know that they're very sort of S3 oriented, right? so they're just like fully bet on S3. And you get to benefit from S3's distribution and infrastructure. So I would imagine that Neon doesn't have to care, whereas Lynn maybe has to care a bit more because obviously she's doing GPU inference. And, for listeners, we did an episode with her, one and a half years ago. And you have to care. But like, right?Ivan [00:25:54]: Parag cares for sure, and Nikita.Swyx [00:25:58]: And Parag is C of, Parallel.Ivan [00:25:59]: Parallel, yeah.Swyx [00:26:00]: Former CTO of Twitter.Ivan [00:26:01]: Twitter, yeah.Swyx [00:26:02]: They are the search.Ivan [00:26:03]: Yeah, they're search, yeah.Swyx [00:26:03]: I You and I know but the listeners don't know.Ivan [00:26:08]: Yeah, we can put it down in the screen, and so ‘cause we, when we were talking.Swyx [00:26:11]: I'll put it up on the, on the screen.Ivan [00:26:12]: Yeah, right.Swyx [00:26:12]: People can look it up if they need.Ivan [00:26:14]: Look it up. And, yes, but they still have CPU and RAM, allocation that you have to have up and running. And so CPU and RAM, you have to allocate that and have that ready. And so there's basically two ways to do it. One is you either over-provision and you can handle the bursts, or two, you basically have, I don't know if this is a term, just-in-time compute, which is like as your load becomes, as your usage comes in, you can fire off requests for VMs or bare metals at other cloud providers and then get them up and running.Swyx [00:26:43]: This is if you go above 100%, right?Ivan [00:26:45]: Yeah, this is.Swyx [00:26:46]: Like your overflow.Ivan [00:26:46]: If your overflow, like spillage or whatever you do.Swyx [00:26:48]: You probably lose money on it, but it doesn't matter, right?Ivan [00:26:50]: It, not Well, you might, you might not That is a more cost-effective way to do it but it's a slower way to do it. Because basically what you have to do is you have to like queue your requests, spin up these just-in-time compute, get it all ready, provision it, and then get your workload there. And so if the time isn't important that much, that's fine, and you can do that. But if your customer, and especially for, let's say, the RL training runs, the reason why a lot of people come to us is because GPUs are more expensive than CPUs, right? So you want your GPU running at, what, 100% the entire time. And so when you're running runs on CPUs, when the when the CPU cycle is like down and spinning up the next one, you want that to be instantaneous so that your GPU doesn't go down, right? And if you then have to like go out and provision machines, you're essentially telling the GPU that it has to wait, and that's incurring our cost. So there's things that you have to try to solve for there.RL Workloads, Declarative Images, and Kubernetes ReplacementSwyx [00:27:43]: Yeah, let's talk about the different workload, right? You said that, what was it? A few months ago, you had zero RL workload and now it's 50%.Ivan [00:27:52]: It will be this one, 50%, yeah.Swyx [00:27:54]: Let's talk about how different it is, right? Like I imagine, for example, a lot less dynamic code generation of like arbitrary code. Like here, it's probably all the same code. You're just doing parallel runs or something, I don't know.Ivan [00:28:05]: Yeah. So you'll have multiple Depends on the like for each run, you'll have a snapshot. And they, for the most part, they actually do use our declarative image builder, which is like, “Oh, we, the agent wants these dependencies, these env vars.”Swyx [00:28:17]: These ones, yeah.Ivan [00:28:18]: Yeah, the declarative image builder, it.Swyx [00:28:20]: Which is a very modal like thing that they.Ivan [00:28:22]: Yeah. And so we build it on the fly and then we propagate that snapshot, and you can spin up as many sandboxes as you want against that snapshot. And then if you have to do changes, the model can, or like it could be also be automated. It's like, “Oh, now for the next run, we need to install these things or remove these things or whatever to get, a task done,” and then it goes off and runs that. So yes, that is something that it seems that they prefer. The number one reason I found, or should I say, let's take a step back. What we are competing against in that environment is essentially managed Kubernetes. So EKS, GKE, whatever. That is what the vast majority run on. And anyone that has tried Daytona versus GKE, EKS is like, “I'm never going back.” That has always been. There's a few reasons. One is the ergonomics. So if you have, if you're using Kubernetes to spin that up, you have to essentially manage the interface interactions with that. Daytona, although as a compute provider, it's more akin to a Twilio and Stripe from a consumption perspective than it is an AWS. Like you have an API, an SDK, it's quite like easy and seamless to get these things up and running, that's one. The other is the speed to which we spin up, which we mentioned earlier, which is much faster, and the scale to which we can go to. We haven't got into features, but an interesting feature is that it's very hard to OOM, or out of memory, our sandboxes, because we can dynamically on the fly.Swyx [00:29:48]: Resize.Ivan [00:29:49]: Resize, which is like impossible on almost any other thing. There are some technologies that enable you to do that, but it's like a very hard thing. And so we actually saw this when, the Terminal Revenge team is, brought us actually. So thank you, Alex and the team, that brought us into this whole space.Swyx [00:30:05]: It's just very rare that, a framework would just say, “Guys, just use Daytona.”Ivan [00:30:11]: Yeah, I think it says it somewhere. Yeah.Swyx [00:30:13]: Yeah. I was like, “What is this?”Ivan [00:30:15]: There's all, there's multiple there, but they also mention a few other places. and so Daytona specifically-We have, the, just jumping on themes here We, I don't know where it says Data Center.Swyx [00:30:27]: I, there.Ivan [00:30:27]: Doesn't matter.Swyx [00:30:28]: There's a very strong recommendation, which is, very unusual. Which is, it's.Ivan [00:30:33]: We do not pay them for this, just.Swyx [00:30:34]: I know, yeah. They just like you.Ivan [00:30:35]: Yeah, they like us. yeah, and also a thing, so, Data Center has multiple isolation sets underneath. The customer doesn't have to know what they are. But basically we have Docker, which is a container, that's hardened with Sysbox. So it's Docker's, isolation that is a security equivalent to a VM, but it's still a container. And that is the default, and they, especially in these training workloads, really like that as an interface to be able to use just a basic Docker container, and we enable Docker and Docker. Which for these RL runs, if you need to do a Docker compose or Kubernetes, you can spin up a K3S inside of these things, which unlocks a huge amount of workloads that you can do that you cannot do on other providers. So just on that part is much more interesting. And so we went that, through that. We showed them that we could do that, and they enjoyed that quite a bit. They being the general venture people.Swyx [00:31:28]: Those people, yeah.Ivan [00:31:29]: And Harbor people.Swyx [00:31:29]: Harbor people, do are they, are they a company yet?Ivan [00:31:33]: As far, I do not know.Customer Pull, Slack Connect, and the Computer Use BetSwyx [00:31:35]: Okay. All right. Yeah. It's like super obvious that like, there's a lot of excitement and success around these things, okay, so yeah, tell us more, right? Like, this is an exploding workload, Harbor adopted you, which helped speed things along. But what are you learning as this new workload comes online?Ivan [00:31:53]: There's a couple things that we learned, which we chat about in the beginning. We, and this has led our story, as we mentioned, we like talked to a lot of customers along the way, and we add more features and more tool sets as we talk to customers. And it's interesting that And I think it's that the ecosystem is so small and/or the models get smarter, where when we see one user come with a request, we know it goes on a roadmap if like three to five customers come with the same request in that week. It's like very bizarre. It happens so many times, which is.Swyx [00:32:27]: Because they're all friends.Ivan [00:32:28]: Sorry?Swyx [00:32:28]: They all, they're all friends. They're all in the same group chat.Ivan [00:32:30]: Yeah, probably, yeah. ‘Cause and they're like, “Oh, can you do this?” And I'm like, “Okay, this is interesting. We'll put it on a feature request.” And then the next one's like, “Oh, can you do this?” “Okay.” It's all the same, right? It's always the same. And so what we try to do, and I personally try to do, I try to be on as many call, quote-unquote “sales calls” I can. I'm in every Slack channel. We literally have about 1,000 Slack Connect channels, something like that. It's an interesting, there's so many interesting things you find out when you have all the Slack channels. You can also see where people, transfer between companies. You see leave Slack channel, enter Slack channel. It's an interesting thing. Also, just I digress, I feel that Slack Connect is literally LinkedIn what it should be. You have a list.Swyx [00:33:08]: LinkedIn charges you to, use your own connections, but Slack doesn't, right? Slack is like, do it for free. It's more lock-in. It's great.Ivan [00:33:15]: Yeah. It's amazing. Yeah. It's one of the reasons.Swyx [00:33:17]: You're gonna pay Slack for life.Ivan [00:33:18]: Exactly. You're there for life. So that's interesting. And so one of the things, the newer things we were talking about earlier is we made a big bet and put a lot of investment on computer use. that is not seen publicly the light of day. We haven't GA'd that yet, but we have.Swyx [00:33:32]: Is there a thing I can pull up?Ivan [00:33:33]: There is computer use there. It's right up a bit.Swyx [00:33:36]: Oh, yeah. Okay.Ivan [00:33:38]: What we have, what we talked about and what we've seen publicly is there's this theme now about, the human emulator where And Elon from XAI has talked about this publicly, and if you think about the models today, they're actually quite sophisticated and they can do a lot of work, but they still don't have access to all the tools. Like, I'm a strong believer that the most efficient way for an agent to work is essentially headless or through, terminal or whatnot. But if we, if we look at knowledge work in general, there's about 100 million knowledge workers in the US, about a billion in the world, and knowledge workers, and the salaries of them aggregate to 10 trillion in the US 50 trillion worldwide.Swyx [00:34:24]: Wow.Ivan [00:34:25]: Something like that. And if we look at, the five most important sectors of that, so like healthcare and government and financial services and whatnot, that's about 56% of that. So let's say it's about half of that. So in the US it's about 25 trillion, and most of them, most of that work is actually still locked into legacy apps inside of Windows, which is not going anywhere for a very long time. Like, people just won't invest in that. How much of it? our assumption is the following: if, in the RPA market, which is similar market, well, not the same 25% of, these white collar, workers', work is automated. If an agent is more sophisticated, can go through more runs, figure stuff out, let's say it's, 40%, right? And so if you take 40% of that, you get to essentially, $10 trillion a year.Swyx [00:35:17]: That's a TAM.Ivan [00:35:18]: That is a that is a TAM. So that's the TAM of the models, right? That's not our, essentially ours. But you get to that size, and to be able to do that, you essentially have to give agents these computers with the legacy. So computer use, either Mac or Windows or Linux. Linux we also obviously have and others have. But Windows specifically is something very new, and the only option right now is an EC2 with, Windows or on Azure. Both of them take anywhere from three to five minutes to spin up. We've created an actual sandbox, so it's a second instead of milliseconds, but you have, point in time snapshots, you have, forking, you have all the things that you have from a sandbox, but essentially enables you to hopefully unlock all this value. And so that's been our big push and bet, but we've sort of, kept our ear to the ground. What is sort of the next things in the market?RPA Returns: Why Agents Still Need ComputersSwyx [00:36:06]: Yeah, knowledge work, and building, and sort of RPA, the next wave of RPA. I got very excited about RPA kind of during COVID times. The UI path was IPO-ing. And it was, a very hot Isn't it, Eastern European?Ivan [00:36:20]: It is, Romanian.Swyx [00:36:21]: Romanian?Yeah, it might be the only Romanian, big unicorn okay, yeah. This I don't I don't, I don't have like a I think there's, I think there's a stage being set for the resurgence of RPA, ‘cause everyone understands that, yeah, no one wants to deal with these shitty apps and no one's gonna rewrite them. Like, you just have to do, a remote operation and programmatic operation of them.Ivan [00:36:45]: If you wanna unlock it, my own setup was basically the following. So I was doing a board deck recently, last month, whatever, and I'm like, “Okay, let's just, let's just do automated.” So, all our data's in, ClickHouse and PostHog and QuickBooks, where everyone else's is, and I'm basically, connected that all to, my Cloud code, like go off and go Cloud code whatever. Go off and, here's the integrations, go do that. It pulled out the first report, which was great. It connected to Brex and all these things, pulled it, which was great, and then I say, “Okay, now pull out this, and this,” and I kept getting, really well McKinsey-style design reports, but the data said partial data. all the missing data, partial data. Like, it can't access all the things, and I got so frustrated, and so I got, I got, my Mac Mini virtual sandbox with OpenClaw. I gave it its own account in our company, and then I went to all these services and created a read-only account, so literally like an intern in your company. And so I would say, “Now go and do this report,” and it would get the same, or like, “I can't via the MCP or the API or whatever. I can't get all the information.” I'm like, “Go log in.” And it will log into the website, then go in, export the data. It'll export the data and do the thing end to end. So even for things that have today APIs, not all of it is exposed, and I to get value, I get immense value right now, but it has to be a computer usage, unfortunately, and so I spend a bunch of tokens just on that, but I get the job done. And so if even a startup like ours, and using all the hottest tools, still needs a computer agent what hope does, Goldman have to have a headless, right?Swyx [00:38:22]: Yeah, what a - Why isn't Microsoft doing this?Ivan [00:38:27]: I'm pretty sure, Satya had a post yesterday.Swyx [00:38:29]: Oh, okay. I see.Ivan [00:38:29]: Which was like, “Every agent needs a computer.”Swyx [00:38:31]: I see, I see.Ivan [00:38:32]: So they have launched something recently.Swyx [00:38:34]: Yeah, they have Microsoft Power Automate, I'm sure, I'm sure, they're gonna have their version.macOS Sandboxes, Apple Constraints, and the Windows OpportunityIvan [00:38:39]: Version of that, yeah.Swyx [00:38:39]: You're gonna try to do yours, and it - I always know there's always demand for Mac, but I know it's, tricky to host, macOS sandboxes.Ivan [00:38:49]: We will have macOS sandboxes fairly soon. The problem with macOS, OS sandboxes is, I'm deep in this, I don't know how much interesting is.Swyx [00:38:55]: No, it's.Ivan [00:38:56]: MacOS has this problem.Swyx [00:38:57]: It's a licensing thing, right?Ivan [00:38:58]: Licensing thing. So one, you're allowed to run only two parallel VMs per machine, so that's one. Two, you can only license to a different user every 24 hours. So if you come in and theoretically, if I wanna charge you per second and I charge you one second, I have to have it idle for the rest of the day. I can't have anyone else doing that. So the pricing will be different in the sense that I will have to - we would have to charge for 24 hours, and that's not even, that's not even the most difficult thing. But the, thing above that is, from a security perspective, they enable you to do memory snapshot, pause, resume, but only on the same physical drive, physical machine. And so what you can do in, Windows world or Linux world is that I can move in the background, your snapshot from one to the other and manage load, right? Here, if you wanna do that, you essentially have to have your.Swyx [00:39:49]: Yeah, snapshots. Yeah.Ivan [00:39:50]: Your.Swyx [00:39:51]: It's like.Ivan [00:39:51]: Physical machine.Swyx [00:39:52]: You can't break it up.Ivan [00:39:53]: You can't, you can't move things around that, and all of that is, that part is, from a security standpoint, if it is written. Like, I understand the security aspect of that, but it disables you from doing these agentic, like really scalable agentic workloads.Swyx [00:40:08]: You need to do a vibe-coded, clean room implementation on macOS that you can then - That's like Clean OS or something. I don't know.Ivan [00:40:17]: So. We have.Swyx [00:40:18]: ‘cause like Linux was originally like a clean room rewrite of Unix.Ivan [00:40:21]: Okay. Yeah.Swyx [00:40:21]: Or something like that, right? Like same thing to macOS. Someone needs to do it.Ivan [00:40:25]: Someone will do that, and someone will have some long-running agents for a few days to figure this stuff out. But yeah. So definitely we - we're really close to offering something ‘cause people do want it, but the pricing will be different, and the feature set will be sort of stringent.Swyx [00:40:38]: Yeah, nobody's gonna use this. like, the labs, the labs will because they want to automate macOS.Ivan [00:40:42]: They have to do RL. They have to do RL again. But even if you The - So the point is with the RL part, if you, if you do RL on macOS, then the next iteration of the model comes out, it will be able to use these tools significantly. Then you actually need to run those, that somewhere. So you're gonna have to have that, later on. And from, if anyone at Apple is listening, I very much feel that they are shooting themselves in the foot of the scale of the revenue of compute or licensing they could get if they would just enable a concurrency model similar to what you can get on a Windows and a, and Linux.Swyx [00:41:17]: Yeah. Yeah. And I'm sure they've heard this before. They just don't care. Yeah, it's And maybe they will change their mind with the new CEO.Ivan [00:41:24]: Yeah. We'll see.Swyx [00:41:25]: We'll see.Ivan [00:41:25]: High hopes.Swyx [00:41:26]: High hopes.Ivan [00:41:26]: High hopes.Swyx [00:41:27]: Okay. But I, it's very clear the market opportunity is huge in Windows, and you can go for a long time on just Windows, but your customers are gonna want both. and I think, it is interesting to me that, this is the sort of God application of agents, right? Like, I don't It was - How big was OpenClaw for you guys? Like, was it, was there, a significant bump.OpenClaw, Agent Labs, and the B2B2C Sandbox MarketIvan [00:41:54]: Not for us because we.Swyx [00:41:54]: Because you already.Ivan [00:41:55]: We're kind of positioned differently. Whereas although it's completely PLG and we have individual developers that use it, most of the users that use Daytona are sort of a B2B2C. Sort of it's either B2B or B2B2C. So, in the researcher world, it's B2B, so you're selling to, labs and neo labs and things like that. But on the long-running agents, it's mostly, from a scale revenue perspective, it's mostly B2B2C, where you have a app layer agent that uses you at a big scale.Swyx [00:42:26]: Like a Manus. Yeah.Ivan [00:42:28]: Like a Manus Lovable type of thing.Swyx [00:42:31]: Yeah. I think that's the question of, well how, um-Uh, yeah, B2B to C is basically to me what I've been calling an agent lab, which is kind of like you're not in a model lab, but you're making a very good wrapper that is a platform that other people can sign up so they don't have to code those things. Yeah, it sound, it sounds like a much better market than the direct OpenClaw market.Ivan [00:42:56]: I've like - We I've done multiple things. So the CodeAnywhere's part of our career path R in the calendar, was very much an end user developer product. And so that is great. It You can get a lot of developer love, and I feel that we do as a company have a bunch of developer love. But it's a different type, where it's people building these things. Again, it's more akin to a Twilio because you don't really run - As a person, you wouldn't run Twilio. I don't know how many people remember. It was like ask your developer billboard and whatnot. And people really love Twilio, but they only used it inside of like, “Oh, I'm building this app or service for thing.” And so we're very much directly to that. And you also know that I used to work for a competitor for Twilio, so it's kind of ingrained, in my DNA.Swyx [00:43:35]: People don't know InfoBip is that big.Ivan [00:43:38]: Yeah, it's.Swyx [00:43:39]: Because.Ivan [00:43:40]: It's a billion euro.Swyx [00:43:40]: They're all American. They're like, “Whatever's in Europe doesn't matter to me.” But like it's the, it's the same size or bigger? Same size?Ivan [00:43:46]: It's about half the size.Swyx [00:43:47]: Half the size?Ivan [00:43:48]: Yeah, about half the size.Swyx [00:43:48]: It's like, yeah.Ivan [00:43:48]: Still huge. Multiple billions a year. Yes.Swyx [00:43:51]: That's crazy.Ivan [00:43:51]: Exactly, and so that - These are like really interesting and large revenue-generating, very sticky businesses. Whereas when you're selling to the - When your focus is the end developer, it is a very hard sell because they're very price sensitive, very price conscious, very around that. And there's very It's very hard to scale. Your cap is the number of people that are willing to spin up - First of all, wanna spin that up, and then spin up multiple of these. Whereas if you're in the enterprise one, like we know everyone's talking about like how many tokens they're spending, I'm spending. Like a lot of companies today are like, “If this is our company, spend as much as you can.” Like basically that is where we're going. And so if you think about that paradigm, where you're selling to companies that say, “Spend as much as you can to generate, productivity,” versus, “Oh, I'm a single person. I have this much budget, and I'm doing this thing because it's fun or it's helping me out or whatever.” Like it is a different, it's a different go-to-market, I think, strategy.MCP, CLIs, and Sandboxes as the Agent RuntimeSwyx [00:44:50]: Yeah, there's a lot of discussion. I'm just kind of going through like the mental list of things that are in your favor, which is, for example, MCP versus CLI. Like obviously you want CLI. It's been very good for you. I feel like it's maybe a drop in the bucket or maybe it's huge. I'm just checking whether it's like these are big trends.Ivan [00:45:10]: Those things you - work well in our favor, to your point just because every.Swyx [00:45:13]: They're kind of drop in the bucket, right?Ivan [00:45:15]: I think it's like sort of all the things come together. And so there's so many things that impact that. To your point, like OpenClaw wasn't huge for us, but like having the agent SDK, from Anthropic, so or Cloud Claude Code was very interesting. The reason why it was interesting is that a lot of, let's call them app I don't know what to call them, app layer agent companies, essentially they are like, “Oh, I can create this new app, this new agent. All I need, I just use Claude Code, and I throw it into a sandbox, and then I have my interface to the human to that.” And so that enabled so many more companies to actually offer this, and then they would pull on sandbox. So that was, that was interesting. And to your point, like MCP, versus the CLI, the MCP is an interface against an API, whereas the CLI is like you can actually go do things. Like this is it. The difference between integrations and actually running scripts or data or analysis against a thing. So being able to use a CLI very well enables the agent to do more things, and it's because that people will invoke a sandbox, they'll run it in the CLI, and but it'll do anal-analysis on that data and then give you an actual result versus just, pulling data from an API source.Swyx [00:46:29]: Yeah, it's a layer of indirection basically, it's the same thing as agentic search versus RAG, which where you're.Ivan [00:46:34]: Exactly, yeah.Swyx [00:46:34]: Just like you just win whenever people put more agents into their workflow. And so like it doesn't really matter, but I'm just kinda teasing out like what else have people heard about that like it's sort of, “Oh yeah, this is another sandbox use case. Oh yeah, that's another one.” Am I, am I missing any big ones?Ivan [00:46:51]: The thing, the thing that people, which is the computer use stuff, which I think is probably the most interesting one, is, and to your point, we've talked to so many people over the last year. It's like, “Oh, like why do you need a sandbox? Why do you need this? Why this?” And to your point, it's like, “Oh, I need sandbox for this. I need sandbox for that. I need sandbox-” It's like, “Oh, I need it for every single thing.” And so basically what I, what I - and it sounds like a broken record, it's like you use a laptop every single day, right? And you are n of one. It's just you. But now imagine how And by the way, the laptop, the computer PC market, the PC market is about equal to the cloud market in total. So it's about 150, 180 billion a year. Something like that. It's about roughly the three cloud hyperscalers is about equal to like Apple, HP, Lenovo, whatever, It's a little bit less, but it's sort of like that. And now imagine And that's just like, so how big is the addressable market? What, how many people are there in the world now? What's the last data?Swyx [00:47:45]: Let's call it eight billion.Ivan [00:47:46]: Eight billion. And so let's say you can have two computer, like you have one personal and one business, whatever. Like so it's double that, right? and so that's 16 billion, right? How many agents are gonna be running in two years, in 10 years, in 100 years? Like And for every single task, they will need one of these. And so how big is that? That market is essentially quote unquote “infinite”. You will get to the point, and Dylan Patel was at the conference talking about, from SemiAnalysis, that talks usually about GPUs, was also talking about how CPUs will now be a bottleneck because it will be the constraint. You won't be able to grow, or we won't be able to have enough of these because there won't be enough CPUs to basically do.Swyx [00:48:23]: Yeah. Well, I actually had a really good podcast with Doug Oliphant, who, which was his president at SemiAnalysis, where they've basically been like, yeah, it's been a GPU shortage first, but then it's cascaded down to memory and now to CPUs.Ivan [00:48:35]: CPU, yeah.Swyx [00:48:35]: It-What's next? So networking. So, networking actually has been in shortage for a while if you're looking at, just GPU networking. But, yeah, it's really crazy the amount of computer use that's going on, yeah, cool. I, other questions are, just the one very big part is the open sourceness which you didn't have to do, your competitors don't do, like it's not, a lot of people are worried about keeping their projects open source because some competitor can just slot fork it. I don't know if there's any reflections on just being an open source company.Open Source, Trust, and Enterprise ProcurementIvan [00:49:15]: Yeah. There's a bunch. So we the original product that we did was open source.Swyx [00:49:19]: Yeah. CodeAnywhere.Ivan [00:49:20]: So doing that was actually very good for us. There's basically a saying of, What's the saying? Like, companies that are, that are doing really well, measure themselves against, free cashflow, that are kinda okay, it's EBITDA, then, it's, it goes all the way down.Swyx [00:49:36]: The worst is like GitHub stars.Ivan [00:49:37]: GitHub stars. GitHub stars are the worst, yeah. So you go all the way down to GitHub stars. And so our original one was GitHub stars. That's what we talked about, we're at the point we're talking about revenue, so we're we've gone up the stack on that. And so we started.Swyx [00:49:47]: No, profit.Ivan [00:49:48]: Yeah. We haven't, we're, we'll get there. We'll get there. But basically at that point we did stars and GitHub and it was useful, and the original variation that we did, it we split the core into its own repo and it was Apache 2.0, so very, permissive. And then we basically would bundl

The team were full of laughs this week (even more than usual) to bring you episode 195. We hear a miracle story from The Great Ocean Road Marathon as well as a less-miraculous tale from Tess that involves mixing up the taps in her San Francisco office. A strong training week from Brett, Tess runs everyday while in USA and Joel heads out for his first long run in many moons. The BIG Q submission this week has Brett, Joel & Tess attempt to solve how best to plan your training week when away on holiday. Give Some Kudos has plenty of love being spread around and TWHSOITWTWATSA includes one of the greatest ever on-air FTK blunders. SIGN UP TO OUR PATREON TODAY: www.patreon.com/forthekudos Instagram: https://www.instagram.com/forthekudos Facebook: https://www.facebook.com/forthekudos TikTok: https://www.tiktok.com/@forthekudos Brett: https://www.instagram.com/brett_robinson23 Joel: https://www.instagram.com/joeltobinblack Tess: https://www.instagram.com/tesssicaa_/  

We take a trip (in more ways than one!) to Phoenix Springs Developer: Calligram Studio | Publisher: Calligram Studio | Initial Release: October 7, 2024 PLAYERS: Travis Colenutt (Bluesky) Katie Lesperance (Bluesky) SHOW NOTES: 0:00 – Intro 02:20 – Fast Pitch 03:03 – Where we discovered Phoenix Springs 04:18 – Origin of Katie's love of point and click adventure games 05:55 – Our playtime/Travis' experience with point and click adventure games 10:02 – Story and gameplay setup 17:01 – Red herrings 18:04 – Difficulty 19:43 – Spoiler Wall / Continued discussion of some of the hardest puzzles 24:01 – Things are just weird 27:00 – Lynchian storytelling is not for Katie 34:09 – Visual style 39:38 – Story deep dive 48:36 – But what does it mean? 52:12 – Kudos to Calligram Studio 57:32 – Outro BLUESKY: leftbehindgameclub.bsky.social DISCORD: The Left Behind Game Club is a monthly game club podcast that focuses on positivity and community. To talk to members of the community, join our Discord server!

Take the 2026 AI Engineering Survey and get >$2k in credits and AIE WF tickets!This was recorded before Railway suffered a major GCP outage on May 19, despite being a multi-AZ, multi-zone mesh ring, with HA fiber interconnects between their Metal GCP AWS, because workload discoverability was unintentionally still tied to GCP. All has been resolved with a post-mortem.Railway did not start as an AI infrastructure company.It was founded in 2020 years before agents became the default way people thought about deploying software. Jake Cooper, formerly at Bloomberg and Uber, started Railway with a simple obsession: the activation energy to ship something to production should be near zero. Push code, get a URL, iterate. No Docker files, no Kubernetes manifests, no Ansible scripts stacked on Ansible scripts.For years, this was a slow grind. Railway spent its first 18 months hand-acquiring its first 100 users with Jake personally greeting every Discord signup on a second monitor.Today, Railway has raised $124m and is growing very fast. A 35-person team supports 3 million users, adding roughly 100,000 signups a week. Their bare metal data centers have a 3-month payback period vs. renting in the cloud, with 70% margins funding aggressive cloud bursting when needed. The servers they own have actually appreciated in value as RAM prices have climbed basically meaning the value of their hardware now exceeds the capital they've raised.From rebuilding Railway's network overlay over a weekend to moving the vast majority of workloads onto its own bare metal data centers, Jake Cooper is trying to build a new cloud for an agent-native world. In this episode, Railway's founder and “conductor” joins swyx and Alessio to unpack why the next era of software infrastructure is not just “Heroku but newer,” what agents need that humans did not, and why the old deployment loop of Git, PRs, CI/CD, and static cloud resources may be heading for a rewrite.We go deep on Railway's infrastructure stack: own-metal data centers, three-month cloud payback periods, cloud bursting, data center debt, Railpack, Nixpacks, Temporal, feature flags, Central Station, content-addressable filesystems, agent-safe production forks, and why the CLI may become more important than the canvas in an agent world. Jake also shares the founder journey behind Railway, how the company survived losing $500K/month, why it now serves millions of users with only 35 people, and why he believes the pull request is dying.We discuss:* How Railway went from a slow six-year grind to adding 100,000 users a week* How Railway thinks about agents as the next dominant software species* Why agents need version control, observability, compute, storage, and orchestration at 1000x scale* The economics of Railway's own-metal data centers and three-month payback* How Railway uses cloud bursting while scaling its own infrastructure* Why data center debt can be a better tool than venture debt for infra startups* Central Station, Railway's internal system for clustering customer feedback and incidents* Why responsible disclosure and over-communication matter for platforms* Why feature flags, progressive rollouts, and shadow traffic are essential for agents* Temporal's strengths, pain points, and why workflows matter for agents* Railpack, Nixpacks, Nix, and lazy-loaded content-addressable filesystems* Why “cattle, not pets” may change if you can clone the pets* Why Railway is building a new cloud from scratch instead of copying hyperscalers* The solo founder path, focus, writing, and how Jake thinks about company buildingRailway:* Website: https://railway.com/* X: https://x.com/RailwayJake Cooper:* LinkedIn: https://www.linkedin.com/in/thejakecooper/* X: https://x.com/JustJakeTimestamps00:00:00 Introduction: What Is Railway?00:02:07 Jake's Path to Railway00:06:13 Railway's Six-Year Growth Story00:08:52 Rebuilding the Business After the Free Tier00:11:17 Agents as the Next Software Platform00:13:29 Railway's Infrastructure Philosophy00:15:42 Bare Metal, Cloud Economics, and the Compute Crunch00:17:22 Cloud Bursting and Five-Cloud Networking00:20:20 Data Center Debt and Infra Financing00:23:31 Data Centers in Space00:25:24 What Agents Need From Infrastructure00:28:24 CLIs, Canvas, and Agent-Native UX00:35:15 Central Station, Incidents, and Responsible Disclosure00:40:30 Safe Rollouts, SRE Agents, and Production Forks00:45:00 AI SRE, Specs, Code, and Tests00:48:24 Self-Replicating Infrastructure and the New Serverless00:53:18 Heroku, Temporal, and Workflow Engines01:04:07 Railpack, Nixpacks, and Lazy-Loaded Filesystems01:06:01 Coding Agents, Token Spend, and Roadmap Acceleration01:10:56 The Pull Request Is Dying01:12:28 Feature Flags and the Agent-Era SDLC01:16:15 Cattle, Pets, and Cloning Machines01:19:29 Solo Founder Lessons01:24:12 Focus, GPUs, and Building a New Cloud01:28:20 Closing ThoughtsTranscriptAlessio [00:00:00]: Hey, everyone. Welcome to the Latent Space Podcast. This is Alessio, founder of Kernel Labs, and I'm joined by Swyx, editor of Latent Space.Swyx [00:00:10]: Hey, hey, hey. Today we're in the studio with Jake Cooper of Railway.Alessio [00:00:14]: Conductor of Railway.Swyx [00:00:15]: Conductor at Railway. Yeah.Alessio [00:00:16]: Choo-choo.Swyx [00:00:17]: Do you actually have that anywhere, like on your business card?Jake [00:00:20]: We call some of our volunteer moderators conductors. I don't have a business card. We're not that big yet. At some point I will. I got handed a nice business card from the Supermicro folks, and I was like, “Damn, this is pretty official.”Swyx [00:00:30]: Business cards are coming back.Jake [00:00:32]: They're cool. They're hip. The conductor thing is good. We're trying to figure out what we want to call each other internally. Some people think it's super cringe and say, “You don't need a name for people internally.” Some people want to call each other something. We still don't have a really good one.Jake [00:00:55]: We've got New Railcrews, Trainiacs. Nothing has stuck yet.Swyx [00:01:00]: I like Trainiac. Trainiac sounds good. Railwayians. For those who don't know, what is Railway? Let's give people a crisp definition up front.Jake [00:01:09]: Railway is the easiest way to ship anything. You go to the canvas, or you talk with Claude, and you say, “Deploy a Postgres instance, deploy my GitHub repository, run this code,” and you're off to the races.Swyx [00:01:22]: You've got a nice animation on the landing page.Jake [00:01:24]: Thank you. None of my work, by the way. They don't let me touch the design stuff anymore.Jake [00:01:25]: We want to make it trivially easy not just to deploy things, but to evolve applications over time. Most tooling right now stacks entropy on top of entropy: Docker, Kubernetes, Ansible scripts, and all these other things. If we can version all of your software and keep track of all the changes, then we can make it trivial to clone environments, fork into a parallel universe, get copies of production data, get copies of any services, make changes, validate them, and collapse them back in without reproducing everything across a staging environment.The Railway Origin Story: From Uber Systems to a New CloudSwyx [00:02:07]: I was looking at your background: Bloomberg, Uber. Nothing immediately stands out as, “This guy is going to found the next great platform as a service.” What prepared you for Railway?Jake [00:02:21]: It was curiosity to keep going deeper. I started out on front-end stuff, working on Wolfram Mathematica and porting it over. Then I briefly moved to Bloomberg, then toward Uber and distributed systems, taking the Jump Bikes systems and moving them to a distributed system built on top of Cadence, the pre-Temporal Temporal.Swyx [00:02:44]: Which, by the way, I'm happy to talk about, pros and cons.Jake [00:02:48]: Totally.Swyx [00:02:51]: But let's do the Railway story.Jake [00:02:52]: It has been a continual step of wanting an experience. Whether it's walking up to a bike, unlocking it, and having it work frictionlessly, or something else, the depth required to make that happen follows from the experience. A lot of the work I do, and a lot of the team does, is in service of that experience. We fundamentally don't care how deep we have to go. We will swim to the bottom of the swimming pool to get the experience.Jake [00:03:17]: I don't have a physics PhD. I did an EECS degree. It has always been about figuring out the next step: how do we get there? That's what led to starting Railway for that experience and then moving all the way to bare metal data centers. I was adding patches to the kernel this week to get the experience there because I can see how much better it can be.Swyx [00:03:49]: Other patches to the Linux kernel this week?Jake [00:03:51]: Yeah. Not upstream. Our fork.Swyx [00:03:52]: That's a flex. Railpack? No, this is different. This is the OS on top of Railpack?Jake [00:03:57]: No, this is an actual kernel patch. It's always literally: what do we have to do to get that experience? Then figure it out. Anything is figureoutable.Swyx [00:04:10]: Would you send the patch upstream, or does it not fit other use cases?Jake [00:04:13]: Maybe. We have to work out the experience internally. It has to do with the storage layer we're building for some of the agentic stuff. Maybe it'll be useful upstream, but it's deeply useful for us internally.Open Source, Forks, and Non-Deterministic VersioningSwyx [00:04:29]: You mentioned open source before. How do you think about starting from open source, and then coding agents letting you do a lot more from forks of it?Jake [00:04:38]: GitHub's original sin is that it's almost a series of broken pointers. You have this thing, then you clone it, and now you've lost the whole upstream. How do we make it trivial for people to modify really small pieces of it?Jake [00:04:51]: We think of Git in a discrete sense: I've either made a change and merged upstream, or I haven't. What would it look like if it were percentage-based, a little more non-deterministic, or a stream of changes that users traverse as a percentage rolled out in general and then rolled all the way up?Jake [00:05:13]: We have the open-source kickback program and let you deploy templates because we want to make it trivial for people to version these shards over time. It solves a large problem around authentication, authorization, and security. NPM has a way to define, “Don't take any new packages.” The ideal end state is that you roll out progressively to users with the minimum impact zone and continue rolling up. JPMorgan should probably be the last one on the patch line, for all our sakes, because our money and livelihoods are there.Jake [00:05:53]: It's okay if Johnny Vibe Coder gets a broken patch because there's so much entropy in the system that the rubber has to meet the road at some point. You have to test at varying levels.The Long Grind: First Users, Free Tier, and Making the Business WorkSwyx [00:06:13]: I wanted to pull up this glorious chart, which is your usage or number of daily signups?Jake [00:06:22]: Daily signups, I think.Swyx [00:06:24]: You started six years ago. It was a slow grind, and now you're on a rocket ship. You say, “Don't doubt your fight and don't quit.” Maybe pick out certain points that were key inflections for the company.Jake [00:06:40]: At the start, it's about getting your first 100 users, hell or high water. We had a website and a support link. The support link was the Discord channel. I had notifications on with two monitors: the monitor I was working on and the other monitor with Discord. If anybody came in, I was immediately like, “Hey, how's it going?” It was rare, so getting those first 100 users to come back was the start.Jake [00:07:14]: Then you build a consultancy factory because users want all these things. You have to go back to the board and ask, “What is the actual product offering I want to build on top of this?”Jake [00:07:28]: VCs want charts that always go up and to the right, but in reality you don't necessarily want charts that look like that. For us, there have been periods of expansion where we add features to test use cases, and periods of compaction where we ask, “If the experience we have is good, how do we make it significantly better?” Maybe we strip out features that don't fit our ICP anymore.Jake [00:07:57]: The boom from 2022 to 2023 came from the free tier. Everybody under the sun was using it.Swyx [00:08:09]: A lot of Reddit bots and Discord bots.Jake [00:08:12]: And crypto miners. When you build an open product on the internet where anybody can sign up, the internet is a horrible place with so many things. You go through periods of asking, “How do I reach as many people as possible?” Then, “How do I fit the exact use case for the people who really matter and are really excited about this specific thing?”Jake [00:08:39]: Then there was a two-year period of making the actual business work. During the free-tier era, we were losing about half a million dollars a month.Swyx [00:08:59]: On a $20 million bank account.Jake [00:09:02]: On a $20 million bank account with maybe $50,000 a month in revenue. That's a horrible business. I don't know how anybody invested. But you have to go through it and say, “We have an experience people love, but the business has to work.”Jake [00:09:17]: There are two schools of thought. You can run the horrible business all the way up with bad margins, or you can go back and make it work. We've always wanted a super lean team. We're 35 people right now. It's very small.Swyx [00:09:36]: Supporting three million already?Jake [00:09:38]: Yeah. We're adding 100,000 users a week right now, so it's growing fast. We don't want to add headcount for the sake of headcount or throw bodies at problems. We want to build systems. It's hard to build systems during expansion because you're adding things to the system because people are asking for them or things are breaking.Jake [00:10:00]: We had to cut off the free users for a little while, rebuild the business, and make sure it worked. We want to reach as many people as possible because software is important. It's become difficult to create things in the physical world, so it's important to make it easy for people to build in the virtual world and have access to creation. But there are legs to that journey.Jake [00:10:30]: You can see divots in the charts. If you follow between 2025 and 2026, it's either summer or winter. People go on holiday with family.Swyx [00:10:50]: It affects that much?Jake [00:10:51]: Yeah. It's kind of B2C and kind of B2B. People are shipping constantly, then they stop. Our activation curve now shows more people activating on weekdays because we have more business users, so it smooths out over time.Agents as the New Interface to DeploymentSwyx [00:11:17]: Was there a point where you started prioritizing AI development or agent development?Jake [00:11:24]: We've prioritized agentic as a top-of-funnel thing. Over the last six months, we've deeply prioritized agentic as a mechanism to build and deploy things because we believe the curve is so steep and that is how people will build and deploy software.Jake [00:11:42]: It almost fundamentally doesn't matter whether this is dot-com or not because we're all on the internet anyway. If agents are going to deploy a bunch of things and we hit an inference wall at some point, we'll fix those problems. The dominant species over the next 10 years is that we've moved from assembly to C to C++ to JavaScript to words. You're going to need to close that loop.Swyx [00:12:13]: When you say this is dot-com, did you mean buying the domain, or the general case?Jake [00:12:17]: I mean the dot-com era, when companies had a huge run-up because people understood the internet was important. Then they hit bottlenecks, fundamental laws of physics, math didn't work, and everybody came back down to earth. But it didn't matter because the internet became so impactful. If you operate on a long enough time horizon, you should build these things anyway because you can see where it's going.Jake [00:12:45]: That's where I think a lot of agent stuff is. You get to a point where you're running thousands of agents in parallel. What is the inference cost? What is the compute cost? How do you make that efficient? How do you coordinate all this? We have issues coordinating humans; we don't even have good tooling for that. Now we have to figure out how to get agents to coordinate, safely version changes, and know when to raise their hand for someone to intervene. Otherwise it becomes an interrupt factory.Railway's Infrastructure Thesis: Network, Compute, Storage, and MetalSwyx [00:13:19]: Let's go right into the technical side. What are the core infrastructure or architectural beliefs of Railway that allow you to do what you do?Jake [00:13:29]: The primitives matter a lot for us. We need network, compute, storage, and orchestration around it. You need control over a lot of those things. We've talked a lot about how we don't really use Kubernetes because we want higher-order control to place workloads in very specific places.Jake [00:13:48]: The reason is that you have to be very efficient with agents: memory reuse and all these other things, or you're going to massively blow up your cost structure. Being able to rack and stack your own servers and build your own metal unlocks performance and cost. Experiences where you're running 1,000 agents in parallel are not massively cost prohibitive.Jake [00:14:13]: Token use and compute use are blowing up. Over time, those things have to get a lot more efficient. You can get a lot of margin to make those experiences solid by building your own metal. That's all in service of offering a differentiated experience to as many people as humanly possible.Swyx [00:14:51]: You have a data center in Singapore.Jake [00:14:53]: Yeah. We have two in every other region now. In Singapore, we're adding a second one in Q3.Swyx [00:14:58]: What's it like? I've never built a data center. Do you go to Equinix and say, “I want some slots?”Jake [00:15:05]: Yeah. Equinix. You basically go and say, “I want power and I want a cage.” They say, “Great, here's what it's going to be.” You rent the cage for a period of time, fill it with racks and servers, and hook up internet to it. That's all the pieces.Swyx [00:15:36]: Then you handle everything else.Jake [00:15:37]: You handle everything else.Swyx [00:15:39]: What's the math versus clouds doing it for you?Jake [00:15:43]: If we rented in the cloud, our payback period when we go to metal is about three months.Swyx [00:15:50]: Which is crazy.Jake [00:15:51]: It's nuts. That's four years of depreciated hardware. You're going to see a lot of this compute crunch because hyperscalers are buying up a lot of stuff. We're working directly with OEMs, resellers, and people building these machines: Supermicro, Dell, and others.Jake [00:16:11]: Upstream, there's a bunch of supply pressure. When we raised our last round, between deploying capital for servers and now, the amount of money we've raised is less than the amount of money we have in the bank plus the value of the servers because the servers have appreciated as RAM has gone up. It's nuts how valuable hardware has become.Jake [00:16:50]: If you look at hyperscalers, they deployed around $80 billion of capital expenditures this year, and next year will be more. That's a massive infrastructure build-out. You look at that and think it's crazy that they're spending way more than the Manhattan Project. But if every person is going to run dozens or hundreds of agents in parallel, you have no conceptual idea how much compute is required to make that experience happen, even if you're deeply efficient and sharing resources. And that doesn't even count inference.Swyx [00:17:22]: How do you plan the build-out? The growth chart is so vertical. Are you usually at 100% utilization as soon as racks are live? How far ahead are you planning?Jake [00:17:33]: We still maintain cloud presence for bursting. We work with AWS, GCP, and a few other clouds. We can rent, and then the moment we get space or power, we compact those workloads off the cloud. We started on the clouds, then built a system to migrate to our own metal. There's nothing that says you can't continually do that again, and that's exactly what we do. We never want to be compute constrained.Jake [00:18:09]: At the start of the year, we actually became compute constrained because one upstream provider wasn't able to give us quota at the rate we needed, and the hardware was slower. I spent a weekend rebuilding our entire network overlay so we could straddle five clouds: Oracle, AWS, ourselves, GCP, and one other one. We can do more than that now.Jake [00:18:38]: We got into a spot where we were trying to pack instances tight because we couldn't get enough compute. That led to a few reliability issues, which are now past us. I made a tweet pointing out that it's becoming harder and harder to acquire compute at the rate these models need to acquire compute. We got bit by it.Swyx [00:19:15]: How do you think about pricing knowing you might not have your own metal available at all times? Are you pricing assuming you need extra margin if you end up going into the cloud?Jake [00:19:26]: Because we've built out our metal data centers, our margins on metal are around 70%. We can deeply subsidize the cloud business if we want to scale at a reasonable rate. We have a few levers: metal, which makes the margins; cloud burst; debt to buy servers; and venture capital. It's an interesting operational problem: how much cash do we have, how much should we raise, how quickly can we deploy it, and can we scale revenue as quickly as we scale compute?Jake [00:20:05]: If we continue making it trivially easy for people to build and deploy, then the faster we close that loop and the more operationally excellent we are with capital, the faster the business can scale. It's almost a straight linear deployment rate.Financing Infrastructure: Hardware Debt, VC, and Operational LeverageSwyx [00:20:20]: I think infra startups raising debt is a tool people don't utilize enough or know enough about. What can you tell us about that? Is it secured against your CPUs?Jake [00:20:32]: It's secured against our hardware.Swyx [00:20:37]: What rates do you get? Who are the lenders?Jake [00:20:39]: We pay prime plus a spread, and we can refinance any of the debt as rates go down. The terms are pretty good. The unfortunate thing is that Twitter has no nuance, so people say, “Venture debt bad.” But as with all things, there are specific tools and areas where you can be deliberate instead of using one tool as a hammer. Venture capital is not the hammer for everything. You have to explore and figure out what works.Swyx [00:21:12]: VC is usually the most expensive financing you can get.Jake [00:21:15]: Yeah. I also think people think about VC incorrectly from a capital-raising perspective. Most people think, “How do I raise as much money as possible from whoever is probably the best I can get at that time?” That's close to right, but what we've tried to do is figure out what unfair advantage we can buy with that equity.Jake [00:21:34]: It's the most expensive equity you're going to give away at that point in time, assuming the company keeps getting better. How do you use it to work with someone stellar who complements you? In the seed stage, I had never started a company. Ray Tonsing had good advice, and I could text him all the time. He was really fast. Awesome.Jake [00:22:01]: Then with John and Erica at Unusual, they said, “You roughly know what you're doing building a product. We'll mostly leave you alone and be available for advice.” Amazing. Then we got to Series A and the business was an operational tire fire because we didn't know how to scale a business. Work with Erica, and Jordan is over at Redpoint, so bonus.Jake [00:22:28]: Now we've raised from TQ and FPV as we're moving into enterprises. Every step of the way, we've asked: who can we partner with at this specific time to unlock the next section of the journey? I don't know enterprise sales. As an engineer, I can eyeball what features we might need, and we have wonderful people internally who can help. But you want boardroom dynamics where everyone is aligned and asking, “How do we win this?” instead of bickering about strategy.Data Centers in Space and the Physics of ComputeSwyx [00:23:31]: You had a tweet about data centers in space. Why no data centers in space?Jake [00:23:37]: It's not “no data centers in space.” My hot take is that I think it is solvable. I've just never seen anybody solve it.Swyx [00:23:49]: You said, “How are you going to dissipate that much heat in a vacuum?” You're making a physics claim.Jake [00:23:55]: I haven't seen anybody prove how you're going to dissipate that much heat in a vacuum. It doesn't mean it's not possible. It just means nobody has brought it up yet.Swyx [00:24:05]: Astrophage.Jake [00:24:06]: I don't know what that is.Swyx [00:24:07]: The Martian thing. Okay, you're very logical.Jake [00:24:09]: It could work. A lot of people are putting the cart before the horse. They say, “We're going to put data centers in space.” Okay, but how? “We have time to figure it out.” It's like in The Martian where they ask how they're going to intercept something and say, “We'll figure it out.”Swyx [00:24:36]: Making a bet on human invention is weird because you blind trust that it can be solved. But with physics, there are first-principles bounds you can put on it. Maybe not. Maybe you're asking to travel time or break a fundamental thermodynamic law.Jake [00:24:57]: I don't know how VCs do this either. How do you know what's not possible and a grift versus what's possible but sounds completely insane? “We're going to put data centers in space.” Coin flip as to which it is, and I guess you'll know in 10 years. That's one cycle.What Agents Need: Versioning, Observability, and 1,000x ScaleSwyx [00:25:23]: Moving back to agents. The branching, fast spin-up, and orchestration you do feels like pre-work that happened to be exactly what agents want. What do agents want differently than humans?Jake [00:25:37]: They want the ability to version things. It's not that different; it materializes slightly differently. Agents want a way to test changes incrementally. Engineers have feature flags. Is there a reason agents can't use feature flags? I don't think so.Jake [00:25:54]: They want version control. Can we use Git or not Git? That one is up in the air. I think something outside Git will emerge for how we version these things over time. They need observability. You need to query what happened, when it happened, which steps failed, traces, logs, metrics, and all the rest. They need network, compute, and storage. They need to write files, save files, iterate on files, and snapshot file systems.Jake [00:26:25]: A lot of what humans needed is in line with what agents need. Branching and forking are not different; we're just moving 1,000 times quicker. It can look like you need something massively different, but what you need is something massively better than what existed. You need orchestration massively better than Kubernetes. You need networking probably better than Envoy. It goes all the way down the stack.Jake [00:26:55]: If the workload profile doesn't change so much as it gets massively compressed because you need thousands of these things, what assumptions change? etcd is going to melt. You need to replace it with something. You can go all the way down the stack and say, “That part has to change, that part has to change, and that part has to change.”Jake [00:27:19]: The interesting thing about the super-exponential curve is that you have to build systems where you can rip out those parts at any time because a new bottleneck might emerge. You get good at parallel agents, and a different part of the system breaks. So it's similar to what humans needed, but at 1,000x scale.Jake [00:27:55]: How do you do code review in the age of agents?Swyx [00:28:00]: You throw more agents at it.Jake [00:28:01]: You don't. But then who reviews for CVEs and all these other things?Swyx [00:28:07]: More agents.Jake [00:28:08]: And that's how we hit the inference wall. You can continually throw agents at the problem, but I think there's a limit to the number of agents you can throw at a problem.CLI, Agent Handles, and Closing the LoopSwyx [00:28:24]: You already had a CLI before it was cool. How is the shape of what you're exposing changing, if at all?Jake [00:28:28]: CLIs have always been cool. The CLI changes because we think about how to give Claude, Codex, ChatGPT, or any model a handhold.Jake [00:28:50]: A CLI is a single command: deploy, get logs, and so on. Things that were prohibitively annoying to humans are not annoying to agents. They're nice. If I handed you a CLI with 40 arguments and 600 flags, you'd think, “I'm never going to use all of this.” But if you hand it to an agent, it says, “This is excellent. I have so many handles to work with.”Jake [00:29:24]: If you're going to expose things to agents that way, you want as many handles as possible where they can get information, query dynamic information, and close the loop quickly. Most problems right now are about how to close the loop as quickly as possible. Where does the agent get stuck, and how can you remove that?Jake [00:29:49]: Telemetry is important. If you can tell where the agent gets stuck from the CLI and say, “12% of people deviate from the happy path because of this, and now I add this argument and drive it down to 2%,” you massively increase the rate of loop closure.Jake [00:30:03]: That's how we think about not just the CLI, but every point in the dashboard. It's a user journey: I hear about Railway. I get something deployed. I get my first green build or aha moment. I see an endpoint, logs, whatever. Then I iterate. The iteration loop is indefinite. The user wants to deploy a new thing, a Postgres instance, change code, and keep iterating.Jake [00:30:36]: If you focus on the iteration loops and what's blocking them from closing quickly, one thing we say internally is: you never want to be waiting on compute anymore. You always want to be waiting on intelligence. If you're waiting on compute, there's a bottleneck that needs to be destroyed because eventually that bottleneck becomes so large that another workflow emerges to change it.Jake [00:31:04]: We've built a product where you push code, build it, and so on. But I fundamentally believe the push-pull loop is going away. We'll get to a point where you make a small change in production, that change is versioned across your infrastructure, you're working alongside copy-on-write versions of your database and infrastructure, and then you merge it in and it's instantaneously live. That's the holy grail of loops. The push-pull-rebuild thing is a point of friction that we're removing entirely.Canvas as Output: Dashboards, Context Anchors, and HyperstructuresSwyx [00:31:43]: It's incredibly fast. If anyone hasn't tried it, that fast feedback is great. My hot take is that Railway was famous for its canvas, which visualizes your infrastructure and lets you manipulate it visually. But that was for humans. For the next phase of growth, Railway CLI is more important than canvas.Jake [00:32:05]: The canvas is funny because it's a mechanism to show changes over time. You're right that previously we used it a lot as an input. Moving forward, its goal is more like an output. You would go to the canvas, make changes, see them, and watch your infrastructure evolve. Now agents have access to the CLI and can make those changes. So the canvas becomes an output: what information does the human need at this moment to make suitable decisions about control requests? Do I approve this or not?Jake [00:32:57]: It also has to be an anchor for your context, a port in the storm. Think of it like layers in a file system. You start with a project, then drill down into services, then into a function or code, because you want to represent the entire thing not just in your head, but in the canvas. Other people can share that representation, think on the same wavelength, and move quickly.Jake [00:33:33]: A lot of organizations get in trouble as they scale because all the context lives in someone's head. “How does this microservice work?” “I have no idea; go ask this person.” Then you have whole categories of products built around context discovery. A lot of that melts away if you have a solid hierarchy and can infinitely nest services, code, context, and everything else all the way down. That's what lets you build these structures over time.Jake [00:34:18]: It's also what lets us build what I've called hyperstructures: things that are way bigger. You look at the Golden Gate Bridge and ask, “How did we build that?” There's a meme that we lost the technology. To some extent, yes, because the coordination that built those things evolved and changed. We lost some of the art of building structure as we jammed everything into Slack.Swyx [00:34:52]: But you jam everything in Discord.Jake [00:34:53]: Same point. It doesn't matter. It's message passing and interrupts, message passing and interrupts.Swyx [00:35:00]: So you're arguing there should be something better and more structured than Slack?Jake [00:35:04]: Yeah. For sure. I think Slack is awful, and Discord is awful too.Central Station: Context Routing, Support, and Incident ClustersSwyx [00:35:09]: This is the equivalent of my mom test. What have you done that has your solution to this?Jake [00:35:15]: Internally, we've built a tool called Central Station that aggregates all the context from our users. Every piece of feedback, every customer support item, everything gets aggregated into clusters. If an incident is brewing, we can determine how many users are affected and break off a discussion based on that.Jake [00:35:40]: That is more helpful than long-running channels where you're trying to decide which channel to put something in. If you can dynamically aggregate information and dynamically route it to the right person based on context, it works better. We know internally that these four people are close to networking. If we see a networking thing, we can drill it down to those four people. If it's with this part, we can look at the commits. This is no longer a manual process internally.Jake [00:36:13]: If you go to station or help.railway.com, that's why we built it. We wanted to scale with a massive amount of leverage by aggregating feedback.Swyx [00:36:27]: This is built in-house?Jake [00:36:28]: Yep.Swyx [00:36:29]: I remember helping out on this one with Angelo in 2023. You scale a lot with a very small team.Jake [00:36:38]: Yeah. We're about 10 times bigger now.Swyx [00:36:40]: You have your full developer code here? Very cool.Jake [00:36:44]: If you go to railway.com/stats, we expose this as a pub-sub-able thing. It's all real-time metrics. There's a way to get it as JSON somewhere if you care.Jake [00:37:01]: We're big on trying to build everything in public and talk about what we're working on. We've had issues in the past, and we'll say, “Here's how we're fixing these things.” We've gotten compliments and flak for incident reports. We're always trying to make them better and talk with people.Incidents, Disclosure, and Progressive RolloutsSwyx [00:37:20]: You had a big one recently. I liked that it was scoped to 3,000. You presumably used Central Station. Talk through what happened and how you address it internally as a team.Jake [00:37:38]: Internally, this one really sucked. It had to do with an upstream provider that didn't do the behavior it said it documented, which is unfortunate given they wrote the RFC for how the behavior should work. We rolled those things out, and Central Station caught it initially when a couple users said caches weren't invalidating. We turned it off immediately.Jake [00:38:03]: When you roll out to a large user base of three million people, you get a lot of disparate behaviors. We tested in staging and had tests, but we hit an edge case. We've hardened those systems, and now we can make that better. But it was a tough one.Swyx [00:38:39]: I always wonder how private disclosure is supposed to work if people find an issue. Are they supposed to contact you first? When you run a platform, these things will happen. What channels should people pursue to quietly resolve it before it becomes a bigger incident?Jake [00:38:59]: There's responsible disclosure. We err on the side of over-disclosing and letting you know something is wrong versus having your provider gaslight you. We've erred on sharing those things more publicly, even if they impact a small subset of users. That's a decision we've made internally. We have four values. One is honor. The honorable thing is to notify people to the widest degree at which they may have been affected or there was an issue, and then confront it head-on: why did it happen, what can we do better?Swyx [00:39:45]: Not the whole user base. That's because of incremental rollouts and other things?Jake [00:39:50]: Yeah. Progressive rollouts.Swyx [00:39:54]: That should be the norm at all large platforms.Jake [00:39:58]: It should. A variety of companies do this. There's the quote that Meta runs 10,000 different versions of Meta. To our earlier point about agents, they need the same thing. They need shadow traffic and all these other things. We've built so much ceremony around production being sacred that we need to make it trivially easy to test different behaviors in a safe environment. Then you can make mistakes in a safe environment.Safe AI SRE: Customer Agents, Forked Environments, and Production ParityAlessio [00:40:30]: Do you see a world where these things get automatically caught, not necessarily by your agent, but by your customer's agent? The cache invalidation issue seems easy to check if you know to look for it.Jake [00:40:44]: It's hard because to determine it, we almost need to hook into your observability infrastructure. That's why we have the template loop on the platform: so you can roll things out progressively. You can roll out to Johnny Vibe Coder initially, or push a shard that someone consumes at their own leisure. Or you can roll it out over weeks: 0.1% of people, 1% of people, early adopters, then all the way up. That's the non-deterministic version control we talked about earlier.Jake [00:41:30]: I believe that's where most things should go, because most companies end up building staged rollout systems in-house. It's the same thing built again and again at every company. There's a massive opportunity to consolidate developer debt.Alessio [00:41:45]: You should have a free tier. Model providers give free tokens if you let them use the data. You could give free compute if someone is the number-one shard that goes out and lets you plug into their observability.Jake [00:41:55]: We do that. That's why we talked about the impact on 3,000 people. We start with lower-impact people. Larger companies on the platform are last to receive those rollouts so they have a version of the platform that's deeply stable.Alessio [00:42:16]: I have three services, so I'm sure I get the first rollout. You can nuke my thing at any time. There are all these SRE agent companies. Observability people also want agents that fix upstream problems. You have your own agent in the canvas now. How do you see that playing out?Jake [00:42:39]: It's the stacking entropy problem. If you don't have primitives to make iteration in production safe, it becomes difficult. If you're an observability provider saying, “Here's the fix to this error,” assume 80% are good and make sense. But in the last 20% long tail of complex issues, if you let somebody stamp it, you create an opportunity for an incident.Jake [00:43:08]: That's why forked environments are important. People have staging, but it always drifts from production. You need primitives, workflows, and experience built first-party on the platform so you can fork any service at any point in time.Jake [00:43:33]: I think of the canvas as a sheet of transparency paper. The agent is a little guy you push up into the canvas. It should say, “I need to copy that service and that service so I can test these two things.” It gets a read-only copy of production. Anything that's PII gets marked as a transform when we clone the database, create a copy-on-write version, or read from it. Then the agent makes changes and asks, “Does this actually work?” as close to production as possible.Jake [00:44:22]: That's how close you have to be, or you get massive drift. The system becomes unstable. You see this with massive systems built on Docker for local, Kubernetes for production, and a specific thing for something else. That complexity slows developers and becomes unstable at scale, making it hard to iterate. We want to compress that way down and say, “As close to prod as possible is where we want to be.”From AISRE Skeptic to Agent BelieverSwyx [00:45:00]: I was texting Erica for questions, and she says you were originally not a believer in AISRE. Have you come around on it?Jake [00:45:10]: I flipped, but I'm still not a believer in AISRE if you don't have the primitives to make it safe. If you unleash AISRE on production infrastructure without safe primitives for copying volumes and making sure things are fine, it's going to nuke your production database. It's not a matter of if, but when. I'm a big believer in making those loops safe.Jake [00:45:33]: I was a deep AI skeptic until 2023. In 2024, I thought, “Maybe I can roughly make this thing do it.” In 2025, I thought, “Now I can hold this.” Over winter break, everybody came back saying, “It's almost impossible to hold this.”Swyx [00:46:01]: Did you see this on the Claude docs? CloudBot? OpenCloud?Jake [00:46:06]: It's gotten to a point where it's harder to hold it wrong than to hold it right. There's a scene in Avengers where Vision picks up Thor's hammer and says it's terribly well-balanced. It self-balances and works well. I'm a deep believer at this point that this will be the dominant species: assembly, C, C++, JavaScript, words.Swyx [00:46:35]: It feels like a big jump.Jake [00:46:37]: It is. But it's not like you abandon CPU-based discrete logic and move straight to fuzzy logic. You need both. Your skills should call code or applications or some static structure. You can use skills to distill what the procedure should be or how the code should act.Jake [00:47:02]: I'm coming to a thesis: you need three points. You need a clear spec defining the system, the code, and the tests. When you say it out loud, if you've been in engineering long enough, you're like, “Of course. That's an RFC, tests, and code.” But they all matter. Having them together lets them reinforce each other: the spec and tests match, but the code doesn't, so reconcile it. Or the tests and code match but the spec doesn't, so reconcile that. That's the iteration loop.Jake [00:47:41]: That's why you're seeing people talk about software factories, docs, and reconciliation. Some of that is architectural astronomy if you don't implement it, but that loop is where most things will end up.Swyx [00:48:07]: For listeners, we've been talking about this on the pod for three years: the holy trinity of specs and tests. Itamar Friedman from Qodo is the reference if people want to look it up.Self-Modifying Infrastructure and the End of Push-Pull-RebuildSwyx [00:48:18]: One thing I want to mention on the OpenCloud idea is self-modification. I don't know how Railway would support it, but I have my OpenClaw, and I just tell it it has the Railway CLI and can do whatever. In theory, whatever capabilities or new infra it needs, it can call the Railway CLI, provision it, and add it to itself. The agent can modify its own infra.Jake [00:48:45]: It's nuts. I have a loop set up where you put the Railway CLI on top of something that runs on Railway. You're authenticated as whatever the current box is, and you can make any changes to it. Then you call Railway deploy, and it deploys itself.Jake [00:49:04]: It's like: “I need to spin up this instance of this environment. I already exist in this environment. Excellent, I have access to a Postgres instance now.” That's where we want to go with agentic, self-replicating infrastructure. That's your loop: iterate in production. You continue making changes. If it works, merge it upstream. If it doesn't, throw it away.Jake [00:49:37]: How do you make throwaway copies trivial to spin up and super cheap? The era of “I have an AWS instance with four vCPU and 16 gigs of RAM” is going to get destroyed. If you do that for agents, you need a thousand of those machines. It's prohibitively expensive compared with what we've spent a ton of time figuring out: the atomic unit of deploy, whether you call it isolates, sandboxes, or something else. Only pay for what you use, spin up instantaneously, and close the loop as quickly as possible.Jake [00:50:15]: If the system can self-replicate safely and say, “This is my environment, I'm making these changes,” it can come back with, “Does this look good? This is a new state of infrastructure given this prompt. I think I've solved it.” Then you go back and say, “Actually, it looks different.” It does the loop again. Then you say, “Cool. Apply.”Swyx [00:50:38]: That's retroactively obvious, which is the most useful kind. Any other comments on agent deployment on Railway?Jake [00:50:51]: It's getting better every day. I'm on X or Twitter. You can always yell at me about the parts not working as well as they should, because plenty of things should work way better.The New Serverless: Stateful, Long-Running, Pay-for-What-You-Use LinuxSwyx [00:51:04]: At this stage, when people want massively or embarrassingly parallel compute, they usually talk serverless. I feel like there's a new serverless compared to the previous five years of serverless. You're in that new bucket. Do you have comparisons or philosophical differences you want to call out?Jake [00:51:31]: It's somewhere in between. It's the ability to run stateful, long-running workflows or executions.Swyx [00:51:42]: Vercel has Fluid Compute, Cloudflare has some container thing, Google has App Runner and others.Jake [00:51:55]: That's where everything is roughly going, and it's why we've been working on this for six years. We believe users need access to a computer: a box that speaks Linux. They need to deploy what they want. Other systems change the surface area of what you can build. For us, users need a computer and need to deploy anything they truly want. That's why we've focused on the primitives: network, compute, storage. If we give you those and expose them so you can run things indefinitely, that's where we believe it's going.Jake [00:52:43]: Twitter has no nuance, so everyone says “servers” or “serverless.” It's always somewhere in the middle: I want to run it for a long time, but I don't want to provision the resource statically or pay for things I'm not using. That's been our thesis from day one: pay only for what you use, run it indefinitely, and it is full Linux.Swyx [00:53:12]: That's why I like the naming of Fluid. It's fluid. Flexible.Heroku, Focus, and Carrying the Torch Without Becoming the PastSwyx [00:53:18]: Another milestone is the Heroku official deprecation. You're one of the presumptive new Herokus. “New Heroku” has been a category for as long as I've been in developer tooling. It's finally happening. What was that like? Any behind-the-scenes of, “This is the moment”?Jake [00:53:42]: You have people where you're like, “You were running stuff on here? You, as this company?” It's crazy that names you would know are running on it and now coming to us saying, “We want to move a lot of this off.”Swyx [00:54:00]: Any behind-the-scenes on why Salesforce let Heroku stagnate?Jake [00:54:05]: I can only guess. It's hard when it's not your business. Salesforce's business is to build a great CRM. That's their focus. Then you acquire a compute business as an offshoot. A lot of early Meta people talk about focus. Boz has a write-up about how in the early days of Meta they had no money, so they were forced to focus. Then they turned on the money tree and had no reason not to split their focus.Jake [00:54:52]: But that dilutes your product. You get offshoots where you ask, “Is this the focus of the business?” If it's not core, it languishes. A lot of companies get in trouble when they split focus because they're fighting a multi-front war, not just externally but internally for alignment. Where are we going? What are we doing? What is our purpose?Jake [00:55:24]: If you're Salesforce-built and mission-driven, you want to work on Salesforce. Heroku is off to the side. It's not core to the business. Getting resources, budget, focus, and alignment internally becomes hard. It was a matter of time.Swyx [00:56:06]: Kudos for them to call it out instead of leaving it unknown.Jake [00:56:12]: Their release was a little odd. They called it out, but they didn't say they were shutting it down. Behind the scenes, I think they issued messages to people saying they should close accounts and that they were going to deprecate and remove things over time.Jake [00:56:30]: It's crazy because some of my first deployment experiences were on Heroku. You start with dragging things into an FTP server, then you try to get a deploy working, and then it's Heroku. It was the on-ramp for us. But the wheel turns. New things emerge. We're happy to carry the torch for a lot of that. But we don't want to be the new Heroku. We want to be the way people build and deploy software, and ultimately the way people monetize software over time.Swyx [00:57:19]: It's still a big crown to be the new Heroku. There are 50 companies that fought for that.Jake [00:57:23]: Everybody is holding some portion of it. We're happy to support people and companies. The platform works differently. The game loop is similar, but we've been dogmatic about where these things are going: primitives, agents, fan-out. Some things fit; some workflows need to change. We have an approximation of Heroku pipelines with the environment system. It's exciting. We've got a ton of people we can support, and it's growing a lot.Temporal, Workflow Engines, and State MachinesSwyx [00:58:12]: I have one more technical question about Temporal. I've sold my shares. You're a power user and one of our earliest customers. I met you through Temporal. You built on Temporal. You have complaints. This may be the most neutral and informed conversation anyone will hear about Temporal without someone working at the company.Jake [00:58:39]: That's fair. I've used Temporal for almost 10 years because of Cadence at Uber.Swyx [00:58:52]: Give people a sense of what Cadence was at Uber.Jake [00:58:57]: Cadence was the precursor to Temporal. It powers trip actions, rides, when you rent a Jump bike or scooter or car. You're running workflows for a period of time and saying, “This ride will run indefinitely until it finishes.” You attach information: you paused in this zone, so add this charge to the bill. When you end the trip, the workflow is done. That experience was powered by Cadence at the time.Swyx [00:59:34]: I used to say it's like programming the entire user journey top-down as one function.Jake [00:59:39]: It's a powerful idea and important. It's also important for the next phase of the agentic journey. You want an agent to do a specific task, be complete or incomplete on that task, and move on to the next thing. You need a way to manage workflows dynamically.Jake [00:59:59]: Temporal was always great in theory, and great when you got it working the way you wanted in production. But it required you to model the entire journey in your head. If you didn't, you could cause issues where replaying the state of the workflow causes non-determinism.Swyx [01:00:25]: Because it works on deterministic workflow history.Jake [01:00:28]: Exactly. I describe it as a jet engine. If you know how to operate it and run it, it's great. But you can't hand it to people trying to build complicated things if they don't have the whole state in their head.Jake [01:00:48]: We run our whole deployment pipeline on top of it. That's a reasonably complicated workflow: pre-commit hooks, signaling, queuing, and all the rest. We ran into the same thing at Uber. As you express a large workflow, it gets more complicated, with more states in the state machine that you have to map back to the workflow.Swyx [01:01:15]: It's a lot of ifs.Jake [01:01:16]: Exactly. At Uber, we built a system for doing the state machine and testing it. We've started to build some of those things here because it's grown heavily. It's not quite love-hate. When it works well, it works super well. But if someone who doesn't have full context puts something into the system that invalidates state or causes non-determinism, or spins off a ton of activities, you have to keep track of underlying SRE knobs like activity slots. Those should scale with memory, vCPU, and so on. It becomes a bear to scale.Swyx [01:02:10]: You need a capable sysadmin running things behind the scenes. If you moved off, what would you do?Jake [01:02:19]: We'd build our own workflow engine. We have a few internally that we've worked on.Swyx [01:02:27]: This is one of those classes of things you typically wouldn't vibe code, but I'm wondering if you can.Jake [01:02:33]: I still don't think you should vibe code it. You still want to run decent tests to make sure it works.Swyx [01:02:39]: Timo didn't invent that from scratch either. There are libraries you can run. On top of that, it's just a state machine that you have to map out. Ultimately, you define the instructions you want and run them through a state machine.Jake [01:03:00]: It's very doable. Workflow stuff is interesting. Restate is doing neat stuff here.Swyx [01:03:10]: You're tied into JavaScript. Are you a JavaScript maxi?Jake [01:03:13]: Internally, we have TypeScript, Rust, and Go. We don't add more languages. Actually, we have a little C because we write BPF code and hooks. But those are the languages.Swyx [01:03:28]: Is this for sidecars?Jake [01:03:32]: No. It's for the networking stack, volumes, and things like that. We use TypeScript a lot because it powers the dashboard, but we're moving a lot of workflow stuff off the dashboard stack and into the infrastructure stack.Railpack, Nixpacks, and Content-Addressable FilesystemsSwyx [01:04:00]: Cool. Any other technical infrastructure stuff? Railpacks?Jake [01:04:07]: We built an engine for determining dependencies based on source code. It's called Railpack. We built the first version, Nixpacks, on top of Nix, and then we moved.Swyx [01:04:17]: People have been trying to get me to adopt Nix and NixOS for four years. Is it ever going to be a thing?Jake [01:04:23]: I don't know. We're excited about it, but it has pain points. Think of it as a stack of versioned binaries at specific slices in time. If you want version X and version Y, you bloat the package space, which blows up image size and makes real-world workloads difficult.Swyx [01:04:53]: But you content-address it and cache it. In theory, there are optimizations.Jake [01:05:00]: In theory, yes. But with a large enough user base and disparate enough machines, you run into a problem Meta described in the XFAAS paper, their internal serverless system. It becomes difficult at scale unless you break out specific runtimes.Jake [01:05:24]: We didn't want to do that because we wanted to truly allow you to deploy anything. That was our initial thing with Nix. But we've moved toward interesting work around content-addressable file systems that can lazy-load anything from any point and page it into memory.Swyx [01:05:48]: Amazing.Jake [01:05:49]: The future is very bright. It's crazy, and it's going to be nuts.Coding Agent Spend, Roadmaps, and Token ROISwyx [01:05:54]: Founder journey stuff?Alessio [01:05:56]: Your cloud usage: you tweeted you're going to spend $300K this month?Jake [01:06:01]: I think we got to $200K.Alessio [01:06:02]: Coding agents?Jake [01:06:03]: Yeah.Swyx [01:06:04]: Across the company?Alessio [01:06:05]: You only have 35 people, so I'm sure they're not all spending $10K a month. What's the distribution?Jake [01:06:10]: I think I'm at about $25K. We have power users all the way down. We came back from winter break, and I basically said, “If you're writing code by hand, you're doing this wrong.” The tools are good enough now that you can move extremely quickly. There are issues and pain points, but you should be reviewing the code you are writing instead of writing it by hand.Jake [01:06:40]: Architectural patterns matter more now than ever, but you shouldn't spend your time generating code you would write. If you know how to write it, ask the agent to write it and reconcile it until it looks like you would have written it yourself.Jake [01:06:58]: People misconstrue my propensity to push people toward agents as connected to our growth and some reliability bumps. They're not necessarily related. The tools are good enough to move extremely quickly and build things way larger than you could before.Jake [01:07:19]: To the earlier point about cooling data centers in space: I don't know. But with software, you can ask, “How would I build block storage from scratch? How would I do these things?” I have ideas because I have history and have read papers. Let me work them out and build massive test benches with thousands of tests, because those are now free to author. If you're not using AI systems to speed-run your roadmap and reconcile your existing system onto the future, you're missing a large point of what's happening.Alessio [01:08:12]: What's the path to spending $3 million a month? Is it bound by ideas and things customers can absorb?Jake [01:08:19]: For most companies, it's bound by deployment at this point. That's why we've seen a massive boom in users and companies, from Fortune 50s down, asking how to get developers to move faster. You'll probably hit your CFO before any technical limits because they'll look at the eye-watering amount of money spent on tokens. Inference costs have to come down, but we're inference constrained now. There will be price discovery around what makes sense for an org to adopt.Jake [01:09:06]: I think you'll end up with the F1 driver concept. If someone is really adept at these things, it makes sense to put them in a $3 million car. If they're not, it probably doesn't make sense. You'll take a few people and say, “You can drive the F1 car. We need to go in this direction. Figure out if it works and prototype it.”Jake [01:09:33]: We've done some of that and vastly accelerated our roadmap. We thought we'd ship something in a few years; now we can probably ship it in a few months because we validated it and don't have to build it incrementally. We can skip steps and move toward our vision.Alessio [01:09:58]: A lot of people are realizing the roadmap doesn't always have a business impact, so they say tokens are too expensive. But if your roadmap were built to make more money by the time you built it, you'd have token pricing for it, the same way you do with sales. You'd spend a billion dollars on sales if you knew you would get $2 billion of revenue.Jake [01:10:19]: Exactly. A naive way to measure this is the percentage of tokens that end up in production. If you can measure impact because those tokens end up in production, that's awesome. But the burden of proof will rise. Internally, we have a growing number of pull requests that haven't merged. The question becomes: how do you get this into production? It's about how quickly you can build and deploy software, which is exciting because that's our whole thing.The SDLC Shift: Prompt Requests, Feature Flags, and Safe RolloutsSwyx [01:10:56]: The SDLC is changing. One thesis is that the pull request is dying. It's going to be the prompt request. Beyond that, code review is also kind of dying if you have all the other systems in place. What else is changing about the SDLC?Jake [01:11:19]: The AISRE and the tools to make it happen. AISRE is pie-in-the-sky aspirational. What does it take to get an AISRE? What tools do you need to build?Swyx [01:11:32]: You should expose your tooling to customers at some point. The Central Station command center.Jake [01:11:39]: We have it for template maintainers. Template maintainers can deploy and maintain templates, and they get feedback. We're going to expose those things incrementally.Swyx [01:11:51]: Clustering around incidents. Everyone has a version of that, but I don't think anyone has solved it.Jake [01:11:56]: I won't say we've solved it internally, but it's gotten so good that we can see incidents forming pretty quickly. At some point, those will be things either someone else builds or we build. We've always built things purpose-built for us. If it makes sense to make it useful for users, monetize it, or turn that loop into a profit center instead of a cost center, we want to do that.Jake [01:12:28]: Pull request is definitely dying.Swyx [01:12:29]: Do you do first-party feature flagging and incremental rollout stuff?Jake [01:12:34]: We have a feature-flagging engine we built internally and will eventually roll out.Swyx [01:12:38]: I don't see it as a user. How come you didn't give us what you have?Jake [01:12:43]: We have to beta test it. We care a lot about the quality of the things. There's plenty we've used internally that doesn't make it all the way through the journey because it fails. It works for one service but not multiple services. We'd have to build it for multiple services and know that if we released it, we'd rebuild it again and again. Some things are worth that, but many inform the roadmap.Jake [01:13:18]: We don't want to dilute the experience by saying, “This works, but only for this service,” unless it's a core initiative. Over the next few months, we'll roll out things that work for a single service, then multiple services, then multiple services across the environment. You have to be deliberate. Otherwise you create broken disparate experiences and support load because people ask how to use the feature.Jake [01:13:52]: It's the earlier expansion and compaction pattern. You expand the company to get features, then compact and smooth them out so the experience is stellar. You told me in the hallway, “It's gotten so much better.” Internally we're saying, “This part really sucks. We need to make it significantly better.”Swyx [01:14:11]: I can attest to that over the last three years watching you build Railway. For listeners, feature flagging is a huge part of Uber culture. So much so that they have too many feature flags and another thing to remove feature flags. Facebook has Gatekeeper. Agents are going to need this. It's fundamental to incremental rollouts. OpenAI acquired Statsig. GPT-5 is routing and flagging through different models.Jake [01:14:56]: It's super important. If the software development lifecycle is going to change because we're doing things 1,000 times faster and 1,000 times more concurrently, what becomes important at scale?Jake [01:15:16]: Before I started Railway, I built a feature-flagging product and tried to sell it. It was an easier version of LaunchDarkly. I ran into a problem: anyone small enough to adopt your technology doesn't care about feature flags, and anyone large enough to need feature flags needs so much scale that you have to build out all the infrastructure. I scrapped it.Jake [01:15:42]: But what is old is new again. Companies are trying to move quickly, but you can't YOLO a vibe-coded thing straight into production. You need to say, “Here's my blast radius, my impact, and I want to shadow it for these users.” Feature flags. You're going to need the tools larger companies built to maintain their structures. Everything gets compressed by 1,000x so everybody can build those structures quickly.Jake [01:16:07]: That's exactly where we are: compressing the software development lifecycle, then expanding it and adding more new things.Cattle, Pets, and Clonable InfrastructureSwyx [01:16:15]: Another term that comes to mind for newer developers is “cattle, not pets.” People treat production like a pet. It has a name. You baby it and keep it alive. With cattle, you can mass farm, roll out, portion parts out, and kill them.Jake [01:16:37]: I think that might change. You can move toward having pets as long as you have a cloning machine for your pets.Swyx [01:16:52]: Yeah.Jake [01:16:52]: If you can snapshot every single thing at every frame, it doesn't matter if something gets obliterated because you have a snapshot of it. The things we've built right now are designed to block changes from the hermetically sealed DevOps line. You have to write a Dockerfile because you nee

You've worked hard, saved well, and now you're thinking about giving back—maybe to your kids, your grandkids, or a cause you care about. But should you wait and pass that wealth on later, or give while you're still around to enjoy the impact? Let's talk about how to make that decision with confidence.   Helpful Information: PFG Website: https://www.pfgprivatewealth.com/ Contact: 813-286-7776 Email: info@pfgprivatewealth.com   Disclaimer: PFG Private Wealth Management, LLC is an SEC Registered Investment Advisor. Information presented is for educational purposes only and does not intend to make an offer or solicitation for the sale or purchase of any specific securities, investments, or investment strategies. The topics and information discussed during this podcast are not intended to provide tax or legal advice. Investments involve risk, and unless otherwise stated, are not guaranteed. Be sure to first consult with a qualified financial advisor and/or tax professional before implementing any strategy discussed on this podcast. Past performance is not indicative of future performance. Insurance products and services are offered and sold through individually licensed and appointed insurance agents.     Marc: Welcome in once again to another edition of Retirement Planning, Redefined with John and Nick, and we're going to talk about gifting money while you're alive or leaving a legacy. You work hard, you saved well, so let's talk about how to gift and leave a legacy.   Welcome into the podcast everybody. Thanks for hanging out with John and Nick and myself as we talk about these topics this week. And guys, it's gifting, right? So I want to go over some basics here. It seems like there's been a trend the last couple of years for people to enjoy their retirement legacy with the family versus the old way of you pass and you'll leave a check, right? Here's your inheritance, we're gone, that kind of thing. So let's talk about that a little bit this week on the show and just kind of see what you guys are seeing in your neck of the woods. How you doing this week, Nick?   Nick: Good, good. How about yourself?   Marc: Doing pretty good's. How's the wedding action coming?   Nick: Planning's moving along.   Marc: Nice.   Nick: Did some, hopefully we got the food picked out, so trying to check off all the big things, so.   Marc: That's important. Got to have that good food going on for sure. Well, good. Kudos. Good. Glad to hear that. And John, my friend, how are you this week?   John: I'm good. I'm good. Summer just started for the kids, so getting used to waking up in the morning and they're hanging out with me as I'm getting ready for work-   Marc: And they're ready to go.   John: Versus me just dropping them off. Yeah.   Marc: That's right.   John: It's a lot of fun.   Marc: There you go. Are you guys seeing this trend that I talked about, not necessarily a new trend. It's been going on for a number of years now, but I think where people just want to maybe enjoy some experiences with their loved ones while they're still here versus just leaving that check, so to speak? Are you guys seeing that in your practice as well?   Nick: Yeah, I'd say so. We've had, what are we on now? A 14, 15 year bull run from the standpoint of people have kind of exceeded what their perspective on goals was for the money that they might have in retirement and, so especially I would say, at least from what I've seen, the vacation side of things is kind of the biggest thing that people have been doing where they'll do a large family vacation and pay for the kids and their families to go so that they can all enjoy that together.   Marc: Yeah, that's very cool. And we'll talk about some of the numbers and things in just a few minutes, but John, I'll kick this over to you. I'd say the first step probably still should be, make sure you are covered first, right? We all want to leave and do things for our kids and loved ones, but don't sacrifice your own retirement in order just to do that. Is that a fair place to start?   John: That is 100% where you should start. The last thing you want to do is start gifting and spending money on a vacation, and then you look at it and you're like, "Oh man, I don't have enough money to live anymore." So first thing we do in this situation where it comes up with clients is like most things we say, we look at the plan and we will stress test it and look at different scenarios to make sure, hey, if this were to happen, how does your plan react to it? So we'll throw out some scenarios out there, whether it's healthcare, inflation, social security, things like that. And if the plan looks solid, we will typically give somewhat of a green light of, we think you should budget X amount for this. Or we can also look at scenarios where Nick talked about vacation, but we've seen some others where it's like, "Hey, I want to help my son, daughter with a home purchase." And with the way prices are going now, it's very difficult for first time homeowners to be buying houses. So we've seen a lot of people basically lending, not giving money to their kids for buying homes. So we will put that in the plan and say, "Hey, what does your plan look like if you were to give X amount for a down payment?"   Marc: Gotcha. Okay. And we'll talk about some of those numbers and ways to do that here in a few minutes. So I would say if step number one, as John pointed out is make sure you are covered. The next step number two is maybe just kind of clarify your motivation. He kind of touched on that a little bit, but why are you giving, I mean, again, we all love our kids. We want to help, but what's the purpose? Is that an important kind of factor to decide through?   Nick: Yeah, I've had some recent conversations where maybe there's specific topics like, okay, we're off conversions, and because somebody has read or seen an article or something like that, the thought process is, all right, well let's go ahead and let's convert all of our qualified money to Roth accounts and leave the money to them. And a tricky thing with that can be, as an example, is maybe their kids are not in the same sort of economic space as they are and they're not going to ever make nearly the same amount of money. Them taking a hit right away from a tax perspective maybe doesn't make sense, so try to take them back to the initial point in, Hey, what's your motivation? What are you trying to do? What's most important to you? Is it making sure that your plan is structured well to protect you first and then start to do some giving while you're alive? Or is it more focused on you want to give after you pass away and let's structure your assets accordingly?   So just so many things, making sure that you fully understand what your objectives are because it can be a little bit of the shiny new thing or a shiny new strategy that weren't familiar with at first or initially, and then once you go through and evaluate it in more detail, maybe it doesn't make a whole lot of sense. But yeah, really understanding how account types work, what your goals are and really what your focus is really important.   Marc: And of course, working with a financial professional is going to help you identify that because often we're not going to know what the account types and the rules and the taxation things are going to be, so that's why you want to turn to the pros on that. So let's get into some of the numbers a little bit, guys, because I actually want to point out a couple of things that based on what you've said so far, and just kind of ask you some clarifying questions on that. But let's start with understanding the gifting rules. So John, what's some of the numbers that we need to know if we just want to gift money in general?   John: So you want to look at what is the gifting amount before you trigger having to file a gift tax return or putting that on your return that you gifted money. So this number changes from year to year typically, and in 2025, it's $19,000 per person. So example, let's say you have a mother, father, and they want to gift to a child. They can each give $19,000 apiece.   Marc: So married couples 38 grand, right?   John: Yes. So that's a good starting point. And then if you have grandkids involved or whatever, you can start gifting to that. So it's $19,000 per person per year without triggering the gift tax filing.   Marc: And that's hefty. Now I'm sure somebody listens going, "I love my kids, but I ain't giving them 38 grand."   John: Again, everyone's situation's different.   Marc: And you can do that. And it doesn't matter if it doesn't have to be family either, right? This could be anybody, right? You can give 19,000.   John: It can be anybody. Yeah. If you want to just find a random person in the street, you're more than welcome to-   Marc: Your favorite podcast host. I mean, podcast hosts need love too, so I'm just saying.   John: Yeah. So that's definitely the starting point. If you're going to be gifting money to any particular individual. If you want to help out with tuition and medical expenses, as long as it's paid directly towards those institutions, you don't have to file any type of gift tax return.   Marc: Now, I wanted to ask you about that because a minute ago you guys were talking about helping with school. Now you can't gift the money and pay the loan, right? It's not paying the student loan, it's paying the tuition. There is a difference there, correct?   Nick: Yeah. And you want to pay it directly to the institution.   Marc: Gotcha. Okay. That's important to know too, right? I'm sure from a tax standpoint as well. All right. What about QCDs, John? Can we do that in that arena as well? If you want to do some gifting?   John: Yeah. So let's explain what that is. So it's qualified charitable distributions from your IRAs. Nick and I use this quite a bit. So when we're doing the fact-finding with clients, one of the main, not one of the main, but one of the questions we go through is, do you do any charitable gifting? And if they check that box, we'll typically find out what institutions and how much they're giving. And once someone hits RMD age, a great way to save on taxes is gifts directly from your IRA. So you could save quite a bit depending on how much someone's gifting. So example, we have someone that doesn't necessarily need their distribution from the IRA, and they were just taking money out of just cash flow, whether it was social security or pension, they were gifting it to their church. What we would typically do is say, "Hey, let's kind of switch this. Let's go to, let's pull out of the IRA." Let's just use number. Maybe it's 10 or 15 grand and we're going to go directly from the IRA to the charitable institution. In this example, it's a church, and you don't pay any taxes on that amount that came out.   Marc: That's ideal, right? And Nick, thinking about how you, if you're a charitably minded person and talking about leaving a legacy, since this kind of rolls into this conversation, people often ask, "Well, which account should I use for what?" And John mentioned that earlier. So if you're thinking about leaving money to your kids and you've got money in a Roth, you might want to leave the kids that right? And then maybe QCD some money from the IRA over to the church, for example, because that's a tax benefit to everybody. Correct?   Nick: Yeah, for sure. That makes sense. I would say to one kind of red flag, or at least something to be very aware of and had this conversation recently with a client is, while you're alive, if you're in a position to be able to gift and if you're in a position to be able to choose where you want to gift money from, avoid gifting from highly appreciated assets from the standpoint of let's say there's a property or there's a taxable brokerage account that maybe you've held 10 different stocks for 20 years and they have a substantial gain. If you gift that while alive, then the recipient, when they sell those is going to pay taxes on the gain versus if you gift it after you pass away, those investments will get a step-up in cost basis, which can save a significant amount of money from a tax perspective. So I would say where you gift from is absolutely, probably if this is something that's important to you, that's where the largest amount of strategy comes into play and doing it from the right place.   Marc: Nick, any other things we missed as far as with the QCD or some of the numbers there?   Nick: Yeah, one thing that we have run into is that some custodians, including the one that we use, Charles Schwab, they don't send out a specific tax document when somebody processes a qualified charitable distribution. So that's something that you want to keep records of and indicate that you've done that with your tax preparer. We've had a couple of clients where they were anticipating that they were going to receive a specific document that laid out exactly what they did, who it paid to, and that sort of thing and that was not the case. It shows the distribution via the 10-99, but they have to notify the tax preparer and usually provide some sort of documentation showing that they made that gift to a charity. So just from a best practice sort of standpoint, that's something to keep in mind.   Marc: All right. All right. Good stuff guys. So as always, if you've got questions and concerns, need some help when it comes to any kind of the financial pieces, the X's and O's when it comes to retirement, you always want to check with qualified financial professionals who do this day in and day out. And John and Nick certainly do so if you need some help, reach out to them online at pfgprivatewealth.com. That's pfgprivatewealth.com and don't forget to subscribe to the podcast on Apple or Spotify or whatever podcasting app you enjoy using. You can reach out to the guys on the website. You can also call them at (813) 286-7776. And don't forget to tune in for new episodes as they come out. I appreciate the time guys. Thanks so much for being here and we'll catch you next time here on Retirement Planning, Redefined with John and Nick.   Get yourself a plan, get yourself a strategy. Reach out to John and Nick today at pfgprivatewealth.com, that's pfgprivatewealth.com, to get started on your situation or to tweak your situation and dive into that process with the guys. You can reach out to them at 813-286-7776. Or again, find them online at pfgprivatewealth.com. Don't forget to subscribe to us on the podcast on Apple or Spotify, or whatever platform you like using. We'll see you next time here on Retirement Planning Redefined with John and Nick.  

I recently welcomed my friend Sky Smeed to spend an hour with me on the Mid-Coast Live! program on KKFI. I have a fifteen-year history with this Kansas songwriter; he was the first artist I had join me live in the KKFI studios as I launched The Tasty Brew Music Radio Show in 2010. I've  hosted Sky at my home for a house concert.  A good number of the songs masterfully captured by Barak Hill on his latest album, a live recording at The Rock House in Reeds Spring, Missouri are familiar to me as are some of Sky's life experiences that gave rise to songs like “Don't Know What to Do” “Lunker Bass” and “Without Music.”  That familiarity does not diminish the emotional impact of hearing these songs on this recording nor is it required to appreciate the underlying artistry of the words, stories and guitar accompaniment.  It is ALWAYS a treat to hear a new (to me) Sky Smeed tuneand this recording introduces me to precious guitar work on “Hangin' On”, the affirmation that “Good Luck” is indeed “sick” according to Sky's daughter Rosalie, the bittersweet and comedic reality of not wanting to work “Nine to Five” anymore and concurrence with “Keep Rolling On” that things do/life does change in the blink of an eye.Sky exhibits wonderful crowd work and pacing on this record;his Prine-like sense of humor is front and center on tunes like “Chicken of the Trees,” “Barbecue” and “Bumper Sticker.” I have always appreciated his homage to those masters that came before him. His take on Dylan's “Don't Think Twice” is stellar.  Just sing along…it's okay.I have been privileged to attend a number of musicalevenings at The Rock House over the years.  The folks that were in attendance on this particular evening got to witnesslightning being caught in a bottle.  Kudos to Rock House Co-Hosts Jeanette Bair and Bruce Anderson, recording engineer (and awesome songwriter in his own right) Barak Hill and of course, to my friend, Sky Smeed.  Well done!#songwriter #rootsmusic #communityradio #tastybrewmusic

Welcome to Kudos Kirby, a comics journey into Jack Kirby's lesser known works. Angus will be your guide through this monthly expedition to uncover those hidden gems from “The King of Comics” over 20,000 comic book pages! We hope you enjoy this latest adventure in the journey!In this episode Angus discusses Jack Kirby SUPER POWERS Vol 1 Issue 4 and conducts the review within the context of the history of the comic book, toy line, and animated series tie-in craze that would explode in the 1980's.Super Powers by Jack Kirby⁠⁠⁠⁠https://www.amazon.com/Super-Powers-Jack-Kirby-ebook/dp/B077YXRW55/⁠⁠⁠⁠We will review, in issue order, one issue each month (Vol 1 > #1 - #5 from 1984 / Vol 2 > #1 - #6 from 1985) in 2026.Leave a message at kirbyskidspodcast@gmail.comPlease join us for our 2026 Graphic Novel Reads⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.kirbyskids.com/2025/11/the-kids-talk-2026-kirbys-kids-graphic.html⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠For detailed show notes and past episodes please visit ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠www.kirbyskids.com⁠⁠

Progress can take many forms. Lenny cue the 5.2 music.  Want bonus content? Join the Velcro: patreon.com/chasingscratch  Kudos to Titleist - Titleist.com Kudos to Mizzen+Main - use code SCRATCH20 at mizzenandmain.com for 20% off your first purchase Kudos to Lagoon - go to lagoonsleep.com/scratch for 15% off your first purchase MUSIC CREDITS: "Dangerous" by Kevin MacLeod is licensed under a Creative Commons Attribution license (creativecommons.org/licenses/by/4.0/) Source: incompetech.com/music/royalty-fre…isrc=USUAN1100414 Artist: incompetech.com/ "Summer Noir" purchased via PremiumBeat.com "Meaningful Change" purchased via PremiumBeat.com "Amazing World Time Lapse" purchased via PremiumBeat.com The Lincoln Commercial: https://www.youtube.com/watch?v=bPLFqtV7dGY  "Epic Battle Speech" is by Wayne Jones "C Major Prelude" is by Bach "Air to the Throne" is by Doug Maxwell "Connect The Dots" purchased via PremiumBeat.com "The Latest Scandal" purchased via PremiumBeat.com "The Old Tale" purchased via PremiumBeat.com "Philosophy" by Eskimotion purchased via PremiumBeat.com Mixed by Lenny Sterner Copyright © Drupelets Media LLC

Brett and Joel are left to their own devices this week with Tess in the USA for work. The pair chat through Brett's birthday weekend before recapping the highlights of the weekend's AthsVic 5k at Albert Park to kick off the XCR season. Brett has an easier Tuesday before joining Jack for a marathon workout on Friday, and sneakily uses the Big Q segment to fire off some questions towards Joel about where he's at with his running. They return to the trails for Give Some Kudos and Brett arrives at TWHSOITWTWATSA with an absolute smorgasboard. SIGN UP TO OUR PATREON TODAY: www.patreon.com/forthekudos Instagram: https://www.instagram.com/forthekudos Facebook: https://www.facebook.com/forthekudos TikTok: https://www.tiktok.com/@forthekudos Brett: https://www.instagram.com/brett_robinson23 Joel: https://www.instagram.com/joeltobinblack Tess: https://www.instagram.com/tesssicaa_/  

Most people leave money on the table every time they swipe — not because they're careless, but because the credit card rewards ecosystem is genuinely complicated. Thousands of cards, millions of merchants, shifting bonus categories, buried benefits. The promise of AI is that it can do that optimization work invisibly, in the background. Today I'm joined by Tikue Anazodo, co-founder and CEO of Kudos — an AI-powered smart wallet that tells you which card to use at checkout, recommends cards based on your spending habits, and layers on additional rewards on top of what your cards already earn. Kudos has raised over $17 million, is backed by QED Investors, and was named to Forbes' Fintech 50. Tikue, welcome to Tearsheet.

Namibia sits on the south-west coast of Africa. Below Angola, above South Africa, with Botswana to the east.Portuguese explorers first reached the coast here in the 1480s. No natural harbour, brutal surf, cold Atlantic fog, the Namib Desert running straight into the sea, little access to fresh water. They planted crosses to mark their claims, turned around and went home again, never to return.Today that coast is known as the Skeleton Coast because of shipwrecks and whale bones.Three hundred years later, having decided there was too much tropical disease in Gambia, the British looked at Namibia as a possible penal colony. They decided it was too inhumane.It was Germans and Finns who eventually settled on the coast another hundred years on.Namibia is about three and a half times the size of the UK, and yet its population is only 3 million. It is big and empty. Most of it is desert.I've got more endless expanse shots than I know what to do with. Here is just one of them. Plus a short vid shot from a hot air balloon which gives you an idea of the sheer endlessness of the place.Even in the capital city, Windhoek, there is just so much space.The only two places in the world that are less densely populated are Greenland and Mongolia. Namibia beats even Australia and Mauritania, which is mostly Sahara desert.Demographically, the country is roughly 87% black, 6% white and 5% mixed race, with the Ovambo people to the north making up about half the population. I saw a few Asians while I was there too.A country of extremesThere are still bushmen and other ancient hunter-gatherer people living as they have lived for centuries, yet other parts of the country are extremely modern. There are shopping centres to rival our own, good roads (the best in Africa, I was told), great restaurants, commercial farms and more. About half the population is urban. The national language is English, adopted after the country gained independence from South Africa in 1990, but I found that people, black and white, would as often speak amongst themselves in Afrikaans and, up north, Ovambo. On the coast German is widely spoken. (The country was a German colony from the 1880s until World War I, when South Africa, then British, invaded. Hence it has great beer.)The controlling political force is the South West Africa People's Organisation (SWAPO), which has governed since independence in 1990. SWAPO is nominally social democratic, but there are still strong liberation-era left-wing instincts, as evidenced by streets in the capital renamed after independence: Fidel Castro Street, Robert Mugabe Avenue and so on.All being said, Namibia functions well.It is a stable democracy with rule of law, an independent judiciary (the government sometimes loses cases), relatively free markets and low crime by African (and European) standards. Immigration law is tight too. Having seen the problems stemming from mass immigration into South Africa, Namibia has taken a more controlled approach.Indeed I heard repeated frustrations from mining companies trying to obtain visas for geologists and mining engineers where the local expertise either does not exist or is employed elsewhere.Official unemployment is 37%, but I heard from several different sources that the real number is above 50%. 50%! Very sad.Nominal GDP per capita sits around US$5,000, roughly double that adjusted for purchasing power, which puts it above most of sub-Saharan Africa. The World Bank classifies Namibia as a lower-middle-income country, alongside countries such as Albania, Argentina and Belize. But these numbers are misleading.The country has vast wealth through its natural resources and related industries: uranium, copper, diamonds, fishing and tourism. Spread that revenue across just 3 million people and the averages look impressive.There is also serious rural poverty.Namibia combines first-world infrastructure with third-world unemployment.The currency is pegged to the South African rand, not one I would have chosen. Official inflation sits in the 2-3% range.About 88% of the country's sovereign debt is held domestically, and there appears to be healthy demand for its bonds. The country has also recently begun a sovereign wealth fund, which is reportedly growing at an impressive 16% since 2022. The central bank has recently also implemented a gold acquisition programme. Kudos.The country has high institutional savings and one the larger stock exchanges in sub-Saharan Africa.Food is cheap, protein in particular. The country has an enormous cattle herd, almost as large as its population. Recent outbreaks of foot-and-mouth disease in neighbouring countries are therefore a cause for concern, as you can imagine. (Not my bag, but I reckon there is an opportunity exporting Namibian biltong to the UK, where it is expensive. I brought back loads). Other goods, however, can be expensive because the country relies heavily on imports.If you live in a third world country such as the UK, I urge you to own gold or silver. The pound will be further devalued, as will the euro and dollar. The bullion dealer I use and recommend is The Pure Gold Company. They deliver to the UK, the US, Canada and Europe. More here.The main industries - tourism and natural resourcesPorts are expanding. The railways are not great, though I hear they will be improved. The roads, however, are excellent, as I said. Namibia is also the world's third-largest uranium producer after Kazakhstan and Canada. Chinese interests hold majority stakes in the country's three largest uranium mines, not to mention other metals.Oil and gas have recently been discovered offshore. Shell plc is one of the pioneers.As for gold, Namibia only really became a meaningful gold player after independence, since when roughly 15 million ounces have been discovered, much of it alongside copper. Among the larger players is B2 Gold (BTO.TO), which is well known in the country. Large parts of the country remain un- or under-explored. And I think that is where a lot of the big opportuities lie.There also appear to be rare earth deposits in some abundance. Kendrik Resources (KEN.L) recently made some progress here. Solar, wind and hydrogen projects are also attracting investment tooChinese money helped build the SWAPO headquarters, and they are investing significantly in mines in the country. Of note is that the USA recently spent heavily developing their embassy. It is big. Former Trump attorney John Giordano is now ambassador, a surprisingly high -profile appointment for such a low-profile country.One theory I heard repeatedly was that, given deteriorating US relations with South Africa, Washington increasingly sees Namibia as strategically important in terms of Atlantic access, energy routes and influence in the south Atlantic. Not quite the Panama Canal or Strait of Hormuz, but it could be something of a chokepoint. Namibia feels like a country at the cusp of something.It has space, resources, energy, political stability and strategic importance.Next week I want to look in more detail at Namibia as an investment destination, particularly its mining sector, where some very interesting things may be developing.My thanks go to to Rowland Brown and Chanel Marais of Cirrus Capital for bringing me to Namibia and for organizing what was a brilliant and instructuve conference.Thank you for reading the Flying Frisby.Until next time,Dominic This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit www.theflyingfrisby.com/subscribe

This episode is about the AVP Huntington Beach, with a concentration on the qualifiers. With only 4 spots available per gender, who's it going to be? 00:27 - Kudos to everyone representing the best in their volleyball region 02:10 - Prediction picks for the men's side 12:21 - Prediction picks for the women's side 22:11 - The main draw, comment section, final thoughts

Three letters sum up our feelings right now: WOW. Just WOW. We have so many thoughts on everything that we, as a fandom, were just treated to within the last four episodes of this series! Of course, if you haven't yet seen the episodes, here's your reminder that there are big spoilers ahead, so beware! There's so much emotion in these episodes, so many characters, so much action...we try to put all of our thoughts in this episode, but please join in the conversation with us on our social media! One thing is certain: we had SO much fun watching this show. Kudos to absolutely everyone on the team who created, wrote, directed, edited, and voiced this fantastic first season. We can't wait for Season 2!⁠Listen to our episode on Maul: Shadow Lord episodes 1-4⁠⁠Listen to our episode on Maul: Shadow Lord episodes 5-6⁠Watch our special EXTRA 200th episode for free on our Patreon (it's different from this audio episode): ⁠⁠https://www.patreon.com/posts/its-our-200th-156470434⁠⁠Support us on Patreon for as little as $3/month: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠patreon.com/MostThingsKenobi⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Instagram: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠most_things_kenobi⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Website: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠mostthingskenobi.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠YouTube: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠MostThingsKenobi⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Threads: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠most_things_kenobi⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Tumblr: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠MostThingsKenobi⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠

If you've been building your expertise for years but still feel like the world's best-kept secret, this episode is going to land in a useful way. David Newman - author of Market Eminence - makes his second appearance on the show, and we get into the thinking behind what it actually means to be an expert today, how to stop sitting on your best ideas, and why the company you keep shapes the business you build.This one is for consultants, coaches, and thought leaders who are done being invisible.Three key areas we explored:✳️ Being an expert is no longer about what you know - it's about what you're curious about. David reframes expertise as an active, evolving identity built on curiosity and curation, not a static body of knowledge you've already accumulated.✳️ Giving away your best thinking is the business model, not a threat to it. Using the celebrity chef analogy, David unpacks why holding back your "secret sauce" is the thing that's actually holding you back - most people won't implement it anyway, and the ones who can tell the difference will want the restaurant.✳️ The room you're in sets the ceiling on what you think is possible. Whether it's a mastermind, a peer group, or a loose network of fellow travellers, surrounding yourself with people solving A-level problems changes what you consider normal - and that changes everything.David's Amplifiers - three things you can do right now:✳️ Go back and listen to three previous episodes of this podcast - not to tick a box, but to build your expert databank and practise the habit of learning from other experts.✳️ Listen to each episode with a curiosity lens - write down three questions or angles the conversation sparked for you. Not "do I know this?" but "what am I wondering about because of this?"✳️ Interview three people you admire - colleagues, friendly competitors, people you follow. Showcase their expertise. Promote their work. Get into the habit of featuring other experts, and you build your authority by association.Timestamps:00:00 - Introduction00:47 - Welcome and what the show is about01:47 - Introducing David Newman and Market Eminence03:03 - David's new Watch Smarts podcast and the "no commercial intent" principle07:31 - Thought leadership without being the expert - imposter syndrome unpacked08:02 - Three non-traditional definitions of what it means to be an expert12:24 - Build your platform on curiosity, not static knowledge13:27 - Rick Rubin, taste, and the value of discernment when information is free15:56 - Audience vs market vs prospects - three very different things18:34 - Treating prospects like they've already bought21:56 - Love Them in Advance - the chapter on radical generosity23:00 - Why your "secret sauce" is not as secret as you think27:20 - The cookbook metaphor and who actually goes to the restaurant29:06 - What does it take to go from capable to recognised - building the roadmap33:51 - Offer structure, gateway services, and scaling from small to large37:28 - The Kudos file - why you need one and how to use it on a bad day40:29 - Quality recognises quality - how peer groups change your identity42:22 - Connecting with fellow travellers and "friendly competitors"48:19 - Identity shapes personal brand - your internal reality creates your external one51:05 - David's three amplifiers54:49 - Wrap-up and where to find DavidIf you enjoyed this episode, follow or subscribe wherever you listen - it genuinely makes a difference. And if you want to explore your own roadmap for building authority, the Personal Brand Business Roadmap is 50 pages of everything you need to get started or grow.https://doitmarketing.com/----Get your copy of my Personal Brand Business BlueprintIt's the FREE roadmap to starting, scaling or just fixing your expert business.www.amplifyme.agency/roadmap----Subscribe to my Youtube!! Follow on Instagram and Twitter @bobgentleJoin the Amplify Insiders Facebook Community : www.amplifyme.agency/insidersPlease take a second to rate this show in Apple Podcasts. ❤ It will mean a lot to me.

Welcome back to the NoCo Pulse as we kick off the second week of May following a surprise snow day that had Northern Colorado kids out of school and riding bikes by afternoon. This week we're covering community news, business updates, and local highlights while celebrating the resilience and energy that makes NoCo special. What's moving features Miles Beyond Running Community and their upcoming Weld Your Metal Running Festival on May 30th and 31st in Eaton. This 146 acre private property event offers distances from a 7K run walk up to 100 miles, plus a 36 hour total mileage contest, complete with camping, glamping, sauna, cold plunge, massage, and mountain views. We also share an update on Mandy Mullen's attempt at the Cocodona 250 in Arizona. While she didn't finish, making it past the 155 mile mark before missing the time cutoff is an incredible achievement worth celebrating. Kudos to Don't Ember Productions for traveling with her to document the journey. On a sadder note, Saffron Scoops and Bites, the Indian restaurant and ice cream shop, has permanently closed but shared plans to return bigger and better than ever. Community gatherings spotlight Ginger and Baker's Murder Mystery Party coming up May 19th, with only about a dozen tickets remaining for the Baker's Half Dozen event. Fork Fun celebrates 25 years this summer, operating two mini golf courses, go kart track, laser tag, arcade, bumper boats, and restaurant while gifting millions of dollars of free usage to nonprofit children's causes like Boys and Girls Clubs, Matthews House, and Respite Care over the years. Friday Fest returns to downtown Greeley June 5th through August 7th, kicking off with the blues jam and featuring the go cup program where you can carry open alcohol from participating restaurants into 9th Street Plaza during events. Keeping the beat highlights the Loud Frame Film Festival coming to the Lyric May 22nd through 24th, an international film festival created by the same mind behind EDIY Horror Film Fest. They're seeking volunteers and vendors for the event. Thursday Night Live Concert Series returns May 28th for 16 consecutive weeks at Old Town Square, starting with The Burrows and their nine piece lineup at 7 PM, perfect for families and kids ready to dance. Community support features Stay: A Night of Metal and Hope, a metal concert at The Sound Bar on May 17th benefiting the Suicide Prevention Alliance of Larimer County. We share an inspiring story of Shana from a local cleaning company who moved to NoCo two years ago from Columbus, Ohio with her daughter in her car on gas cards. After her car broke down, a daily rental owner gifted her a vehicle for $250 with new tires and fresh oil, House of Neighborly Services helped with housing, and she's now thriving with stable housing, a $4 raise, and representing her cleaning agency at networking groups across Fort Collins. Business news celebrates Andrew Johnson with Business Networking Done Right, a former BNI director who started his own brand and has grown to four chapters with 20 members each. He's hosting a lunch and learn workshop May 20th through the Loveland Chamber on Building Stronger Referral Relationships, open to anyone for $30 including lunch. Shout out to Dixie Daly, who's everywhere in the community from creating pink coffee with Top of the Light Coffee to being named grand marshal for the upcoming Larimer County parade. She's also running for some kind of entrepreneur of impact recognition worth voting for. Food picks feature The Taco Stop, nationally recognized by USA Today, serving incredible tacos al carbon so full you can barely pick them up, led by classically trained chef Caesar from Mexico City. Yellow Crunch Colombian Restaurant opened their massive new location at The Exchange in the former Crooked Stave space, featuring giant murals by artists flown in from Colombia and a 12 by 20 foot television screen in a beautiful 3500 square foot space. Important announcement: The LoCo PULSE is officially becoming the NoCo PULSE in the coming weeks and getting its own RSS feed, making it easier for listeners who love the weekly community news format to find and follow along. Shout out to Laughing Buck Farm for being weekly listeners and sharing the podcast with their entire newsletter. They offer markets, vegetable swaps, and kids summer camps including homesteader camp and horse camp, plus a nonprofit supporting gardening and vegetables for people in our community. Stay connected, NoCo.

Week off? Nah. We're back with some bonus content - we answer a few listener questions about the last few episodes and then talk with actor Timothy Simons about how he got into golf, Veep, Hollywood Program Height, Celebrity Tournaments, his first full bag fitting at TPI, and whether he's a Bear or a Shark.  Want bonus content? Join the Velcro: patreon.com/chasingscratch  Kudos to Titleist - Titleist.com Kudos to Shot Pattern - https://shotpattern.app/chasingscratch  MUSIC CREDITS: "Dangerous" by Kevin MacLeod is licensed under a Creative Commons Attribution license (creativecommons.org/licenses/by/4.0/) Source: incompetech.com/music/royalty-fre…isrc=USUAN1100414 Artist: incompetech.com/ "Faceoff" by Kevin MacLeod is licensed under a Creative Commons Attribution license (creativecommons.org/licenses/by/4.0/) Source: incompetech.com/music/royalty-fre…isrc=USUAN1100414 Artist: incompetech.com/

Kudos to NBC Bay Area for this fascinating report on MediCAL Fraud involving taxis paying the homeless to drive to methadone clinicsSee omnystudio.com/listener for privacy information.

With Tess back with us permanently she's implemented a new rule: no more detailed episode descriptions that give too much away! You'll just have to listen to hear everything that happens in the EP :) Brett is back at full mileage as Ballarat fatigue sets in later in the week for him. Tess shares the importance of rest days following goal races which allows the body to absorb the race effort. FTK "Friend Of The Show" Chris Barclay submits "THE BIG Q" this week around gym loading and whether or not you should be seeing improvements week after week. In "Give Some Kudos" Tess shouts out a sport close to her heart, Brett hypes up a worm-dance submission from a listener and Joel sends his kudos to a recent music project from a close friend. The episode closes out with three solid "TWHSOITWTWATSA" submissions. SIGN UP TO OUR PATREON TODAY: www.patreon.com/forthekudos Instagram: https://www.instagram.com/forthekudos Facebook: https://www.facebook.com/forthekudos TikTok: https://www.tiktok.com/@forthekudos Brett: https://www.instagram.com/brett_robinson23 Joel: https://www.instagram.com/joeltobinblack Tess: https://www.instagram.com/tesssicaa_/  

Mary Lewandowski works on her family’s dairy farm in Wisconsin. Her great-great-great-grandparents founded the farm more than a hundred years ago. Today, the farm has some fifty cows that must be fed, milked, and kept happy and healthy. Corn and alfalfa need to be planted and harvested for their feed. It’s all a lot of work for Mary, but she loves her cows, and they provide us with milk to drink, cheese and ice cream to eat, and many other delicious dairy treats.Welcome to My Farm is a fun and illuminating look at farm life in the heart of America’s Dairyland. Presenting a day in the life of a small dairy farm, the book shares fascinating facts about dairy cows and the crops that farmers grow. Readers will also meet cuddly kittens and Mary’s two collies, Buffy and Buddy! Kiley Allan visits with the author about what she hopes kids take away from the book. Another morning of frost statewide. Soil temperatures are becoming a worry for farmers that already have seed in the ground. Stu Muck says the sun today should help that situation, but overnight lows will continue to bring frost. Wisconsin’s potato industry is facing market pressure despite planting season being underway. Ben Jarboe talks with Tamas Houlihan, executive director of the WI Potato & Vegetable Growers Association. Global changes are forcing a reassessment of WI potatoes. Houlihan says western U.S. potato exports have declined as countries like China and India increase competition. Key international markets such as Japan, Malaysia, and Indonesia are no longer as strong for U.S. potatoes. Much of the western potato supply is used for French fry production, which has been heavily impacted. U.S. processors are cutting supply needs by 30–40%, reducing demand for grower. That trickle down effect is forcing changes in Wisconsin's potato strategy. Consumers will likely benefit from lower potato prices at the store. Kudos to Mary Cooper, middle school teacher from Richland Center. She's been named the 2026 WI Ag in the Classroom Teacher of the Year. Plus Bob Hagenow of Deforest is receiving the Guest of Honor award from the National Dairy Shrine this September. Hagenow's been a long time fixture in Wisconsin's dairy industry. Consumer's pocketbooks continue to constrict with escalating energy costs. They're making changes at the grocery store and when they dine out too. Mike North, dairy analyst with EverAg joins Pam Jahnke to explain how those buying patterns ripple through dairy pricing. He also notes that milk production is not backing down. The upside of all of this is that dairy plant expansion continues in Wisconsin and across the U.S.See omnystudio.com/listener for privacy information.

The Middle East is a place where people swear "on the honor of their mom" without thinking too much. Guy teaches us all the uses of the Hebrew word כבוד – "honor" – right from the Prime Minister's official title to what you jot on the front of an envelope. Hear the All-Hebrew Episode on Patreon   New Words and Expressions: Kavod – Respect, honor – כבוד Kol ha-kavod – Well done – כל הכבוד Kol ha-kavod lecha/lach – Kudos to you – כל הכבוד לך "Kvodo shachach levarech" – You (formal) forgot to say the prayer – כבודו שכח לברך "Ze kavod gadol she-" – It's a great honor that… – זה כבוד גדול ש Ani mitkabed lehazmin – I am honored to invite – אני מתכבד להזמין "Ha-rishon she-hevin et godel ha-eru'a" – The first to understand the magnitude of what happened – הראשון שהבין את גודל האירוע Kvod Rosh memshelet Israel – His Excellency, the Prime Minister of Israel – כבוד ראש ממשלת ישראל Kvod ha-shofetet – Your Honor (to a female judge) – כבוד השופטת Kvod nesi ha-medina – His Excellency the President – כבוד נשיא המדינה Titkabed, titkabdi, titkabdu – Help yourself – תתכבד, תתכבדי, תתכבדו Kibood – Refreshment – כיבוד Mis'hakei kavod – Ego games – משחקי כבוד Ani nishba ba-kavod sheli – I swear on my honor – אני נשבע בכבוד שלי Sharaf (Arabic) – Honor – שרפ – شَرُفَ Be-kha-vod – I'd be honored, Gladly – בכבוד Likhvod – For (formal) – לכבוד Likhvodekh – For you (formal) – לכבודך Nikiti et ha-bayit likhvodkha – I cleaned the house for you – ניקיתי את הבית לכבודך   Playlist and Clips: Yehoram Ga'on – Kol Ha-kavod (lyrics) David Broza – Tio Alberto (lyrics) Hagiga Ba-snooker Netanyahu – Ceremony  Ariel Israelov & Idan Baranes – Mishakim shel Kavod Avi Biter – Ba-kavod sheli (lyrics) Roulla Saad – Bisharafak  Gazoz – Likhvod ha-kayits (lyrics) Shlishiyat Gesher Ha-Yarkon – Likhvodekh (lyrics)

Cankles Caligula confesses he's turned the U.S. Navy into pirates. How long ago did I say that? Secret Service shuts down the White House because shots were fired a mile or so away in D.C. Legal expert confirms Nitwit Nero has a bunch of problems in the Cole Allen trial. Said that already, too. I swear sometimes it's like I live in a bubble-off-plumb future. Polk County Sheriff comes nigh giggling when he takes down a J6 terrorist for trying to hire a sex worker. Kudos for showing his pic with Julius Geezer.

Today on WKXL's NH Unscripted we are taking a more in depth look at the history of Motown, the artists, the music, and chart topping stories surrounding them! (Kudos to the YT channel "Groove Lens" for the transcript I used). Some of the greatest Motown hits almost never happened. Here's the crazy story along with the songs that were massive hits, but, almost weren't. Think: Ain't Too Proud to Beg, I Heard it Through the Grapevine", "Tears of a Clown", just for starters!

"This Club Mix 'Just Close your Eyes' was live streamed on April 25 at IbizaStardust radiostation. This is my first Clubmix recorded as a Back2Back with my son DJ Flouze. It has been amazing to do this together! A nice blend of younger generation house music with a groovy touch and the sounds of old style club music! 15 tracks with Kudos to the various producers/ artists like; @prunk.dj @anotr.music @mil.jesdj @rangertrucco @devinjetski @jaydelysmusic @ruzeuk @midas.field @soulcentral.official @djmarkknight @whOplaysrecords @crusyofficial @groove_p_ And more Happy to link up on Insta: remko_remx #ibizastardustradio #housemusic #toolroomrecords #Flouze #remx"

Fifty Shades of Gray Aliens: In Consideration of Aliens, UFOs, Abductees, Contactees, Experiencers, Channeling, and More In Consideration of aliens, UFOs, Billy Meier, Erich Von Daniken, Robert Temple, Travis Walton, Whitley Strieber, Ancient Aliens, Manly P. Hall and more."One theory which can no longer be taken very seriously is that UFOs are interstellar spaceships"—Arthur C. ClarkeThis is not your typical UFO book as it is UFO nonfiction and contains much background on the phenomena and personages involved in abductee, contactee, experiencer and channeling experiences?What are aliens and UFOs?What do aliens want and what is their messages for us?How does pop-culture in general interact with such phenomena?These questions and much more are explored within this text. This is an aliens and UFOs non-fiction Kindle book or paperback book.“I could actually borrow some of your work to answer some questions people have asked me. Kudos to what you did with this book”—Joseph Jordan, president and co-founder of the CE4 Research Group and former investigator for MUFON“This book contains a great amount of research on the origins of gray aliens, extraterrestrials, dimensional travelers or demons. The research includes thorough examples…From Pop culture to the occult, the origins of the modern gray alien are pieced together”—John Razimus, occult researcher and independent investigator“Ken's work boldly considers all angles and perspectives to every aspect of this topic. He provokes the reader to consider all aspects of a situation that many may overlook because it may interfere with our preconceived ideas that, knowingly or not, we want to prove”—Jim Wilhelmsen, MUFON research specialist and author of Beyond Science Fiction!#aliens #ufos #extraterrestrials #whitleystrieber #billymeier #traviswaltonhttps://amzn.to/42epqj0Become a supporter of this podcast: https://www.spreaker.com/podcast/the-opperman-report--1198501/support.

There was only one way to follow up my interview with the iconic, the unique Steven Blier published earlier this week, and that is with an episode dedicated to his dazzling at the keyboard and his accomplishments as the co-founder and artistic director of NYFOS, the New York Festival of Song, which is just concluding its 38th season. Going all the way back to Steve's first recordings in the late 1980s, I have compiled a setlist that is a testament to his love of song, and his ever-expanding interests in that field. Performances both live and studio, many of them straight from Steve's own archives, feature composers ranging from Franz Schubert to Leonard Bernstein, Eubie Blake to Albert Roussel, Eduard Toldrà to Marc Blitzstein, and Billy Strayhorn to Kurt Weill , including work commissioned specifically by and for Blier and NYFOS. And that's just the tip of the iceberg. These are performed by vocal colleagues of Steven's past and present, including William Sharp, Lorraine Hunt Lieberson, Darius de Haas, Stephanie Blythe, Christopher Trakas, Corinne Winters, Kurt Ollmann, Lisa Vroman, Federico De Michelis, Joshua Blue, Sasha Cooke, Brett Polegato, and many, many others. Kudos to this magnificent artist who has enriched all of our lives! Countermelody is the podcast devoted to the glory and the power of the human voice raised in song. Singer and vocal aficionado Daniel Gundlach explores great singers of the past and present focusing in particular on those who are less well-remembered today than they should be. Daniel's lifetime in music as a professional countertenor, pianist, vocal coach, voice teacher, and author yields an exciting array of anecdotes, impressions, and “inside stories.” At Countermelody's core is the celebration of great singers of all stripes, their instruments, and the connection they make to the words they sing. By clicking on the following link (https://linktr.ee/CountermelodyPodcast) you can find the dedicated Countermelody website which contains additional content including artist photos and episode setlists. The link will also take you to Countermelody's Patreon page, where you can pledge your monthly or yearly support at whatever level you can afford.

Kudos to Rena Cohen for crafting an excellent crossword, her first to appear on a Friday. The clues were quite interesting: we always appreciate crosswords that both entertain and teach, as this one does so well.Speaking of entertaining and teaching, we also have a Fun Fact Friday segment that does just that. Check it out!Show note imagery: Yes, this too is a baguette (technically, it's a type of cut, used for diamonds and other precious stones)We love feedback! Send us a text...Contact Info:We love listener mail! Drop us a line, crosswordpodcast@icloud.com.Also, we're on FaceBook, so feel free to drop by there and strike up a conversation!

Mike and Eli recap their trip to TPI and round with Jayson Nickol in California. Want bonus content? Join the Velcro: patreon.com/chasingscratch  Kudos to Titleist - Titleist.com Kudos to Mizzen+Main - use code SCRATCH20 at mizzenandmain.com for 20% off your first purchase MUSIC CREDITS: "Dangerous" by Kevin MacLeod is licensed under a Creative Commons Attribution license (creativecommons.org/licenses/by/4.0/) Source: incompetech.com/music/royalty-fre…isrc=USUAN1100414 Artist: incompetech.com/ "Meaningful Change" purchased via PremiumBeat.com "Amazing World Time Lapse" purchased via PremiumBeat.com The Lincoln Commercial: https://www.youtube.com/watch?v=bPLFqtV7dGY  "Epic Battle Speech" is by Wayne Jones "C Major Prelude" is by Bach "Air to the Throne" is by Doug Maxwell "Connect The Dots" purchased via PremiumBeat.com "The Latest Scandal" purchased via PremiumBeat.com "The Old Tale" purchased via PremiumBeat.com "Philosophy" by Eskimotion purchased via PremiumBeat.com Mixed by Lenny Sterner Copyright © Drupelets Media LLC

We decided (well, mostly me, Lily K) to do a little movie fights on our own. (Kudos to Screen Junkies, who have the long-running series). So we have Brian and Iain joining so we can butt heads over serious and not-so-serious movie questions. Are you ready for this? Who's gonna win the fight? Come and find out!Thank you for watching! Please remember to like, subscribe, and share with the people you know and love

The inimitable Lisa Blatt joins Sarah Isgur and David French to discuss the two business docket cases named Cox and Chevron, a message to the judges and justices who like concurrences, and advice for aspiring lawyers. The Agenda:–We are launching a newsletter!–The 5th Circuit's Ten Commandment Ruling–Ditch the coercion test–How to become Lisa Blatt–Does the internet always win?–Peak sexiness, federal removal–Kudos to the government on its birthright citizenship oral argument–Shut down forum shopping–Hypothetical:  A daughter from a conservative Muslim family leaves the house every morning wearing a hijab … Show Notes:–Stone v. Graham–Cox Communications, Inc. v. Sony Music Entertainment–Chevron USA Inc. v. Plaquemines Parish, Louisiana (24-813) Order Sarah's bookhere. Advisory Opinions is a production of The Dispatch, a digital media company covering politics, policy, and culture from a non-partisan, conservative perspective. To access all of The Dispatch's offerings—including access to all of our articles, members-only newsletters, and bonus podcast episodes—click here. If you'd like to remove all ads from your podcast experience, consider becoming a premium Dispatch member by clicking here. Learn more about your ad choices. Visit megaphone.fm/adchoices

Josh Nichols re-joins the show to explain the "This is It" Practice Plan; Mike plays Old Town; Eli has doubts.  Mike & Eli go into a mental coaching session with Josh Nichols.  Want bonus content? Join the Velcro: patreon.com/chasingscratch  Kudos to Titleist - Titleist.com Kudos to Vuori - save 20% off your first purchase at vuoriclothing.com/chasingscratch Kudos to Footjoy - Footjoy.com Kudos to ShotPattern - save 20% off at shotpattern.app/chasingscratch MUSIC CREDITS: "Dangerous" by Kevin MacLeod is licensed under a Creative Commons Attribution license (creativecommons.org/licenses/by/4.0/) Source: incompetech.com/music/royalty-fre…isrc=USUAN1100414 Artist: incompetech.com/ "Meaningful Change" purchased via PremiumBeat.com "Amazing World Time Lapse" purchased via PremiumBeat.com The Lincoln Commercial: https://www.youtube.com/watch?v=bPLFqtV7dGY  "Epic Battle Speech" is by Wayne Jones "C Major Prelude" is by Bach "Air to the Throne" is by Doug Maxwell "Connect The Dots" purchased via PremiumBeat.com "The Latest Scandal" purchased via PremiumBeat.com "The Old Tale" purchased via PremiumBeat.com "Philosophy" by Eskimotion purchased via PremiumBeat.com Mixed by Lenny Sterner Copyright © Drupelets Media LLC

Friday, April 24, 2026 Kudos to Rep. Madeleine Dean Kudos to Senator Elizabeth Warren Boot + Tongue The New Secretary of the Navy Witch Supremacists Have a Great Weekend!   The Daily beans is donating $10,000 and invites you to give what you can to support their life-affirming work at https://itgetsbetter.org/dailybeansdonate   Subscribe to the MSW YouTube Channel - MSW Media - YouTube Dr. Allison Gill - The Breakdown | Allison Gill, Mueller, She Wrote (@muellershewrote.com) — Bluesky, MSW & The Daily Beans Podcast (@muellershewrote) - Instagram, MSW Media - YouTube   Dana Goldberg - @dgcomedy.bsky.social on Bluesky, Dana Goldberg (@dgcomedy) - Instagram, Dana Goldberg - Facebook, DanaGoldberg.com   More from MSW Media - Shows - MSW Media, Cleanup On Aisle 45 pod, The Breakdown | Allison Gill Beans Talk is the video companion to The Daily Beans with Allison Gill and Dana Goldberg. Subscribe now to stay informed and entertained!  Reminder - you can see the pod pics if you become a Patron. The good news pics are at the bottom of the show notes of each Patreon episode! That's just one of the perks of subscribing! patreon.com/muellershewrote Listener Survey:http://survey.podtrac.com/start-survey.aspx?pubid=BffJOlI7qQcF&ver=shortFollow the Podcast on Apple:https://apple.co/3XNx7ckWant to support the show and get it ad-free and early?https://patreon.com/thedailybeanshttps://dailybeans.supercast.com/https://apple.co/3UKzKt0 Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

TRAINING WEEKS After his short trip to Sydney Brett lays down a big week of training. Back to hitting higher mileage (with Ballarat Half Mara in his sights) he claims to cheat-code Thursday threshold which allows him to fly on Saturday hills. The segment ends with Joel sharing details of his "comeback" race, something very different indeed! THE BIG Q FTK "Friend Of The Show" Kim Way asks a question about managing mental burnout / low-mo in running. Brett & Joel share personal stories as well as coaching guidance to answer the question. GIVE SOME KUDOS Brett & Joel join forces to spread their kudos to the recent Sydney Backyard Ultra. They chat about a few highlight performances from the meet and discuss how they think they'd fair at something like that. TWHSOITWTWATSA Joel isn't sure about a Kenyan runners finish at the Annecy Marathon over the weekend while Brett brings up an old Brown Cardigan upload from one of their good friends Ange Testa. SIGN UP TO OUR PATREON TODAY: www.patreon.com/forthekudos Instagram: https://www.instagram.com/forthekudos Facebook: https://www.facebook.com/forthekudos TikTok: https://www.tiktok.com/@forthekudos Brett: https://www.instagram.com/brett_robinson23 Joel: https://www.instagram.com/joeltobinblack

Leeds United are nearly there - there or thereabouts. In this week's Inside Elland Road Podcast, Graham Smyth and Chris O'Connor review the performance and consequences of the win over Wolves and react to Georginio Rutter's helpful screamer against Spurs.The pair also talk about the side that could face Bournemouth and predict the scoreline as Chris looks to extend his lead after a pair of bang-on predictions.

This episode was recorded live at the Traprock 50K in Bloomfield Connecticut home of Penwood State Forest. This race is the first in the 12 race blue blaze series where runners will compete for the overall series prize. This is indirect support of Connecticut Forest & Parks Association, the group that is responsible for protecting and maintaining the over 825 miles of blue blaze trails in the state of Connecticut. If you're not from Connecticut, perhaps you have your own trail stewards and hopefully you were able to support them. Because, after all, SUPPORT is good. During this episode, we get to speak to the gentleman who coordinates all of these races in the Blue Blaze Series, Paul Ladd. We also speak to RD Director, Karen Prado, and the top finishers in the 17 K as well including two fast dudes from Brooklyn, Calvin Cameron, and Greg Cartelli, The Beast Coast's own Kristin Loiko who is good Friends with VT100 RD Amy Ruesecki.  As well as Kara Goucher, whoops, I mean Kara Mcknight.   Then we get a talking to the fast cats of the 50k, Matt Pacheco, Ben Niebla and running legend Brian Rusiecki. Speaking of legends, Kehr Davis is back along with young gun 19 year old Maddie Kaplan.   So many Cultra Personalities at this event, and it was great to work the aid station and hang out with this great community. Kudos to The CT Trail Mixers for carrying the great tradition of this rust busting spring race. Speaking of KUDOs, Hundo Joe was also there, as it is typical for him to volunteer, and hang out.  After a Patreon roll call we have prepared a very special song in tribute to Hundo Joe's uncanny ability to give and keep track of KUDOS. So please be sure to listen for this at the end of the episode.  Traprock results Get your official Cultra Clothes and other Cultra TRP PodSwag at our store! Outro music by Nick Byram Hundo Joe by Suno Become a Cultra Crew Patreon Supporter  basic licker.  If you lick us, we will most likely lick you right back Cultra Facebook Fan Page Go here to talk shit and complain and give us advice that we wont follow Cultra Trail Running Instagram Don't watch this with your kids Twitter @BlueBlazeRunner Sign up for a race at Live Loud Running and feel better Buy Fred's Book Running Home More Information on the #CUT112   

Mike & Eli go into a mental coaching session with Josh Nichols.  Want bonus content? Join the Velcro: patreon.com/chasingscratch  Kudos to Lagoon Sleep - save 15% at lagoonsleep.com/scratch  Kudos to LMNT - DrinkLMNT.com/chasingscratch MUSIC CREDITS: "Dangerous" by Kevin MacLeod is licensed under a Creative Commons Attribution license (creativecommons.org/licenses/by/4.0/) Source: incompetech.com/music/royalty-fre…isrc=USUAN1100414 Artist: incompetech.com/ "Meaningful Change" purchased via PremiumBeat.com "Amazing World Time Lapse" purchased via PremiumBeat.com The Lincoln Commercial: https://www.youtube.com/watch?v=bPLFqtV7dGY  "Epic Battle Speech" is by Wayne Jones "C Major Prelude" is by Bach "Air to the Throne" is by Doug Maxwell "Connect The Dots" purchased via PremiumBeat.com "The Latest Scandal" purchased via PremiumBeat.com "The Old Tale" purchased via PremiumBeat.com "Philosophy" by Eskimotion purchased via PremiumBeat.com Mixed by Lenny Sterner Copyright © Drupelets Media LLC

No one thought it was possible. They said it couldn't be done. But they were wrong.Richard and Nate managed to get a second episode out this month! Kudos to Richard for his herculean efforts editing this in time. I hope you all enjoy our recap of one of the best Street Sharks episodes ever (in Nate's opinion)!

Eli finds a new weekly competitor; Mike plays the Cardinal with an LPGA Tour pro. Want bonus content? Join the Velcro: patreon.com/chasingscratch  Kudos to Titleist - want to join us at our San Diego event? Register here: The 4th Annual Mantooth Kudos to Mizzen+Main: Use code SCRATCH20 for 20% off your first order at mizzenandmain.com  Kudos to Fit For Golf: Go to fitforgolf.app/chasingscratch for 25% off any subscription and a 7-day free trial MUSIC CREDITS: "Dangerous" by Kevin MacLeod is licensed under a Creative Commons Attribution license (creativecommons.org/licenses/by/4.0/) Source: incompetech.com/music/royalty-fre…isrc=USUAN1100414 Artist: incompetech.com/ "Meaningful Change" purchased via PremiumBeat.com "Amazing World Time Lapse" purchased via PremiumBeat.com The Lincoln Commercial: https://www.youtube.com/watch?v=bPLFqtV7dGY  "Epic Battle Speech" is by Wayne Jones "C Major Prelude" is by Bach "Air to the Throne" is by Doug Maxwell "Connect The Dots" purchased via PremiumBeat.com "The Latest Scandal" purchased via PremiumBeat.com "The Old Tale" purchased via PremiumBeat.com "Philosophy" by Eskimotion purchased via PremiumBeat.com Mixed by Lenny Sterner Copyright © Drupelets Media LLC

Finish Your (Easter) Brunch (4.5.2026): Yes, I took the morning off and attended Sunday service with the family, but I'm still here with your daily dose of Black baseball highlights. The story of Saturday had to be Jo Adell's hat trick of home run robberies. The last one on JP Crawford was unreal. Adell is known more his power, but he is proving he can flash the leather in right field. Congratulations are in order for CJ Abrams. His twelve RBIs in the Nats' first seven games is a modern-day franchise record. Kudos to Justin Crawford for the first stolen base of his MLB career. Jordan Walker (STL) and Cam Smith (HOU) both hit homers on Saturday. Jack Flaherty (DET) and Kumar Rocker (TEX) both had solid outings on the bump. All of that and more on Easter Sunday. Finish Your Easter Brunch.

A lot is happening right now in terms of internet censorship and AI, and the fanfiction world is paying attention. We share some updates on this means for all of us, what to look out for, as well as some personal updates from the fanfic space. Kudos to all for listening!See omnystudio.com/listener for privacy information.

Mike and Eli travel back to River Bend for the first major of the year.  #LGLG Want bonus content? Join the Velcro: patreon.com/chasingscratch  Kudos to Titleist MUSIC CREDITS: "Dangerous" by Kevin MacLeod is licensed under a Creative Commons Attribution license (creativecommons.org/licenses/by/4.0/) Source: incompetech.com/music/royalty-fre…isrc=USUAN1100414 Artist: incompetech.com/ "Meaningful Change" purchased via PremiumBeat.com "Amazing World Time Lapse" purchased via PremiumBeat.com The Lincoln Commercial: https://www.youtube.com/watch?v=bPLFqtV7dGY  "Epic Battle Speech" is by Wayne Jones "C Major Prelude" is by Bach "Air to the Throne" is by Doug Maxwell "Connect The Dots" purchased via PremiumBeat.com "The Latest Scandal" purchased via PremiumBeat.com "The Old Tale" purchased via PremiumBeat.com "Philosophy" by Eskimotion purchased via PremiumBeat.com Mixed by Lenny Sterner Copyright © Drupelets Media LLC

Sometimes you gotta go back ... to actually move forward.  #LGLG Want bonus content? Join the Velcro: patreon.com/chasingscratch  Kudos to Titleist MUSIC CREDITS: "Dangerous" by Kevin MacLeod is licensed under a Creative Commons Attribution license (creativecommons.org/licenses/by/4.0/) Source: incompetech.com/music/royalty-fre…isrc=USUAN1100414 Artist: incompetech.com/ "Meaningful Change" purchased via PremiumBeat.com "Amazing World Time Lapse" purchased via PremiumBeat.com The Lincoln Commercial: https://www.youtube.com/watch?v=bPLFqtV7dGY  "Epic Battle Speech" is by Wayne Jones "C Major Prelude" is by Bach "Air to the Throne" is by Doug Maxwell "Connect The Dots" purchased via PremiumBeat.com "The Latest Scandal" purchased via PremiumBeat.com "The Old Tale" purchased via PremiumBeat.com "Philosophy" by Eskimotion purchased via PremiumBeat.com Mixed by Lenny Sterner Copyright © Drupelets Media LLC  

On today's Breitbart News Daily podcast, our stalwart host Mike Slater covers a story about some brave American women refusing to sell their family's land so that more artificial intelligence facilities can be built. Kudos to them! Listen in as Slater explains why more patriots should follow their example... Following that opener, Mike speaks with William J. Federer, Senior Fellow at the D. James Kennedy Center for Christian Statesmanship, about the history of Islam in the United States of America and how that religion impacts contemporary politics. Don't miss it! MAGA! Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

The House Oversight Committee has boldly released full video footage of Bill and Hillary Clinton's depositions on their ties to Jeffrey Epstein, finally bringing transparency to the American people about the elite's connections to this monster. Bill dodges tough questions with convenient memory lapses, while Hillary grows visibly upset and snaps during pointed grilling by Rep. Nancy Mace (R-S.C.), exposing her arrogance and defensiveness when confronted with uncomfortable facts. The Clintons' evasive answers and heated outbursts only confirm their long history of putting personal power above accountability and justice for victims. Kudos to the committee for cutting through the swamp and getting these damning truths out — America deserves to see the real Clintons unfiltered. We also cover: Marco Rubio on imminent threat. Pete Hegseth's strong message to the military. Does Trump have authority to attack Iran? Tampons derail Netflix-Warner Bros. deal. 00:00 Pat Gray UNLEASHED! 00:25 Countries that Iran has Attacked 02:08 Six U.S. Service Members Dead 02:34 Bret Baier on President Trump & Iran 06:48 President Trump's Statements on Iran Campaign 08:07 Marco Rubio Discusses Attack on Iran 15:05 Tom Cotton on Legality of Iran Strikes 22:49 How Excited is Lindsey Graham? 26:12 Why is Kuwait Shooting Down U.S. Pilots? 28:33 Iranian Ships Obliterated! 31:05 Pete Hegseth on Decision to Attack Iran 32:21 Pete Hegseth's Message to the U.S. Military 34:41 Talking about the Lunar Eclipse this Morning 38:48 Fat Five 51:46 President Trump's Message to Iran 53:15 Message from Iranian Girl to the U.S. 56:33 Hillary Clinton's Crash Out over Photo 58:53 More of Hillary Clinton's Deposition 1:06:22 Even More of Hillary Clinton's Deposition 1:12:12 Update on Netflix & Warner Bros. Discovery 1:15:45 Bill Clinton's Deposition 1:33:17 Vh1 Segment on Jeffrey Epstein Learn more about your ad choices. Visit megaphone.fm/adchoices