Podcasts about aws

SUMMARY: After the first successful AI IPO of 2026, we dig into what makes the Cerebras WSE architecture unique in the market for fast inference. GUEST: Andy Hock, at Chief Strategy Officer at Cerebras AISHOW: 1033SHOW TRANSCRIPT: The Enterprise AI Show #1033 TranscriptSHOW VIDEO: https://youtu.be/ed2nVbOtZiASHOW SPONSORS:OutShift - “Scaling Out Superintelligence”  The Internet of Cognition architectureShareGate - ShareGate Protect. Microsoft 365 Governance, we got this!Nasuni - Activate your data for AI and request a demoSHOW NOTES:OpenAI announces 750MW partnership with CerebrasCerebras and AWS partnershipCerebras announces IPOTopic 1 - Welcome to the show. Tell us about your background, and what you focus on today. Topic 2 - For anyone that's not familiar with Cerebras, give us an overview of the company, and especially an overview on the Cerebras technologies (e.g. Wafer-Scale Engine).Topic 3 - Cerebras' WSE architecture is different from many of the GPU or GPU-like architectures in the market today. Centralized vs. distributed architectures always have their tradeoffs. Walk us through the technical and economic value of the Cerebras architecture.Topic 4 - Congratulations on the recent IPO (raised $5.55B). Let's use that as a point in time vs the previous planned IPO. How has the market changed in that timeframe, and how has the Cerebras position changed? Topic 5 - Cerebras (today) offer both WSE hardware, and Cerebras Cloud (API) - very different GTM paths. Can we expect both of those to stay top priorities, or have the market dynamics shifted such that the priorities shift more towards the WSE business - as we're seeing OpenAI, AWS and other engagements announced?Topic 6 - Is Cerebras a training and inference company, or are the economics of inference significantly different enough that it needs to be the sole focus of the company (for now)? Topic 7 - How much effort is it for any company to add support for the Cerebras chips if they have previously been using other architectures?Topic 8 - An IPO is a major milestone for any company, but the markets will now look for your future story. How do you see the AI market evolving over the next 2-5 years, and what are some things that people aren't understanding yet about how it will evolve?FEEDBACK?Email: show @ the enterprise ai show dot comeBluesky: @TheEntAIShow.bsky.socialTwitter/X: @TheEntAIShowInstagram: @TheEntAIShow

The growth of data centers, and the amount of electricity expected to be required to meet that demand, is probably the biggest issue in the US power sector.  US grid power supplied to hyperscale, leased and crypto-mining data centers reached about 64.4 gigawatts in 2025, nearly tripling since 2020. And that growth is accelerating. In this episode, host Dan Testa speaks with Brandon Oyer, head of energy and water for the Americas at Amazon Web Services. Oyer breaks down what he describes as misperceptions regarding the water and power impacts of data centers, the ways in which many people rely on data centers without realizing it and how AWS works with utilities to develop new projects.

Lots of people move to the cloud; it's common. In fact, it's very common to hear customers who are being asked to migrate their workloads to a cloud vendor for a variety of reasons. You might not agree, but often there is some reason to move to the cloud. Sometimes it's even moving from one cloud to another, just because one of the big three (AWS, Azure, GCP) seems more attractive this year than the one from last year. When you move, do you size your system for the peak? 80% of the peak? Perhaps there is another goal for which you design. Do you worry about ever being under-provisioned and letting customers have a slower system? Or do you ensure you never hit the peak, which increases costs? Read the rest of Over or Under Provisioned

In this episode, Neil explores how agents, foundation models, and AI are set to transform the Computer-Aided Engineering (CAE) and Electronic Design Automation (EDA) landscapes. He shares a comprehensive historical perspective and predicts a near-future where AI-driven automation redefines engineering workflows, productivity, and innovation.Main Topics:The evolution of simulation codes from the 1960s to modern commercial softwareThe rise of cloud computing, GPUs, and their impact on CAE and EDA industriesThe integration of AI, surrogate modeling, and foundation models into simulation workflowsThe emergence of agentic AI systems capable of autonomously performing complex engineering tasksThe strategic responses of major software companies to AI and agent technologiesThe potential democratization and automation of engineering design through AI agentsCritical questions on model ownership, transparency, and industry adoptionTimestamps: 00:40 - Introduction: How agents and foundation models will disrupt CAE & EDA01:40 - Historical overview: From code writing in the 60s to commercial software03:10 - Growth of aerospace and automotive industry codes and commercialization04:40 - The impact of HPC, cloud computing, and hardware evolution06:25 - Rise of cloud SaaS models and "sassification" of simulation tools07:40 - Big tech entrance: AWS, Microsoft, and Google in CAE & EDA09:00 - GPU acceleration: Changed landscape in past three to four years09:10 - The role of AI startups offering surrogate models and real-time simulation10:40 - Industry consolidation: Mergers and acquisitions among software giants11:40 - The emergence of foundation models and surrogate systems in simulation13:00 - The significance of agents: Combining AI, models, and automation14:10 - Capabilities of autonomous AI agents in complex engineering workflows15:25 - Practical use cases: Running simulations, setting up experiments, and data analysis16:40 - How agent-driven automation could democratize engineering expertise16:10 - Questions about model ownership, open source codes, and licensing19:40 - The future of AI in engineering: Collaboration, transparency, and scientific rigor21:25 - Final thoughts: Opportunities, challenges, and the transformative potential of AI* Please note that this a personal opinion and not that of NVIDIA

Patrick Moorhead and Daniel Newman cover Daniel's acquisition of Enterprise Technology Research, IBM's historic $15 billion single-day commitment spanning quantum and open-source security, Anthropic's Claude Opus 4.8, and the heaviest single earnings night of the season featuring Dell, Marvell, Salesforce, Synopsys, Snowflake, HP, and Micron crossing $1 trillion in market cap. The handpicked topics for this week are: Anthropic Releases Claude Opus 4.8: Six Weeks After 4.7 Anthropic dropped Opus 4.8 just six weeks after 4.7, claiming it surpasses GPT-5.5 and Gemini 3.1 Pro on agentic coding, knowledge work, and computer use. Benchmark improvements across the board: agentic coding up from 64.3% to 69.2%, knowledge work from 1753 to 1890, agentic computer use from 82.8% to 83.4%. Three new features ship alongside it: Dynamic Workflows for multi-subagent orchestration inside Claude Code, Effort Control for managing token spend, and mid-task system messages via the API. Fast mode is now 2.5x faster and 3x cheaper. Pat's honest take: what it says on paper is good, particularly on tool triggering and citation precision, but he has lost significant trust in the company and is watching closely. (The Decode)   IBM Commits $10 Billion to Quantum: The Largest Single Quantum Bet in History IBM announced a $10 billion commitment over five years targeting a large-scale fault-tolerant quantum computer by 2029, landing the same day as the $5 billion Project Lightwell announcement for a single-day IBM strategic commitment of $15 billion. Pat has been calling 2029 to 2031 as the realistic commercial quantum window and calls this the strongest single corporate financial signal yet that the timeline is real. Daniel's framing: IBM wants to be the NVIDIA of quantum, and with a $10 billion commitment, it's sending a flare to the entire industry that pure-play quantum companies cannot compete at this balance sheet level. (The Decode)   IBM and Red Hat Launch Project Lightwell: $5B to Secure Open-Source Software IBM and Red Hat committed $5 billion and a global force of 20,000 engineers to secure open-source software for enterprises through frontier agentic AI, anchored by 11 of the largest US and Canadian banks including Bank of America, Goldman Sachs, JPMorgan Chase, Mastercard, and Visa. Pat's read: this is the productization answer to Anthropic Mythos. Mythos found the vulnerabilities. Lightwell is the industrial-scale patching and validation layer enterprises can actually buy on a subscription. Daniel adds that IBM is flexing its engineering talent base as a premium strategic asset, a direct counter to the narrative that AI replaces engineers. (The Decode)   Anthropic Project Glasswing: 23,000 Vulnerabilities Found Across 1,000 OSS Projects Anthropic's Claude Mythos scanned more than 1,000 widely deployed open-source projects and surfaced approximately 23,000 candidate vulnerabilities, with 1,094 confirmed as critical severity. The Cyber Verification Program now gates the strongest cyber-capable Claude variant behind vetted defenders only. While the tool creates real value, the surface of attack will likely grow as fast as any tool built to defend it. (The Decode)   Anthropic in Talks to Run Claude on Microsoft Maia 200 CNBC and The Information reported Microsoft is in active negotiations to supply Anthropic with its custom Maia 200 inference chip, which would make Anthropic the only frontier lab simultaneously running production workloads on four distinct silicon stacks: NVIDIA, AWS Trainium, Google TPU, and Microsoft Maia. Pat's context: Maia 200 delivers 30% better tokens per dollar than the latest Azure fleet per Satya Nadella, and this deal would be Maia's first major external deployment. Daniel's read: what can be built will be sold right now, and Anthropic chasing every available compute source is simply the structural reality of growing at 80x when you planned for 10x. (The Decode)   The Flip: Is AI CapEx Too Expensive to Earn Its Return? Pat takes the affirmative. With $725 billion in hyperscaler CapEx tracking for 2026, likely $1 trillion next year, memory has become the choke point making it even more expensive, and open-source models have closed enough of the quality gap for most enterprise tasks that the premium of frontier APIs is increasingly hard to justify. A recent Signal65 white paper shows on-prem payback at 18 months. Daniel's counter: Dell just booked $24 billion in AI orders in a single quarter. Agentforce crossed $1 billion ARR at 169% growth. NVIDIA guided to $91 billion. Only 20% of enterprises are using AI and only 2% of consumers. Both hosts admitted off the flip their notes looked nearly identical. (The Flip)   Micron Crosses $1 Trillion Market Cap Micron became the 12th US company ever to cross $1 trillion in market cap, surging 19% on May 26th as UBS raised its price target to $1,625, implying a $1.8 trillion market cap. Samsung's Q1 memory ASP jumped 146% year over year. DRAM spot prices spiked 55 to 60% quarter over quarter. Daniel has been pounding this call since sub-$100 and calls it a cycle elongated beyond anything seen in the 27 prior memory cycles, driven by HBM capacity reallocation away from consumer DRAM creating structural shortage. (Bulls and Bears)   Dell Technologies Q1 FY27: The Biggest Enterprise AI Infrastructure Print of 2026 Record $43.8 billion revenue, up 88% year over year, crushing the $35.7 billion consensus by $8 billion. AI-optimized servers at $16.1 billion, up 757% year over year. $24.4 billion in AI orders booked in a single quarter. FY27 AI server revenue guide raised from $50 billion to $60 billion. Non-GAAP EPS of $4.86 beat the $2.96 consensus by 64%. Stock up 18% after hours. Pat's framing: Dell was very clear about what they were going to do. Rack engineering, sales, and service. The basics. And they executed the basics at an extraordinary level while building a special relationship with NVIDIA who views Dell as a market maker for both enterprise and NeoCloud. Daniel's add: play nice and win. Michael Dell navigated the political landscape brilliantly and pulled the entire Dell brand along with him. (Bulls and Bears)   Marvell Technology Q1 FY27: Record Revenue, Data Center at 76% of Mix Record $2.418 billion revenue, up 28% year over year. Data center at $1.833 billion, up 27% year over year, now 76% of total revenue. Q2 guide of $2.7 billion at midpoint accelerates growth to 35% year over year. Operating cash flow a record $638.8 million. Daniel went on TV and said it's "written in the stars," arguing the market had misunderstood this one for too long by conflating its custom AI ASIC story with the full breadth of its connectivity and networking portfolio. Pat's closing: the shorts are eating it now and the custom AI ASIC versus merchant GPU debate is finally settling into the right answer, which is both in lockstep. (Bulls and Bears)   Salesforce Q1 FY27: Agentforce Crosses $1 Billion ARR Revenue $11.13 billion, up 13% year over year. Non-GAAP EPS of $3.88 crushed the $3.12 consensus by 24%. Agentforce ARR crossed $1 billion, up 169% year over year, with 28.6 trillion tokens processed, up 152% quarter over quarter. 50% of Agentforce bookings came from existing customers expanding. Daniel flagged the $25 billion accelerated buyback funded by new debt as an interesting signal worth watching. Pat's bottom line: it's not perfect, but certainly no "SaaSpocalypse" in those numbers. (Bulls and Bears)   Synopsys Q2 FY26: First Full Quarter With Ansys Integrated Revenue $2.276 billion, up 42% year over year, beating consensus. Non-GAAP EPS of $3.35 beat $3.15. FY26 guide raised to $9.665 billion midpoint. Daniel's framing: every chip runs through Synopsys tools, and the Ansys addition makes it the full-stack co-design platform Jensen Huang keeps talking about. Synopsys is not just the pick and shovel of current AI silicon. It is the pick and shovel of quantum, robotics, and space as well. (Bulls and Bears)   Snowflake Q1 FY27: Strongest Sequential Dollar Growth in Company History Product revenue $1.33 billion, up 34% year over year, the strongest sequential dollar growth in Snowflake history. Net revenue retention 126%. FY27 product revenue guide raised to $5.84 billion. Natoma acquisition announced for secure agentic enterprise connectivity. New $6 billion multi-year AWS commitment. Daniel's closing: proprietary unique data is the real moat of the agentic era, and that data has to live somewhere. It is going to go to platforms like Snowflake. (Bulls and Bears)   HP Inc. Q2 FY26: Eight Straight Quarters of Growth With AI PCs at 44% of Shipments Revenue $14.4 billion, up 9% year over year, the company marks its eighth consecutive quarter of top-line growth. Non-GAAP EPS of $0.86 beat the prior guide. Personal Systems at $10.2 billion, up 13%, with 30% operating profit growth. AI PCs jumped from 35% to 44% of shipments quarter over quarter, with HP guiding to 60 to 70% next fiscal year. FY26 EPS guide raised. Pat's note: they still need a permanent CEO, which would help investors sleep better at night. Daniel's add: the real explosive moment for device companies comes when AI moves to the edge and enterprises shift from expensive frontier model consumption to on-device inference. (Bulls and Bears)   Everpure Q1 FY27: Record Revenue, Rebrand Complete Record revenue of $1.1 billion, up 35% year over year. Product revenue $577 million, up 55%. Subscription ARR at $2 billion. FY27 guide raised to $4.41 to $4.51 billion. Pure Storage officially completed its rebrand to Everpure. Daniel's emerging thesis: the agentic era has focused enormous attention on memory and compute, but after the inference runs, the data has to sit somewhere. Storage has not seen its full inflection yet and Everpure is well positioned when that wave arrives. (Bulls and Bears)   The Decode Anthropic Releases Claude Opus 4.8 May 28  https://techcrunch.com/2026/05/28/anthropic-releases-opus-4-8-with-new-dynamic-workflow-tool/ IBM Commits $10B Over Five Years to Quantum Computing the Same Day as $5B Project Lightwell, Bringing IBM's One-Day AI https://www.barrons.com/articles/ibm-stock-quantum-computing-aafbb1eb IBM + Red Hat Announce Project Lightwell  https://newsroom.ibm.com/2026-05-28-ibm-and-red-hat-commit-5-billion-to-redefine-the-future-of-open-source-in-the-ai-era Anthropic Project Glasswing / Claude Mythos Finds 23,000 Potential Vulnerabilities Across 1,000+ Open-Source Projects https://www.securityweek.com/anthropic-mythos-detected-23000-potential-vulnerabilities-across-1000-oss-projects/ Anthropic Negotiating to Run Claude on Microsoft's Maia 200 AI Chips  https://www.cnbc.com/2026/05/21/anthropic-microsoft-maia-200-ai-chip.html OpenAI + Anthropic Walk Back the AI Jobs Apocalypse Ahead of IPOs https://finance.yahoo.com/sectors/technology/articles/ai-chiefs-walk-back-job-193605798.html https://x.com/RiskCentre/status/2059397756016611668 The Flip Is AI Capex Becoming Too Expensive to Earn Its Return — and Will the Result Be a Forced Shift to Open-Source and Smaller Use-Case-Specific Models, or a Continued $725B+ Hyperscaler Buildout That Vindicates the Capex on Productivity Gains? FOR:  The shift is to open-source + smaller use-case-specific models with better token economics, not away from AI https://x.com/danielnewmanUV/status/2059822712122400975 DeepSeek 75% permanent price cut + Anthropic Claude Code restriction reversal https://www.buildfastwithai.com/blogs/ai-news-today-may-26-2026 $190B Microsoft capex + $725B+ aggregate hyperscaler capex with no analog ROI yet  https://www.buildfastwithai.com/blogs/ai-news-today-may-26-2026   AGAINST:  Salesforce Agentforce ARR crossed $1B this quarter on 28.6T tokens processed  https://www.stocktitan.net/sec-filings/CRM/8-k-salesforce-inc-reports-material-event-3b8ead2852bb.html Lenovo +105% AI revenue, +84% Q4; Dell $43B AI backlog: the AI infrastructure flywheel is converting capex to revenue today https://investor.marvell.com/news-events/press-releases/detail/1023/marvell-technology-inc-reports-first-quarter-of-fiscal-year-2027-financial-results NVIDIA $91B Q2 guide + $1T Blackwell+Vera Rubin CY25-CY27 reaffirmed  https://www.cnbc.com/2026/05/20/were-raising-our-price-target-on-nvidia-after-another-knockout-quarter-and-guide-.html DeepSeek + Chinese price war is a Chinese export-controls story, not a US economic ceiling story https://www.cnbc.com/2026/05/21/anthropic-microsoft-maia-200-ai-chip.html   Bulls & Bears Micron (NASDAQ: MU) Crosses $1 TRILLION Market Cap for the First Time https://www.cnbc.com/2026/05/26/micron-stock-trillion-market-cap.html Dell Technologies Q1 FY27 ACTUALS  https://www.cnbc.com/2026/05/28/dell-q1-earnings-report-2027.html Marvell Technology Q1 FY27 ACTUALS https://investor.marvell.com/news-events/press-releases/detail/1023/marvell-technology-inc-reports-first-quarter-of-fiscal-year-2027-financial-results Salesforce CRM Q1 FY27 ACTUALS  https://investor.salesforce.com/financials/quarterly-results/ Synopsys SNPS Q2 FY26 ACTUALS https://investor.synopsys.com/events-and-presentations/events/event-details/2026/Q2-Fiscal-Year-2026-Earnings/default.aspx Snowflake SNOW Q1 FY27 ACTUALS  https://www.businesswire.com/news/home/20260527027931/en/Snowflake-Reports-Financial-Results-for-the-First-Quarter-of-Fiscal-2027 HP Inc. HPQ Q2 FY26 ACTUALS https://finance.yahoo.com/markets/stocks/articles/hp-q2-earnings-call-highlights-230459161.html Everpure (NYSE: P, formerly Pure Storage) Q1 FY27 ACTUALS  https://investor.salesforce.com/financials/quarterly-results/ Synopsys SNPS Q2 FY26 ACTUALS https://investor.synopsys.com/events-and-presentations/events/event-details/2026/Q2-Fiscal-Year-2026-Earnings/default.aspx Snowflake SNOW Q1 FY27 ACTUALS  https://www.businesswire.com/news/home/20260527027931/en/Snowflake-Reports-Financial-Results-for-the-First-Quarter-of-Fiscal-2027 HP Inc. HPQ Q2 FY26 ACTUALS  https://finance.yahoo.com/markets/stocks/articles/hp-q2-earnings-call-highlights-230459161.html Everpure (NYSE: P, formerly Pure Storage) Q1 FY27 ACTUALS https://www.prnewswire.com/news-releases/everpure-announces-first-quarter-fiscal-2027-financial-results-302783502.html

Dan Nathan hosts David Schamis (CEO, Hyperliquid Strategies) and Jeroen Nieuwkoop (COO, Hyperliquid Strategies) to explain Hyperliquid, a three-and-a-half-year-old L1 blockchain built for high-throughput exchange activity and best known for perpetual futures trading. They discuss how Hyperliquid aims to be an “AWS of on-chain trading,” enabling permissionless exchanges like Trade XYZ to list perps on assets such as major U.S. equities, gold, silver, and oil, and why decentralized custody, speed, and UI/UX differentiate it from prior DEXs. They outline HYPE tokenomics, including using ~99% of protocol fees for token buybacks and burns, and define perp pricing via funding rates. The conversation covers U.S. regulatory constraints, Hyperliquid Strategies' Nasdaq-listed DAT (PURR) formed via reverse merger to provide U.S. access to HYPE exposure, and emerging use cases like pre-IPO perps (e.g., SpaceX) for 24/7 price discovery. —FOLLOW USYouTube: @RiskReversalMediaInstagram: @riskreversalmediaTwitter: @RiskReversalLinkedIn: RiskReversal Media

Carl Quintanilla, Jim Cramer and David Faber drilled down on tech and the AI trade: Salesforce shares fell in reaction to the company's mixed Q1 results and lighter-than-expected revenue guidance for the current quarter. Shares of Snowflake soared on news of its Q1 beat, raised outlook and a $6 billion commitment to its multiyear partnership with Amazon's AWS.  On the M&A front: Fertitta Entertainment agrees to buy Caesars Entertainment in an all-cash deal valued at $5.7 billion. Also in focus: Crude oil prices rise amid faltering hopes for a U.S.-Iran deal, Marvell extends its rally, Dell wins Pentagon contract, retailers surging on earnings, Meta launches subscriptions, Cramer's take on investing in Microsoft, economic data deluge. Squawk on the Street Disclaimer Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

In this episode, Corey Quinn sits down with Dexter Horthy, CEO and Co-founder of Human Layer, to unpack what engineers are getting wrong about AI, especially when it comes to coding agents.From the obsession with “just throwing more tokens at the problem” to the reality of building scalable AI workflows, Dexter shares hard-earned insights on how to actually push models to their limits. They dive into the evolution of developer workflows, the rise of AI-powered software factories, and why understanding context and verification matters more than raw model power.If you're building with AI or trying to, this episode will challenge how you think about what these systems can (and can't) do.Show highlights: (00:00)Throwing Tokens Too Far(01:04) Meet Dexter Horthy(01:52) Personal AI Benchmarks(04:12) Human Layer Race Condition(05:59) Rewrites and Tech Debt(07:19) Software Factories Mindset(10:20) Verifiable Problems and Token Limits(13:45) Agents in the Trenches(18:05) GitHub at Agent Scale(26:23) Safety Ethics and Closing ThoughtsAbout Dexter: Dexter Horthy is the CEO and Co-Founder of HumanLayer, where he helps engineering teams tackle complex problems in large codebases using coding agents. Previously, he worked in DevOps, SRE, and Solutions Engineering at Replicated, and contributed to lunar navigation software at NASA JPL. Outside of work, he's a fan of tacos and burpees, though not necessarily in that order.Links: LinkedIn: https://www.linkedin.com/in/dexterihorthy/Website: https://humanlayer.devSponsored by: duckbillhq.com

AI subscriptions are becoming as essential as internet bills - and just as expensive. The vBrownBag gang takes a hard look at the real cost of LLMs and what happens when the free ride ends. Chris, Shala, and Damian dig into the Anthropic pricing plot twist, why AI data centers consume 10x the power of traditional racks, the DeepSeek distillation controversy, and what happens when the first hit's free phase ends. You'll learn practical strategies for reducing token burn, why local models are becoming a viable cost escape hatch, how to pick the right model for the right job, and why blindly using Opus for everything is lighting money on fire. This is the unfiltered conversation every AI practitioner needs to have - before the subsidies disappear and the real bills arrive. Timestamps 0:00 Cold Open: Get These Darn Kids Off My Lawn 1:27 Chris's Big News: Leaving IBM for Six Feet Up 8:09 How Many AI Subscriptions Do You Have? 16:41 Stack Overflow Is Dead, Long Live Claude 17:12 Don't Just Blindly Copy and Paste (AI Edition) 31:00 Anthropic Gross Margin 2025: Negative 53% 35:30 When Token Costs Exceed a Junior Dev's Salary 42:02 Find the Model That Fits the Job 46:11 AI Multitasking Is a Lie (Just Like Humans) 49:05 We Are Uniquely Bad at Making Money Off This Show 53:19 Supply Chain Attacks and GitHub Actions 54:45 Did We Solve Anything? Yes. No. Maybe. 55:58 Grateful for Friends & Wrapping Up Links from the show:

Are you looking to save time, make money, and start winning with less risk? Then head to https://www.ovtlyr.com.Learn more about OVTLYR: https://youtu.be/TUCbD5KovlcSnowflake just absolutely ripped the market apart after earnings, and honestly… this is the kind of move traders dream about catching early. We're talking about a monster gap up after announcing a massive AWS deal, raising guidance, and completely blowing past expectations. Meanwhile, OVTLYR had already flashed a buy signal weeks before the explosion happened.But here's where things get really interesting…While tech stocks are heating up hard, there are some weird signals showing up underneath the market right now. The S&P 500 and Nasdaq still look bullish on the surface, but fear and greed data is starting to tell a different story. That's the stuff most traders miss.In this breakdown, we're looking at the stocks and sectors getting real momentum right now:✅ Snowflake going full beast mode after earnings✅ Navitas Semiconductor flashing fresh bullish momentum✅ Groupon, Spotify, and Meta setting up strong✅ Carnival Cruise Lines quietly turning around✅ Energy stocks like Exxon and Chevron starting to crackThere's also a look at meme stock momentum coming back with AMC and BlackBerry making noise again.If you're trying to stay ahead of the next big move instead of reacting late, this is the kind of market breakdown you need in your routine.Subscribe to OVTLYR for disciplined trading strategies that actually make sense.

Semantic diffusion, combined with the pace of technology change, makes talking about AI-adjacent practices and techniques incredibly diffficult. There are few better examples of this issue than the term 'spec-driven development'. Although it's not new — its coinage precedes our current AI moment — it has become ubiquitous over the last six months or so as software professionals attempt to develop a vocabulary for talking about how they're developing methods for working successfully with coding agents. On this episode of the Technology Podcast, Birgitta Böckeler is joined by Laura Tacho — Developer Experience at AWS — to discuss all things spec-driven development. From competing definitions to different interpretations, implementations and workflows, the discussion provides a frank and grounded look at one of the most discussed and debated terms in modern software engineering. Learn more about Laura's work by visiting her website: https://lauratacho.com/ Read Birgitta's article on spec-driven development on Martin Fowler's website: https://martinfowler.com/articles/exploring-gen-ai/sdd-3-tools.html Learn more about The Future of Software Development Retreat discussed on this episode and explore some of the key insights: https://www.thoughtworks.com/about-us/events/the-future-of-software-development

Dr. Yana Werner and Phil LeBrun are senior leaders at Amazon Web Services who help Fortune 500 companies navigate AI innovation, organizational change, and leadership transformation. Yana is an Executive in Residence at AWS, a Harvard Business Review Press author, and a global transformation leader with experience spanning financial services, startups, and DHL. Phil is the former international CIO of McDonald's, where he led technology modernization across 38,000 restaurants in 120 countries. Together, they co-authored The Octopus Organization, a book focused on helping organizations embrace decentralized leadership, AI adoption, and human-centered change. On this episode we talk about: Why most corporate transformations fail — and how to avoid “soul-destroying” change initiatives The rapid acceleration of AI and why companies are struggling to keep up How Amazon approaches AI innovation internally and encourages experimentation at scale The meaning behind “The Octopus Organization” and decentralized intelligence Why curiosity is one of the most valuable career skills in the modern economy Phil's journey from flipping burgers at McDonald's to becoming international CIO Yana's philosophy of saying “yes” to opportunities and connecting the dots later Why leadership isn't tied to a title — and how anyone can become a leader The importance of learning over certainty in today's workplace How AI tools are reshaping organizational structures and decision making Why transformation projects fail 70–90% of the time Advice for young professionals navigating today's corporate and AI-driven landscape How experimentation and autonomy create innovation inside large organizations The role of curiosity, lifelong learning, and ownership in career growth Why successful leaders ask better questions instead of pretending to have all the answers Quotes from the Episode: “We prefer two teams solving the same problem rather than everyone waiting for permission.” — Phil LeBrun “If AI stopped developing today, it would still take companies five years to catch up.” — Dr. Yana Werner “We train people to have answers, not ask questions.” — Phil LeBrun “My career is a strange connection of dots because I said yes to a lot of things.” — Dr. Yana Werner Connect with Dr. Yana Werner & Phil LeBrun: The Octopus Organization Official Website A Word from Our Sponsors: - Are you ready to start your own creatorjourney and make it big? Visitwww.fanvue.com today and launch yourcareer! - To learn more about Mode Mobile and its investor community, go to https://invest.modemobile.com/travismakesmoney-Travis Makes Money is made possible by High Level – the All-In-One Sales & Marketing Platform built for agencies, by an agency.Capture leads, nurture them, and close more deals—all from one powerful platform.Get an extended free trial at gohighlevel.com/travis Learn more about your ad choices. Visit megaphone.fm/adchoices

Hosts Ned and Kyler compare notes on everything they've been doing with AI, including the successes they’ve enjoyed and headaches they've suffered building and implementing AI agents. They talk about how AI has sped up their workflows, how managing multiple AI agents is akin to raising toddlers, the necessity of using deterministic scripts for increased... Read more »

Hosts Ned and Kyler compare notes on everything they've been doing with AI, including the successes they’ve enjoyed and headaches they've suffered building and implementing AI agents. They talk about how AI has sped up their workflows, how managing multiple AI agents is akin to raising toddlers, the necessity of using deterministic scripts for increased... Read more »

SUMMARY:  Brian Gracely (@bgracely) and Brandon Whichard (@bwhichard, Software Defined Talk and Failover Media) discuss the biggest AI news stories from the month of May, 2026. SHOW: 1031SHOW TRANSCRIPT: The Reasoning Show #1031 TranscriptSHOW VIDEO: https://youtu.be/MNihDdBSteISHOW SPONSORS:Nasuni - Activate your data for AI and request a demoShareGate - ShareGate Protect. Microsoft 365 Governance, we got this!SHOW NOTES:Links to all the AI News covered in this month's showFEEDBACK?Email: show @ the enterprise ai show dot comeBluesky: @TheEntAIShow.bsky.socialTwitter/X: @TheEntAIShowInstagram: @TheEntAIShow

Hosts Ned and Kyler compare notes on everything they've been doing with AI, including the successes they’ve enjoyed and headaches they've suffered building and implementing AI agents. They talk about how AI has sped up their workflows, how managing multiple AI agents is akin to raising toddlers, the necessity of using deterministic scripts for increased... Read more »

AWS Morning Brief for the week of May 25th, with Corey Quinn. Links:Amazon Bedrock expands support for request-level usage attributionAmazon ECS introduces pause and continue controls for service deploymentsAWS announces AWS Interconnect - multicloud connectivity with Oracle Cloud Infrastructure in previewAWS Organizations now supports higher quotas for service control policies (SCPs)Amazon Aurora MySQL 8.4 is now generally availableIntroducing ExtendDB: An open source DynamoDB-compatible adapter with pluggable storage backendsNine Entertainment's journey: Achieving 98% cost savings with Amazon ElastiCache Serverless for ValkeyAnnouncing updated retry behavior for AWS SDKs and ToolsAnnouncing AWS CDK Mixins: Composable Abstractions for AWS ResourcesCVE-2026-8838 - Remote Code Execution in amazon-redshift-python-driverCVE-2026-9133 - Arbitrary file read in rabbitmq-aws plugin

Join us as Brian Hough (CEO & Founder of Tech Stack Playbook, AWS Hero) gets brutally honest about the state of tech hiring and what skills developers actually need to survive - and thrive - in the AI era. Brian walks through his frontline perspective on why tech layoffs aren't about skills - they're about market economics - and what that means for engineers trying to stay relevant. You'll learn which roles are actually hot right now (ML engineer, AI engineer, cloud architect, full stack dev), why companies want utility players who can build end to end, how to use social media and building in public to get quietly hired, and why the engineers who thrive will be those who can go from vision to deployed system. Brian also covers practical strategies for positioning yourself before the next wave hits, including using roadmaps as a personal curriculum and leveraging AI as a career accelerator rather than a threat. Timestamps 0:00 Cold Open 0:11 Welcome & Introduction 2:16 Taking Vibe Code to Production-Grade Systems 3:01 Brian's Update: Dog Feeding & Building Internal Tools 8:05 Mac Maximus: Building on AWS EC2 Mac 9:49 Let's Get Into the Presentation 10:10 Agenda Overview 11:11 Is Anyone Actually Working Less Because of AI? 12:52 What Happens When You Don't Understand What You Built 20:10 AWS Root Account Horror Story 23:24 The Skills You Need in 2026 24:09 Tech Scene Overview & Job Posting Divergence 26:19 What Companies Actually Want: Utility Players 28:00 Hot Roles: ML Engineer, AI Engineer, Cloud Architect 32:00 The Layoff Reality: It's Market Economics, Not Skills 40:49 Now Is the Best Time to Start a Startup 42:31 Roles & Salaries Breakdown 43:55 This Advice Is for Everyone - Not Just Job Seekers 48:01 What's Getting Replaced vs. What's Irreplaceable 49:14 How to Become an Irreplaceable Engineer 52:42 Maximum Viable Product 53:02 Building in Public & Social Media Strategy 55:32 Positioning Yourself Before the Next Wave 56:19 Brian's Closing Thoughts 57:03 AI on Your Resume = Getting Hired Fast 58:12 Using Brian's 30-Day Plan as a Claude Curriculum 59:55 Platform Engineering Hot Take 1:03:05 Wrap-up & See You in Seattle How to find Brian: https://brianhhough.com/techstackplaybook Links from the show: https://roadmap.sh/python https://roadmap.sh/ai-engineer https://roadmap.sh/machine-learning https://roadmap.sh/ai-agents

By Selva Ozelli Esq, CPA, Author of Sustainably Investing in Digital Assets Globally This is the second article in a series of articles I am writing for Irish Tech News to explore the financial, technical, legal aspects of utilizing space solar energized orbital data centers that are rapidly evolving into "AI Factories, designed specifically to convert massive amounts of electrical power into intelligence, measured in tokens" around the world. The US Space Race My new series is a follow up to an interview ITN conducted with me in 2020 exploring how space solar energy could sustainably energize the tokenization of the global financial markets which is projected to grow to multi-trillion dollars by the end of the decade. The shift toward space-solarized data infrastructure is accelerating in the US rapidly following the historic March 1, 2026, drone strikes on AWS data centers in the United Arab Emirates and Bahrain which has extended during April and May. Executed by Iran's Islamic Revolutionary Guard Corps (IRGC), these kinetic strikes marked the first time commercial hyperscale data centers were directly targeted and physically damaged in active warfare. The attacks caused prolonged service disruptions, exposed the vulnerability of terrestrial tech infrastructure, and proved that earth bound data centers are now prioritized military targets. As detailed in the table below US technology and aerospace companies are increasingly looking to space-solarized solutions to address the immense energy and cooling demands of AI, with several key initiatives emerging. US Tech and Aerospace Companies Focused on Space Solarized Data Centers Hyperscale Cloud Company Orbital Edge Computing Orbital Data Center/Number of Satellite Constellation Space Solar LEO Network Rocket Launch Robotics Amazon Web Services (AWS) Y Y, Blue Origin – Blue Ring spacecraft/ Project Sunrise 51,600 Y Y, Amazon LEO Y Y Microsoft Azure Y, Azure Space N, Sold Azure Orbital Ground Station N, Space Azure Solar Cell Tech N N Y Google Cloud Y, Space Llama Y, Project Suncatcher in partnership with Planet Labs a high-profile "moonshot" initiative aimed at building and deploying artificial intelligence (AI) data centers in space/81 Y N Space X Y, Google Deep Mind Meta N, Terrestrial Edge Computing N Y, Metasat & Overview Energy N, High-altitude, solar-powered drones (Aquila project) N Y Starcloud Y Y Partnership with AWS/88,000 Y Y, Starcloud-1 (November 2025): first test satellite containing an Nvidia H100 chip, that survived radiation and function in space. SpaceX Y Space X – Orbital Data Center Y Y/ 1,000,000 Y Starlink Y Y Nividia Y, NVIDIA Space-1 Vera Rubin computing platform Y Y Y Space X Y Atherflux rebranded to Cowboy Space Y Y/ 20,000 Y N N Y Lone Star Y, (2021) First data storage and edge processing test at International Space Station Y, Orbital and Lunar Data Center with NASA Y Y Space X Y Axiom Space Y, In March 2025, Axiom deployed Red Hat Device Edge on the ISS to test terrestrial cloud applications in space, serving as a prototype for ODC Nodes. Y Y Y Space X Y Two Distinct Approaches in Space Solarized Data Center Operations in the US US technology and space companies in a race are aggressively pursuing orbital and space-solarized data centers and are tackling these operations through two distinct methodologies: orbital data processing (in-space edge compute) and space-based terrestrial power harvesting. Both approaches aim to bypass the escalating energy demands, cooling constraints, and land footprint limitations of Earth-based data center infrastructure. The two approaches differ significantly in how they utilize space and solar resources. Here is a summary: Terrestrial vs. Space-Based AI Compute Constraint Terrestrial Data Centers Orbital Data Centers Power Source Strained local power grids Unlimited, direct solar energy Cooling High water and energy consumption Natural cold of space vacuum Space & Regulation Tight zoning laws and land limits No ter...

Interview with Rob Allen from Threatlocker This week, Rob Allen from Threatlocker is with us to discuss the importance of EDR and MDR visibility. We discuss some real world attacks and anecdotes where EDR was able to save the day when threats were missed by other controls. Topic: Do the basics, they said. Easier said than done. Guillaume and Adrian discuss the futility of attempting to do all the foundational work standards, best practices, and regulations expect of organizations. Adrian has given up. Fortunately, Guillaume has some excellent advice and hope to share on this front. The weekly enterprise news Finally, in the enterprise security news, a really interesting vibe check funding acquisitions the verizon DBIR we give a tutorial on how to leak AWS keys on github OH NEVERMIND, SOMEONE AT CISA ALREADY MADE THE TUTORIAL agents versus agents exploitbench the vulnpocalypse robot dogs are SO EASY to take out, we don't need to be too scared of them yet All that and more, on this episode of Enterprise Security Weekly. Visit https://www.securityweekly.com/esw for all the latest episodes! Show Notes: https://securityweekly.com/esw-460

Interview with Rob Allen from Threatlocker This week, Rob Allen from Threatlocker is with us to discuss the importance of EDR and MDR visibility. We discuss some real world attacks and anecdotes where EDR was able to save the day when threats were missed by other controls. Topic: Do the basics, they said. Easier said than done. Guillaume and Adrian discuss the futility of attempting to do all the foundational work standards, best practices, and regulations expect of organizations. Adrian has given up. Fortunately, Guillaume has some excellent advice and hope to share on this front. The weekly enterprise news Finally, in the enterprise security news, a really interesting vibe check funding acquisitions the verizon DBIR we give a tutorial on how to leak AWS keys on github OH NEVERMIND, SOMEONE AT CISA ALREADY MADE THE TUTORIAL agents versus agents exploitbench the vulnpocalypse robot dogs are SO EASY to take out, we don't need to be too scared of them yet All that and more, on this episode of Enterprise Security Weekly. Show Notes: https://securityweekly.com/esw-460

News and Updates: Microsoft Ditches SMS Two-Factor Authentication: Microsoft is phasing out SMS-based login codes, citing fraud vulnerability, and pushing users toward more secure passkeys using biometrics or device PINs. Faulty Drivers Secretly Draining Windows 11 Batteries: Microsoft admits third-party drivers have silently prevented laptops from entering hibernation for years, announcing stricter driver evaluation and automatic rollback via Windows Update. ShinyHunters Targets Cybersecurity Researcher: Hacking gang ShinyHunters is flooding Unit 221B with calls and emails after researcher Allison Nixon publicly urged victims not to pay the group's ransom demands. CISA Exposes Own Passwords on Public GitHub: The U.S. cybersecurity agency left plaintext passwords, AWS tokens, and access keys in a public GitHub repo named "Private-CISA" for approximately six months before discovery. Kindle Owners Jailbreak Devices After Amazon Drops Support: Amazon is ending support for 13 older Kindle models on May 20, prompting users to jailbreak their devices to maintain full functionality beyond already-downloaded content.

SUMMARY: The biggest enterprise AI question may no longer beWhich model is smartest? Instead, which organization can most effectively operationalize, govern, and economically scale AI agents across the business?'SHOW: 1030SHOW TRANSCRIPT: The Enterprise AI Show #1030 TranscriptSHOW VIDEO: https://youtu.be/acOBfRI0P3USHOW SPONSORS:ShareGate - ShareGate Protect. Microsoft 365 Governance. We got this.Nasuni - Activate your data for AI and request a demoSHOW NOTES:Opening Thesis - Was the first wave of AI adoption artificially cheap? - The industry may be transitioning from subsidized growth to usage-based economics. Key Topics 1. Evidence AI Was Subsidized Massive CAPEX vs low end-user pricing Generous enterprise bundles Frontier model access for $20/month 2. The Hidden Economics of AI Agents - Agents consume exponentially more inference Tool orchestration, retries, memory, verification 3. Why Frontier Labs Are Shifting Focus From benchmark supremacy to orchestration Governance, memory, connectors, MCP, workflows 4. Forecasting AI Pricing 12 Months:  Commodity inference gets cheaper - Frontier reasoning remains premium 24 Months:  AI billing resembles AWS-style infrastructure billing Runtime, memory, latency and orchestration become billable 36 Months: Outcome-based pricing emerges AI spending shifts from IT budgets to labor budgets Final Takeaways  Commodity AI becomes utility-priced Frontier reasoning becomes premium Agents reshape enterprise economicsKey Conclusions1. AI probably was subsidizedThe economics strongly suggest adoption-first pricing.2. The subsidy era may be endingPremium tiers and metered pricing are emerging.3. AI agents fundamentally alter economicsUsage scales exponentially with autonomy.4. Commodity AI and frontier reasoning are separatingOne becomes cheap.One becomes premium.5. The real battle is moving upward in the stackThe future moat may be:orchestrationgovernanceworkflowsenterprise contextoperational toolingFinal Closing Thought“The biggest enterprise AI question may no longer be:‘Which model is smartest?'Instead:‘Which organization can most effectively operationalize, govern, and economically scale AI agents across the business?'”FEEDBACK?Email: show @ the enterprise ai show dot comeBluesky: @TheEntAIShow.bsky.socialTwitter/X: @TheEntAIShowInstagram: @TheEntAIShow

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

Starting an AI company is all about spotting a real problem and using AI to solve it in a smarter, faster way than what's out there today. It's less about having the perfect idea and more about starting focused, learning fast, and building something people actually want.This week, Dave, Esmee, and Rob are joined by Gijs van de Nieuwegiessen and Tijn van Daelen, founders of One Horizon AI, to explore what it really takes to start and build an AI‑native company TLDR00:32 – Introduction00:55 – Hang out: Why Dutch names can be a real tongue-twister02:00 – Dig in: Exploring how an AI-native culture fits with human-to-human interaction13:35 – Deep dive with Gijs van de Nieuwegiessen and Tijn van Daelen1:01:54 – Following AI: Bloopers, reflections, and field hockey with the kids GuestGijs van de Nieuwegiessen: https://www.linkedin.com/in/nieuwegiessen/Tijn van Daelen: https://www.linkedin.com/in/tijn-van-daelen-495986131/Open source repo: https://github.com/onehorizonai/ink HostsDave Chapman:  https://www.linkedin.com/in/chapmandr/Esmee van de Giessen:  https://www.linkedin.com/in/esmeevandegiessen/Rob Kernahan:  https://www.linkedin.com/in/rob-kernahan/ ProductionMarcel van der Burg:  https://www.linkedin.com/in/marcel-vd-burg/Dave Chapman:  https://www.linkedin.com/in/chapmandr/ SoundBen Corbett:  https://www.linkedin.com/in/ben-corbett-3b6a11135/Louis Corbett:   https://www.linkedin.com/in/louis-corbett-087250264/ 'Realities Remixed' is an original podcast from Capgemini

Today our Packet Pushers team assembles to discuss whether the grass is greener on the NetOps or DevOps side of the telemetry fence. William of The Cloud Gambit, Scott of Total Network Operations, and Ned and Kyler of Day Two DevOps discuss the difficulties and differences of getting telemetry and state from devices across different... Read more »

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

In today's Cloud Wars Minute, I examine how AI demand is reshaping rivalries between Google Cloud, AWS, NVIDIA, and Anthropic. Highlights 00:03 — According to reports, Anthropic has committed to a $200 billion five-year agreement for Google Cloud services and Google-designed chips, a deal that could account for more than 40% of Google Cloud's revenue backlog. 00:18 — This represents yet another escalation in the rapidly expanding partnership between Google Cloud's parent company, Alphabet, and Anthropic, following Alphabet's previously announced $40 billion investment into the company. 00:49 — The company also holds considerable infrastructure deals with providers, including AWS and NVIDIA, and what this deal underscores is the extraordinary scale of demand for AI services. The need for compute capacity has grown so large that even a $200 billion agreement may not be enough to meet future requirements. 01:33 — However, companies like Google Cloud, with the infrastructure required to support hyperscale AI development, are positioned at the very center of this massive transformation. Visit Cloud Wars for more.

Send us Fan MailSpectrum had us paying big money for coax internet that still acts flaky, and the moment a fiber option showed up it felt like freedom. Then the real world kicked in: a line gets cut, the repair window stretches out, and suddenly you're solving work-from-home problems with a last-minute hotspot. We talk through what it's like living where the ISP knows they have leverage, why fiber vs coax actually matters, and how competition from fiber builds, 5G home internet, and even Starlink is changing the rural internet conversation.From there we get into the stuff that keeps our brains busy: studying for an AWS certification, what helps learning click, and why cloud architect interviews care about cost, tradeoffs, and real projects more than memorized terms. We also share what we've been collecting lately, from vinyl records logged in Discogs to the weird joy of finding out what old albums are worth, plus the daily battle of bird feeders versus squirrels (spicy bird seed really might be the cheat code).We also address a wild lesson from social media: how a 10-second clip can explode and spark arguments from people who never watched the full context. And since we can't resist tech news, we debate an Xbox disc-to-digital rumor and what it could mean for game ownership, DRM, and preservation, then pivot into Apple's innovation problem and why Macs keep earning their “buy once, use forever” reputation.If you like honest talk about tech, games, and real-life problem solving, subscribe, share the show with a friend, and leave a review. What's one thing you refuse to go fully digital on? https://www.carolinaotakus.com/

In this episode of the Sports Tech AllStars Podcast, we present Josh Helmrich, Senior Director of Media Strategy, Business Development and Next Gen Stats at the NFL.The conversation explores how the NFL went from zero player tracking data to a platform that powers broadcast graphics, officiating decisions, coaching strategy, health and safety research and the Madden video game - and what the next evolution of that platform looks like now that optical tracking has entered the picture.TakeawaysNext Gen Stats started as a working project name that nobody gave much thoughtThe NFL chose wearable ultra-wideband tracking over optical at the start because of the unique occlusion challenges in American football In the first game of tracking, the NFL collected more data than in the entire history of the league combinedMarrying optical and wearable tracking together is the real unlock The Big Data Bowl identified a winning rushing yards model from a Japanese team that had never watched American football and did not speak EnglishBall tracking at the bottom of a pile-up remains an unsolved problem The NFL now has 29 data points per player at 10 frames per second Innovation partners do not need to wait for the NFL to come to them The Big Data Bowl has become a talent pipeline, placing graduates directly into NFL clubs and the league officeTo learn more, visit: https://nextgenstats.nfl.comGet in touch with Josh Helmrich at: linkedin.com/in/josh-helmrich-07a93510 Hosted by ⁠Rohn Malhotra⁠ from ⁠SportsTechX⁠ - Leading source of Investment and Innovation insights in sports. As promised, here's your small surprise:Unlock your 30-day growth plan (worth €49) on the SportsTechX Intelligence Hub for free!Simply verify your company details and you get access to 1,500+ investors, programmes, initiatives and events in the sportstech ecosystem.Here's how to get set up and if you'd like a walkthrough of the platform, feel free to book a call here.More from SportsTechX:Explore the SportsTechX Intelligence Hub, an interactive database of over 8,000 sports tech companies, 8,000+ deals, 1,000+ investors, programs and events - HEREDownload the latest Global Sports Tech Ecosystem Report - HERESign Up for the Sports Tech Weekly Newsletter for more news, features & insights on Sports Tech - HERE Stay Connected and follow for more:LinkedInYouTubeSpotifyApple PodcastChapters00:00 Introduction02:11 Sports Innovation Düsseldorf and the NFL in Europe03:17 How the NFL Is Building an International Fan Base05:18 The Origin of Next Gen Stats 06:02 Why the NFL Chose Wearable Tracking Over Optical08:17 The Evolution of Sensors10:34 Why Optical Tracking Took 10 Years to Arrive in the NFL12:27 Ball Tracking in Football vs Other Sports13:17 Was There a Plan or Did the Use Cases Reveal Themselves?14:27 Enabling Coaches, Officials and Health Teams to Find Their Own Use Cases15:49 AWS, the Big Data Bowl and Opening Up NFL Data16:33 What the Big Data Bowl Actually Is and Why It Works18:24 The Japanese Team That Won Without Ever Watching American Football20:31 How the Big Data Bowl Became a Talent Pipeline for NFL Clubs21:45 How the NFL Evaluates and Partners With New Technology Providers22:56 The Unsolved Problem: Ball Tracking at the Bottom of a Pile-Up24:09 What Kind of Technology the NFL Is Actively Looking For25:09 What the Next 12–18 Months Look Like for Next Gen Stats26:23 A Call to Action for International Sports Tech Innovators27:42 Favourite Sporting Moment

Greg Murphy of Vectra AI explains why no single security tool is enough in 2026, and how AI is transforming overwhelmed security teams into lean, highly responsive defense operations.Topics Include:Vectra AI helps enterprises detect and respond to cyberattacks before they become breaches.CISOs face millions of alerts monthly with dangerously understaffed security teams.Vectra pioneered AI-driven triage to prioritize only the most critical threats.The result: analysts act on two or three alerts, not thousands.Generative AI is now actively being weaponized by sophisticated bad actors.The first fully AI-orchestrated cyberattack by a nation state has already happened.Vectra and AWS Bedrock are building autonomous agents to fight back.Agentic AI can investigate thousands of incidents and surface only what matters.Over-reliance on single tools like EDR leaves dangerous gaps in defense.Modern attacks move fluidly across identity, network, and cloud environments simultaneously.AI stitches cross-surface signals together, revealing attacks hidden in isolated events.Best practice: assume breach, expand your network definition, and layer best-of-breed solutions.Participants:Greg Murphy – Chief Business Officer, Vectra AISee how Amazon Web Services gives you the freedom to migrate, innovate, and scale your software company at https://aws.amazon.com/isv/

A poisoned software package compromised OpenAI employee devices before security teams could stop it. The company behind critical Ozempic injection components has been offline for weeks after a ransomware attack. And Change Healthcare is now facing another major lawsuit tied to the 2024 breach that crippled healthcare payments nationwide. Three stories. One message: Your business is now exposed to companies you don't control. On this episode of Security Squawk, Bryan Hornung, Randy Bryan, and Reginald Andre break down three cyber incidents that reveal how third-party trust has become one of the biggest operational risks in business today. This Week's Cybersecurity Breakdown 1. OpenAI, TanStack & the npm Supply Chain Worm A software supply chain attack spread through trusted developer ecosystems at massive speed: 42 npm packages poisoned in six minutes Malware stole GitHub tokens, AWS credentials, and CI/CD secrets OpenAI confirmed two employee devices were compromised ChatGPT Desktop, Codex App, Codex CLI, and Atlas certificates rotated Demonstrates how modern attacks now spread through trusted development infrastructure 2. West Pharmaceutical Ransomware Attack A cyberattack against a company most people have never heard of — but nearly everyone depends on: West Pharmaceutical components are used in roughly 43 billion injectable drug deliveries annually Includes Ozempic, Wegovy, insulin pens, vaccines, and hospital injectables Systems taken offline globally after ransomware deployment Manufacturing disruptions continue weeks later 3. Allied World v. Change Healthcare — The Financial Fallout Begins The legal consequences of the Change Healthcare breach are escalating: Cyber insurer Allied World filed suit seeking more than $1 million in damages Avesis operations were disrupted for roughly 90 days Root cause traced to a low-level Citrix account with no MFA Credentials were reportedly circulating on Telegram prior to the breach The Bottom Line The modern business attack surface is no longer just your company. It's: your software vendors your healthcare clearinghouses your package repositories your pharmaceutical suppliers Every trusted relationship is now a potential point of failure. And when those companies get breached, your business absorbs the consequences. Support the show: buymeacoffee.com/securitysquawk Subscribe for weekly breakdowns of ransomware, supply chain attacks, AI threats, and executive-level cybersecurity strategy.

The calm before the AI storm? ⛈️You bet. Although we had a bevy of new AI releases, fresh drama and a HUGE IPO from an AI company, this week's biggest AI news is about what's around the corner: - An upcoming decision in the Musk vs. OpenAI lawsuit - How the big Cerebras IPO will impact the other AI giants- Google's I/O conference Tuesday, which will likely set off a firestorm of updates. The hot AI summer is around the corner, so we'll get you caught up and prepared for what's coming next. Newsletter: Sign up for our free daily newsletterMore on this Episode: Episode PageToday's Episode on LinkedIn: Thoughts on this? Join the convo on LinkedIn and connect with other AI leaders.Upcoming Episodes: Check out the upcoming Everyday AI Livestream lineupWebsite: YourEverydayAI.comEmail The Show: info@youreverydayai.comConnect with Jordan on LinkedInTopics Covered in This Episode:OpenAI Codex Remote Control Feature LaunchCerebras AI IPO Debut & Market ImpactGoogle Book Laptops with Gemini IntelligenceAnthropic Programmatic Usage Policy BacklashUS-China Talks on AI Safety GuardrailsOpenAI Considers Legal Action Against AppleGoogle IO 2024: Gemini 3.2 and Spark LeaksAI Industry Partner Updates: AWS, PWC, MetaTimestamps:00:00 OpenAI adds remote control feature03:46 Codex remote features for mobile08:54 Cerebras IPO and tech market resurgence12:41 Introducing the Google Book laptops13:55 Google books hardware partners and AI competition17:09 Changes to agent SDK credits21:15 Developers react to pricing changes25:25 US-China AI negotiations overview28:04 Concerns about AI and security34:03 Anticipating Google IO announcements36:37 Gemini Omni leaks and speculations40:07 Recent AI advancements and industry moves42:50 Introducing Firefly AI AssistantKeywords: AI IPO, Cerebras Systems, Cerebras IPO, AI chipmaker, $95 billion market cap, wafer scale AI chips, OpenAI, Anthropic, Anthropic criticism, Claude subscriptions, programmatic API usage, Claude Dispatch, Claude CoWork, AI subscription limits, OpenClaw, autonomous AI agents, ChatGPT mobile app, Codex remote control, Gemini Intelligence, Google I/O, Google Book laptop, Android XR glasses, Gemini Spark, Gemini 3.2, Google AI assistant, multimodal AI models, persistent AI agent, Apple Intelligence, Siri integration, OpenAI vs Apple, class action lawsuit, ChatGPT paid subscription, Google-Microsoft-Amazon AI rivalry, AWS partnership, developer backlash, AI agent SDK, AI regulatory talks, US-China AI relations, model distillation, data center, AI cybersecurity, Daybreak, personal finance AI, Meta Muse Spark, Thinking Machines Lab, multimodal human collaboration, AI widget, custom widget creation, agent memory, cloud agent, real-time AI, verticalized AI, legal AI, finance AI, small business AI.Send Everyday AI and Jordan a text message. (We can't reply back unless you leave contact info) Start Here ▶️Not sure where to start when it comes to AI? Start with our Start Here Series. You can listen to the first drop -- Episode 691 -- or get free access to our Inner Cricle community and all episodes: StartHereSeries.com Also, here's a link to the entire series on a Spotify playlist. 

AWS Morning Brief for the week of May 18th , with Corey Quinn. Links:Announcing general availability of Amazon EC2 M3 Ultra Mac instancesAmazon EventBridge Scheduler adds 619 new SDK API actions, including Lambda Managed InstancesAmazon Redshift launches RG instances powered by AWS GravitonAmazon Route 53 Domains adds support for 34 new Top Level Domains including .app, .dev, and .health.ENA Express for Amazon EC2 instances now supports traffic between Availability ZonesStreaming CloudWatch metrics to VPC-based OpenTelemetry collectors using LambdaHow HotelTrader cut inter-AZ cost 95% and latency by 49% with Valkey GLIDE on Amazon ElastiCacheIntroducing Claude Platform on AWS: Anthropic's native platform, through your AWS accountAmazon CloudFront Premium flat-rate pricing plan now supports higher, configurable usage allowancesScalable cross-cloud data migration to Amazon S3 with distributed rcloneDirty Frag and other issues in Amazon Linux kernelsCVE-2026-8178 - Remote Code Execution via Unsafe Class Loading in Amazon Redshift JDBC DriverFragnesia Local Privilege Escalation report via ESP-in-TCP in the Linux KernelOngoing updates on Copy.fail and variantsIssue with Amazon SageMaker Python SDK - Model artifact integrity verification issues (CVE-2026-8596 &: CVE-2026-8597)

Our 245th episode with a summary and discussion of last week's big AI news!Recorded on 05/13/2026Hosted by Andrey Kurenkov and Jeremie HarrisFeel free to email us your questions and feedback at andreyvkurenkov@gmail.com and/or hello@gladstone.aiRead out our text newsletter and comment on the podcast at https://lastweekin.ai/In this episode:OpenAI released new voice intelligence API features including GPT Realtime 2 (GPT-5-powered) plus realtime translation and Whisper transcription, emphasizing the latency–reasoning tradeoff, larger context, and new guardrails amid fraud risks.Thinking Machines previewed a low-latency, full‑duplex conversational system with a two-model architecture and custom inference stack, reporting strong interactivity benchmark results but without public access or third‑party validation yet.Anthropic pushed further into vertical products with Claude for Legal and deeper AWS availability, while ongoing ecosystem tension grows as platform model providers compete with application-layer companies.Safety, policy, and research updates included OpenAI's self-harm trusted contact feature, Anthropic work on reducing agent misalignment by training ethical “why” reasoning, OpenAI's investigation of accidental chain-of-thought grading in RL, and Meta horizon eval updates showing benchmarking limits for long task horizons.Timestamps:(00:00:10) Intro / Banter(00:01:35) Response to listener comments(00:03:27) Sponsor Break Tools & Apps(00:06:27) OpenAI launches new voice intelligence features in its API | TechCrunch(00:15:52) Thinking Machines drops a new, highly responsive model designed for humanlike interactions in real time - SiliconANGLE(00:27:49) Claude For Legal Launches, May Reshape the Legal Tech World – Artificial Lawyer(00:40:27) Threads tests a Meta AI integration that works similarly to Grok | TechCrunch(00:43:08) Google brings agentic AI and vibe-coded widgets to Android | TechCrunch(00:45:33) Google updates AI search to include quotes from Reddit and other sources | TechCrunch Applications & Business(00:47:38) Sam Altman was winning on the stand, but it might not be enough | The Verge(00:55:04) Nvidia C.E.O. Jensen Huang Hitches Ride With Trump to China After Last-Minute Invite - The New York Times(00:58:40) AWS expands Anthropic partnership with Claude Platform launch(01:01:13) Chinese grey market sells Claude API access at 90% off by using stolen credentials, model substitution, and harvesting users' prompts and outputs for resale as AI training data — 'transfer stations' operate through proxy networks that harvest user data(01:06:43) DeepMind Spinout Isomorphic Labs Raises $2.1 Billion to Design Drugs With AI - BloombergProjects & Open Source(01:09:04) Petri: Anthropic Hands Its Alignment Toolbox to Meridian Labs with 3.0 Update(01:12:25) Daybreak': OpenAI's Answer to Anthropic's Project Glasswing Has ArrivedPolicy & Safety(01:14:04) Teaching Claude why(01:21:45) Import AI 455: Automating AI Research(01:28:31) ChatGPT's New Safety Feature Could Alert 'Trusted Contact' to Risk of Self-Harm - CNET(01:30:09) Investigating the consequences of accidentally grading CoT during RL(01:34:46) Natural Language Autoencoders criticism(01:39:15) Review of the "Risks from automated R&D" section in the Anthropic Risk Report (February 2026)Synthetic Media & Art(01:43:39) George Clooney, Tom Hanks, and Meryl Streep back new ‘Human Consent Standard' for AI licensing | The VergeResearch & Advancements(01:45:10) METR says Claude Mythos is testing the limits of AI evaluation – Startup FortuneSee Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Cerebras just had one of the biggest tech IPO debuts in years. The AI chip company listed at $185, opened at $350, and closed up 68% at $311 — giving it a roughly $95 billion valuation and making it the largest U.S. tech IPO since Uber. The AI hardware window is officially open, and the market is now treating non-NVIDIA AI infrastructure as a real public-market category. Anthropic is now sitting at the center of the AI compute economy. After locking in massive infrastructure deals with Google, AWS, and SpaceX-linked compute, the company is also expanding Claude access, rate limits, and deployment through partnerships like its new $200 million Gates Foundation deal across global health, education, and agriculture. The model lab is no longer just competing on chatbot quality — it is becoming an infrastructure-scale AI institution. Cisco shocked the market with a major AI infrastructure guide. Revenue hit $15.84 billion, AI infrastructure orders were lifted from $5 billion to $9 billion for fiscal 2026, and the stock jumped 15%. The same day, Cisco cut 4,000 jobs to fund the pivot. The AI capex boom is no longer just NVIDIA — it is spreading into networking, optics, security, and the second layer of the infrastructure stack. The Trump-Xi Beijing summit ended without a formal AI deal. The U.S. cleared major Chinese companies including Alibaba, Tencent, ByteDance, JD, and Lenovo to buy up to 75,000 NVIDIA H200 chips each, but Beijing paused the orders almost immediately. AI infrastructure is no longer just a company-level decision — it is now a geopolitical bargaining chip. Google disclosed the first confirmed AI-built zero-day exploit used in the wild. The attack targeted a two-factor authentication flow in a widely used open-source system administration tool, and Google says the planned mass exploitation event was stopped before it scaled. The cybersecurity impact of AI is no longer theoretical — AI is now accelerating both offense and defense. Inflation came in hot again. April CPI rose 0.6% month over month, the Fed held rates at 3.50%–3.75%, and markets are now pricing a higher chance of a rate hike than a cut. And yet the S&P 500 still closed above 7,500, while the Nasdaq and Dow also hit major levels. The AI trade is overpowering the macro signal — for now. Runner-up: VoltaGrid raised $1 billion from Blackstone and Halliburton at a $10 billion-plus valuation to build behind-the-meter power systems for AI data centers. Power, not just chips, is becoming one of the biggest constraints in the AI boom. Runner-up: Amazon is reportedly preparing another 14,000 corporate layoffs, which would bring 2026 reductions to roughly 30,000 jobs if confirmed. The AI labor reduction cycle is widening across Big Tech. Runner-up: A former Google engineer was convicted of stealing TPU trade secrets after transferring more than 500 confidential files tied to Google's AI chip architecture and software stack. It is one of the clearest legal templates yet for AI-era intellectual property enforcement. Ricker and Bon #431If you want a prize, send us a DM: http://instagram.com/rickerandbonhttps://www.tiktok.com/@rickerandbonhttps://www.youtube.com/@rickerandbon

Jennifer Langton is an expert in transformational leadership who bridges bold innovation with human impact. As the former Senior Vice President of Player Health and Innovation at the NFL, Jennifer pioneered the league's first injury reduction strategy, achieving a groundbreaking 25% concussion reduction through initiatives like the Digital Athlete, developed in partnership with AWS.Her business acumen is just as impressive: she restored profitability as North America CFO for Atari, and led a revenue-boosting RFP at the NFL that delivered a 220% increase in the league's apparel portfolio.Jennifer's leadership is defined by her CTG Methodology, Connect, Trust, Grow, a framework for navigating high-stakes environments with clarity and heart. An NYU Stern MBA and AWS Women of the Cloud honoree, Jennifer embodies results-driven leadership powered by purpose, people, and progress.SHOW SUMMARYIn this episode of Selling from the Heart Podcast. Larry Levine and Darrell Amy are joined by Jennifer Langton, former SVP of Player Health and Innovation at the NFL, who led the league's first injury-reduction strategy and helped drive a 25% reduction in concussions, including work on the AWS-partnered Digital Athlete. Langton explains her CTG methodology, connect, trust, grow, emphasizing authentic connection to overcome resistance to change, trust built through leadership and data to scale beyond pilots, and growth through iterative wins. She shares how purpose rooted in personal adversity fueled her leadership, how aligning personal mission with organizational priorities creates transformation, and why technology and AI require a “human path” for adoption by building with, not for, stakeholders.KEY TAKEAWAYSAuthentic connection must come before trust , and trust must come before growth. Skip one, and the whole framework breaks.Your personal "why" is your most powerful sales asset. Aligning your purpose to your client's or organization's greatest need creates unstoppable momentum.You don't need to be the expert , you need to connect the experts. Leadership and sales are about asking the right questions and keeping everyone aligned to one mission.Build with people, not for them. Co-creation drives adoption; top-down mandates don't.Data empowers people, it doesn't replace them. The human path to adoption is just as critical as the technical solution.Adversity can become your superpower. Lived experience creates authentic credibility that no credential can replicate.HIGHLIGHT QUOTESIf you don't connect, your stakeholders will resist. If you skip trust, what you're building will never scale beyond a pilot.Technical playbooks don't create change, people do.People follow the version of you that's true.We built with, and not for, them. That's how we empowered them.Every time an injury was predicted or prevented, it was me winning back a piece of myself.ADDITIONAL RESOURCESExplore the secrets of heart-centered leadership and thriving workplace cultures with Culture from the Heart Podcast! Nominate a visionary CEO at www.culturefromtheheart.com!Listen to Larry Levine's Bestselling Book: Selling in a Post-Trust World! Now available on Audible! Transform your sales approach with insights that matter.  Subscribe to The Selling from the Heart Podcast Youtube Channel! Stay updated with the latest episodes and leadership tips: Selling from the Heart YouTubeGet Your Daily Dose of Inspiration:Click Here for Your Daily Dose

This week, we discuss how security gets sold to execs, where agentic coding and security collide, and Cloudflare vs. Datadog's diverging paths. Plus, Coté weighs in on sugar cookies. Watch the YouTube Live Recording of Episode 572 Runner-up Titles Sugar Kingdom Bastard Sugar Choose butter It's just AI now People don't like paying for software It's an exciting time to be writing software Are we going to start funding open source? Speaking of that, but not that, it's totally unrelated We're leaving the table Weird network stuff That box of cables on GitHub Rundown Security Mini Shai-Hulud Is Back: npm Worm Hits over 160 Packages Fedora Hummingbird Linux Brings Agentic Linux to Builders Red Hat Hardened Images Palo Alto Networks to Acquire Portkey to Secure the Rise of AI Agents Mythos finds a curl vulnerability Redis and the Cost of Ambition AI is restructuring the software industry — winners and losers Datadog's stock jumps 31% on crushing earnings beat Cloudflare stock sinks 24% after earnings as company cuts 1,100 employees Linear increases workforce Relevant to your Interests Laws, anecdotes, idioms, and other shit people say - cote.pizza The smart lock standard that could replace your keys is finally here dirtyfrag/README.md at master · V4bel/dirtyfrag · GitHub Red Hat Summit Newsroom Finally, texts between Android and iPhone users can be end-to-end encrypted Your Container Is Not a Sandbox OpenAI launches the OpenAI Deployment Company Corporate Card Startup Ramp Raising Funds at $40 Billion Valuation Cyberattack shutters Canvas learning platform for schools across the U.S. AWS warns of EC2 'impairment' as power loss hits notorious US-EAST-1 region AI and DevOps Maturity Anthropic raises Claude Code usage limits, credits new deal with SpaceX Announcing Agent Toolkit for AWS He's not wrong, but what can they do? How are those Microsoft foundation models going? Sponsors WebRTC.ventures – Real-time communication & Voice AI integration Conferences WeAreDevelopers Europe, July 8-10, 2026 Berlin, Coté speaking. DevOpsDays Graz, Sept 4-5, 2026 DevOpsDays Rockies, Sept. 22 – 23, 2026, Discount Code: 26DODSWEDEFTALK WeAreDevelopers NA, Sept 23-25, 2026, Discount Code: DEVPOD26 DevOpsDays Dallas, Sept 28-29, 2026 DevOpsDays Vilnius, Sep 30 - Oct 1. 2006 DevOpsDays Istanbul, October 24th, 2026 - Coté keynoting. VMware User Groups (VMUGs): Dallas (June 9-11, 2026) Orlando (October 20-22, 2026) SDT News & Community Join our Slack community Email the show: questions@softwaredefinedtalk.com Free stickers: Email your address to stickers@softwaredefinedtalk.com Follow us on social media: Twitter, Threads, Mastodon, LinkedIn, BlueSky Watch us on: Twitch, YouTube, Instagram, TikTok Book offer: Use code SDT for $20 off "Digital WTF" by Coté Sponsor the show Sponsor more podcasts with Failover Media Recommendations Brandon: Xcode MCP Matt: whatcable Coté: Shogun.

In this episode, Corey Quinn sits down with AWS Senior Principal Engineer David Yanacek to explore the next evolution of DevOps.After two decades of building systems to reduce operational pain, David shares how AWS's new DevOps Agent is pushing automation to a whole new level, autonomously diagnosing incidents, suggesting fixes, and proactively improving systems before engineers even log in.From pager overload to autonomous remediation, this conversation is a glimpse into a world where software isn't the bottleneck anymore, operations are evolving into something entirely new.If you care about DevOps, SRE, platform engineering, or just want fewer 3 a.m. alerts, this episode is for you.Show highlights: (00:00) DevOps Meets Agents(00:13) Welcome and Sponsor Break(01:29) David Yanacek Backstory(02:34) DevOps Roots at Amazon(04:22) DevOps Agent GA Overview(05:32) LLMs MCP and Any Cloud(08:32) Guardrails and Safe Changes(11:47) Beta Results and Consistency(14:13) Troubleshooting Theory and On Demand(17:29) Future of DevOps and ClosingAbout David: David Yanacek is a Senior Principal Engineer at AWS and a lead advisor on the Agentic AI team. His current work focuses on Kiro, Amazon Bedrock AgentCore, and AWS's operational agents, where he helps shape the future of intelligent, autonomous systems.Over a 19+ year career at Amazon and AWS, David has been at the forefront of building services that simplify life for developers and operators. His experience spans serverless, DevOps, and CloudOps, including launching Amazon DynamoDB and AWS IoT Core, and contributing to the direction of cornerstone services like AWS Lambda, Amazon API Gateway, and Amazon CloudWatch.David also served as the lead publisher for the Amazon Builders' Library, helping customers apply Amazon's hard-earned architectural and operational lessons to their own systems.Outside of engineering, David plays the French horn in a local Seattle ensemble.Links:LinkedIn: https://www.linkedin.com/in/david-yanacek/Website: https://aws.amazon.com/builders-library/authors/david-yanacek/Sponsored by: duckbillhq.com

Podcast del programa Imagen Empresarial transmitido originalmente el 14 de mayo del 2026. Conduce Rodrigo Pacheco Los entrevistados de hoy: Entrevista: Helmuth Cepeda, líder del Cloud Sales Center Organization región Latinoamérica de AWS (en inglés lo pusieron como: Head of LATAM Cloud Sales Center Organization) Tema: Aceleración de la adopción digital Entrevista: Ernesto Piedras, CEO de The CIU (The Competitive Intelligence Unit) Tema: Registro de usuarios de líneas telefónicas y SIMs

Open Source is giving AI a real boost, making it easier and faster for organisations to build and experiment with new ideas. As adoption grows, these open ecosystems are helping businesses move quicker, stay flexible, and unlock value with more confidence.This week, Dave, Esmee, and Rob are joined by Richard Harmon, VP & Global Head of Financial Services at Red Hat to explore how Open Source is shaping AI, from mainframes to Kubernetes, and from regulation and sovereignty to a future of AI agents writing code. TLDR00:25 – Introduction00:52 – Hangout: Deep democracy training and “what instrument are you?”03:19 – Dig in: Open‑source culture and AI, do they complement each other?10:02 – Conversation with Richard Harmon51:12 – Sitting in the chair and trying to keep up with AI GuestRichard Harmon: https://www.linkedin.com/in/richardlaurenharmon/ HostsDave Chapman:  https://www.linkedin.com/in/chapmandr/Esmee van de Giessen:  https://www.linkedin.com/in/esmeevandegiessen/Rob Kernahan:  https://www.linkedin.com/in/rob-kernahan/ ProductionMarcel van der Burg:  https://www.linkedin.com/in/marcel-vd-burg/Dave Chapman:  https://www.linkedin.com/in/chapmandr/ SoundBen Corbett:  https://www.linkedin.com/in/ben-corbett-3b6a11135/Louis Corbett:   https://www.linkedin.com/in/louis-corbett-087250264/ 'Realities Remixed' is an original podcast from Capgemini

Don DeCorte spent 46 years in resistance welding, including 31 at Roman Manufacturing, and now teaches the AWS Certified Resistance Welding Technician (CRWT) certification through his consulting company DTS Technical Services. He sits down with Jason to pull the curtain back on the welding process most arc guys never think about — but interact with constantly. From the 1,300+ resistance-welded products hiding inside your local Home Depot, to the flash welds on every commercial jet's front landing gear, to the butt-welded steel wheels under every 18-wheeler and state trooper car, Don makes the case that resistance welding is everywhere — you just can't see it. We cover the four core processes (spot, seam, projection, upset), the physics behind Force, Current, and Time, why aluminum welding took off thanks to chromate treatments and Elon Musk, the codes and standards that govern it (C1.1, D8, D17.2, J1, J6), and what it takes to earn your CRWT. Don also shares the story of how an $8 roast beef dinner in Detroit in 1980 turned into a lifetime with AWS — and a friendship with Amos Winsan that changed his career.    

Ned and Kyler are joined by Dr. Cat Hicks to discuss her new book “The Psychology of Software Teams.” They talk about software development from a psychological perspective, including how negative stereotypes of developers can lead to them being treated simply as “brains in jars” in toxic environments. They also point out the pitfalls of... Read more »

Ned and Kyler are joined by Dr. Cat Hicks to discuss her new book “The Psychology of Software Teams.” They talk about software development from a psychological perspective, including how negative stereotypes of developers can lead to them being treated simply as “brains in jars” in toxic environments. They also point out the pitfalls of... Read more »

SUMMARY: RIP Reasoning, hello The Enterprise AI Show. We do a point-in-time analysis of the AI market for May 2026, across 11 major categories. SHOW: 1026SHOW TRANSCRIPT: The Enterprise AI Show #1027 TranscriptSHOW SPONSORS:Nasuni - Activate your data for AI and request a demoShareGate - ShareGate Protect. Microsoft 365 Governance, we got this!SHOW NOTES:Reviewing the Major AI Vendors FEEDBACK?Email: show @ the enterprise ai show dot comeBluesky: @EntAIShow.bsky.socialTwitter/X: @TheEntAIShowInstagram: @TheEntAIShow

Incorruptible with Eric RiesWhat if the companies that last the longest are the ones building enough trust that people want to keep participating in them? That's the idea behind this conversation with Eric Ries — entrepreneur, author of The Lean Startup, and now Incorruptible.Through stories such as Volvo giving away the seatbelt patent, Tony's Chocolonely opening its ethical supply chain to competitors, and Mary Parker Follett's idea of the “invisible leader,” we explore how organizations create lasting advantage through trust, shared purpose, and systems that hold together as companies scale.We also unpack why so many businesses drift toward short-term extraction, what leaders misunderstand about organizational health, and why AI is exposing deeper weaknesses in how companies operate.If you're building a company and questioning whether business-as-usual is still the right operating system, this conversation is for you.Key TakeawaysEthical business can outperform extractive business models: Eric argues that mission-driven companies are not sacrificing performance. In many cases, trust, alignment, and long-term thinking create stronger economic outcomes.Volvo used open ecosystems as strategy: Giving away the three-point seat belt patent helped establish safety as an industry standard while positioning Volvo as the global leader in automotive safety.Tony's Chocolonely treats its mission as infrastructure: The company's goal is not simply selling chocolate. Its mission is to eliminate child slavery from the cacao supply chain through systems that competitors can also adopt.Positive externalities can strengthen competitive advantage: Eric explains how companies can create value by improving the broader ecosystem around them instead of maximizing short-term value extraction.Organizations are shaped by invisible leadership: Mary Parker Follett's idea of the “invisible leader” shows how shared purpose influences decisions when executives are not in the room.Organizational health cannot be commanded: Leaders can issue instructions, but trust, accountability, and commitment have to be cultivated through systems and behavior over time.Additional InsightsThe current business narrative rewards extraction over durability: Barry and Eric discuss how modern startup culture often glorifies hyper-efficient solo founders, aggressive cost-cutting, and short-term returns while ignoring long-term organizational health.AI is amplifying leadership weaknesses, not solving them: As companies use AI to accelerate decision-making and productivity, leaders are being forced to confront whether their systems actually create clarity, trust, and aligned behavior.Mission statements are easy. Mission transmission is harder: Eric argues that values only matter when they shape real decisions, incentives, hiring, product tradeoffs, and customer experience.Open systems can expand both impact and market position: From Linux and Git to Netflix influencing AWS through open source tooling, the episode explores how sharing infrastructure can strengthen an ecosystem while also benefiting the originating company.Profit becomes dangerous when it ignores externalities: Eric explains how traditional profit models often fail to account for long-term brand damage, human cost, environmental impact, and deferred liabilities.Episode Highlights00:00 – Episode RecapEric Ries explains why organizations are living systems, not machines to be controlled. Leaders can command action, but organizational health has to be cultivated through purpose, trust, and the systems people use when no one is watching.00:57 – Barry's Opening ReflectionBarry connects AI, leadership, and decision-making systems before introducing Eric's new book, Incorruptible.02:14 – Guest Introduction: Eric RiesBarry introduces Eric Ries, entrepreneur, author of The Lean Startup, and author of Incorruptible, framing the conversation around ethical business as a path to long-term prosperity.04:34 – Researching the Stories Behind IncorruptibleEric shares how much research went into the book, including the challenge of finding stories that were not just interesting, but genuinely useful for leaders.08:07 – Volvo and the “Seatbelt Heist”Eric breaks down how Volvo's decision to give away the three-point seat belt patent created a prosperity cascade that reshaped the industry while strengthening Volvo's long-term brand position around safety.16:45 – Open Source as StrategyBarry connects Volvo's story to Netflix and cloud computing, where open sourcing internal tools helped shape the direction of the broader ecosystem.17:57 – Positive Externalities as Business StrategyEric explains why companies often overlook opportunities to create value by improving the wider system around them.20:18 – Tony's Chocolonely and Slave-Free ChocolateEric tells the story of how a Dutch journalist turned frustration over child labor in cacao production into a fast-growing chocolate company with a much larger mission.24:03 – Mission Beyond the ProductTony's mission is not simply making chocolate. The business exists to eliminate child slavery from the cacao supply chain and align economics with ethical sourcing.26:00 – Tony's Open ChainEric explains how Tony's opened its ethical supply chain to competitors while requiring them to commit to the same standards across all their chocolate products.30:32 – The False Tradeoff Between Ethics and PerformanceEric challenges the business-school assumption that companies must choose between mission and profit, arguing that the data often shows the opposite.33:23 – Redefining ProfitBarry and Eric discuss why traditional definitions of profit often ignore externalities, deferred liabilities, human cost, and long-term brand damage.39:19 – The Myth of the Solo FounderBarry pushes back on modern founder mythology and explains why anything built to last depends on systems, teams, and shared ownership.40:36 – Mary Parker Follett and the Invisible LeaderEric introduces management thinker Mary Parker Follett and explains why her ideas about shared purpose and distributed authority were decades ahead of their time.45:00 – What Guides Decisions When Leaders Aren't PresentEric explores Follett's idea of the invisible leader: the shared sense of purpose that influences behavior when no executive is in the room.49:35 – Organizations as Living SystemsEric compares organizations to emergent intelligence systems like ant colonies or the human body, arguing that leaders can cultivate organizational health but cannot directly command it.52:30 – Closing ReflectionsBarry and Eric reflect on the need for new business models that prioritize trust, mission alignment, and long-term value creation over extraction.Useful ResourcesEric Ries — IncorruptibleEric Ries — The Lean StartupEric Ries on LinkedIn - https://www.linkedin.com/in/eries/ The Eric Ries Show YouTube - https://www.youtube.com/@theericriesshow Barry O'Reilly — Artificial Organizations - https://geni.us/artificialorgsFAQsQ1: What is Eric Ries' book Incorruptible about?Incorruptible explores how leaders can build companies that stay aligned with their mission as they grow. Eric looks at stories from business history to show how purpose, governance, incentives, and ownership shape whether companies create long-term value or lose their way.Q2: Why does Eric Ries use Volvo as an example?Volvo's three-point seat belt story shows how a company can create value by spreading a mission beyond its own products. By making the patent available to others, Volvo helped establish safety as an industry standard while strengthening its own reputation for safety.Q3: What is Tony's Chocolonely trying to change?Tony's Chocolonely is trying to eliminate child slavery from the cacao supply chain. The company sells chocolate, but the deeper mechanism is building an ethical supply chain that other companies can use through Tony's Open Chain.Q4: What does Mary Parker Follett mean by the invisible leader?The invisible leader is the shared purpose that guides people's decisions when no formal leader is present. It is what shapes behavior in everyday moments, such as how teams handle quality issues, customer problems, or ethical tradeoffs.Q5: Can leaders...

AWS Morning Brief for the week of May 11th , with Corey Quinn. Links:Announcing Agent Toolkit for AWS — help AI coding agents build effectively on AWSAmazon CloudFront Announces WebSocket Support for VPC OriginsAmazon EventBridge supports data plane logging to AWS CloudTrailAWS IAM now provides higher maximum quotas for roles, role trust policies, instance profiles, managed policies, and identity providersAWS Marketplace now supports programmatic procurement with Agreements APIThe AWS MCP Server is now generally availableAnnouncing Valkey 9.0 for Amazon ElastiCacheQuery billion-scale vectors with SQL: Integrating Amazon S3 Vectors and Aurora PostgreSQLYou Wanted to Become AI-Native, and All You Got Was a Lousy FoundationCVE-2026-7461 - OS Command Injection in Amazon ECS Agent via FSx Windows File Server Volume CredentialsCVE-2026-7791 - Local Privilege Escalation via TOCTOU Race Condition in Amazon WorkSpaces Skylight AgentCVE-2026-31431

The episode reveals a structural shift in the technology landscape: artificial intelligence is becoming a new layer of managed consumption, with measurable impact on infrastructure, contract terms, and operational accountability. This shift is illustrated by leading technology platforms explicitly metering AI usage through compute tokens, storage footprints, and local model deployments. Companies such as Alphabet, Amazon, Microsoft, and Google are integrating AI not only as features but as quantifiable workload layers, leading to economic and governance questions regarding who controls consumption and who assumes the risk of overage or misuse. The most consequential development discussed is the rapid, capital-intensive scaling of AI infrastructure by leading hyperscalers. Alphabet raised its 2026 capital expenditure guidance to a possible $190 billion; Amazon's AWS revenues rose 28% year-over-year to $37.6 billion, with quarterly capital expenditures reaching $44.2 billion— both moves directly tied to AI infrastructure investments. At the same time, endpoint and storage vendors, such as Apple and Backblaze, are experiencing elevated demand from AI workloads. On the software side, companies like Anthropic are explicitly raising API rate limits and deploying features to formalize the measurement and orchestration of AI-driven processes. Supporting developments include the migration of management and control functions into enterprise platforms and endpoint environments. Microsoft Agent 365 is now broadly available, offering admins centralized policy controls over AI agents across cloud and local machines, with integration into Intune for granular restriction and monitoring. Google's Chrome browser now automatically downloads 4GB Gemini Nano models to support local AI functions, raising new operational considerations around storage, policy management, and user approval. These developments anchor the thesis that AI is no longer a passive toolset but a consumption and policy domain that requires active oversight. Operationally, MSPs and IT service providers face heightened exposure to contract and governance risk. The presence of invisible AI consumption— in the form of storage expansion, token overages, unauthorized agent actions, or degraded endpoint performance— requires explicit clauses in client agreements and new monitoring capabilities. Providers unable to demonstrate control over AI usage, policy enforcement, and exception handling may inherit both support burdens and unresolved liability. The practical implication is clear: future margins and contract viability will increasingly depend on the ability to meter, document, and govern AI-related activities, rather than simply enabling client access. 00:00 AI Infrastructure Surge  04:17 Control Layer Wins 06:41 MSP Liability Shift 10:50 Why Do We Care?  Supported by:  ScalePad CometBackup Moovila 

David covers three Friday stories: Coinbase's hours-long outage on the back of an AWS cooling failure, the data on whether prediction markets are actually beating memecoins, and the dueling Solana + Google Cloud / AWS + Coinbase + Stripe agentic commerce announcements. TIMESTAMPS: (00:00) Intro (01:23) Coinbase AWS Outage (07:20) Nexo Ad (07:55) Prediction Markets, Memecoins, and HIP-4 (15:58) Nexo Ad (16:51) Prediction Markets, Memecoins, and HIP-4 (Cont.) (19:15) Agentic Commerce Meta FOLLOW THE SHOW › David — https://x.com/dcanellis › The Breakdown — https://x.com/TheBreakdownBW SPONSORS › NEXO Nexo is the premier digital wealth platform. Receive interest on your crypto, borrow against it without selling, and trade a range of assets. Now available in the U.S with 30 days of exclusive privileges. Get started at http://nexo.com/breakdown Get top market insights and the latest in crypto news. Subscribe to the Blockworks Daily Newsletter: https://blockworks.co/newsletter/ DISCLAIMER As always, remember this podcast is for informational purposes only, and any views expressed by anyone on the show are solely their opinions, not financial advice.

Elon Musk spent a lot of his week trying to explain how OpenAI wronged him — but mostly just seemed to annoy everyone else in the courtroom. Nilay and David discuss Musk's testimony in the OpenAI trial, and what it might mean for the trial going forward. After that, the Hype Desk gang recommends a couple of new things to watch, before the hosts chat about the week's new gadgets, including the Steam Controller and the dual-screen Zephyrus Duo laptop. Finally, in the lightning round, Brendan Carr picks a fight over Jimmy Kimmel again, Netflix buys into the clip economy, and Taylor Swift fights the AI. Further reading: Elon Musk confirms xAI used OpenAI's models to train Grok All the evidence unveiled so far in Musk v. Altman  Elon Musk appeared more petty than prepared  Elon Musk tells the jury that all he wants to do is save humanity  Elon Musk's worst enemy in court is Elon Musk  Jury selection in Musk v. Altman: ‘People don't like him'  Microsoft and OpenAI's famed AGI agreement is dead  Now that OpenAI's Microsoft exclusivity is over, it has a new deal with Amazon and AWS. ChatGPT downloads are slowing — and may cause problems for OpenAI's IPO Meta lost 20 million users last quarter The more young people use AI, the more they hate it Google Search queries hit an ‘all time high' last quarter Valve's new Steam Controller isn't perfect, but I'm buying one anyway  Valve launches the Steam Controller without the Steam Machine  Why the Steam Controller is (and isn't) a big deal  Samsung's first smart glasses have leaked  Is this Samsung's upcoming wide foldable?  The long rumored foldable iPad may never see the light of day.  The new Razr Ultra is still the best-looking phone out there  Asus ROG Zephyrus Duo (2026) review: 2 screens 2 furious Trump demands ABC fire Jimmy Kimmel The FCC is going after the broadcast licenses of Disney-owned ABC stations  Former FCC staffers agree: Brendan Carr needs to be stopped  The FCC is saving Amazon's Eero and Leo routers from its ban, too.  Taylor Swift deepfakes are pushing scams on TikTok  Here's what Netflix's new vertical video feed is like Subscribe to The Verge for unlimited access to theverge.com, subscriber-exclusive newsletters, and our ad-free podcast feed.We love hearing from you! Email your questions and thoughts to vergecast@theverge.com or call us at 866-VERGE11. (Timestamps are approximate.) 00:00:00 Intro 00:03:00 Elon vs OpenAI Overview 00:07:00 Jury Selection Drama 00:12:00 Elon's Testimony Begins 00:23:00 Trial Implications 00:26:00 Microsoft and OpenAI Split 00:30:00 The AWS Deal 00:32:00 Consumer AI Backlash 00:41:00 AI Powered Ad Targeting 00:44:00 Enterprise AI Success Story 00:45:00 Widow's Bay Recommendation 00:46:00 Apple TV Quality Content 00:48:00 Coyote vs Acme 00:55:00 Steam Controller Review 00:57:00 Universal Remote Theory 01:01:00 Smart Glasses Problem 01:05:00 Wide Foldable Phones 01:09:00 Motorola Razr Ultra 01:12:00 ASUS ROG Zephyrus Duo 01:17:00 Brendan Carr is a Dummy 01:18:00 Jimmy Kimmel Controversy 01:25:00 FCC Open Meeting Response 01:26:00 News Distortion Rule Lawsuit 01:29:00 Router Ban Update 01:33:00 Taylor Swift Trademark Strategy 01:37:00 YouTube Likeness Protection 01:41:00 Netflix Clips Feature 01:44:00 The Clip Economy Shift 01:46:00 Streaming Services vs TikTok 01:49:00 Show Wrap Up Learn more about your ad choices. Visit podcastchoices.com/adchoices