Podcasts about Apis

Needle-Free Peptides, US Manufacturing, BPC-157, Thymosin Alpha-1, GLP-1s, Microneedle Patches, and How to Avoid Contaminated Peptides Peptides are one of the most powerful tools in biohacking and anti-aging medicine, and until now, most people couldn't access them safely, legally, or without a needle. This episode changes that. -Watch this episode on YouTube for the full video experience: https://www.youtube.com/@DaveAspreyBPR -Go to Aminoinnovations.com and use “asprey20” for a discount through the next 7 days Host Dave Asprey sits down with Justin Kirkland, a longevity medicine expert with over 30 years in drug development and pharmaceutical innovation. Kirkland holds multiple drug synthesis and formulation patents, has founded multiple pharmaceutical companies, and is one of the few people in the world manufacturing peptides entirely on US soil, controlling every step of the synthesis process from raw amino acids to finished product. If you want to understand what is really inside your peptides and why it matters for your longevity and human performance, he is the person to listen to. Dave and Justin go deep on why most peptides on the gray market contain dangerous residual compounds that can spike liver enzymes and cause real harm, why Chinese-sourced APIs are not always what they claim to be, and how a new generation of needle-free delivery systems including microneedle patches and auto-injectors is making peptide therapy accessible to anyone serious about longevity and human performance. They also cover how AI and functional medicine are converging to make peptide protocols personalized based on genetics and microbiome status, why the thymus gland is one of the most overlooked anti-aging targets in the body, and what the suppression of peptide research reveals about who really controls your access to health tools. You Will Learn: Why many gray market peptides contain toxic residual acids that damage the liver and how to identify clean products How microneedle patches and auto-injectors are replacing traditional injections for peptide delivery Which peptides are most effective for longevity, immune system repair, and human performance including BPC-157, Thymosin Alpha-1, and growth hormone secretagogues Why your genetics and gut microbiome determine whether a peptide will work for you at all How the thymus gland controls your immune system and why it disappears by your mid-20s What the suppression of peptide research tells you about Big Pharma's control over your supplement and nootropics access Why US-manufactured peptides represent a new standard for safety and quality in biohacking How AI is transforming personalized peptide protocols in functional medicine Which peptides are overhyped and which ones actually move the needle on anti-aging and recovery How to store, mix, and dose peptides correctly to avoid the mistakes most people using them are making right now Thank you to our sponsors! - Danger Coffee | Grab yours at DangerCoffee.comand use code DAVEPOD at checkout for 15% off. - The One Device | Use code DAVE for $10 off at theonedevice.com/dave - Fatty15 is on a mission to support Healthy Aging for All, including all ages and stages of life. You can get an additional 15% off their 90-day subscription Starter Kit by going to fatty15.com DAVE and using code DAVE at checkout. - ENERGYbits | If you want a simpler, smarter way to support your body… this is it. Head to ENERGYbits.com and use code ASPREY for 20% off your order. Dave Asprey is a four-time New York Times bestselling author, founder of Bulletproof Coffee, and the father of biohacking. With over 1,000 interviews and 1 million monthly listeners, The Human Upgrade brings you the knowledge to take control of your biology, extend your longevity, and optimize every system in your body and mind. Each episode delivers cutting-edge insights inhealth, performance, neuroscience, supplements, nutrition, biohacking, emotional intelligence, and conscious living. New episodes are released every Tuesday, Thursday, Friday, and Sunday (BONUS). Dave asks the questions no one else will and gives you real tools to become stronger, smarter, and more resilient. Keywords: Justin Kirkland, peptides, needle-free peptides, microneedle patch, BPC-157, Thymosin Alpha-1, ipamorelin, CJC-1295, PT-141, KPV peptide, Dihexa, growth hormone secretagogue, peptide purity, TFA contamination, gray market peptides, US manufactured peptides, oral peptides, transdermal delivery, thymus gland, anti-aging, biohacking, longevity, functional medicine, peptide auto-injector, compounding pharmacy Resources: • Go to Aminoinnovations.com and use “asprey20” for a discount through the next 7 days • Get My 2026 Clean Nicotine Roadmap | Enroll for free at https://daveasprey.com/2026-clean-nicotine-roadmap/ • Dave Asprey's Latest News | Go to https://daveasprey.com/ to join Inside Track today. • Danger Coffee: https://dangercoffee.com/discount/dave15 • My Daily Supplements: SuppGrade Labs (15% Off) • Favorite Blue Light Blocking Glasses: TrueDark (15% Off) • Dave Asprey's BEYOND Conference: https://beyondconference.com • Dave Asprey's New Book – Heavily Meditated: https://daveasprey.com/heavily-meditated • Join My Substack (Live Access To Podcast Recordings): https://substack.daveasprey.com/ • Upgrade Labs: https://upgradelabs.com Timestamps: 00:00 – Intro & Guest Welcome 01:55 – Censorship & Platform Bans 06:20 – Peptide Science & Bioavailability 07:20 – Delivery Methods 14:30 – Supply Chain & US Manufacturing 17:01 – Manufacturing Risks & Contamination 24:43 – Peptide Stacks 28:41 – Immune Peptides & Thymus 30:57 – Overhyped Peptides 41:00 – Alternative Delivery (Patches, Nasal, Rectal) 47:25 – Side Effects & Risk 50:30 – Mixing & Storage Tips 54:05 – Wrap-Up & Where to Buy See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

In this episode of The Broadband Bunch, host Pete Pizzutillo welcomes Rhyan Neble for a conversation about the evolution of artificial intelligence, agentic frameworks, and what these technologies mean for broadband operators. Drawing on decades of experience building telecom networks, OSS/BSS platforms, and software solutions, Rhyan explains how AI has progressed from a simple assistant to a true workforce multiplier capable of accelerating software development, automating complex workflows, and helping organizations solve problems that once required large teams and months of effort. Rhyan also shares practical advice for broadband providers looking to prepare for the next wave of AI adoption. Topics include open APIs, operational runbooks, AI agents as employee assistants, governance frameworks, security considerations, and the growing importance of data accessibility. They discuss both the opportunities and risks of AI, offering a balanced look at how operators can use these tools to improve efficiency, streamline reporting, surface operational insights, and empower employees while maintaining human oversight.

What happens when the weakest link in your technology supply chain becomes the entry point for a national security incident? In this episode of Tech Talks Daily, I welcome back Haydn Brooks, CEO and founder of Risk Ledger, to discuss why supply chain security has moved from an IT concern to a boardroom and government priority. As organizations race to adopt AI, connect more systems, and depend on increasingly complex ecosystems of vendors, partners, cloud providers, and third-party services, the attack surface continues to expand in ways many businesses still struggle to understand. Haydn explains why supply chains remain one of the largest blind spots in cybersecurity, despite years of warnings and a growing list of high-profile incidents. We explore how attackers increasingly target smaller suppliers that lack the resources and expertise of larger enterprises, using them as stepping stones to reach critical infrastructure, government agencies, and major corporations. The conversation also examines how AI is reshaping the risk equation. As organizations rapidly integrate AI tools, APIs, and third-party models into existing technology stacks, many are creating new forms of concentration risk. What happens when multiple services rely on the same AI provider? And how can businesses maintain visibility over technology dependencies that are constantly evolving? Haydn shares his perspective on why collaboration and information sharing have become far more common across the cybersecurity community, and why security leaders are beginning to recognize that defending against modern threats requires collective action rather than isolated efforts. We also discuss accountability, resilience, and why organizations must move beyond simply identifying risk and develop the ability to understand the impact of incidents when they occur. Along the way, Haydn offers practical advice for security leaders, explains why now is the time to reassess supply chain security strategies, and shares insights into Risk Ledger's international expansion as the company grows its presence in the United States. As AI accelerates innovation and organizations become increasingly interconnected, are businesses truly prepared for the risks that come with that progress? And could an overlooked supplier become the starting point for the next major cybersecurity crisis?

In this episode of the Crazy Wisdom Podcast, host Stewart Alsop sits down with returning guest Ekue Kpodar for their third conversation together, covering a wide range of topics at the intersection of technology, geopolitics, and the evolving information age. They dig into Ekue's unconventional setup of running local AI models across roughly 15 computers, the growing case for open source models over closed ones from companies like OpenAI and Anthropic, and how Chinese open source models may be positioned to outcompete Western alternatives on a global scale. The conversation also touches on vibe coding and the democratization of software development, the strategic use of small models for IoT and enterprise applications, the role of Israel and China as dominant players in the information age, and how smaller nations and even individuals may wield outsized power as AI continues to collapse the cost of knowledge work. You can find Ekue Kpodar on X @ekpodar and LinkedIn.Timestamps00:00 Stewart welcomes Ekue for their third episode, diving into vibe coding and AI-driven development changes.05:00 Ekue explains using Claude on Chrome to auto-reply on Skool, burning tokens through screenshots, and Playwright as a more efficient alternative.10:00 Stewart describes his Claude-dependent planning and coding agent system breaking after a model update, prompting him to build his own chatbot.15:00 Small models discussed as critical for IoT, defense, and privacy-focused enterprises building internal APIs instead of routing traffic to OpenAI.20:00 Open source versus closed source debated, with Chinese models gaining global traction while US foundational labs remain expensive and restrictive.25:00 SaaS apocalypse explored as AI commoditizes knowledge work, with Linux and Terraform cited as proof open source still generates wealth.30:00 OpenAI's sci-fi terminator fears explained as the reason they stayed closed source, ultimately handing China a strategic open source advantage.35:00 China's economic dumping strategy applied to AI, potentially displacing US model dominance globally the same way manufacturing was disrupted.40:00 Israel's signals intelligence dominance discussed alongside asymmetric warfare, drones defeating tanks, and information control replacing military muscle.45:00 Global information age rankings debated, Israel leading, US and China tied, France and Poland emerging as sovereign tech players.50:00 Qatar, NVIDIA, and Iran cited as proof that rare resources and technology matter more than population size in the 21st century power landscape.Key Insights1. Running local AI models on a network of affordable computers can be more cost-effective than relying entirely on third-party APIs. By using compressed or smaller open source models locally, developers can handle repetitive or lower-stakes tasks without burning through expensive tokens from providers like Anthropic or OpenAI.2. Small AI models are becoming increasingly important for IoT, defense applications, and companies that do not want to send sensitive data to external providers. Organizations can download open source models, run them on internal servers, and build proprietary APIs around them, creating something like an intranet of specialized small models.3. The value created by AI tools is being redistributed away from traditional SaaS companies toward foundational model providers and individual builders. People are canceling subscriptions to software they once paid hundreds per month for, because AI now allows a single person to build comparable tools themselves.4. Open source technology does not eliminate the ability to profit. Linux and Terraform are both open source yet made their creators wealthy. People will still pay for installation, setup, troubleshooting, and customization even when the underlying software is free.5. China is applying its longstanding manufacturing dumping strategy to artificial intelligence by releasing cheap open source models globally, which threatens to erode US dominance in AI the same way Chinese manufacturing undercut other countries for decades.6. In the information age, the size of a country or institution matters far less than its access to rare resources or advanced technology. Qatar, Israel, and NVIDIA each demonstrate that small populations or headcounts can wield enormous global negotiating power through concentrated technological or resource advantages.7. Asymmetric warfare is redefining military power, with inexpensive drones defeating tanks that cost millions to build. This shifts the advantage toward nations that excel at signals intelligence and information management rather than those with the largest conventional military forces.

The options market is entering a new era. Quantitative strategies are no longer confined to institutional desks — they're being deployed by a new class of self-taught, tech-enabled participants leveraging data analytics, APIs, and algorithmic execution. This panel explores how this shift is reshaping intermediation, liquidity, and education. Moderator: Jermal Chandler, Head of Options Strategy, tastylive Panelists: Jessica Inskip, Director of Investor Research, Stockbroker.com Brent Kochuba, Founder, SpotGamma Steve Quirk, Chief Brokerage Officer, Robinhood This panel is proudly sponsored by Theta Data.

Can Aavegotchi DAO takeover the project, the State of Pixels, and the rise of open source in the agentic era. [00:35] Aavegotchi dev Pixelcraft is one of the OG web3 gaming studios.[05:16] It's looking to hand over control of Aavegotchi to the DAO.[06:28] DAOs haven't been successful for reasons like coordination and authority.[07:25] It's a nice vision, but the reality is Pixelcraft ran out of money. [08:01] By 1st September, the DAO has to have decided what's happening going forward. [09:16] Why “gamey games” are harder to hand over to communities or DAOs.[09:55] State of Pixels. It's sustainable but not growing.11:30 Pixels is now considering adding open-source elements. [12:05] AI significantly changes what community developers can build in blockchain games.[13:50] The emerging pattern is surviving web3 games are moving to APIs, MCPs and agent access.[15:15] Why blockchain and AI fit together culturally and technically.[19:05] Define “game games” versus “non-game games”.[20:49] Why blockchain games should focus less on moment-to-moment fun and more on meta. [23:30] EVE Frontier, MapleStory and Soccerverse as examples of meta-focused web3 games. [25:25] These games have emergent experiences. They don't require constant content updates. [28:30] Don't put things onchain to create value. Put existing value onchain so it can be realized.[32:40] Community-built Soccerverse fantasy football as a sign of where this goes next.[35:05] The first 10 years of blockchain gaming were about discovering what didn't work.[35:40] AI plus blockchain will enable things the traditional games industry won't build.[37:06] Why agents will become native players for blockchain games. [38:20] The future split: Mario-like gameplay games versus agent-filled systemic web3 worlds.

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

Favour Obasi-ike, MBA, MS provides a deep dive into the 2026 scheduling landscape, comparing Cal vs. Calendly. As a digital marketing expert, he explores the benefits of white-labeling, custom APIs, and recurring events. The discussion addresses the polarizing nature of scheduling links in professional networking and offers a guide on using these tools to maintain a long-term business presence. Favour emphasizes that while Calendly is a pioneer, Cal.com's open-source nature provides unique flexibility for modern entrepreneurs. Check Calendly.com vs Cal.com on G2 Reviews here.Who is this for?This content is tailored for entrepreneurs, small business owners, and digital marketers who want to streamline their online booking systems. It's for those deciding between established tools like Calendly and open-source alternatives like Cal.com to manage their time and client interactions more effectively.Key MomentsFavour introduces Cal.com as a powerful alternative to Calendly, highlighting that many features Calendly charges for are free on Cal (03:43). He breaks down a comparison chart, noting that Cal offers custom routing logic, custom domains, and two-way Salesforce/HubSpot synchronization—features often missing or restricted in Calendly (05:36, 08:33).A significant portion of the room debates the etiquette of scheduling links, with some participants viewing them as "self-serving," while others defend them as essential tools for protecting a creator's time (13:11, 16:22).Favour also explains the authenticity of Trustpilot reviews, emphasizing the platform's transparency in business validation (09:56).Timestamps00:18 – Introduction and shoutouts to the Business and Marketing House.02:26 – Discovering Cal.com: A backstory from LinkedIn to Berlin.04:29 – The legacy of Calendly and its impact on time management.05:36 – Feature Breakdown: Custom routing, domains, and API access.08:33 – Integration Deep Dive: Salesforce, HubSpot, and two-way sync.09:56 – Understanding Trustpilot: How to verify business authenticity.13:11 – The "Pain in the Ass" Factor: A debate on scheduling link etiquette.20:45 – Best practices for using schedulers in podcasting and networking.FAQsIs Cal.com really free? Favour notes that many features Calendly charges for are available for free on Cal.com.What is "white-labeling" in scheduling? It allows you to remove the platform's branding and use your own domain, a feature unique to Cal.com.Why do some people hate scheduling links? Some find them impersonal or "self-serving," preferring direct email or text communication to set meetings.How does Cal.com sync with my CRM? Unlike some tools that only offer one-way sync, Cal.com provides a two-way synchronization with platforms like Salesforce and HubSpot.Action StepsAudit Your Booking Flow: Review your current process and identify if you are paying for features that could be free elsewhere.Check the Comparison: Visit the Cal.com vs. Calendly chart to see which tool aligns with your technical needs.Verify Your Presence: Ensure your business is claimed on platforms like Trustpilot to build authentic social proof.Soft-Launch Your Link: Pair scheduling links with a personal note to avoid the "self-serving" perception.Test Custom Domains: If using Cal.com, explore custom domains to enhance your professional branding.Ready to Rank? Book Your SEO & Web Dev Services Today

Podcasting 2.0 May 29th 2026 Episode 261 - "Podhemian Grove" Podcasting 2.0 May 29th 2026 Episode 261 - "Podhemian Grove" Mike Dell joined the board room to help Adam and Dave with the solution to the Secret Pdcast Group's Problems. Download the mp3 Podcast Feed PodcastIndex.org Preservepodcasting.com Check out the podcasting 2.0 apps and services newpodcastapps.com Support us with your Time Talent and Treasure Show Notes ----------------------------------------------------------------------------------------------------------------------------------------- 01 - ALLIANCE FOR MEASUREMENT IN PODCASTING — Podnews press release this morning: Alliance for Measurement in Podcasting (AMP) launches. Industry consortium for podcast measurement standards. Dave reblog with snark (May 29): "They want better app metrics for their ad-tech but the only 'app' in their council is Spotify.

Want more exclusive content?! http://prometheuslens.supercast.com to sign up for the "All Access Pass" and get early access to episodes, private community, members only episodes, private Q & A's, and coming documentaries. We also have a $4 dollar a month package that gets you early access and an ad free listening experience!====================

This week's Department of Know is hosted by Rich Stroffolino, with guests Bruce Schneier, chief of security architecture, Inrupt, and Chris Ray, field CTO, GigaOm. Missed the live show? Check it out on YouTube. Huge thanks to our sponsor, Guardsquare Mobile security incidents are no longer the exception—they are the norm. Last year, seventy-two percent of companies suffered a mobile app security incident. As the primary gateway to your APIs and data, your mobile app requires more than just basic encryption; it needs a multi-layered security strategy. Protect your brand and your bottom line with layered mobile app protection. Learn more at Guardsquare.com.  

How is AI transforming accessibility for indie authors — and why should you care even if you consider yourself able-bodied? What happens when the tools designed to help people with disabilities end up making everyone's creative business better? Jeff Adams, accessibility expert and romance author, explores how AI is opening doors that were previously closed. In the intro, Spotify Audiobook Innovations; The Economics of Convention Life [The Indy Author]; Friction in your Author Business [Self-Publishing with ALLi]. Today's show is sponsored by Draft2Digital, self-publishing with support, where you can get free formatting, free distribution to multiple stores, and a host of other benefits. Just go to www.draft2digital.com to get started. This show is also supported by my Patrons. Join my Community at Patreon.com/thecreativepenn Jeff Adams is the author of YA thrillers and gay romance, and the co-author of Content for Everyone, a practical guide for creative entrepreneurs to produce accessible and usable web content. You can listen above or on your favorite podcast app or read the notes and links below. Here are the highlights and the full transcript is below. Show Notes How ending a long-running podcast made space for more writing — and how to know when it's time to let go of a good thing What accessibility really means for indie authors and why your digital content might be excluding part of your audience How AI agents like Claude Cowork are removing physical and cognitive barriers for authors with disabilities, chronic pain, or limited energy The culture of shame around AI use in the writing community and why blanket anti-AI statements can be ableist Practical tools including NotebookLM, ElevenReader, and ChatGPT for marketing copy, metadata management, and multimodal research Exciting futures in personalised reading, real-time translation, and AI browser agents that could change how everyone interacts online You can find Jeff at JeffAdamsWrites.com. Jeff also now has a SubStack at contentforeveryone.substack.com Transcript of the interview with Jeff Adams Jo: Jeff Adams is the author of YA thrillers and gay romance, and the co-author of Content for Everyone, a practical guide for creative entrepreneurs to produce accessible and usable web content. Welcome back to the show, Jeff. Jeff: Thanks so much, Jo. It's good to be back. Jo: It is. You were last on the show in March 2023, so over three years ago now. Give us a bit of an update on your writing and publishing business and what it looks like at the moment. Jeff: Sure. I think the biggest thing that happened is that my husband Will, who is also a writer, we ended the Big Gay Fiction Podcast at the end of 2024, after 470-something episodes. It was basically time to do that. So we both focused on writing from that point. In 2025 we had some of our biggest successes in getting writing out into the world. I refound my groove—my difficulty in writing went away finally. We talked a little bit about that back in 2023 too. Will started a new pen name and started producing again, and it was really good to be able to move in that direction. Jo: Was this the hockey romance that really hit at the right time? Jeff: You know, I wish I could have capitalised more on Heated Rivalry when it came out, but I did get hockey books out, and I think I did get to ride that wave a little bit there too. Jo: Yes, and if people don't know about that, that was a super popular streaming series. Was that based on a book? Jeff: It was, yes. Rachel Reid was the author of that book and that series that then Jacob Tierney optioned and made into what fairly turned into a global phenomenon at the end of 2025. Jo: Yes, absolutely. Although I particularly liked Red, White and Royal Blue. That was the one I liked. Not so much into hockey. But anyway, I just wanted to ask you about the Big Gay Fiction Podcast. As you say, you did hundreds of episodes over many years. You and I met over podcasting. You've had lots of connections with people. You ended it, and I know you struggled with ending it, but it sounds like it went really well for you. So maybe you could talk a bit about— How do you know when it's time to end something—a good thing rather than something bad? Does that make more space for writing, essentially? Jeff: It absolutely did make more space for writing for both of us, in particular for me because I have a day job. I balance everything on the creative side with the day job. Will and I had been talking about it for over a year. It just was like, it's really time. After nine years, getting to that 470 mark, we thought about trying to get to 10 years and we thought about, if not 10, then getting to 500 and ending on a milestone. As we looked at everything in our creative business, it was like, this is fun, we enjoy it, but we're not getting as much out of it as we might be if we were actually also writing books, which we also really want to do. It became a time thing and what was the best use of the time. We absolutely miss it occasionally. The whole Heated Rivalry thing, I would've loved to have had episodes to talk about that on, but in the long run, it was worth it. Jo: I mean, one of the things with a podcast, particularly around fiction, was that it was a marketing angle for your fiction. This show is a marketing angle mainly for my nonfiction. So what did you replace the podcast with, in terms of book marketing? Jeff: It was really stepped-up email marketing. I'd always had a list. Will started a list, of course, as he started his new pen name. So it was really turning on that, focusing on that, getting some email marketing with a Bargain Booksy and a Fussy Librarian and a BookBub occasionally to do that work. To be honest, even though we covered things in our genre that if you like what we're talking about, you should like our books, there was never as much of a connection there as you'd want there to be. Even from that book marketing angle, these other things that we can do, it's also a better spend of the money to get those types of promos than it was to continue running the show. Jo: Yes, that is interesting. I mean, obviously I think about podcasting a lot since I have this one, and I put Books and Travel on a hiatus and that was meant to help my fiction and definitely didn't help my fiction sales. But I want to bring it back again because I love doing it. Do you have this hankering sometimes? Do you think you'd ever do the podcast again? Because you are also quite into all the technical stuff and all that. Jeff: It's possible. I've toyed with the idea of doing a short accessibility podcast geared towards creatives, tilting to the same audience that Content for Everyone does. Then I come back and look at the time—is my time better served writing new fiction or perhaps starting a Substack, which I also toy with the idea of, for accessibility stuff? So it bounces around in my head to do another show, but I haven't really decided to jump on that yet. Jo: Yes, and I think that waiting is really good. As you say, you quit a big thing and you don't have to rush to fill it again. I love that you guys are writing more books. So I wanted us to talk about that up front because I know people who listen to this show—I encourage people to start podcasts if you want to, but equally it can take a lot of time. So that's fantastic. Now, you mentioned accessibility, and I feel like the word can be quite difficult for people. So let's just start with a definition. What is accessibility? Why do you care and why should we care? Jeff: So accessibility is really about making sure that whatever the thing is, whether it's something out in the physical world or in the online world, that everybody has access to it. Access to the information, access to getting into a building or being able to cross the street appropriately, whatever that is—that the accessibility of the thing is high. So that regardless of who is approaching it, they can interact with whatever the thing is. If we put that into the digital world, it's about making sure that text on a screen can be perceived by anybody, whether they're trying to read it visually or if they're trying to read it through a screen reader or through a braille monitor. Whatever that is, they need to be able to interact with it, get the information they need, do all the functions of whatever it is on the screen. Check out on Amazon, check out at their favourite e-commerce place, be able to get the products in their cart, check out, et cetera. For creatives, it's about the things that we do: the websites that we build for ourselves, the e-commerce platforms that we use, our email marketing, our social media posts. Making all of that as accessible as we can so that we're not perhaps missing a part of our audience or our prospective audience from being able to engage with our work and in turn, hopefully, buy our books and enjoy our books and become a fan. This became important to me because of my day job. I hadn't really considered this—like, I think most people don't—until I started working at UsableNet. It's going to be 15 years I've been at that company come this autumn, and I really started to see the impacts because UsableNet is all about accessibility on the digital front. I really started to learn, being a project manager for them, what all of that meant and how it impacted people who couldn't buy something online, couldn't book a hotel room, couldn't book an airline ticket. It just really became something I got passionate about. I ended up writing the book because I realised that nobody talks to creatives about this. Nobody tells the independent author what they should do to help make their digital stuff accessible so that they don't miss people. I never expected my day job to interact with my creative side so much, but this certainly has over the last few years. Jo: I mean, has it got better? Like we said, you were on here three years ago. We did talk about some of the things around EPUB formats and taking off DRM and what we need to do on our websites—labelling images, for example, and that kind of thing. Do you think accessibility has gotten better? Jeff: I think the awareness of it has improved, both within the creative community and in the broader web ecosphere, that the awareness is better. There's so much knowledge that needs to go into creating something that is accessible. Sometimes there's so much that you have to think about with colours and alt tags on images and all the little bits and pieces, if it doesn't really come to muscle memory, it's easy for it to fall off. There's a survey that's done by WebAIM every year about the top one million homepages out in the universe, and they surveyed those for just the things that an automated scan can detect, which is a small portion of overall accessibility, and the number of errors across that top million actually ticked up this year. Even though there's all these laws around the world—people get sued all the time in the US—the number of errors ticked up for the first time in a few years. So I think the awareness is up, but I think being able to take action on it and make the time to take action on it isn't where it needs to be. Jo: So last time you gave us all those tips. I'll refer people back to that and also to your book Content for Everyone, which has got loads of great stuff in. I wanted to talk to you for this show because I was sitting watching Claude Cowork—now I use Claude Code a lot more—but updating 140 titles on IngramSpark, where me clicking things and there's like 15 clicks per record on IngramSpark updates for pricing, is an absolute nightmare. I was watching the AI do the work and I realised this isn't just saving me time, it's actually saving my wrist and my arm from repetitive strain injury. That's when I thought about this accessibility thing. As you mentioned, for example being physically accessible into a building, say someone's in a wheelchair, they can't necessarily get into a building if there's no ramp. I was thinking that for many years, being an indie author, being a writer online, there's also been these physical barriers because there's a lot of plumbing and clicking for us. So I wondered, starting with an attitude around a shift in who this is opening up to— How is AI starting to help people with these accessibility issues? Jeff: Yes, there's so much opportunity around this. We should note, just to timestamp this, that we're talking on 14th April 2026, because who knows what will change, even in an hour from now. I think Cowork was one of the first things that we saw, and that's only been out since the very top of this year. Being able to do actual agentic tasks. Other things have sort of gotten there, but Cowork really opened it up. You mentioned the repetitive stress that you would've had clicking all of those forms on IngramSpark across 140 books. But there's that type of stress, chronic pain, cognitive drain for somebody who may have some cognitive disability and trying to work through that form. The cognitive energy just might drain out and maybe knock them out for several days after trying to get through that, or the tasks take them multiple days to do. Someone who has lower vision, someone who's trying to work through that form with a screen reader—all of that draws energy, draws focus. Now we've got something where, with plain language, we could say something like: here's all my pricing information, I've logged into IngramSpark, go update these books. Obviously the prompt's going to be a little more than that, but in broad terms, that's what we're going to tell it. Jo: Hmm. Jeff: And being able to have it go through and do the thing. If it gets stuck, have it come back and say, “Hey, I've got trouble with this. Please help me.” That can just free up so much of the drains that people can have—the things that can take them out of doing the part of the work that they need to do for an author business. They can go write the book through whatever process you're going to use to do that, rather than getting caught up in something like having to update all those books on IngramSpark. Jo: You mentioned writing the book there. I have this real sense of being an able-bodied indie author in terms of my computer use and my ability to write a whole book, a 70,000-word thriller that I write regularly. We're all special in some way, but I do have a reasonably normal brain where I can do this work without too much strain. It's hard work, but I can do it. I meet people who are now using AI to help them write, to help them organise their work—maybe someone has dyslexia or ADHD or cognitive issues or pain—there's just so many things that I take for granted that don't affect me. I hear from people who, at this point in time in the community, are almost shamed for using AI to write. So I wanted to bring this up to discuss it under the terms of accessibility. Do you have any thoughts on that? Jeff: I have real difficulty with people who will say anything in the broad range of, “I don't need to use this thing, and therefore you should not either.” Which is adjacent to indie anti-AI speak that there is out there. Certainly we're living right now at probably the highest point that it's ever been, where more and more there's a sentiment towards not using AI for whatever the reason is. I totally respect that people can have concerns about the environment and about energy use and water use, et cetera. Not to mention all the other things that are on the more difficult side of AI. To shame someone who may not be able to put their story out there without the use of that AI, whichever one they're using, or to shame them because they're using AI to run part of their business—updating IngramSpark, doing other things like that—I think it can come down to there being some ableism there. Ther is some privilege behind that too, where they're just like, “I don't need this, and you shouldn't have it either.” I want to give people just a sliver of an idea of what this can mean for someone who is disabled and what AI can unlock for them. There is a person on LinkedIn that I follow whose name is Hannah Desmond. She's an ADHD coach and a former software developer, and very recently she posted this on LinkedIn. This is a paraphrase of what she said, but: having something that can meet you where you are and help you bridge that gap is what I think I have found so helpful about using AI. Here's what I keep coming back to. Without that support, I wasn't more motivated or more capable. I was just stuck. That's the bit that gets lost. We've been taught that struggling is how you know you're doing it properly. So when something reduces the struggle, it can feel wrong—even when it's the thing that actually makes the work possible. Because there's a difference between avoiding thinking and being able to think at all. I think that rounds it up. She's talking about her time as a software developer, but you can apply that to any realm of AI when we're thinking about trying to shame someone for why they may be using it. We may not know that they have a disability because we don't always share that part of ourselves. So I really feel strongly about that and how we are in this culture of shame. Jo: Yes. It drives me up the wall, actually. But I will also say: you don't have to have a disability or accessibility issues in order to use AI in whatever way you personally decide is okay—talking to the listeners now. I think Orna Ross from the Alliance of Independent Authors says it well, which is you should have your own AI policy. So you personally decide where your lines are, how it helps you, what you want to keep for you, and what you want help with. I was also thinking in terms of accessibility around money. Again, for many of us, professional cover design, professional editing, professional human-level translation, these are things that are pretty pricey for many people. So again, this makes it more accessible. One of the reasons we got into the indie way and being indie authors was to try and remove the barriers to entry to people who have been excluded from the environment of publishing. So, yes, it is really hard to talk about this, and yet that's why I wanted to talk about it, because— There's so many variables for each individual and there's no situation that's the same, really, is there? Jeff: No, not at all. The things that I may need to do my work in the most efficient way possible is different from the way that you're going to work, is different than the way my husband's going to work, is different than every other person and the way that they're going to work. Which is why any kind of blanket statement about “I don't need something and therefore you shouldn't need it either” can just be so problematic, because we have no idea what someone else is going through. Either it's a permanent part of their lives or maybe it's something that is happening temporarily with them where they might need to leverage other tools. Jo: Yes. Talking about that temporary, I think I really got the first sense of this when I had COVID the first time, which was really bad. I remember I was so sick, the only thing I could do was listen to an audiobook. I couldn't think, I couldn't read. It was really probably months of not having my brain back. Then the other thing that's happened as I age, as women age, is menopause kicks in and the brain fog is a real thing. I've heard from other people too who've said having Claude or whoever, an AI tool, to help with the brain fog is so important because otherwise I just wouldn't be able to gather my thoughts. Again, as you said— Even if we don't need these things now, it's quite likely we're going to need them at some point, given ageing, given the potential for injury and disease. I mean, we don't escape this alive, do we? Jeff: Yes, that's a great point because unless we're extremely lucky as individuals, we're all likely to have some sort of a disability in our lives at some point. I know for me, as I age and my eyes get more and more tired after being in front of a screen all day for work, and then whatever creative stuff I do in the afternoon on a book—when it comes near bedtime and I do want to read, I probably want to do that with an audiobook, much more audio, especially for any long reading project. That can also be like, if I have a long document or a long article to read, I am likely to give it to ElevenReader, let it load itself up, and then listen to it, because I take the information in better than trying to follow words across a screen. Jo: Yes. Jonathan, my husband, now also listens to a lot of academic papers on ElevenReader. Most of us will know it as where we publish some audiobooks from ElevenLabs, or you can also publish other things there. So it is super useful to think about what we can do with ElevenReader. Another thing that I found really useful recently is NotebookLM. On NotebookLM, there is a free tier. You can put various things in there and then create a custom audio. So this is something I've been doing as part of research. You can put in, say, 10 YouTube videos or some PDFs or your book or whatever, and then you can create a custom audio. Then I'll go for a walk and I'll listen to the custom audio, and then I'll go back and look at the detail of what it was. It gives me the framework of whatever I'm thinking about on a broader level, and then I can come back to the details. So again, it's this multimodal approach that can help us manage our energy, I guess. Jeff: And it's all about the managing of the energy, I think, too. That is a great way to think about the accessibility of it all. You mentioned a great use there for NotebookLM. That could also be putting your book in there and having it help you build a world bible or something like that. Or building marketing materials off of that. There's a lot of things now that NotebookLM can do in terms of helping you create FAQs maybe for a newsletter or for your website, and building video stuff off of the material that it has. So there's a lot of options there, and ever-growing options that can be useful for someone to manage any number of the things that they may need in their creative business. Jo: Yes. In fact, talking about Claude, there are a lot of Claude plugins now, skills and integrations. Shopify just released a Claude plugin and many of us now have Shopify stores. I have a lot of products with a lot of different variations and the metadata. There's so much metadata. And again, I'm just so pleased now that I can work with Cowork and get it to actually update directly into Shopify. In fact, coming back, you mentioned updating alt tags earlier. That's something again that AI could help you update—the back list of your alt tags on a website. I've now got my Cowork doing EPUBs so I could finally update all my EPUBs with back matter and all of this kind of thing. So I feel like perhaps we could go beyond accessibility to talk about amplification. All the things that we didn't do because it was too tiring and we just couldn't be bothered, or it would just be way too much work, that now it's opened up as a possibility because of these tools. Jeff: Absolutely. I mean, you look at a backlist as large as yours and the things that you're now able to do. I didn't know that Claude had a Shopify plugin. So the abilities that we have now to maybe do things in the business that we hadn't before. One of the things I've been working with Claude on is rewriting my website and creating a more proper website for Will. I'm really making sure that it is not only SEO prepared but also GEO prepared, with all the metadata and all the backend code schema that it needs so that LLMs can find me, can understand what I do, can understand the books, branch out to the other areas that it needs to. Doing that through WordPress would've been so much more difficult, even with Claude, that to be able to rewrite the site in a way that is going to let me manage it better so that I will do it on a more consistent basis. Whatever that thing is, we're now able to do these things. That could be updating keywords in Amazon or making sure we're aligned across all of the sales platforms that we might be on and things like that, that Claude can do and do well. Jo: Yes, I think marketing is just the killer app really for people, isn't it? I think most authors do not enjoy marketing. I find Claude better for creative work, for strategic work, for doing work through Cowork or Code, but— ChatGPT with marketing copy is very, very good. So I've actually been using that as we record this. I've got a Kickstarter launching next week, so I've been getting it to do ad copy and social media copy and all that kind of thing. This is stuff when you have to produce—give me 20 taglines, give me 20 hooks, give me another 20 and another 20. I mean, we just cannot do it as humans, right? Jeff: Yes, I have found GPT wildly helpful. I mentioned trying to get Bargain Booksy and Fussy Librarian promos. Jo: Mm. Jeff: And you have to give it the marketing hook, and it can't just be the blurb that's on Amazon—it's got to be something fresh, and they each have slightly different requirements. Having GPT—here's the blurb, give me a dozen different options—and then I may take pieces of all of them and create one of my own. But it reworks that much faster than my brain was ever going to try to find the right thing I want to give to Bargain Booksy. Jo: Yes, you are right. Or it says write this in 300 characters or less. Jeff: Yes. Jo: I do exactly the same. That kind of transformative work can be really good. In fact, there was somebody I know who has been rampantly anti-AI for years and then said, “Would this help me? I have to do a synopsis for an agent, so I've got this 100,000-word book and it needs to be a 10-page synopsis. How would I do that with AI?” So I was encouraging her to take each chapter and ask it to summarise the chapter, and of course read through it and everything. But I mean, doing a synopsis once you've actually written a book—that can be super useful. So I think what we're saying is— There are levels of need in terms of both the author and the audience. Then there are levels of your personal use from one end of the spectrum to the other in terms of how far you want to go in every area of the business. And in that way, it's just different for everyone. Jeff: Yes, and I think getting to that mindset shift that we were talking about a little bit—it can be so easy to dip your toes in. That one author came to you and said, “Do you think it could do this?” And I think that's the beginning exploratory area for perhaps anyone. People are going to hear us talk about this and it might inspire them to go try something that we've talked about. But these things, whether it's Claude or GPT or Gemini or whichever one it is, you can come to it and say, “I'm an author, I have X, Y, Z going on in my life”—whether that's a disability, whether that's a time constraint because you have a day job and maybe you have kids and a family that need your attention—”I have these time constraints, I want to do X, Y, and Z in my business. How can you help me with that?” It's going to tell you what it can do to help you with that. I would even say, if you have the ability to have multiples of these, you could ask the same question to GPT and Claude, and they're going to give you similar answers in some instances, but they may also have different ones because of the abilities that the different platforms have around these things as well. That can help you make that mindset shift of, “Well, now I see that it can do that. Could it also do this?” And then ask it if it could do that. Because I know for me, Jo, I've taken so much from you and your journey with Cowork that it's like, “Oh, she did that. I wonder if I could do this.” And all of that piles on top of itself. Then eventually I think your brain starts to think on its own, “Oh, I have to do this task. Can Claude maybe do this for me? Let's go find out.” Jo: Yes, and if it couldn't do it for you yesterday, you never know, it might be able to do it tomorrow. Jeff: Right? Because I haven't tested yet its new ability to actually use your computer. Jo: Mm. Jeff: And I'm curious what that might open up. Because one of the things that I've seen that I wish it would do is be able to take the EPUB that's on my drive and actually put it into a platform I'm trying to upload to. Cowork on its own hasn't been able to cross that barrier, but I wonder if with computer use added to that, if it could. Like, “here's the EPUB, upload that over there,” be able to pick it from the file picker, essentially. Jo: Yes. I think, well, a little tip for everyone: I wouldn't give access to your entire file system to the AI. Jeff: That's a good point too. Jo: Yes. I have a Claude folder in my drive and it only has access there. So if you put files in that drive, it might be able to do that. But I know what you mean. I have been using it to help me publish things in German on KDP. Now I can use the browser, so you can actually do that. In terms of uploading the actual file, I know what you mean. These things will change. As we record this, again middle of April, we are almost about to get the next models being Mythos, which might be Claude 4.7 Opus, or also ChatGPT has a new model coming, and these models are getting very powerful. With every shift they can do more things. So as you say, the very first thing to do is ask it, “I want to do this—what are my options?” And some of them, for example, doing an AI-narrated audiobook, ChatGPT and Claude don't do that. You want ElevenLabs or one of the other services for that, but they can tell you what your options are. So that's one thing, but I wondered if you have any thoughts on the gaps that you are seeing. You mentioned one there around file uploads, but— What do you hope might come and some of the things that might be exciting if they arrive? Because you never know, they might be here already. Jeff: There's certainly some movement in some areas. One of the things I'll share is, in March I was at the 2026 CSUN Assistive Technology Conference—CSUN is California State University, Northridge—and they've run this conference for some 40 years now. One of the sessions I went to was from Tara Maisel—I hope I'm pronouncing her last name right. She's a senior project manager in books accessibility at Amazon, and she was doing a session specifically on readability. She had all kinds of statistics and information about what goes into making something readable. One of the things she talked about with AI was the future of personalised reading. If you think about the Kindle app, for example, there's a lot of settings you can make there—font size, colours, brightness, text spacing. There's a lot of tools in there. She was pointing out that potentially readers don't even know what they actually need for the optimised visual reading experience. She sees a world where AI can perhaps do an analysis of your reading behaviour and then help you find the optimal settings. Maybe even multiple optimal settings for, say, if you were reading in a room that had daylight versus at bedtime, and the ways you might shift it. I was almost thinking of this like when you're at the optometrist and they're like, “Which lens is better—this one or that one?” Jo: Oh, sometimes that is very hard. Jeff: Yes. It's that AI could step you through that a little bit to help you find that optimal reading experience in that moment. And then it might even notice, potentially, if you're changing something in the way that you're moving through a page, that it might flag to say, “Hey, do we need to adjust something?” Some other areas that I think are really exciting, for everyone and perhaps particularly for people who are disabled and needing the support of some assistive technology, is what we're seeing in the browsers. OpenAI's Operator has been out for quite a while now, since sometime I think autumn of last year. Perplexity Comet has been around even longer. Then we've got browser extensions from Gemini and Claude that are available, that can let you just type natural language. You know, “Please go find for me jeans in this size that are on sale on this website. Find me the best price for blue jeans on this site and this size,” and it'll just go do it. Which can certainly speed things up for people in the disabled community to find things quickly, to spend time navigating less, and maybe ending up with the AI coming back and saying, “I found these five things. Which one would you like me to buy for you?” Or, “I found this one thing that you do need and it's waiting for you in your shopping cart.” The ability for that on the horizon is an amazing jump from an accessibility point of view. But really it's one of those things that accessibility will then help everyone because we can all just shop that way, if we choose to. These are early days for these browsers and these extensions. The other side of it comes back to basic web accessibility too, because I've seen these types of activities not work so well on a site that may not actually be accessible on its own. A great example is something I ran into with Claude Cowork about a month ago. I was testing to see if it could help me navigate and get things uploaded together for a site where I wanted to upload books, knowing again that it's not going to upload the actual file, but it could fill in the metadata from my master database of metadata stuff. There were areas on the site that it actually couldn't hit the button, because the site itself was also not functional to a screen reader. So there are gaps there. It's early days, but I really see that as an interesting future that'll really help people with disabilities—but again, help everybody too, just manage time better. Jo: I know exactly what you mean there. I've done some collaborative work with Claude Code when it's like, “I can't click the button,” and I'm like, well, I'll click the button—you fill in everything else. Jeff: Exactly. Jo: It's actually quite a funny situation. But goodness, coming back to IngramSpark again—these things need APIs. We need better functions. It's funny because I think a lot of traditional publishers have these APIs or backend upload things that you can do. I'm like, well, we need to get to that with these systems. But I think things will change. Another thing that I think has also shifted is the use of voice. Voice for dictation—it used to be with dictation that you would have to say “comma,” “open quote,” “new line,” and all of that. And you'd also have to make sense. Whereas now I feel like you can just dictate a whole load of things to these AIs and then say, “Tidy that up,” and they will do a lot more than the old situation. So I think voice will also help. Also automatic translation. I don't know if you know this about X, and if you're on X anymore, but just this week they've made it multi-language. So I can read tweets by people who've posted in another language in English. I can read something from Korean or read something that someone French has posted and it gets translated. It has made a huge difference to the content I'm seeing, which is fascinating because I don't think we've ever had this kind of automatic “everything is translated into your language” situation. It's really got me thinking about how [automatic translation] might work for eBooks or other things if the rights are there. I don't know. Have you seen stuff like that? Jeff: There's so much available now with voice and the ability to not have to speak all the other stuff that went with it—comma, full stop, next line. It was a little mind-bending sometimes, trying to think about quote marks and all that stuff. And now it's so good. Different platforms do it to different degrees of ability. Even being able to speak your prompts into the very platforms themselves without having to type all of it. Chronic pain comes to mind, any kind of mobility thing—all the typing would be a drain or maybe even impossible. So the voice ability is so powerful there and unlocks more things. At the same time, those translation abilities—I believe AirPods now have the ability, if you've got the right stuff on your phone, that you could be talking to somebody, they may speak back to you in a language you don't speak, but your AirPods will give it to you in your language. Jo: Hmm. Jeff: Google has, I believe, a live captioning app that you can use. I think there's even a split screen—I don't know if that's available now or something in their future—where you could put the phone on the table and tell it who's looking at what side of the screen, and it'll put the language that I need on my side and the language the other person needs on the other. So there continues to be such a shift in how we're being able to translate stuff that really opens up communication and can open up our books to so many more people. I'm very interested to see—I haven't pulled the trigger on this yet—but how Amazon's auto-translation rolls out and how that's received in terms of the accessibility around our books and being able to put it in someone's hands who doesn't speak—I think it's only English to other languages right now—but who doesn't speak the language it was written in but wants to read that book. We could never, as indies, or really even big five publishers, wouldn't have the money to create custom translations everywhere. But if the AI can help do that and spread those books around so that everybody could have the story they want to read, I think that's such a win for the reading audience. Jo: Yes, I think it's so exciting to think what might be coming, and that's what I want to stay on the side of on the AI discussion. There's enough negativity out there and you can get that information somewhere else, but for me I want us to stay on the positive side of how this helps both the author and the reader. And hopefully the community, to create more and read more and enjoy being human more. Right? Because I find that I do get out more and listen to stuff, or I'm out walking instead of at my desk, and I mean, that's what it's about. I'm pretty excited about the future. How about you? Jeff: I am. I think there are, quite honestly, some scary things that could be out there in the future. I mean, there's been a lot of talk about what Mythos is capable of. But on the other side of it, there are all these advances. I also look back at Google and AlphaFold and what DeepMind was able to do there for science. There's more of that stuff out there, and individually for each of us, spending a little bit of time—and I do have to say, I think you need to spend time on a paid plan because the free stuff doesn't give you the idea of what these platforms are actually capable of. So if you only drop in, even briefly, to experiment on one of the $20-a-month plans and give it your situation, ask it what it can do for you, I think you'll see where, on a personal level, AI will help you unlock some things. It can help you move some things to the next level in your business that for whatever reason you haven't been able to do. You don't have to use it for everything. You may decide that it's still not for you for whatever reason, and that's fine. But I think there's so much to explore here and to let your curiosity run for a little bit to see what's possible and what you might unlock with it. Jo: Brilliant. So where can people find you and your books and everything you do online? Jeff: So pretty much everything lives at JeffAdamsWrites.com. Jo: Well, thanks so much for your time, Jeff. That was great. Jeff: I loved it, Jo. Thanks for having me..The post Accessibility And AI: How New Tools Are Opening Doors For Indie Authors With Jeff Adams first appeared on The Creative Penn.

With WWDC26 just around the corner, The Trio burns off some Google I/O feelings before getting to the speculation they actually care about. Steve breaks down why AI-slopified search might be quietly destroying the Web's economic model, Aaron wonders what any of these agentic tools actually do right now, and Kotaro lays out a case for why this might finally be the year Siri stops being a punchline. Also: Xcode Pro is coming. Probably. Apple, please don't.## Chapters00:00 Introductions 00:52 Google I/O — "AI" All the Things 09:12 Google I/O — Killing Search with "AI" Slop 13:32 Google I/O — "Agentic Commerce" is Coming For Your Business 15:09 WWDC26 Speculations — Dynamic Widgets 17:58 WWDC26 Speculations — New Siri (Finally) 20:36 WWDC26 Speculations — AppleClaw & Xcode 26:27 WWDC26 Speculations — Folding Phone Tea Leaves 28:24 WWDC26 Speculations — HomeOS 31:11 WWDC26 Speculations — Out of the Box 37:32 WWDC26 Speculations — New Foundation Model 41:49 Outro & One More Thing... 42:51 Tag## Show Notes- Google I/O 2026 went all-in on AI, with Kotaro noting the near-total absence of Kotlin, Jetpack, and Flutter talks at this year's developer sessions.- Gemini 3.5 Flash launched as the new "affordable" model and turned out to be significantly more expensive than its predecessor.- Steve takes apart Google's AI search redesign, arguing it quietly destroys the economic model that funds the Web, including Google's own ad revenue.- Aaron's deadpan verdict on Google's AI search demos: "the only thing it showed was it generating these giant slop docs. Who wants to read those?"- Kotaro and Aaron speculate that WWDC26 could bring more dynamic, context-aware widgets, ones that are smarter about timing and context than the current static rectangles.- The Trio agrees the headline WWDC feature is a Siri that actually understands intent, with Shortcuts workflow building as a hopeful bonus.- Kotaro floats an "AppleClaw" style personal assistant via iMessage, letting developers submit agentic tasks to an Xcode Cloud backend.- The folding iPhone question comes up: does it run iPadOS, iOS, or something in between, and how will apps scale across the form factor?- Steve expects Apple to plant HomeOS seeds at WWDC, APIs and features that will only make full sense once a HomePod-with-a-screen arrives later in the year.- The Trio caps the WWDC wishlist by accidentally inventing Xcode Pro, Apple's inevitable premium developer subscription tier.## Links**Google I/O 2026**Google I/O 2026: https://io.google/2026/Everything Announced at Google I/O 2026 in 13 Minutes: https://youtu.be/qCfARlv74jQ | 100 Things We Announced at I/O 2026: https://blog.google/innovation-and-ai/technology/ai/google-io-2026-all-our-announcements/**WWDC26**WWDC26: https://developer.apple.com/wwdc26/**One More Thing**AppJawn LLC: https://appjawn.comApps: Clipdish, Mio Vino, Minimalist Meditation Timer**PhillyCocoa:** https://phillycocoa.orgIntro music: "When I Hit the Floor", © 2021 Lorne Behrman. Used with permission of the artist.

The fastest way to lose a new pool service customer is painfully simple: let the call go to voicemail while you're out on route. I sit down with Nikki Acosta and Hal Denbar from Skimmer to talk about a practical use of AI that actually earns its keep, an AI phone receptionist built specifically for pool businesses. We get into what AI should do for operators, save time, reduce interruptions, and stop real revenue leaks, instead of adding another shiny tool to the pile.Nikki breaks down how Skimmer's AI Phone works day to day: answering during the hours you choose, asking the questions you design, and routing calls based on rules for existing customers versus brand-new leads. The system can collect contact info, address, service area details, and even pool type, then store the call data inside Skimmer and create a customer record automatically. We also talk about “custom knowledge” so you can embed troubleshooting steps and safety escalations, like when a caller reports smoke or a potential equipment hazard.Hal zooms out on what this means for growth in the pool industry. Bigger companies used to win by default because they could always pick up the phone. If a small operator can answer every call with an AI voice agent, the playing field shifts. We also dig into how to choose pool service software the smart way: stability, security, business continuity, and the ability to integrate with the rest of your tech stack through APIs and webhooks. If you're looking for pool route software, field service management tools, and a realistic approach to AI automation, this one delivers.Subscribe, share this with a pool pro who misses too many calls, and leave a review with your biggest customer communication headache. What would you want an AI receptionist to handle first?We talk with Nikki Acosta and Hal Denbar from Skimmer about why missed calls quietly crush pool service growth and how an AI phone receptionist can fix it without adding office overhead. We also get honest about AI hype, what “real” time savings look like, and why software stability and security matter as much as flashy features.  • AI overwhelm and a simple test for value: does it reduce real work  • How Skimmer AI Phone answers calls and routes them by rules  • Capturing lead details automatically and creating new customer records  • Using custom knowledge for troubleshooting, escalations, and safety  • Why always answering calls changes the growth advantage of big companies  • Pricing, 30-day free trial, and what setup looks like in practice  • What to look for in pool route software: uptime, security, long-term support  • Building an integration ecosystem with APIs, webhooks, CRMs, and ERPs  • Making software simple for techs in the field and back office teams  Are you a pool service pro looking to take your business to the next level? Join the pool guy coaching program. Get expert advice, business tips, exclusive content, and get direct support from me. I'm a 35-year veteran in the industry. Whether you're starting out or scaling up, I've got the tools to help you succeed. Learn more at swimmingpoollearning.com.  If you want to try Skimmer for free, simply go to my website, swimmingpoollearning.com, and click on the skimmer banner that's on the home page of the website.  And if you want more podcasts, you can also go to that same site, swimmingpoollearning.com. On the banner, there's a podcast icon. Click on that, and there'll be over 1900 podcasts there for you to listen to at your leisure.  And if you're interested in the coaching program, you can learn more at pullguycoaching.com.  Send us Fan MailSupport the Pool Guy Podcast Show Sponsors! HASA https://bit.ly/HASAThe Bottom Feeder. Save $100 with Code: DVB100https://store.thebottomfeeder.com/Try Skimmer FREE for 30 days:https://getskimmer.com/poolguy Get UPA Liability Insurance $64 a month! https://forms.gle/F9YoTWNQ8WnvT4QBAPool Guy Coaching: https://bit.ly/40wFE6y

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

Max Anderson is a seasoned product executive with a proven track record of bringing successful technology products to market in the consumer privacy, data management, and marketing space. Prior to Ketch, Max was the Director of Product Management at Krux. After joining Salesforce as part of the Krux acquisition, Max ran data privacy and consumer identity products at Salesforce, including the rollout of their industry-leading GDPR solution set. Prior to Krux, Max was a Product Manager at IPG Mediabrands, where he was responsible for multiple successful advertising measurement products. In this episode… Getting consent and opt-out compliance right requires more than adding a cookie banner or standalone webform. It requires consent tools, consumer identifiers, and downstream third-party systems to work in concert. Regulators are looking closely at whether a consumer's choice follows them across devices, browsers, and the systems where their data is collected and used. When those pieces do not connect, an opt-out can be incomplete, putting companies at risk of regulatory enforcement. So, what does it take to build a complete and compliant consumer opt-out experience?  Identity management is central to effective consent and opt-out compliance because consumer choices need to be honored at the person level, across devices and browsers. Privacy rights forms and consent tools also need to connect, so an opt-out request reaches the CMP controlling tag firing on the site. When data has moved to third-party advertising and marketing vendors, companies need to understand whether they can flow that opt-out downstream. Yet many third-party platforms do not provide privacy APIs or consent-related controls, and building integrations with them can be challenging. Companies should test the process by submitting an opt-out through the webform, returning to the website, and checking whether browser data collection events still happen that could facilitate cross-context behavioral advertising.  In this episode of She Said Privacy/He Said Security, Jodi and Justin Daniels talk with Max Anderson, Co-founder and Head of Product at Ketch, about navigating consent and opt-out compliance gaps. Max explains why identity management matters when honoring consumer choices across devices and browsers, and how disconnected privacy rights forms and consent tools can leave opt-outs incomplete. He also describes the challenges companies face when flowing opt-outs down to third-party advertising and marketing vendors and shares practical steps companies can take to assess vendor controls, cross-device exposure, and the areas that may create enforcement risk. 

In this episode, Peter breaks down the updated Cardano DApp Explorer and explains why curated ecosystem directories matter for newcomers, builders, and researchers. He walks through how the Cardano.org apps directory helps people discover live applications, compare activity, and understand what is already available across the ecosystem.The episode also looks at two complementary discovery platforms, Cardano Cube and AdaStack, before shifting into an interview with AdaStack founder Tucker. They discuss ecosystem coverage, multilingual resources, project listing workflows, AI-assisted maintenance, plans for richer project metadata, smart contract audit tracking, and how structured ecosystem data could power future APIs and developer tools.If you want a practical overview of where to discover Cardano applications, how projects can improve visibility, and why better ecosystem data matters, this episode offers a grounded tour without hype or speculation.Key Takeaways:- The updated Cardano.org DApp Explorer gives newcomers a clearer way to discover live applications by category and activity.- Transaction and activity indicators can help users identify which applications appear active, but they should be used as context rather than a guarantee of quality.- Projects can submit their applications to the Cardano.org directory through a documented workflow, improving visibility across the ecosystem.- Cardano Cube and AdaStack provide additional perspectives on the ecosystem and can complement the official directory.- AdaStack is tracking nearly one thousand projects across more than one hundred categories, along with resources in multiple languages.- AdaStack plans to expand its structured data with project history, team details, on-chain references, and smart contract audit information.- AI-assisted monitoring may help ecosystem directories keep links, listings, and project status more up to date over time.- Accessible ecosystem data and APIs can make research, discovery, and builder tooling easier across Cardano.Links & References:- Cardano Apps Directory https://link.learncardano.io/JIJdb3- Add your Application https://link.learncardano.io/W52NlV- CardanoCube https://link.learncardano.io/k9zcxs- Adastack https://link.learncardano.io/gdYxSdWebsite: https://learncardano.ioX/Twitter: https://x.com/astroboysoupDisclaimer: This content is for educational purposes only. Nothing constitutes financial advice.DISCLAIMER: This content is for informational and educational purposes only and is not financial, investment, or legal advice. I am not affiliated with, nor compensated by, the project discussed—no tokens, payments, or incentives received. I do not hold a stake in the project, including private or future allocations. All views are my own, based on public information. Always do your own research and consult a licensed advisor before investing. Crypto investments carry high risk, and past performance is no guarantee of future results. I am not responsible for any decisions you make based on this content.

L2BEAT verifies Lighter's emergency exit hatch. Blocknative sunsets its APIs as its team joins Deloitte. And Aave Pro now supports wallet monitoring. Read more: https://ethdaily.io/950 ETH Daily sponsorships are now open. Reach over 10,000 Ethereum-native subscribers every weekday. Learn more at ethdaily.io/sponsor Disclaimer: Content is for informational purposes only, not endorsement or investment advice. The accuracy of information is not guaranteed.

If your MCP server has dozens of tools, it's probably built wrong. You need tools that are specific and clear for each use case—but you also can't have too many. This creates an almost impossible tradeoff that most companies don't know how to solve.That's why we interviewed Alex Rattray, the founder and CEO of Stainless. Stainless builds APIs, SDKs, and MCP servers for companies like OpenAI and Anthropic. Alex has spent years mastering how to make software talk to software, and he came on the show to share what he knows. We get into MCP and the future of the AI-native internet. [Disclosure: Dan is a small investor in Stainless.]If you found this episode interesting, please like, subscribe, comment, and share.To hear more from Dan Shipper:Subscribe to Every: https://every.to/subscribeFollow him on X: https://twitter.com/danshipperGet started with Braintrust at https://www.braintrust.dev/ Timestamps: 00:01:15 - Introduction 00:05:09 - APIs and MCP, the connectors of the new internet 00:11:00 - Why MCP exists 00:17:15 - Why MCP servers are hard to get right 00:20:24 - Design principles for reliable MCP servers 00:25:06 - Using MCP for business ops at Stainless 00:40:57 - Alex's take on the security model for MCP 00:44:42 - How one-off AI actions become permanent production softwareLinks to resources mentioned in the episode:Alex Rattray: Alex Rattray (@RattrayAlex), Alex RattrayStainless: https://www.stainless.com/

In this episode, host Olivier Lafontaine speaks with Kevin Cummer, Director, Life Products Management, and Nick Rohan, Director, Partner Management from TruStage, about how the company is rethinking life insurance for the middle market. TruStage has evolved from its roots in the credit union space to expand distribution through strategic partnerships, making life insurance more accessible to underserved consumers. You'll hear how they leverage instant decision underwriting to remove friction from the buying process, improving the customer experience and conversion rates; about the role of APIs and embedded distribution to integrate directly into partner ecosystems; and about how simple products drive scale. Key Takeaways: TruStage is expanding access to life insurance by simplifying the buying experience through instant decision underwriting, removing traditional barriers and long approval cycles. By leveraging APIs and embedded distribution, TruStage integrates life insurance directly into partner ecosystems, creating seamless customer experiences that improve reach and conversion. With a focused strategy on the underserved middle market combined with strong partnerships and operational simplicity, TruStage is able to scale efficiently while delivering meaningful value to consumers. Jump Into the Conversation:(00:00) Meet Kevin Cummer and Nick Rohan (02:01) TruStage's internal culture and long-tenured leadership in life insurance (04:01) TruStage's roots in credit unions and middle market focus (05:00) Shift to simplified and instant decision underwriting (06:00) Expanding beyond credit unions through partnerships (07:00) Why instant decision underwriting is a key differentiator (08:41) Building APIs and simplifying partner integration (11:37) Implementation timelines and scaling integrations (13:10) TruStage's evolving approach to AI (18:47) Partner strategy and distribution model (22:14) Collaborating with other insurance carriers (27:45) Product evolution and future outlook Resources: Connect with Kevin Cummer: https://www.linkedin.com/in/kevin-cummer-5b728b1a/ Connect with Nick Rohan: https://www.linkedin.com/in/nick-rohan-1337935/ Discover TruStage: https://www.trustage.com/ Connect with Olivier Lafontaine: https://www.linkedin.com/in/olivierlafontaine/

Steve Domin, Founder & CEO of Duffel, the company rebuilding the infrastructure layer of the global travel industry.Duffel is taking on one of the most complex and outdated sectors, creating modern, developer-first APIs for flights, hotels, and more. Backed by investors including Index Ventures and Benchmark, the company has raised over $50M to transform how travel is bought and sold.Steve shares the journey of building Duffel from scratch, including: Why the travel industry is fundamentally broken  The insight that led to Duffel's API-first approach  Building deep supply-side integrations with airlines and incumbents  Navigating COVID when travel demand dropped to zero  The painful reality of scaling, resetting, and rebuilding product-market fit  Where long-term defensibility comes from in complex infrastructure businesses We also explore: What makes companies like GoCardless “talent factories”  How AI is changing how modern engineering teams are built  The future of smaller, highly efficient companies  Steve's view on the next generation of AI-native products This is a masterclass in persistence, infrastructure thinking, and building through uncertainty.

Scott is with Brett Bohannon to talk about the fast-moving shift from basic AI chat tools to agent-driven Amazon workflows. They discuss Claude, OpenClaw, MCP servers, APIs, and how sellers can connect private catalog data, public marketplace data, and advertising insights into one AI-powered operating system. Brett shares how he uses AI agents to reduce repetitive Amazon tasks, audit catalogs, connect tools like Keepa and Data Dive, and build workflow automations for ads, inventory, and listing optimization. They also shed light on what this means for Amazon software, why unique data still matters, and how sellers can start using AI to solve specific operational problems instead of chasing every new tool.   Episode Notes: 00:09 - Intro to Brett Bohannon, Claude, and AI agents 01:40 - From custom GPTs to faster AI workflows 02:37 - Why recent AI progress feels different 02:55 - OpenClaw, AI agents, and business context 06:28 - Data Dive adapter for Claude and API data 07:18 - Three AI user levels: LLM users, builders, and MCP users 08:13 - How MCPs connect Claude with hosted or local data 09:49 - Combining Amazon tools under one AI workflow 12:33 - Using catalog data, Keepa, and niche analysis together 14:05 - Automating daily Amazon workflows 16:18 - Skill Create, GitHub, and open-source Amazon tools 17:45 - Replacing software with custom AI tools 19:31 - Maintenance tradeoffs with DIY AI workflows 20:08 - What stays valuable in Amazon software 22:57 - Talking to Amazon data inside Claude or ChatGPT 25:16 - Combining profitability, ads, and marketplace data 27:22 - Using agents to scale as a solo consultant 29:08 - Brett's Amazon background and catalog expertise 30:34 - Catalog audits using category listing reports 31:17 - Rufus scoring and listing data quality 33:38 - Helm and layered MCP workflows 34:25 - AI agents and the future of Amazon software   Related Post: How to Sell on TikTok Shop 2026 (Guide For Beginners)   LinkedIn: https://www.linkedin.com/in/brett-bohannon-1992329/ Website: https://voartex.com/   Scott's Links LinkedIn: linkedin.com/in/scott-needham-a8b39813 X: @itsScottNeedham Instagram: @smartestseller YouTube: www.youtube.com/@smartestamazonseller2371 Newsletter: https://www.smartscout.com/newsletter-sign-up Blog: https://www.smartscout.com/blog

In this episode, we sat down with Richa Gual, CEO of Complyance, the AI-first enterprise GRC platform that recently raised a $20M Series A led by GV (Google Ventures), to dig into how legacy GRC is finally being disrupted and what role AI agents play in that transformation.We discussed why GRC has lived in the dark ages for so long, stuck in static documents, snapshot-in-time assessments, system sampling, and self-attestations while the rest of IT moved to cloud, APIs, and automation. We unpacked the credibility crisis caused by commoditized compliance and rubber-stamp audits, the limits of the first wave of GRC automation, and what genuinely changes when agentic AI takes on evidence review, vendor risk, policy drafting, and customer trust workflows end-to-end.Richa shared Complyance's perspective on building agentic AI for the most sensitive data an organization holds, why explainability and isolation matter more in GRC than almost anywhere else, and how customers like Dropbox, CVS Health, and Major League Soccer are using AI agents to cut manual GRC work by 70% without lowering the assurance bar. We closed on what the next five years look like for the GRC workforce and whether the field can finally restore credibility to the phrase “compliance equals security.”

Harry Duran, founder of Fullcast and creator of Podisphere, joins Jeff Mains to explore what it really takes to build a sustainable podcast, grow a content brand, and stay ahead in a rapidly AI-shaped media world.Harry shares his journey from corporate marketing at JPMorgan Chase and E-Trade, to launching his first podcast Podcast Junkies in 2014, to building Fullcast — a podcast production and marketing consultancy that has helped over 130 business owners launch and grow shows. He also dives deep into his newest ventures: Podisphere (a G2-style SaaS directory for podcast tools) and Podclaw (an agent-first podcast hosting platform built for AI agents, not humans).The conversation covers the seismic shift happening in content creation right now — from vibe coding and Claude Code to autonomous AI agents that market products while you sleep. Harry and Jeff also discuss why long-form human conversations are becoming more valuable in an era flooded with AI-generated content, the power of niche podcasting, and why the most important skill for the next decade may simply be learning how to talk to robots.Key Takeaways0:00 — Intro: What it takes to build a podcast and a business around it in an AI-driven content landscape4:40 — Recap of previous guests: Justin Trombold on AI strategy and Rick Delisi on The Effortless Experience6:10 — Welcoming Harry Duran — how he helped launch SaaS Fuel and what Fullcast does9:50 — Harry's origin story: From JPMorgan Chase and Unilever to electronic music, DJing, and discovering podcasting at New Media Expo in 201413:30 — Meeting Pat Flynn and Amy Porterfield; pivoting from a DJ podcast to Podcast Junkies; recognizing podcasting as your own personal stage17:10 — How Harry's first paying client (a $1,000 PayPal from John Livesay) launched Fullcast in 201522:10 — Introducing Podisphere: A G2.com-style directory for podcast tools — the inspiration, the build journey, and why traffic is the only metric that matters to sponsors27:30 — Building with no-code tools (Airtable, Webflow, Bubble), the frustrations of non-technical founding, and how vibe coding changed everything in 202531:30 — Claude Code, Agent OS, and spec-driven development: how Harry built more in six months than in five years combined37:50 — SEO strategy for Podisphere: Fathom Analytics, Ahrefs, programmatic blog posts, Google Search Console, and hitting 7,000 page views/month without a press release45:20 — The power of founder relationships: How 12 years of Podcast Junkies led to meeting Andrew Mason (Descript), the SquadCast acquisition, and building a network that fuels Podisphere51:00 — Why every founder should have a podcast: relationship-building, opening doors, and earning "street cred"54:40 — Introducing Podclaw: An agent-first podcast hosting platform built for AI agents, not humans1:01:30 — Moltbook: The AI agent social network, digital wallets for agents, and autonomous marketing via cron jobs1:08:00 — The "agent economy" and why SaaS companies that block agents are "dead men walking"1:15:30 — Why the most important future skill is learning how to talk to robots; parallels to the dot-com era of 19991:21:30 — The future of podcasting: AI-generated shows, long-form authentic conversation, niche doubling down, and why human voices are becoming more valuable1:28:00 — NotebookLM and the rise of AI podcast hosts; the disclosure debate1:33:20 — Harry's personal operating system: morning meditation, written intentions, strength training, and protecting attention before screens1:37:30 — Where to find Harry: fullcast.co, thepodisphere.com, podclaw.ioTweetable Quotes"The most important skill in the future is learning how to talk to robots." — Harry Duran"You can't speak to someone for an hour and forget their face. That's the magic of podcasting — it builds relationships that nothing else can replicate." — Harry Duran"The people who made money in the gold rush were the ones who sold the picks, the shovels, and Levi's." — Harry Duran"Companies that block agents are dead men walking. If agents can't get the data from you, someone else will build what they need." — Jeff Mains"It never feels done — you just have to ship it. Get it out there." — Harry Duran"AI is like having the vision in your head and finally being able to build at the speed of thought." — Harry DuranSaaS Leadership Lessons1. Build Your Distribution Before You Need ItHarry spent over a decade building Podcast Junkies before it became the foundation of Podisphere. His relationships with founders like Andrew Mason (Descript) and the SquadCast team weren't accidental — they were built over 500+ interviews. Leaders who invest in platforms, relationships, and audiences compounding quietly are the ones who have leverage when they need it.2. Sell Picks and Shovels — Build for the EcosystemRather than fighting for space in a crowded software category, Harry positioned Podisphere as the infrastructure layer (the G2 of podcasting). Great SaaS leaders ask: What does this entire ecosystem need that nobody is building? Being a connector and aggregator often outlasts being just another point solution.3. Non-Technical Founders Must Learn to Build at the Speed of ThoughtHarry's journey from Airtable → Bubble → Fiverr developers → Claude Code is a roadmap for any non-technical founder in 2025. The bottleneck is no longer code — it's vision and prompting. The founder who can articulate their product clearly to an AI builds faster, iterates faster, and maintains greater ownership of the product direction.4. Traffic Is the Only Metric That Converts to Revenue — Build for Discovery FirstPodisphere hit 7,000 page views/month organically before a single press release by treating every page as an SEO asset. Harry obsessed over internal links, programmatic blog posts, and AEO (Answer Engine Optimization) for AI search. SaaS leaders building content or marketplace products should think like search engines think — not just build pretty interfaces.5. Agent-First Is the New Mobile-First — Design for It NowHarry didn't build Podclaw for human users. He built it for AI agents, complete with clean APIs, no unnecessary dashboards, and agent-friendly architecture. As agent economies emerge (complete with digital wallets and autonomous purchasing), SaaS products that block or ignore agents will be displaced. Build your API surface today like agents are your power users tomorrow.6. Protect Your Peak Performance Hours — Your Best Output Comes from Taking Care of Yourself FirstHarry meditates 20 minutes every morning, writes intentions in the present tense, and strength trains three days a week before opening a laptop. He's explicit: this is not a nice-to-have. The onslaught of screens, AI noise, and constant stimulation hijacks your nervous system. The leaders who perform at the highest level over the longest runway are the ones who treat personal maintenance as a non-negotiable operating system.Guest Resourceshttps://fullcast.co/hdbioEpisode SponsorThe Futureproof Series - https://www.youtube.com/playlist?list=PLfkXKUPZ5xuOqMPR7_gzGybncTtavyR1NThe Captain's KeysSmall Fish, Big Pond – https://smallfishbigpond.com/ Use the promo code ‘SaaSFuel'Champion Leadership Group – https://championleadership.com/SaaS Fuel ResourcesWebsite - https://championleadership.com/Jeff Mains on LinkedIn - https://www.linkedin.com/in/jeffkmains/Twitter - https://twitter.com/jeffkmainsFacebook - https://www.facebook.com/thesaasguy/Instagram - https://instagram.com/jeffkmains

Hello voices from the bench community, John Wilson here and I wanted to share some news about the evolution of the Programill lineup. Most importantly, Ivoclar's new PrograMill 7. What stands out right away is the reduced air consumption this mill requires, but what you'll notice first is that impressive new touchscreen. For us, the biggest advantage has been increased spindle power. My laboratory's known for these larger cases with complex geometries, and I can tell you that extra power really makes a difference. Next time you see your Ivoclar representative, be sure to ask about the PrograMill 7 and tell them John Wilson sent you. Thank you. At exocad Insights in beautiful Mallorca, we finally caught up with Felix from Imagine USA—and the timing couldn't have been better. As an exocad dealer on the front lines of digital dentistry, Felix shared his excitement about the strong turnout, the familiar faces, and most importantly, the innovation coming from exocad. What stood out most? The new exocad Hub and its cloud-based capabilities, along with powerful AI-driven tools inside DentalDB designed for efficient batch processing. For Felix and the Imagine team, it's not just about seeing what's new—it's about putting it to the test. By running new features through their own production facility first, they ensure real-world performance before bringing solutions to their customers. Beyond the technology, Felix emphasized the value of being there in person—connecting face-to-face with partners, having meaningful conversations, and stepping back to see where the industry is headed. And of course, doing it all in Mallorca doesn't hurt either. This week at the Dental Laboratory Association of Texas Meeting 2026, the microphones stayed hot as three completely different conversations all circled around the same thing: how fast the dental lab industry is evolving. First up, the crew sat down with Tony Aliatim from Axis Dental Milling to talk about going from biomedical engineering and printing silicone heart models for surgeons… to becoming one of the go-to names in dental milling. From industrial machining roots in Michigan to AI-powered calibration systems and Straumann plug-and-play workflows, Tony breaks down how VersaMill machines are helping labs mill everything from zirconia to implant abutments faster, smarter, and safer. Along the way, the conversation dives into HyperDent, trade show madness, wet vs dry milling nightmares, and why dental technicians may not realize how close this industry really is to aerospace-level manufacturing. Then things shifted from mills to maintenance with Rebekah Serrago and Chris Wilson from Garland Dental Services. What started decades ago as a garage-based repair business fixing handpieces has grown into one of the industry's best-kept secrets for equipment sales, service, and support. Rebekah shares the story of growing up folding flyers for her father's repair company before eventually becoming CEO and expanding Garland into a massive online sales and service operation supporting everything from ovens to mills. Chris joins in to talk preventative maintenance, service certifications, keeping ancient ovens alive, and why labs desperately need dealers that actually understand the equipment they sell. It's equal parts family-business story, repair shop wisdom, and hilarious behind-the-scenes dental lab banter. Finally, the future officially arrived when the podcast crew sat down with Antoine Coppens from Relu and orthodontic lab owner Christian Saurman of New England Orthodontic Laboratory. What started as four engineering students experimenting with AI in Belgium somehow turned into fully automated dental workflows capable of designing surgical guides, night guards, models, and restorations in minutes. The conversation explores how AI is reshaping lab workflows, reducing manual design time, integrating directly into LMS systems, and even learning individual lab preferences. Christian explains how his custom-built orthodontic lab management system helped eliminate workflow chaos and automate huge portions of production, while Antoine gives a fascinating look into where dental AI is headed next. Between AI-generated appliances, automated scan checks, and self-learning workflows, this episode feels less like science fiction and more like a preview of what labs will look like over the next five years.Special Guests: Antoine Coppens, Chris Wilson, Christian Saurman, Rebekah Serrago, and Tony Aliatim.

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)

Episode 428 of The VentureFizz #podcast features Mike Pappas, CEO & Co-Founder of Modulate. Is Boston the best place to build a voice AI company? Based on its rich history in this category, I would have to say 1000%. From the early days of ScanSoft and Dragon to SpeechWorks and Vlingo—all of which eventually fell under the voice juggernaut Nuance, which worked on the early days of Siri and was acquired by Microsoft—the pedigree in this city is unmatched. Add in players like Bose, Vivox, and the sizable presence of Amazon Alexa in the area, and it's clear: Boston is the voice capital of the world. Mike Pappas and his co-founder Carter Huffman are adding a massive new chapter to that legacy and thatis Modulate, a venture-backed voice intelligence company building AI models and APIs designed to understand real-world conversational audio at scale. Modulate is the company behind ToxMod, the world's most advanced proactive voice moderation platform. If you've played Call of Duty lately, you've likely interacted with their tech. And, the company recently launched a new product called Velma, the leading AI-platform for real-world voice intelligence. In this episode of our podcast, we cover: Mike's perspective on the shift from license-based to usage-based pricing models. Mike's background story—from his physics studies at MIT to his early career at Bridgewater Associates. Entering "startup land" at Lola and the critical hiring lessons he learned while working alongside Paul English. The founding of Modulate and the pivotal moment when they realized the tech they built was actually the solution to a massive safety problem in gaming which led to a relationship with Activision. All the details about ToxMod and Velma, including customer examples and use cases. Why their dataset is a "moat" that makes their technology uniquely defensible in the age of generic LLMs. Mike's advice for first-time founders on raising capital and building a high-performance culture. Plus, so much more! This podcast is brought to you by one of the strongest longtime supporters of the local startup ecosystem, Silicon Valley Bank, a division of First Citizens Bank. With more than 1,500 bankers and relationship advisors and $44B in loans as of Q4 2025 – SVB delivers expert guidance, specialized products and a team that knows the innovation economy inside and out. Learn more at SVB.com.

Muy bien, vamos a por otro resumen trimestral, en cuatro de las secciones habituales (ePrivacy y marco regulatorio; MarTech & AdTech; IA, competencia y mercados digitales; y futuro de los medios).Entre otras cosas, hoy tratamos:* Verificación de edad en sus múltiples variantes y la evolución de la prohibición de medios sociales para menores* Memoria de actividad de la AEPD* Directrices varias del EDPB* Campañas en ChatGPT, píxeles y APIs de conversión* Píxeles de apertura en correos electrónicos (Francia, Italia)* Nuevas directrices ICO para ePrivacy (analytics, A/B testing, etc.)* Multas y juicios en California (Meta, General Motors).Hemos incluido las notas detalladas del episodio y todos los links o referencias en un post específico, como siempre, aquí disponible. This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit www.mastersofprivacy.com/subscribe

On this week's episode of The MacRumors Show, we discuss Google's latest wave of announcements for Android and Gemini, the newly announced Fitbit Air, and Apple Watch Series 12 rumors.The centerpiece of Google's announcements this week was Gemini Intelligence, Google's new umbrella platform for AI across phones, watches, cars, and laptops. Its headline capability is cross-app automation: users can photograph an event flyer and ask Gemini to find tickets on Expedia, or pull up a grocery list and have it build a cart in a shopping app. A companion feature called Create My Widget lets users describe a home screen widget in natural language and have Gemini generate it, drawing from Gmail and Calendar to build a personalized dashboard.Google also unveiled the Googlebook, a new laptop category designed from the ground up around Gemini with partners including Acer, Asus, Dell, HP, and Lenovo arriving this fall. Gemini in Chrome for Android gained an agentic browsing layer rolling out end of June, and Android Auto received AI-generated contextual replies and DoorDash voice ordering. A Meta partnership brings Ultra HDR, native stabilization, and night mode to Instagram on Android flagship devices.In January, Apple and Google announced a partnership under which Gemini would power the next generation of Apple Foundation Models, including a more personalized Siri expected this year. Apple's equivalent cross-app ‌Siri‌ actions were announced at WWDC 2024 but have not yet shipped; Gemini Intelligence is rolling out this summer using the same underlying technology.Google also unveiled the Fitbit Air this week, a screenless fitness tracker priced at $99 that ships on May 26. The device weighs just 12 grams with the band and tracks heart rate, AFib, HRV, SpO2, and sleep stages in a pill-shaped pebble with no display, no buttons, and no notifications. Battery life lasts for seven days, with a five-minute fast charge delivering a full day of use. A Stephen Curry Special Edition is priced at $129, with core tracking free and Google Health Premium adding an AI Coach for $9.99 per month after a three-month trial.The launch accompanies a broader rebrand. The Fitbit app becomes Google Health on May 19, with Google Fit folded in, Apple Health data supported on iOS, and APIs for Garmin, Whoop, and Oura. Bloomberg's Mark Gurman reported earlier this year that Apple has scaled back a comparable Health+ coaching service, with the feature now unlikely to launch. The Apple Watch SE starts at $249 and requires daily charging, and the Fitbit Air's $99 price with no mandatory subscription addresses a segment Apple does not cover.We also discuss the Apple Watch Series 12, which is shaping up to be an incremental upgrade. Bloomberg's Mark Gurmansaid in March that he does not expect any major design changes, and a significant redesign is now not expected until 2028.The leaker known as Instant Digital said this week that Touch ID, which appeared in leaked Apple code last year, has been deprioritized in favor of battery life improvements. DigiTimes previously reported an eight-sensor array on the back of at least one 2026 model, though blood pressure monitoring is said to be further out. A new chip is expected, with leaked code indicating a meaningful upgrade from the S10 used across the last three series, and watchOS 27 will be previewed at WWDC on June 8. Start your business with Shopify and get everything you need to sell online and in person. Start today at https://www.shopify.com/mac

In this episode of Business Brain, we unpack why so many websites still have terrible search even with AI everywhere — and it comes down to tokens. We break down what a token actually is, why feeding an LLM your entire knowledge base on every customer query gets expensive fast, and how the math changes dramatically depending on which model you choose. A real-world example shows the difference between a $2.5M-a-month implementation and a $25K one running on a leaner model. The takeaway: figure out what it’ll cost to leverage AI against your existing customer data, then decide if the lift is worth it. Then we dive into xAI’s new Grok Custom Voices feature, which clones our voice from roughly 90 seconds of audio and plugs into text-to-speech and voice agent APIs. We riff on the Charmed Life use cases — turning written posts into audio versions for drivers, recording sponsorship reads without the edit pass, voicing phone trees in our own brand voice, and keeping content flowing even when our actual voices are blown out from too much mic time. Voice cloning is either already here or very close, and we’re going to test it in the coming weeks. 00:00:00 Business Brain – The Entrepreneurs' Podcast #753 for Casual FridAI, May 15, 2026 May 15th: Customer Experience Day 00:01:19 AI compute tokens: Using AI/LLM for search and customer service in your business Sponsors 00:10:54 SPONSOR: Bitdefender. Keep your small business safe with Bitdefender Ultimate Small Business Security. Save 30% when you go to https://bitdefender.com/BRAIN 00:12:25 SPONSOR: Shopify – For anyone to sell anywhere, sign up for a one-dollar-per month trial period at https://Shopify.com/BusinessBrain and upgrade your selling today! 00:13:52 Grok's new voice cloning 00:17:55 This episode's Big Takeaway for Business Blueprints: Figure out how to use AI to leverage your business's existing data 00:21:57 Business Brain 753 Outtro Check out Business Brain Blueprints Tell Your Friends! Business Blueprints Review Business Brain Subscribe to the show feedback@businessbrain.show Call/Text: (567) 274-6977 X/Twitter: @ShannonJean & @DaveHamilton, & @BizBrainShow LinkedIn: Shannon Jean, Dave Hamilton, & Business Brain Facebook: Dave Hamilton, Shannon Jean, & Business Brain The post FridAI – Tokens + xAI Voice Cloning – Business Brain 753 appeared first on Business Brain - The Entrepreneurs' Podcast.

Google Cloud customers are reporting shocking surprise bills after compromised or misused API keys were allegedly used to access expensive Gemini AI services. In one case, Rod Dinan says his monthly Google Cloud costs jumped from under $50 to nearly $8,000. Sydney developer Isuru Fonseka says he was hit despite setting spending controls, raising broader questions about API key security, client-side exposure, billing alerts, and how quickly attackers can exploit AI infrastructure. Cybersecurity Today also covers prosecutors' allegations that two fired brothers sabotaged systems tied to government-related work after access wasn't revoked quickly enough, Santa Clara County's civil lawsuit accusing Meta of profiting from scam ads on Facebook and Instagram, and Horizon3.ai's warning that attackers can exploit newly exposed systems in as little as 73 seconds while many organisations still take 24 hours or longer to respond. If your organisation uses APIs, AI services, cloud billing controls, or internet-facing infrastructure, this episode matters. #Cybersecurity #GoogleCloud #GeminiAI #APIKeys #CloudSecurity #Meta #ScamAds #CyberAttack #CybersecurityToday #AIsecurity CHAPTERS 00:00 Google Cloud API Key Bill Shock 01:20 Real-World Victims: Surprise AI Charges 02:24 Why Spending Caps Didn't Stop the Damage 03:38 The Enterprise Cloud Security Risk 04:19 Fired Employees and Alleged Insider Sabotage 04:55 The Database Destruction Timeline 06:34 What This Incident Teaches Security Teams 07:10 Santa Clara County Sues Meta Over Scam Ads 08:46 Attackers Can Strike in 73 Seconds 10:14 Closing and Next Episode

In today's Cloud Wars Minute, I unpack SAP CTO Philipp Herzig's perspective on AI, APIs, and the company's next era beyond traditional software. Highlights 00:01 — As part of our ongoing analysis of the massive changes that SAP rolled out this past week at their Sapphire event in Orlando, I had an interesting one-on-one conversation with SAP Chief Technology Officer Philipp Herzig, where he discussed a range of things. Particularly this notion of how, as SAP begins to move beyond applications into the realm of AI, what that means across everything from their new Business AI platform [to] updates to their API policy.   00:37 — I think some people got their knickers in a knot unnecessarily over those API changes and the general pace of innovation that not only SAP is cranking out, but that customers are working very hard to consume so that those customers can become leaders in their industries. 01:24 — How does this shape the company that SAP is becoming in the future? And even as talked about with CEO Christian Klein posing the question during his keynote, will SAP be a software company in the future? 02:07 — One of the things that Herzig said was, we've got so many more people using more and more of our APIs, agents are going to access data from all across the company, and certain things just have to be tightened up. One of the biggest things [SAP] did, was try to ensure that there's more security. 03:20 — So, lively discussion here. I think this was a momentous event for SAP, the things they introduced, the way they're talking about going to market, the new sorts of expertise they're putting in. Philipp touches on a lot of this and gives a good insight into the foundational technology layer. Visit Cloud Wars for more.

On this episode, the guys discuss Google's announcement of the new "Googlebook" (a reported merge of Android and Chrome OS), growing controversy and litigation around iReady and screen time in schools, and a debrief of the recent Canvas/Instructure security incident with guest Michael Klein from the Institute for Security and Technology. Unofficial demo of AluminumOS: https://youtu.be/dXmFIfv_tIA?si=Baw0OInBqJf-IkDD The largest segment is a deep dive into the Canvas/Instructure incident with cybersecurity expert Michael Klein. He walks through the timeline (initial unauthorized activity detected April 29; exfiltration via cross‑site scripting of a free‑for‑teachers account; a later attack that posted extortion notes to some users), the involvement of CrowdStrike, the public claims by the ShinyHunters group, and Instructure's statement about an agreement with the actor. The conversation covers the technical nature of the attack, impacts on confidentiality, integrity and availability (including disruptions to finals/registrar functions), the downstream consequences for integrations with SIS and other edtech systems, and why many institutions remain cautious to reconnect APIs. Michael and the hosts discuss practical guidance and explore policy implications. Join us July 6th-10th, 2026 – GAMEIS Conference in Savannah, GA ———— Sponsored by: SysCloud Meter Fortinet Incident IQ ClassLink NTP ———— Join the K12TechPro Community (exclusively for K12 Tech professionals) Buy some swag (tech dept gift boxes, shirts, hoodies...)!!! Email us at k12techtalk@gmail.com OR our "professional" email addy is info@k12techtalkpodcast.com X @k12techtalkpod Facebook Visit our LinkedIn Music by Colt Ball Disclaimer: The views and work done by Josh, Chris, and Mark are solely their own and do not reflect the opinions or positions of sponsors or any respective employers or organizations associated with the guys. K12 Tech Talk itself does not endorse or validate the ideas, views, or statements expressed by Josh, Chris, and Mark's individual views and opinions are not representative of K12 Tech Talk. Furthermore, any references or mention of products, services, organizations, or individuals on K12 Tech Talk should not be considered as endorsements related to any employer or organization associated with the guys.

The integration and impact of advanced artificial intelligence, specifically focusing on Anthropic's Claude 4.7 and its deployment through Microsoft Foundry. Claude Opus 4.7 is highlighted as a premier model for agentic coding, enterprise workflows, and complex reasoning, featuring a 1-million token context window and high-resolution vision. Technical documentation details how developers can utilize Microsoft Foundry to deploy these models using managed compute or serverless APIs while adhering to Responsible AI standards. Beyond technical specs, news reports discuss the broader industry shift toward "vibe coding," where natural language replaces traditional syntax to accelerate software creation. Market analysis also covers the competitive landscape, including Cerebras Systems' massive wafer-scale hardware and its multi-billion dollar partnership with OpenAI. Together, the texts provide a comprehensive look at the AI lifecycle, from specialized hardware and model infrastructure to the evolving practices of digital development.

Special discounts up for AIE Melbourne (LS discount) and AIE World's Fair (group discounts up to 25% - CFPs still open for Autoresearch and Vertical AI) Cya there!Abridge did not start as an “GPT wrapper”. It was founded in 2018, years before the Cambrian explosion of AI application layer companies. OpenAI launched ChatGPT publicly on November 30, 2022 and by then, Abridge had already spent years doing the unglamorous work of building trust for one of the highest context, most important workflows in healthcare: the conversation between a patient and a clinician.Abridge's original wedge was clinical documentation. Listen to the visit, generate the note, reduce the clerical burden, and let clinicians spend more time with patients instead of the EHR. By focusing on how doctors actually document, how health systems actually buy, how EHR integration actually works, how clinicians verify outputs, and how missing context during a visit turns into downstream friction across billing, prior authorization, quality, and follow-up, the adoption of LLMs became a force multiplier on a workflow already optimized for sensitive context gathering.The company has scaled fast: Abridge says it is projected to support 80M+ patient-clinician conversations this year across 250 large and complex U.S. health systems, with support for 28+ languages and 50+ specialties. It raised $300M at a $5.3B valuation in June 2025, after a $250M round earlier that year.Today, Janie Lee and Chaitanya “Chai” Asawa of Abridge join us for another crossover pod with Redpoint's Jacob Effron (who is on the board of Abridge) to dive into how Abridge is building the clinical intelligence layer for healthcare starting with ambient documentation, then expanding into clinical decision support, prior authorization, payer/provider/pharma workflows, and eventually real-time agents that act before, during, and after the patient conversation. We go inside the product, data, infra, evals, workflow, privacy, and org design choices behind bringing AI into one of the highest-stakes enterprise environments from 100M+ medical conversations and specialty-specific evals to real-time alerts, EHR integration, de-identification, clinician-scientist teams, and why healthcare may solve some of the hardest AI problems first.We discuss:* Why Abridge started with clinical documentation, “pajama time,” and saving clinicians 10–20 hours a week* The transition from ambient scribe to clinical intelligence layer: save time, save money, and save lives* Why conversations between patients and clinicians may be the most important workflow in healthcare (patient visit summary feature)* Chai's “healthcare-coded Glean” framing: context is king, but healthcare raises the stakes on safety, evals, and rollout* Why Abridge wants AI to feel like “air conditioning”: always in the background, but only interrupting when it truly matters* The prior authorization example: turning a denied MRI weeks later into real-time guidance while the patient is still in the room* Why payer policies, EHR data, medical literature, and hospital-specific guidelines make the problem hard, and also create the moat* How Abridge thinks about ambient form factors: mobile, desktop, in-room devices, nursing workflows, multimodality, and future AR* The multi-sided healthcare customer: CMIOs, CFOs, CIOs, clinicians, patients, payers, and pharma* The hardest AI problem at Abridge: high-quality, low-latency, low-cost real-time support in a high-stakes clinical setting* When Abridge uses frontier models vs proprietary models, and why its unique data from medical conversations matters* Why “every agent is a coding agent underneath,” and how the EHR can be thought of as a filesystem for healthcare agents* How Abridge approaches personalization across individual doctors, specialties, and health systems* Why “AI slop” is AI without context, and how edits, memories, and clinician preferences create a data flywheel* Abridge's eval stack: LFDs, LLM judges, in-house clinicians, third-party evaluators, specialty-specific evals, and progressive rollout* HIPAA, PHI, de-identification, one-way anonymization, customer contracts, and learning from healthcare data safely* What changes when you operate at 100M+ conversations: reliability, cost, post-training, model routing, and infrastructure optimization* Why the same clinical conversation can serve doctors, patients, payers, pharma, and future clinical-trial workflows* How Abridge works with EHRs, and why deep interoperability is table stakes for clinician adoption* Why healthcare AI has regulatory tailwinds, why 80/20 does not work here, and why high-stakes domains may drive AI forward* Why Abridge embeds “clinician scientists” into product and eval teams* What Chai learned from Glean about search, quality, and durable AI infrastructure* Why the future of AI infra may look like context layers, event-driven systems, Kafka, Temporal, sockets, CRDTs, and tools built for humans* Why Janie changed her mind on “PRDs are dead,” and why crisp written clarity matters more in complex AI products* How Abridge uses Claude Code, Cursor, and coding agents internallyAbridge:* Website: https://www.abridge.com/* X: https://x.com/AbridgeHQJanie Lee:* LinkedIn: https://www.linkedin.com/in/janiejleeChaitanya “Chai” Asawa:* LinkedIn: https://www.linkedin.com/in/casawaTimestamps00:00:00 Introduction and what Abridge does00:02:05 From ambient documentation to clinical intelligence00:04:04 Clinical decision support and context as king00:06:57 Alert fatigue, proactive intelligence, and prior authorization00:12:36 Ambient AI form factors and healthcare customers00:16:59 The hardest AI problems in healthcare00:18:26 Frontier models, proprietary data, and model strategy00:21:07 The EHR as a filesystem for agents00:24:03 Personalization, memory, and clinician preferences00:30:40 Evals, LLM judges, and progressive rollout00:36:47 HIPAA, de-identification, and privacy00:39:21 100M conversations and operating at scale00:44:10 EHR integration and the clinical intelligence layer00:46:39 Healthcare regulation, latency, and high-stakes AI00:50:11 Clinician scientists and long-tail quality00:53:04 Lessons from Glean and durable AI infrastructure00:57:03 The future of agentic healthcare workflows00:57:34 PRDs, product clarity, and building serious AI products01:03:11 AI coding tools at Abridge01:04:06 OutroTranscriptIntroduction: Abridge, Clinical Intelligence, and the Latent Space x Unsupervised Learning CrossoverSwyx [00:00:00]: Okay. This is a special crossover Latent Space Unsupervised Learning pod.Jacob [00:00:07]: Very excited to do this.Jacob [00:00:08]: At this point, we get together once a year.Swyx [00:00:10]: Once a yearJacob [00:00:11]: And this is a fun occasion to get to do it on.Swyx [00:00:13]: I really wanted to talk to Abridge but I felt very underqualified because healthcare is not something we cover very intensely. It just so happens that Redpoint's our big investors and supporters of Abridge.Jacob [00:00:27]: Anytime you want to have a portfolio company on your podcastJacob [00:00:29]: Please, by all means.Swyx [00:00:31]: So we'll introduce our guests. Chai and Janie, welcome to the pod.Janie [00:00:34]: Thanks for having us.Chai [00:00:35]: Thank you.Janie [00:00:35]: We're excited to be here.Chai [00:00:36]: Thank you.Swyx [00:00:36]: So for listeners, what do you guys do, just to situate you guys in the company?Janie [00:00:42]: Abridge is a clinical intelligence layer for health systems. We really started with documentation and building for clinicians and as we think about reducing the burden that clinicians have, they're spending 10 to 20 hours a week on documentation. There's a massive doctor shortage in the country. We also think that conversations between patients and clinicians are probably the most important workflow in healthcare. It's where care is given and received but if you think about the 20% of our GDP that goes towards healthcare, almost everything is a derivative of that conversation, whether it's the claim, the payment, the actual diagnosis given, the treatment. And we've started with a conversation to reduce the burden for doctors on documentation but we're really excited about the path ahead as we become this broader clinical intelligence layer.Chai [00:01:34]: I'm Chai. I work on clinical decision support at Abridge.Swyx [00:01:37]: Yes.Chai [00:01:37]: And so as Janie said, we're uniquely situated where we started off with the clinical note. What I'm really excited about and where we're expanding towards is what are all the things you can do before the conversation, during the conversation and after the conversation if you did have access to all the context about patients, payer guidelines, medical literature and put that together and to serve, how healthcare could look fundamentally different.Swyx [00:02:01]: And that's the context engine that you guys have?Chai [00:02:04]: Yes.Swyx [00:02:04]: Is that what it's called? Okay.Swyx [00:02:05]: So historically, as I understand it, the company started in 2018. A lot of people would be familiar with the AI voice notes form factor that doctors would be “Well, do you consent to being recorded?” It replaces handwriting and what have you. But it sounds like more recently there's been a big transition in the company. Tell me about the broader transition.From Documentation to Clinical Intelligence: Save Time, Save Money, Save LivesJanie [00:02:26]: So from a transition perspective, we really think about our journey as The first act was: how do we help save time? And that's where a lot of that original product was.Swyx [00:02:37]: By the way, one of those interesting statsSwyx [00:02:39]: On your landing page was, doctors spend time after hours.Janie [00:02:43]: They call it pajama time.Swyx [00:02:44]: Why is that pajama time?Janie [00:02:46]: Doctors after work in their pajamasSwyx [00:02:48]: In their pajamas. OhJanie [00:02:49]: At home are just writing and catching up on their notes every day.Janie [00:02:53]: Some of our favorite customer love stories, we have a Slack channel called Love Stories. We have clinicians telling us, “Abridge has helped us, from retiring early or we're now finally able toJanie [00:03:06]: go home and eat dinner with our kids for the first time.”Chai [00:03:08]: Save the marriage in some cases.Swyx [00:03:10]: One of the quotes was “We're not divorcing anymore.”Swyx [00:03:12]: I'm asking, “Why?”Swyx [00:03:14]: Because they're working too much.Janie [00:03:16]: But, in terms of where we're going and where we're expanding, we really think about our second and third acts around how do we help health systems save and make more money. Health systems are operating with record-low operating margins. It's getting harder and harder to serve patients and they have regulatory, some tailwinds but also a lot of headwinds coming their way and AI is ripe for helping on the saving and make-more-money piece. And then ultimately, how do we help save lives? The fact that our software and our product is open millions of times a week before, during and after a patient walks in the room, gives us massive opportunity with products like clinical decision support, which Chai is building but so many others to improve patient outcomes and probably one of the most important workflows and problems to be going after right now.From Glean to Healthcare: Context Is KingJacob [00:04:04]: One thing that's interesting, Chai, is you came over to Abridge from Glean and clinical decision support, which for our listeners is, in the context of a visit, helping a doctor figure out the right type of care. It's really a search problem in many ways, going through lots of different data sources. Very analogous to your previous role as one of the earliest engineers over at Glean. I'm sure a lot of our listeners are curious what's similar about the problems that you're going after now and what feels different, now that you're in healthcare.Chai [00:04:33]: Very similar. Taking a step back, with every wave, there's a lot of very similar patterns that happen across different products. A lot of social networking products look the same. A lot of credit-based products look the same. And we're seeing that very similar in the agent era with many companies, of course, in Redpoint's portfolio and so forth. And the key insight between both companies is that you have amazing models but context is king. Context is what puts them to work. So I see it in a lot of ways, a lot of similarities in this is a healthcare-coded version of Glean but the differences are really interesting. A couple things that come to mind. First and foremost, the rigor of the setting we're in. The downside risk is extremely high here in healthcare. It can be fatal in some cases. You prescribe something that the patient is allergic to for example. Whereas at Glean, it's “Oh, you got the question wrong.” It wasn't the end of the world in most cases. And so what does that mean? That shapes our evaluation strategy, both offline evaluation, progressive rollout and there's a lot more we could go into there. Second thing that comes to mind is, vertical versus horizontal. In both cases, there's a large variance but when Glean is, it's a much more horizontal company, there's a variance of personas, companies that you're working with. We also have a variance of personas, different types of specialties, different hospital systems. But the variance is a little more narrow. So from a product perspective, you're able to focus far more, especially when you have a maturing technology and you're building new products that never existed before. It lets you go after them much more easily and especially in healthcare where so many problems were solved with labor and process, that it's extremely ripe for AI to keep helping augment and enable. And the final thing that's really interesting, Abridge specifically compared to many other companies in the AI area, is the modality we started with where we're ambient and we're always listening in the background. And many more AI products will go that way but it's how we started. And that's the greatest form of AI we can create, AI that's seamless. You're not looking at your screen. It's always there. It's always helping you out and being proactive. The Jarvis vision that, every hackathon I went to over the past decade, there was always a Jarvis competitor. But Abridge very much started from the opportunity and continues to go that way.Ambient AI and Alert Fatigue: When Should the Product Interrupt?Jacob [00:06:57]: One thing that is super interesting then from a product perspective is you have this always-on seamless in the background and then you have to decide when you break the wall almost and say, “Hey, clinician, you might not have thought about X,” or whatever it is that you want to do. And in healthcare traditionally there's been this idea of alert fatigue and a million pop-ups and then a doctor just ignores all of them. It's probably a pattern that a lot of builders are thinking through now. How do you think about the right way to intervene or to pop up in a doctor visit?Janie [00:07:26]: It's such a good question. Alerts are notorious in healthcare specifically. Over 90% of alerts are ignored. The first and most important thing is context is everything, as Chai alluded to and I also think about how do we go from being reactive alerting to really proactive intelligence at the point at which it matters most. One thing we like to say is we want our product to feel like air conditioning. It should be in the background just making things better and if there is something that has great clinical risk and we're acutely aware that intervening now and not later is incredibly important, we should decide to act. But if you think about proactive versus reactive, instead of alerting a clinician during a visit when they're with their patient having a pretty serious and sensitive conversation, how do we prep a clinician before they walk into the room with that patient? And so historically, clinicians might have to manually go through charts with a patient that they've had over the course of months or years and they'll try to suss out what are the things they should be doing. You can imagine a world with Abridge. We'll summarize all of the most recent context for you, tell you based on the reason for a visit the patient is coming in for the types of things you should be discussing. And so you're going into that conversation prepped rather than walking in cold to that patient visit and then having this product interrupt you five or 10 times throughout the visit. And there might be times where it's really important to interrupt. We have a product called Prior Authorization and so this is when you may go into a doctor's office with knee pain. They'll prescribe you an MRI and so many of us have had this experience before, where in four weeks you'll get a call saying, “Hey, Sean, that MRI that you were prescribed wasn't approved and why don't you come back in? We'll figure it out.” In a world with Abridge, we might choose to quietly but still alert a doctor in that visit. And alert is probably not even the word we would want to use. Before a patient leaves, we would want to tell the doctor, “Hey, Doctor, before Sean leaves, you should ask him, has he had physical therapy and has his pain lasted for more than six weeks? Because the Aetna plan that he's on in California requires six things. We've already confirmed four of them have been met ‘cause we have all the context. But these two last criteria, if you can address with Sean before he leaves the room, we could guarantee that your MRI is approved before you leave.” And so when you think about clinical usefulness, impact to the patient, there are instances in which if we can catch a doctor while the patient is still in the room, as we think about save time, save money, save lives, we get to check all of those boxes. But when doctors have 15 minutes between visits, we have to be really thoughtful about when it matters.Prior Authorization: Reducing Latency in CareChai [00:10:23]: There's this interesting product opportunity AI has is reducing latency in the world. For example, prior authorization is an example of where care gets delayed and so great AI can reduce that. And the problem with alerts before partially is a technical problem: the quality of your alerts really matters. They're going to get ignored if you get alerts that... Similarly in engineering, where they're noisy alerts that you can't act on. But if you can make really high-quality alerts with both the context, as Janie said, and really high-quality models, then you can create a whole other game.Janie [00:10:53]: And I really like that experience because it starts to tease apart, what makes this so hard and unique. One, to make that prior authorization example possible, think about all the data that you need to have. You need to integrate with the electronic health record to know all of the patient context. Do we have access to your previous labs, previous imaging? And then to match you and to know that you're on Aetna, we have to collect all of the different payer policies and they vary by state. Some of these payer policies live on websites. Some of them live in unstructured 50-page PDF files.Jacob [00:11:31]: I thought this episode wasJacob [00:11:31]: To make sure we didn't scare people from healthcare.Janie [00:11:34]: But when you think about the things that make it hard, it also gives you the moat.Janie [00:11:39]: And then the second is the AI and the model quality we need to be able to hang our hat on. And so the bar, similarly when I worked at Opendoor, I worked on pricing models. Every outlier wiped out the margins of 30 and so similarly here in healthcare, the bar for accuracy is so high. And then I'd say the last is workflow is everything. If insurance companies deploy AI, it typically happens too late and this is when you have the notorious comical examples of AI just fighting each other when it's too late. But if we can pull forward the use of both the AI but also the ability to solve problems when the patient's in the room, you can start to collapse what typically takes weeks or months after your visit, ideally down to minutes or real-time. And it's where healthcare is both very difficult but also extremely rewarding if you can crack it.Product Form Factors: Mobile, Desktop, In-Room Devices, and ARSwyx [00:12:36]: Just to get some baseline on the form factors, because I've seen some videos on your website and stuff. You guys talk a lot about ambient AI. Is it primarily on the phone? Is there any other form factor that people get Abridge in? Is there an Abridge room setup where it's always on? I don't know.Jacob [00:12:55]: An Abridge podcast studio.Janie [00:12:58]: Primary form factor is mobile and desktop. UsuallyJanie [00:13:00]: Clinicians are walking in and out of rooms with mobile but at the end of the day, when they're closing out their notes or wanting to prep for the day ahead, they might use desktop. We have been having a lot of really interesting partnership conversations with a lot of these in-room device companies as you think about the power of multimodality and even more data, as you think about all of what is not captured today. It is fascinating to think about, especially even as we go into building and scaling our nursing product. It's one where nurses constantly, as they're walking in to check in on a patient for two minutes or maybe even 30 seconds,Janie [00:13:43]: Starting an Abridge experience is probably going to take longer than the visit. And so what can we do with in-room devices that are always on starts to raise really interesting and fun product questions.Swyx [00:13:54]: I was thinking, the way in tech companies we have all these Google MeetSwyx [00:13:58]: And other things, we might as well set up entire rooms with just Abridge tech.Chai [00:14:02]: Very much. AR glasses and related form factors are also relevant: how do we bring the information to the clinician in real-time without a screen, while still letting them focus on the patient?Swyx [00:14:18]: Do you think they want that? I'm skeptical of AR, but I'm curious what you've tried.Chai [00:14:26]: Admittedly, it's not a near-term product roadmapChai [00:14:29]: By any means. I'm being far-fetched.Jacob [00:14:31]: There's some sick AR stuff for surgeries.Swyx [00:14:33]: Really?Jacob [00:14:33]: When people are trying to visualize, you're about to make an incision but you want to see, what the cut might look or what the body might look like inside and they can layer in imaging.Swyx [00:14:43]: That's cool.Chai [00:14:45]: At some point in the future.Janie [00:14:46]: But there are a lot of our largest customers and at the largest health systems integrating already and so even as we think about building into it, unlocks a lot of product capabilities.Swyx [00:14:57]: And just to establish the terminology. Sorry, and I know I'm asking basic questions somewhat for myself but also for the audience who might beHealth Systems, Buyers, Clinicians, Patients, and PayersSwyx [00:15:05]: Less integrated. When you say health systems, it's like the Johns Hopkins, the Kaiser Permanentes.Janie [00:15:09]: Mayos, the Kaisers of the world.Swyx [00:15:10]: These are your customers, right? And the outcome that you deliver for them is happier doctors, reduced cost of processing, reduced mistakes. It's weird in a sense that I feel like there's also, a secondary customer, the customer of the customer and I don't know if you — do you think about it that way?Janie [00:15:28]: The other interesting and complex part of building product is we have our buyers, who are the chief medical information officersJanie [00:15:39]: The chief financial officers, the CIOs of these large health systems. Our users today are clinicians but if you think about who downstream is impacted, it's patients. And so as we build, with every product in mind, we think about who we're building for, who the secondary user is and what does that mean either in terms of experience, security compliance, ROI that we have to make tangible. And so like you said, time savings is one of them. But for CFOs, they care a lot more than just time savings. We have to show for every dollar you put into Abridge, because you have more compliant documentation or because you have fewer queries coming from your billing team, we save or add real dollars to your bottom line or top line, are things that we're constantly thinking about because of the dynamic across all three sets of users.Chai [00:16:32]: There's a whole other axis too with the payers and pharmaChai [00:16:35]: as well. Connecting all these three big stakeholders in healthcare isSwyx [00:16:39]: Do the payers ever see your data? Sorry, the payers meaning the insurers, right?Chai [00:16:44]: Yes.Swyx [00:16:44]: They also see Abridge data?Chai [00:16:47]: NoSwyx [00:16:47]: Like the direct integration to you guysChai [00:16:48]: They wouldn't see the raw Abridge data but when you're working together on something like prior authorization, whatever information they need, we'd communicate to them.Jacob [00:16:59]: That's cool. I would love to dig into the AI side. You still have a lot of problems on the AI side. And so maybe to start at the highest level, what's one of the hardest problems you have to solve in AI at Abridge today?The Hardest AI Problems: Quality, Latency, and CostChai [00:17:11]: To make things simple, let's take, building off the prior auth example. So one thing Janie talked about is okay, this data is all over the place and there's this combinatorial explosion of procedures, payer policies and even sometimes different health systems. There can be some cross-product of all of these different considerations you have to take into account. But what's really hard about this problem is doing it real-time in the conversation. So, in any AI product, usually the three KPIs you care about are quality, latency and cost. Now, what we're saying is we want you to do this real-time in the conversation, guiding the clinician. How do we do it in a way that does not break the bank? But we're using — But we also need very intelligent models because you're working with this cross-product of data and this, all this context layer as well. So you need high intelligence and high-quality because you don't want the alert fatigue but you also need to be fast and cost-effective. And so that's where a lot of clever engineering goes. It's okay, without getting into all the details here, can you model these policies in some intermediate representation or other things that you can do that can make this problem tractable? And of course, the Pareto frontier is always changing but we are also trying to do this now.Model Strategy: Third-Party Models, Proprietary Data, and Medical ConversationsJacob [00:18:26]: What implications has that had for what you take off-the-shelf and say, “ what? We don't need to be world-class at X. We'll just take this from the model providers or from some infrastructure player,” and what you're “No, this is where we spend most of our time focused on”?Chai [00:18:38]: This is, the fun challenge in AI?Jacob [00:18:42]: It changes every three months? SoChai [00:18:42]: Of course, with the shifting landscape, we try to be extremely thoughtful on predicting the trends of where third-party models are going and where we can uniquely go. And, sometimes when you talk about AI models, we're the models are just going to get infinitely better. But I don't think... It may be in the grandness of time you could say that but, within every month, every quarter, there's specific ways they're getting better. They're training on a lot more, coding data to be better coding agents, for example. And soChai [00:19:14]: We have to think about where are the things that won't — unique data that we're uniquely training on or to step back a little, where is a proprietary model bringing advantage to us is if it can give higher quality or lower cost and latency for similar quality, very similar to many other companies. And when we can do that is when we have proprietary data. So, for example, we have on the order of eighty million or hundreds of millions now getting close to of medical conversations.Jacob [00:19:44]: It's insane.Chai [00:19:45]: This is a unique data set. And this data set, it's very interesting because this data set is effectively a large part of the trace between the patient and the provider. That's where the quote-unquote debugging happens in healthcare. We have these traces at scale, as in as, our CEOs even called it, an exhaust that comes out of our product. And so when you have these traces, that's how you can train better agents on certain use cases, whether it's your transcription diarization use cases or so on or like note generation models and we can do that much cheaper and faster. But we're always also working with these third-party model providers. We closely collaborate with them and that's how we predict where the trends are going. The thing that I think about a lot is that, I know that the model providers are going to train much more on agentic workflows and so forth, so that's great, so that you have a better agentic harness. But the other thing that's interesting is that the model providers, because a large class of the consumer model providers is healthcare queries, that they might, optimize to train a lot of healthcare data to encode the knowledge in its weights. And this is just a great thing for us as well, where the off-the-shelf models can keep bett-getting better at general healthcare information, such that what our strategy is, we have a constellation of models, we can use something for this, that and, we only care about, at the end of the day, the best product experience.EHR as File System: Agentic Workflows and Real-Time InterfacesJacob [00:21:07]: And, you have, overall capabilities improving. I'm curious, as these models get better, is there something you look at and you're “, three months ago, we really couldn't do that but God, the the latest models really allow us to do it”?Chai [00:21:19]: So here's something interesting that I've, been toying with. So all models are... This wasn't super obvious a year ago but now it's become clear and clear that almost every agent is a coding agent underneath the hood? So you give it whatever file system, it can write its own code and so forth. So when you think about within healthcare and the use case that we have, you can think of the EHR effectively like a file system. It's just — it's a storage of all this information. It's a lot of information there that cannot fit into the context window, at least of today's models and you want to use that context effectively for all these product use cases we're talking about. And so if you have better agents that can, manipulate data, read that data, treat it as a file system as we see they're going and we know model companies are investing this way, then that very directly benefits us.Swyx [00:22:09]: Yeah. Okay, cool. Again, just establishing basic things. But we're going back to the model stuff. I'm really interested in double-clicking more on the real-time, element, which is pretty important for both of you. Is it — Is real-time just batches of every one minute, every five minutes? Is that how we do it? Or is there some more native, genuinely real-time in the sense that OpenAI has a real-time API or Gemini has a real-time API?Chai [00:22:35]: Yeah. Yeah. So today it is more on the on the batch basis but there's interestingChai [00:22:41]: Prototypes that we have that we're still not fully, full time, voice in text out or in that sense. But, can you trigger your models, your agents or agentic workflows, depending on the right times in the conversation?Chai [00:22:58]: And so you can imagine, different techniques to bring this latency down and, you want to bring the feedback loop down as much as you can. And so a lot of clever engineering there without fully... Maybe one day we'll do full voice in and text out, train a model to do something like that.Swyx [00:23:15]: You do — People don't want voice in voice out?Chai [00:23:18]: Now we aren't creating experiences that are, during the conversation, inter — It's almost likeSwyx [00:23:25]: Might be too disruptiveChai [00:23:26]: Too disruptive until, who knows, maybe eventually you could have full voice agents once we — the quality and we improve the comfort of the technology. But right now gra — that change is much more gradual and it's more text focus, text out.Janie [00:23:42]: And so much of currently what our product is trying to do is allow a clinician to focus on their patient and maybe at some point but right now patients, clinicians don't want a third voice, at least in a literal voice in that room. And so how do we be there with all the contacts and information ready at hand when there's the right moment?Personalization: Individual Doctors, Specialties, and Health SystemsJacob [00:24:03]: Jenny, one thing I'm curious about is how you think about, personalization in the product. I imagine, every doctor is a special snowflake in their own way, has their own way they like to do things. There are probably a bunch of different approaches you could take to doing that, both within the model layer itself but then also just with clever prompting or engineering. How do youJacob [00:24:20]: Deliver on that?Janie [00:24:21]: It's such a good question. Personalization is massive for us. We think about personalization at three levels. The first is at the individual, the second is at the specialty level and then the third is at the health system or the organization level. To your point, there are a lot of individual preferences. You-When a note is produced, it almost is a reflection that is so deeply personal of a doctor's work and how they give care. And so do they have preferences on things like style? They might want bullets versus paragraphs, really concise versus comprehensive. They also might have phrases that they really like to use or the templates that they want every note to be structured. And, we see it in our feedback all the time. We want two spaces in between sentences or I refuse to use this tool. And so that's something that we've had to build in. And the tricky part is how do you make sure that stylistic preferences don't interrupt accuracy and quality and that's something that we've really had to refine and hone over time. Second is at the specialty level. A cardiologist note or workflow is going to look very different from a dermatologist workflow.Jacob [00:25:32]: I assume cardiology notes are the highest stakes for you guys, given your CEO is a cardiologist.Jacob [00:25:36]: It's “Oh my God, make sure we get this one.”Janie [00:25:37]: Shiv, our CEO, is still a practicing cardiologist. He rounds once a month. And so, first call when we want just quick and easy user feedback too.Janie [00:25:46]: But, specialties require a lot of personalization, both in terms of what does the product look and so we make sure that as new users onboard, we catch that and the product proportionally reflects that. But also on the back end, evals at the specialty level, they are hard-earned to calibrate and get. What does a really great dermatology note look like? What makes it complete? What makes it compliant and billable is very different than a primary care doctor. And so it's not just about what does the product experience look but on the back end tuning and really deepening our understanding for the specialists. What does great output look like? And that's, a problem that we need to calibrate internally, externally, online, offline but, takes lots of cycles but is necessary in a high-stakes environment. And then at the health system level, for products like clinical decision support, you have health systems who've spent years or decades refining their best practices and they want to know, “Hey, we love your clinical decision support product but how do we embed our own hospital guidelines into them to inform clinicians before, during or after a visit what brest — best practices should look like?” And as you think about, deepening moats as well, when health systems, trust us with that data, allow us to productize it and directly into the clinical workflow, makes us a really great partner to health systems who want to build something that truly meets their needs, their practicing guidelines.AI Slop, Memory, and Product Data FlywheelsChai [00:27:23]: And I want to add onto that. The for the clinical documentation problem, it's very similar to AI writing that doesn't feel like your own and then we call that slop. But the way I describe one framing of slop is like AI without context. But we have all that context and both the clinicians, can have it and can guide it. And so part of the other interesting exhaust for us is, memory is, one of these new systems recordsChai [00:27:49]: Almost.Janie [00:27:50]: And we also have all the edits people make on our product and when you think about a data flywheel and how we get better over time becomes really powerful as a mechanism to just going deeper in personalization.Jacob [00:28:04]: It's interesting. I love this idea of working with systems on the guidelines they built up over a long time. I feel like so many of the best AI app companies today are... The question is: How do you take the expertise that a law firm or a bank has built up over many years and then add that as context and also a special sauce over, a an AI tool? And so seems like y'all are really doing that very effectively.Janie [00:28:24]: We're now starting to have our customers ask, “What are other customers doing?”Janie [00:28:28]: “And how are they doing it?”Janie [00:28:30]: And as we think about having visibility across such a large set of care being delivered right now, a really interesting place we could also partner.Swyx [00:28:40]: I'm just curious. I — This may be a nothing question but, how different are health system guidelines from each other? Don't they all converge to the same thing? And if not, where do they differ?Chai [00:28:52]: At a really high level, they're going to talk about very similar things but the difference is probably in some more of the details. “Oh, you should refer to specialists only when XYZ conditions are met,” or so forth and maybe different organizations have different practices and guidelines around that. But high level, talking about similar things but the details are what, of course, that shapes the context and the decisions you make.Swyx [00:29:15]: And this all goes into the context engine and it might affect the notes but maybe not.Chai [00:29:21]: The — For these local pathways, we're definitely thinking about it a little more for our clinical decision support product.Chai [00:29:26]: So yeah.Swyx [00:29:27]: Which is your stuff, yeah.Swyx [00:29:28]: And then the memory which you raised, let's just tell us more about that. What have you tried in memory? What's the structure of the memory? What works? What doesn't work?Chai [00:29:38]: There's, of course, many different ways you could do memory, where it's okay, can you bake it into the model weights or can you do it in some external store? For us, what's interesting is, of course, when you think the models are rapidly changing, whether it's in-house or third-party, baking into the model weights, sometimes you worry that it could be a little throwaway. And so, how do you... You need to find a way that you decompose the problem, the preferences from the underlying models and so forth. The thing we're right now most both that's easiest to start with and we're excited about is having, a separate store for memory, where you have, for example, a memory sub-agent that's, working in the background, figuring out what are the important parts of the clinician's actions that we want to remember for the long term. And then you can also imagine, other things where in the — you have background jobs that are running that are collating these, memories similar to Sleep, of course and what other pattern, patterns products do as well. Learning over all these action, all the action data we have, again, note edits, the conversations they did and the actual transcripts.Evals: LFD, LLM Judges, and Clinical SafetyJacob [00:30:40]: What about evals? How in the world do you... It is such a complex product surface area. We would love to hear you riff on that and also how has that evolved? I'm sure you've gotten better at it, so any learnings along the way.Janie [00:30:50]: From an evals perspective, we, from day one when we build any new product or feature, we think about, what does good look like? And there are table stakes things like clinical safety but then you start to get deeper into what does good quality look like. And when you go into something like our core product, there's stuff like style and completeness and there's things like does this note become something that can be billable, which is very high stakes for a health system. We have a number of ways in which we get confidence for this. We have, internal in-house clinicians who do what we call an LFD process to give us our very first pass at is this or isn't this a good enough output, look at the effing data.Jacob [00:31:41]: LFD?Chai [00:31:42]: That's why I was smiling. I was “Is Janie going to mention what it stands for?”Jacob [00:31:46]: I was not... There's like a million acronyms.Jacob [00:31:48]: How am I supposed to know that I don't? So “Oh yeah, of course, an LFD.”Swyx [00:31:51]: I've never heard of LFDs.Chai [00:31:53]: It's a bridge for sure.Janie [00:31:55]: I got through three days and then I had to ask someone.Janie [00:31:58]: I thought it was just me that didn't knowJanie [00:32:01]: It's our internal process.Swyx [00:32:02]: But look at the data as a meme in ML, ‘cause you tend to not look at it. You just want to look at number go up.Chai [00:32:06]: Exactly.Swyx [00:32:07]: But yes.Janie [00:32:08]: But so, we make sure we look at the data and then as we think about all of the components of good output, we, one, create LLM judges across all of these and we make sure with annotated data and either internal or external evaluators, we feel like these judges are calibrated. And then depending on the stakes, we also work with in-house and third-party evaluators across all of these before we ship any big change. And the goal is, in terms of evolution, how do you go from this process taking months, down to weeks, down to days? Some of it is, a true science and ML problem. A lot of it's also just, hard operational work. Have you planned ahead in terms of what you need? Have you really optimized the capacity that you need across all of the different specialties you need? Have you gotten a really good sense of which third parties are great to work with for what use cases? This takes a lot of domain, expertise and, lots of mistakes and errors in figuring that out. And so as much of it is an ML problem, so much of it has also been operational gains that are hugely important, where domain-specific expertise is everything.Specialty-Level Evaluation and Progressive RolloutsJacob [00:33:23]: But it's funny, ‘cause I feel like people talk about healthcare like it's one giant market and the reality isJacob [00:33:26]: It's, dozens and dozens of sub-markets. And so it feels like in your evals you have to build that up across the board, probably.Swyx [00:33:34]: And is specialization the primary cardinality at... That's the word that comes to mind.Janie [00:33:40]: Sometimes, depending on the product or the use case. And so if we're making a note improvement or feature for a particular specialty, definitely but we have products that are for nurses. We have products that, are really aimed at making the document or the output a lot more billable. And so we'll want to work with coding teams and not necessary clinicians. And so likeJacob [00:34:05]: Coding meaning healthcare coding.Janie [00:34:06]: Yes. Yes.Jacob [00:34:07]: NotChai [00:34:07]: Yes. I see you.Swyx [00:34:07]: Other kinds.Janie [00:34:09]: But is this output proportional to the work that was delivered? Is there sufficient documentation to justify the amount that a health system may end up charging? And so, specialty sometimes but also domain, very different across all of the different products that we're working for. And building out that network is, not easy and is where a lot of our operational investments have gone into.Chai [00:34:35]: And I view a lot of analogies to self-driving cars here, where, part of it is we really want progressive rollout of features to test in the real world is this useful? Is this going to work? One big difference compared to past lives is before I'd build a product, maybe I'd alpha it and then I'd like GA it the next week, ‘cause I'm “Go, move fast, ship,” and whatnot. But the mentality is like you... I want to make contact with the reality as quick as possible but I want a progressive rollout. Because as much as I get as large of an offline eval set, I want the distribution of that to match real-life distribution. And over time, by rolling out early, similar to Waymo has a tagline, “The world's most experienced driver,” another thing that can, at least linearly increase for us is, both the size of our evaluation offline and online, that and it all feeds back.Janie [00:35:25]: Something that's been earned over time, speaking of evolution, is just the trust we've gotten with customers. Historically, a lot of these health systems, when they bring on new vendors, their release cycles are quarters, sometimes twice a year. We've gotten our customers onto monthly release cycles, which is pretty fast for health systems but what is more exciting over the last, call it, few quarters, has been, a subset of our customers have said, “We want to innovate with you. We trust you,” and we have a pretty, decent chunk of our customers who say, “We'll develop with you outside of these monthly release cycles. We have a higher tolerance. We know that the stakes are very high but we want to be the first ones using these products, giving you feedback.” And so for a pretty substantial set of our customers, we've been able to convince them to be able to ship, in this gradual way before GA. Something we talk about a lot internally is, trust is earned in drops, earned in buckets and so we still can't do what I used to do when I worked at Loom. We had 30 million users. I'd just be, rolling out experiments left and. The bar is still quite high for iterative rollout but because of the trust we've earned, we're able to learn at pretty high volume very quickly.Privacy, HIPAA, and De-IdentificationSwyx [00:36:45]: Your scale is still pretty huge.Swyx [00:36:47]: One thing I want to... We were going to go into scale? In a sec. One thing I wanted to call up, follow up on evals, which, again, just coming from a generalist engineer point of view, just thinking through what would people be scared of in doing this, the privacy and HIPAAJacob [00:37:00]: Elements of this. I have zero experience in that. What do you have to do? What is surprisingly not that bad?Chai [00:37:06]: So one thing that's really important here from a compliance perspective is very much that any of the data we use needs to be de-identified, any real-world data we use as a basis of online eval sets we're learning from. And so you have to — And there's, very clear, government guidelines, what counts as PHI. And so we've even have built models that can take, for example, a clinical transcript and remove all the key PHI indicators and so you have a scrubbed/de-identified version. And then once you... And so one thing that's important is first you've got to get confidence in that model in the first place? And prove that out. Because, now you have, multiple probabilistic systems on top of each other.Chai [00:37:46]: But once you have that, then you can train on it use it for evaluation and so forth, provided one of the cool things also that you can do from a business side is the right data contracting as well with your partners.Jacob [00:37:57]: Is the anonymization one way? Once it's done, you cannot undo it? Or is there someoneChai [00:38:01]: YesJacob [00:38:02]: Who holds the master key that can... Yeah, okay. So it's one way.Chai [00:38:05]: It's one way. Yeah.Jacob [00:38:06]: That's how it works. I just wanted to... Because, there's a lot of this, learning from feedback and everything that, you would want to debug more but you can't because you just physically don't allow yourself to.Janie [00:38:17]: Some of it's also written in our customer contracts in terms of who can or can't access PHI data, how long do we retain it,Jacob [00:38:27]: Very goodJanie [00:38:27]: Before it gets de-identified. And so we have a pretty high bar for who can access that PHI data, just to make sure that we always respect our customer data and privacy. But that's something that we partner with our customers on too, to make sure that as we want full, as close to precision as possible in that qualityJanie [00:38:48]: We can still use it.Jacob [00:38:50]: But it'll be fascinating to see how that space evolves? Because you think about, I used to work at a company that, did a lot of healthcare data in the cancer space and if you asked, the average cancer patient, “Hey, do you want people, do you want other patients to be able to learn-”Chai [00:39:03]: Take it.Jacob [00:39:03]: “... Learn from your experience?”Chai [00:39:04]: Take it all.Jacob [00:39:05]: They're “Please.”Jacob [00:39:06]: “I'd love, nothing more than for other people to be able to learn fromJacob [00:39:10]: The experience that I had.” And so in the past it was a lot harder to do that learning. But with this technology, that might really be practical and so it'll be fascinating to see how that continues to evolve.Chai [00:39:21]: There's so much in our data set of 100 million conversations.Chai [00:39:26]: You can imagine things like insights that you can give to the clinician. How could you, oh, how could you have reacted to this? In coaching or insights around, which treatments are effective or, like... Because you have this, again, this data source that was never captured before but that's, where, intuition or experience is created from, going back to this idea that the conversation is the agent of truth.Operating at Scale: Reliability, Cost, and Token EfficiencyJacob [00:39:46]: Back to the 100 million conversations, I feel like you have this insane scale that maybe only a few other AI app companies have and everyone else dreams of. So not everyone has had to confront this yet but maybe just talk about some of the challenges of operating at that scale and what, our listeners have to look forward to if they ever get to this level of scale.Chai [00:40:05]: At large and larger in scale, so of course there's a general, infrastructure reliability. When you... In any given startup, you're building the plane while it's flying. So there's some notion of that. But what gets interesting on the AI and ML side for sure is this, as you get at more and more scale, so one, you have the data to first and foremost do this. But, you start thinking about costs or infrastructure in a whole different way at scale versus, a prototype.Chai [00:40:34]: You can use the most expensive model, you can burn as many tokens as you want but when you're doing 100 million conversationsJacob [00:40:41]: Token max on leaderboards are less upsetting than that context.Chai [00:40:45]: . When you're doing that and so that comes for we have the data and we also have the team that's able to post-train based on this and you can optimize for efficiency, especially in areas where you believe that maybe a lot of the quality headroom is less so and you don't expect the other off-the-shelf models to go that way, such that you want to do, efficiency maximization, in terms of compute and tokens.Jacob [00:41:08]: I feel like you guys live in the future in some way where most use cases today are really just in use case discovery mode, where it's “God, I really hope I can find something that can get to scale,” and so you're always going to use the most powerful model. And then the few things that do get to this level of scale, you start to do those optimizations.Chai [00:41:22]: It's a natural trajectory where it's like zero-to-one, we're not talking about any of these optimizations.Chai [00:41:26]: But when maybe we're in the one-to-100 or so forth, then we're in optimization mode and, what works out really well is you've got all this data from zero-to-one that lets you do this.What Comes Next: The Conversation as the Shared Healthcare PlatformJacob [00:41:36]: That's fascinating. I feel like one thing that's so interesting about the Abridge footprint is that you're in the doctor-patient visit in real-time. I always like to say, there's like probably 50 years' worth of product you could build on top of that. What gets each of you, I don't know, what are you most excited about building, either in the short term or medium term or even, long down the line?Janie [00:41:53]: Something that I get really excited about is that the same conversation can serve so many stakeholders. If you think about the conversation, a doctor needs to know what is the documentation, how do I make sure that this fully represent the care I gave? A patient needs to know, “What the heck just happened? This was really overwhelming. What are my next steps?” A payer needs to know, was this the proper and appropriate care given? A pharma company might want to know why isn't this drug being properly used or is there a good candidate for this clinical trial that I'm about to run? And where I get excited is that our product and our platform and our infrastructure can be the same product across all of those things and start to what's today, separate, very expensive, complex systems that serve each one of these stakeholders in very different ways, start to collapse all of that into a singular platform that enables not just more efficiency across the board but also better outcomes for everyone. And, all of us experience healthcare in probably very painful ways and knowing that there is a world in which we can simplify a lot is really exciting to me and it all starts with the conversation.Chai [00:43:15]: It's interesting. Of it very similar to going back to the KPIs that any AI product cares about. How do you increase quality of care? How do you reduce latency to care? And how do you reduce costs? Which is a huge, in healthcareJacob [00:43:28]: They call it the triple aim in healthcare.Chai [00:43:30]: But very similar to building AI products and the thing that really excites me is when we talk about that latency piece, we talked about one example earlier of prior authorization, can you reduce the latency to care? But you can imagine so much more. Oh, as soon as the lab value gets updated, do you have like a background agent that, kicks off and uses all the context to be “Oh, hey, the patient should do this next,” for example. And of flagging that to the clinician who's always in the loop but reducing that latency, to care. And then you can imagine this is much further down the road but it's like even connecting that to the direct patient and the consumer. And so how can you, how can you build a bridge to all of these things?EHR Partnerships and the Clinical Intelligence LayerJacob [00:44:10]: Very cool. The connections piece is just an ever-growing thing. And one of the key partners is the EHR and I wonder what that relationship is like. Will they, look at this as, something that is valuable enough that they want to own someday?Janie [00:44:29]: Our partnerships with the EHR is, we know that we have to be extremely close partners with all the EHRs who we partner with. Being able to not only pull and push all of the data into the right places is, not only table stakes, if we can't do that, health systems don't want to use us. The second and the reality of today is clinicians spend a lot of their days in the EHR. So much of what allowed us to win in the largest health systems was pretty direct and, very close partnerships with some of the largest electronic health records that allowed us to pull and push data with APIs that weren't ready out of the box. And clinicians want to save clicks. Anytime we introduce a new product that, adds two clicks for them in their day, they're “We're not going to use it.”Janie [00:45:21]: They have 15-minute back-to-back appointments with their patients. They're spending, hours during pajama time doing documentation. Every second and every minute counts and so we really think about being deeply integrated into the EHR as also table stakes to getting real usage and adoption. And anything that we build or introduce, we really talk about earn the right internally a lot, which is we have to provide so much value or save so much time that people will use us. But those are the two things that are close to us, is we know that the product won't be used unless it is deeply interoperable.Chai [00:46:01]: And strategically, to your point, it's like what does EHR want to own versus us? EHRs are really focused on the clinical workflows and so forth but some of the things that we're talking about here, I do these traditionally are outside of the domain where it's oh, connecting pairs and providers together with provider policies or the clinical trial matching, as Janie brought up. And so these are, entirely — we position ourselves as building this entirely new intelligence, clinical intelligence layer across, again, providers, pharma and, payers.Chai [00:46:33]: And so that's a it's a whole different ballgame that we try to playChai [00:46:36]: In combination with them.Jacob [00:46:37]: But it's like a different layer of scope.Healthcare AI Regulation, Technical Depth, and What Changed Their MindsJacob [00:46:39]: I'm curious, you are both relatively newcomers to healthcare. People have these, there's lots of futuristic healthcare AI takes of “Oh, everything will look different.”, now that you've been in healthcare for a bit, you live at the edge of AI, what have you, changed your mind on around this, as you think about what healthcare looks like in ten, 20 years? Any updates to your mental model from the time being close to the problems?Chai [00:47:02]: One thing that IChai [00:47:04]: Was hesitant about before and it's a common thing when I'm trying to recruit engineers that people ask me around, is definitely oh, healthcare, heavily regulated space. And it is, rightfully so. You want to keep, the patients at the end of the day safe. But one of the interesting things that, is a that surprised me how much it is coming to the company is there's a lot of really favorable regulatory tailwinds as well. Where you think about, government really wants interoperability between all these systems that we talked about and so agents can access this information. The government just in January, the FDA released updated guidance on clinical decision support, what I work on in such a way that they used to have guidance from like 2022 that required you to have, mention all these options and do all these other things but it's a very forward and forward-looking way. And so for me, what's been really cool to work on is this, there's this very special moment both in AI in general, we all know that but there's a special moment also regulatory in healthcare as well.Janie [00:48:05]: One thing I would call out is for the very reasons things are higher stakes or, potentially considered more difficult in healthcare, it's where some of the hardest AI problems will get solved first, just because the bar is so high. When I first joined, I was “Oh, this is where we'll be on the tail end of where, all of the AI innovation will be able to be applied.” But when you think about, zero error evals or multi-step workflows that have really low tolerance, a lot of the innovation will happen here just because we have to or else we can't ship.Jacob [00:48:42]: ‘Cause like in other domains, you'd much rather just solve the 80%-is-good-enough problems firstJanie [00:48:46]: 80/20 doesn't work hereChai [00:48:48]: And building off that, traditionally, there was a bit of stigma that, oh, healthcare companies are not that interesting from a technical perspective or I've seen that or faced that myself. But these are really hard and fun problems from a pure technical perspective beyond just the impact. How do you bring the latency of this thing down and make it really high-quality?Reducing Latency: Clinical Workflows, Agents, and Implementation RealityJacob [00:49:07]: How do you bring the latency of things down?Chai [00:49:10]: Yeah. Yeah. Yeah. So okay, let's answer the latency question. And maybe hopefully not too redundant with some of the things I've said earlier but some part of it is with any latency, you have to like what is, what is really your bottleneck. In a lot of workflows, it's sometimes it's the model itself. And so that's where like our data flywheel, our post-training team and so forth come in so that can you make the models far more efficient. So that's one aspect of latency. But there's whole other aspects of latency where it's okay, on top of that, if you use a constellation of different models, can you use — can you first use like a — it's like thinking fast and slow. Can you use a cheap, fast model that triages and hands it off to a larger model where you get more intelligence and so forth and so all theseChai [00:49:56]: Clever tricks to make it work.Chai [00:49:58]: And by the way, we are totally — we also realize that the parameter frontier is changing and so these tricks will — may not get us to where we want to be in five years but we need to if we want to build a useful product right now.Jacob [00:50:11]: Should we go to the quick-fire or you want to ask more about Abridge? We can stuff everything that's not Abridge into the quick-fireSwyx [00:50:16]: I don't mind. I was — I feel like Janie was on the topic of more long tail stuff, which isSwyx [00:50:21]: Not the eighty/twenty thing and that really matters. And I'll —, if you have any tips or cool stories or just general approaches that have worked for you that's interesting to dig into.Janie [00:50:32]: One of them is even just how we staff our teams looks different than a traditional software engineering team, I'd say.Swyx [00:50:40]: Let's go.Clinician Scientists, Edge Cases, and Evals at ScaleJanie [00:50:41]: We have a bunch of folks with different roles who are clinicians and so we have this role called the clinician scientist and I heard one of our leaders refer to them as mutants recently. But they are people who've had clinical backgrounds, so MDs typically, who are also deeply technical, somewhere, on the spectrum of like a full stack engineer all the way to like extremely scrappy prompter. But having each of these people embedded within our teams instantly raises the bar for everything that we build because not only are they determining, is this product clinically useful but they're deeply embedded in our whole evals process. And so when we talk about LFDs, when we talk about what is our actual evaluation criteria, you don't want Chai or me creating what those are because we don't have clinical background. But is probably unique to Abridge but has been game changing. And when you think about where the puck is going, you have people build with clinical backgrounds who are technical and where AI tools are going, they just becomeJanie [00:51:53]: More and more, critical and like the killers of the team. And so that's one. And then the second is just the scale at which we do evals to catch that long tail up front before anything ever gets into production is something that we've pretty much like really started to fine-tune, both from a scale but when do we know we need to get several hundred versus several thousand offline responses, what helps us make that quick decision and make this less of an art and as much of a science as possible. But that's also been something we've had to tune over time.Swyx [00:52:27]: And you have partners who opted in to give you those evals.Janie [00:52:31]: So we work either internally or with third-party for offline evals and then we have customers who also agree to give us, whether it's like thumbs up, thumbs down to like choose this or that, a lot of data to get us to what is as close to fully confident as possible.Swyx [00:52:51]: The term that comes to mind isSwyx [00:52:53]: Like active learning on things where you're weak. I feel like it's a lost artSwyx [00:52:58]: Is a lot of the polish that comes into doing something like this.Janie [00:53:02]: Really.Chai [00:53:03]: Hundred percent.Lessons from Glean: Technical Foundations and AI App InfrastructureJacob [00:53:04]: Maybe, on a totally unrelated note, Chai, you had a very, storied run at Glean b

At the tail end of SAP Sapphire Orlando, Jon Reed sat down in a semi-empty location with UKISUG Chair Conor Riordan to get his reactions to SAP's news, AI strategy and how customer value is changing. Amongst the hot topics Riordan brought up were: business cases and SAP's new AI migration tools (and Joule for Consultants). How impactful is this on business cases and customer AI adoption? Will partners/SIs make the shift? Where are we with public versus private cloud ERP? We also discuss Riordan's take on SAP's recent API policy changes - and how user groups got involved. Some back-and-forth on agentic accuracy and consumption pricing kept things lively as the event wrapped up. Note: after this conversation, Jon Reed talked with SAP's Philipp Herzig, who clarified that the ability to compare private and public cloud ERP readiness does already exist, and can likely be enhanced further, re: industry readiness assessments.

What changes when AI agents can transact on their own?Andreas Munk Holm speaks with Viggo Stenseth, CEO and Co-Founder of SolvaPay, alongside Redstone General Partners Samuli Sirén and Mickaël Bellaïche, about building payment infrastructure for the agentic economy.The conversation explores agent-to-agent transactions, usage-based billing, protocol interoperability, regulatory moats and why existing payment rails may not be designed for AI-native commerce.Key highlightsWhy AI agents need payment infrastructure built for agentic commerceHow businesses can monetise APIs, datasets and digital services used by agentsWhy SolvaPay plugs into existing financial rails rather than bypassing themThe “battle of protocols” across agent marketplaces and ecosystemsWhy regulation, licensing and identity matter in agentic paymentsTimestamps(00:00) Why payments are blocking the agentic economy(02:00) What SolvaPay is building(05:10) Why customers already want agent-to-agent transactions(06:30) Existing financial rails versus crypto-native approaches(08:10) The “battle of protocols” and AI marketplaces(12:00) Redstone on why agentic payments are real(17:20) Why Redstone invested before traction existed(27:00) Can SolvaPay become the Stripe for AI agents?(32:00) Why incumbents may struggle to adapt(36:10) Building long term versus building for exit(41:00) Does the world need an agentic bank?Subscribe to EUVC, the home of European tech, for more insights: https://www.eu.vc/subscribe

Joe Lenzie, Senior Vice President, Treasury Management Officer Lead at Associated Bank, joins Steve Grzanich on this week's Thought Leader conversation to explain how companies are modernizing treasury operations through ERP systems, automation, APIs, and real-time cash visibility.

At the tail end of SAP Sapphire Orlando, Jon Reed sat down in a semi-empty location with UKISUG Chair Conor Riordan to get his reactions to SAP's news, AI strategy and how customer value is changing. Amongst the hot topics Riordan brought up were: business cases and SAP's new AI migration tools (and Joule for Consultants). How impactful is this on business cases and customer AI adoption? Will partners/SIs make the shift? Where are we with public versus private cloud ERP? We also discuss Riordan's take on SAP's recent API policy changes - and how user groups got involved. Some back-and-forth on agentic accuracy and consumption pricing kept things lively as the event wrapped up. Note: after this conversation, Jon Reed talked with SAP's Philipp Herzig, who clarified that the ability to compare private and public cloud ERP readiness does already exist, and can likely be enhanced further, re: industry readiness assessments.

Spring is a season of rapid change inside the hive, and in this Bee Science segment, Dr. Dewey Caron walks through what drives colony expansion—and how beekeepers can respond effectively.   Dewey emphasizes that spring growth is fundamentally tied to pollen availability and favorable flying weather. Colonies in warmer climates may expand gradually, while northern colonies often experience a compressed and intense buildup. This variability makes local awareness and timing essential. Nutrition plays a central role. Research going back to Heather Mattila's 2006 work shows that colonies receiving pollen or protein supplements begin brood rearing earlier and build stronger populations. More recent work reinforces that locally sourced pollen may improve effectiveness, and emerging commercial feeds are showing measurable gains in overwinter survival and pollination strength. As colonies grow, so does the risk of swarming. Dewey underscores the importance of proactive management—providing adequate space, maintaining ventilation, and monitoring brood nest congestion. Once swarm preparation begins, options narrow quickly, making early intervention key. The episode also introduces the "Goldilocks effect" in evaluating colony strength. Colonies that are too weak struggle to build, while overly strong colonies risk swarming. The goal is finding that "just right" balance through regular inspection, brood assessment, and strategic frame movement. Health risks remain present during this expansion phase. Diseases like European foulbrood and chalkbrood, along with pesticide exposure and nutritional stress, can limit colony development. At the same time, brood expansion creates ideal conditions for varroa reproduction, reinforcing the need for integrated management. Dewey's central message is clear: spring requires active, informed management—but not overmanagement. Listen to the bees, respond to conditions, and aim for balance between growth and control. Links and references mentioned in this episode: Caron, Dewey M. Bee MD Bee MD [https://idtools.org/thebeemd/index.cfm?pageID=3094] Mattila, Hearther R. and Gard W Otis. 2006. Influence of pollen diet in spring on development of honey bee (Hymenoptera: Apidae) colonies. J. Econ Entomol. 99(3):604-13. doi: 10.1603/0022-0493-99.3.604 Kulhanek, Kelly, et. al.  2026. Enhanced Honey Bee Colony Strength and Economic Returns from Fall and Winter Feeding with a Complete Pollen-Replacing Feed. Insects 2026, 17(3), 243; https://doi.org/10.3390/insects17030243 Basu, Priya. 2024 Honey bee Nutrition HBHC https://honeybeehealthcoalition.org/nutritionguide/ Tew, James. 2025. Giving it Your Best Guess. March. Bee Culture DeGrandi-Hoffman G, Gage SL, Corby-Harris V, Carroll M, Chambers M, Graham H, Watkins DeJong E, Hidalgo G, Calle S, Azzouz-Olden F, Meador C, Snyder L, and  Ziolkowski N. 2018. Connecting the nutrient composition of seasonal pollens with changing nutritional needs of honey bee (Apis mellifera L.) colonies. J Insect Physiol.109:114-124. doi: 10.1016/j.jinsphys.2018.07.002. Epub 2018 Jul 7.PMID: 29990468 Hoover SE, Ovinge LP, and Kearns JD.  2022. Consumption of Supplemental Spring Protein Feeds by Western Honey Bee (Hymenoptera: Apidae) Colonies: Effects on Colony Growth and Pollination Potential. J. Econ Entomol.115(2):417-429. doi: 10.1093/jee/toac006.PMID: 35181788Free PMC article. ______________ Brought to you by Betterbee – your partners in better beekeeping.   Betterbee is the presenting sponsor of Beekeeping Today Podcast. Betterbee's mission is to support every beekeeper with excellent customer service, continued education and quality equipment. From their colorful and informative catalog to their support of beekeeper educational activities, including this podcast series, Betterbee truly is Beekeepers Serving Beekeepers. See for yourself at www.betterbee.com _______________ We hope you enjoy this podcast and welcome your questions and comments in the show notes of this episode or: questions@beekeepingtodaypodcast.com Thank you for listening!  Podcast music: Be Strong by Young Presidents; Epilogue by Musicalman; Faraday by BeGun; Walking in Paris by Studio Le Bus; A Fresh New Start by Pete Morse; Wedding Day by Boomer; Christmas Avenue by Immersive Music; Red Jack Blues by Daniel Hart; Bolero de la Fontero  by Rimsky Music; Perfect Sky by Graceful Movement; Original guitar background instrumental by Jeff Ott. Beekeeping Today Podcast is an audio production of Growing Planet Media, LLC ** As an Amazon Associate, we may earn a commission from qualifying purchases Copyright © 2026 by Growing Planet Media, LLC

This week we're talking about Apple Business and all the changes that Apple's made of late! We're deep into the APIs and promises that exist in this critical platform. Hosts: Tom Bridge - @tbridge@theinternet.social Marcus Ransom - @marcusransom Selina Ali - LinkedIn Links: https://support.apple.com/guide/profile-manager/welcome/mac deploy.apple.com https://support.apple.com/en-us/126655 Sponsors: Iru Fleet Device Management Watchman Monitoring If you're interested in sponsoring the Mac Admins Podcast, please email podcast@macadmins.org for more information. Get the latest about the Mac Admins Podcast, follow us on Twitter! We're @MacAdmPodcast! The Mac Admins Podcast has launched a Patreon Campaign! Our named patrons this month include Weldon Dodd, Damien Barrett, Justin Holt, Chad Swarthout, William Smith, Stephen Weinstein, Seb Nash, Dan McLaughlin, Joe Sfarra, Nate Cinal, Jon Brown, Dan Barker, Tim Perfitt, Ashley MacKinlay, Tobias Linder Philippe Daoust, AJ Potrebka, Adam Burg, & Hamlin Krewson  

In this episode of the Mainframe Connect podcast's I Am a Mainframer series, J.J. Lovett, Lead for Education and Customer Engagement at Broadcom Mainframe Division, shares his journey from CA Technologies customer advocacy to leading Mainframe Open Education, Vitality programs, and practitioner engagement at events like SHARE and IDUG.J.J. tackles the mainframe skills gap head-on, explaining why it's both a navigation challenge (knowing where to find talent) and a time gap (2-4 years to master sysprog/admin roles). He highlights shifting demographics—millennials and Gen Z now dominate BMC surveys—and how Broadcom addresses this through student user groups, mentorship, and open source integration with projects like Zowe and COBOL."The mainframe isn't a job, it's a career" – J.J. advises college grads: start with z/OS Explore, embrace risks, and recognise mainframe's extensibility through APIs. He shares his vision for proactive succession planning and a future where mainframe experience makes technologists more versatile across IT.Celebrating Military Appreciation Month – J.J. represents military veterans bringing discipline and leadership to mainframe education and customer success during May's Military Appreciation Month.#mainframe #IamaMainframer #OpenSource #Broadcom #MainframeSkills #MilitaryAppreciationMonth #podcast #openmainframeproject #LinuxFoundation #StevenDickens #MainframeConnect #Careers #Zowe

Until a few months ago, open source AI was kinda a hobby project. Now, it's tearing corporate boardrooms apart. Why? Over the past 6ish months, the gap between frontier closed AI and open sourced AI has shrunk to pretty much nothing. And with the surge of always on agents driving open models, their development and release schedule is on pace with the frontier labs. So if your team isn't paying attention to -- and running test cases through -- open AI models, there's a good chance you'll either be overpaying or playing catch up soon. We walk you through the 101 and what you need to know when it comes to open source AI in this Start Here Series special. 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:Open Source AI vs Closed Models ShiftChinese Model Distillation & Legal ImpactsEnterprise AI Cost Triage StrategiesGoogle Gemma 4 Local Model CapabilitiesFrontier Model Performance Gap Closing24/7 Agentic AI Systems OverviewAPI Pricing War: DeepSeek vs US VendorsLegal Protection Tradeoffs for Open Source AIAI Workflow Triage: Task-Specific ModelsFuture Trends: Local and Specialized LLMsTimestamps:00:00 Introducing the Firefly AI assistant03:33 Open source AI cost benefits09:25 AI model performance differences10:19 Open source model improvements15:28 Advancements in local AI capabilities17:04 Impact of Google's Gemma four22:15 Introducing Adobe's Firefly AI Assistant24:19 Adobe Firefly AI assistant beta launch29:26 Choosing the right AI tools32:00 Shifting workloads to open source33:31 Using open-source and closed models36:47 The future of open modelsKeywords: open source AI, open source models, local AI models, local models, closed source AI, closed models, proprietary AI, proprietary models, AI agents, agentic AI, AI workflow triage, cheap API, AI API costs, model distillation, Chinese open source models, China AI models, US AI models,Send Everyday AI and Jordan a text message. (We can't reply back unless you leave contact info)

In this episode of Two Bees in a Podcast, Amy Vu and Dr. Jamie Ellis discuss non-Apis bees with Josh Cambell, a Research Ecologist with the USDA-ARS at the Northern Plains Agricultural Research Lab in Sidney, Montana. Check out our website: www.ufhoneybee.com for additional resources from today's episode. 

Rafael (Head of Innovation, iFood) and Daniel (Data and AI Manager, iFood) pull back the curtain on ILO-Agent — iFood's conversational AI ordering system built for 200 million users across Latin America. Recorded live at AI House Amsterdam, this conversation goes deep into the engineering and product decisions behind building recommendation systems and agentic AI, and why the speed of your AI's response might actually be destroying user trust.The Latency Goldilocks Zone Explained // MLOps Podcast #376 with iFood's Rafael Borger (Head of Innovation) and Daniel Wolbert (Data and AI Manager)

Oren Michels is the founder and CEO of Barndoor.ai, the first and only Control Plane for the agentic enterprise. Previously, he co-founded Mashery in 2006 and served as CEO until Intel acquired the company in 2013. When it was acquired, Mashery-powered APIs were used by over 350,000 active developers in over 100,000 active applications, and counted among its customers many of the largest e-commerce, media, and data companies in the world. He is an entrepreneur, investor, board member, and advisor to technology startups in the US and Europe and has made angel investments in several successful companies including Uber, Pebble Post, Addy, Navdy, and eero.Highlight Bullets> Here's a glimpse of what you would learn…. Rapid evolution of AI agents in e-commerce and business operations.Definition and functionality of AI agents that perform actions on behalf of users.Importance of governance and trust in deploying AI agents to prevent errors and misuse.Introduction of Barndoor AI and its role in providing connectivity and governance for AI agents.Practical use cases of AI agents in managing tasks across various platforms (e.g., Shopify, JIRA, QuickBooks).The necessity of setting strict policies to control AI actions and ensure safety.Integration of AI tools with existing software systems and the potential for low-code/no-code solutions.The significance of problem-solving and process design skills in effectively utilizing AI agents.Recommendations for starting small with AI and learning through practical application.Continuous evolution of AI tools and the importance of staying informed and adaptable.In this episode of the Ecomm Breakthrough podcast, host Josh Hadley speaks with Oren Michels, founder and CEO of Barndoor AI, about the growing role of AI agents in business operations. Oren explains how AI agents can autonomously perform tasks within systems like Shopify, Amazon, and Slack, while emphasizing the critical need for governance and trust. He introduces Barndoor AI as a control plane that enables secure connectivity and policy-based guardrails, preventing unintended actions. Practical use cases include email management, JIRA ticket handling, and financial forecasting. Oren advises listeners to start small, experiment with multiple AI tools, and develop strong problem-solving skills.Here are the 3 action items that Josh identified from this episode:Start with low-risk automation Deploy AI agents on simple, non-critical workflows first (e.g., email summaries, reporting) to test value and build internal trust before scaling. Enforce strict governance from day one Define clear permissions, rules, and guardrails—never give blanket access. Every AI action should be controlled, logged, and auditable. Design processes before deploying AI Break workflows into clear steps and craft precise prompts. Strong process design + prompt clarity = better, safer AI performance.Timestamps:00:00:00 The Problem of AI GovernanceOren discusses lack of governance in current AI systems and the risks of AI agents forgetting instructions.00:00:30 Podcast Introduction & Guest BackgroundPodcast is introduced, and Oren Michels' background and achievements are highlighted.00:00:44 The Rise of AI Agents in E-commerceJosh frames the future of e-commerce as dominated by AI agents and introduces Oren as the guest.00:02:06 Oren's Perspective on AI Agent AdoptionOren explains the rapid and slow pace of AI agent adoption, especially beyond coding tasks.00:03:02 What is Barndoor AI?Oren introduces Barndoor AI, focusing on connectivity and trust for AI agents in business systems.00:03:40 How Barndoor AI WorksDetails on how Barndoor AI enables granular control and governance over AI agent actions.00:05:45 Security and Guardrails for AI AgentsDiscussion on security risks, both from bad actors and unintended consequences by legitimate users.00:06:33 Difference Between Barndoor and Other AI ToolsOren explains how Barndoor adds governance missing from tools like OpenClaw and Claude.00:09:24 Use Case: Email Management with AI AgentsOren shares how he uses AI agents to manage and triage his daily email load efficiently.00:12:04 Why Governance Matters in AI ActionsExplains the importance of restricting AI actions to prevent mistakes, especially in sensitive tasks.00:13:00 Custom Rules and Granular PoliciesBarndoor allows highly specific rules for AI actions, such as price-based restrictions in e-commerce.00:13:58 Use Case: JIRA and Finance AutomationExamples of using AI agents for JIRA ticket management and automated financial reporting via Slack.00:16:48 Enterprise Use Cases & E-commerce OptimizationBarndoor's enterprise clients use AI for handling sensitive data and optimizing Amazon listings seasonally.00:19:08 Customer Service and Contextual CommunicationAI agents help draft personalized emails by pulling context from Salesforce and previous communications.00:20:40 AI Agent Adoption is Still EarlyOren emphasizes that AI agent use is in its infancy and encourages experimentation in low-risk areas.00:22:40 Personal Use Cases for AI AgentsJosh and Oren discuss personal productivity applications, like sports team management and scheduling.00:24:14 The Evolving AI Tool LandscapeDiscussion on the rapid evolution of AI tools, the importance of using multiple models, and specialization.00:27:47 Future of AI in Business OperationsSpeculation on the future: specialized AI tools for each business function, governed by platforms like Barndoor.00:31:00 The Importance of Problem-Solving and Prompt EngineeringSuccess with AI depends on defining problems and giving clear instructions, akin to prompt engineering.00:33:46 Actionable Takeaways for ListenersJosh summarizes three action items: start experimenting, document processes, and stay flexible with tools.00:36:44 Book Recommendation: Why Computers ThinkOren recommends a book that explains the probabilistic nature of AI and why it sometimes fails.00:37:34 Favorite AI Tool and Personal UseOren shares his favorite AI tools and how he uses them for both work and personal learning.00:38:49 Who to Follow: Aaron LevieOren recommends following Aaron Levie for insightful commentary on AI and business.00:39:28 Where to Learn More About Barndoor AIOren directs listeners to Barndoor AI's website and their personal product, Zenni, for hands-on experience.00:39:45 Podcast Wrap-UpPodcast concludes with thanks and a call to subscribe and leave a review.Resources mentioned in this episode:Josh Hadley on LinkedIneComm Breakthrough ConsultingeComm Breakthrough PodcastEmail Josh Hadley: Josh@eCommBreakthrough.comTools and Websites"OpenClaw": "00:00:00""Barndoor AI": "00:03:14""

Ready to find out if your brokerage is built to survive the next wave of digital disruption? What does the future of the spot market look like when instant pricing APIs and AI-driven automation become the industry standard? In this episode, Bill Driegert of DAT joined the show at the 2026 TIA Capital Ideas Conference to talk straight about the digitalization of freight! We highlight why operational excellence must come before automation, the shift toward app-centric carriers, and why even the most "old-school" brokers need to start experimenting with different tools to audit their P&Ls and optimize their RFPs!   About Bill Driegert Bill is the EVP of Convoy Platform at DAT and oversees the shipper and carrier business segments. He was previously the EVP of Trucking at Flexport and the co-founder and Head of Operations at Uber Freight, Uber's logistics business. Bill began his career in freight as the fourth employee at Coyote Logistics (acquired by UPS), where he grew the role to Chief Innovation Officer. Prior to joining Uber, he served as COO at Pillow Homes. He also spent time at Amazon as Director of Planning and Innovation. Bill holds an M.A. in Supply Chain from MIT, an M.B.A. from the University of Chicago, and a B.A. from Southern Methodist University.  

In this episode, Michael shares details from a major internal platform shift at work, including the decision to completely remove an underused public JSON API and rebuild integrations around real customer needs instead of hypothetical use cases. The conversation dives deep into Laravel Passport, Sanctum, OAuth flows, request authorisation, and some tricky edge cases around testing authenticated APIs.Jake then broadens the conversation into AI infrastructure, local model hosting, security implications of autonomous AI systems, NVIDIA hardware demand, and the future potential of photonic processors as a solution to the growing power and cooling bottlenecks facing AI workloads.Show linksLaravel PassportLaravel SanctumLaravel Passport actingAs testing helpersPHP enumsPHPStanLarastanZapierClaudeNVIDIA DGX systemsPhotonic processors

We get real about what AI search changes and what it does not, then map SEO back to fundamentals like attribution, buyer intent, and revenue. We also share how agency teams can use agent workflows and governance to move faster without turning the business into chaos. • Matt's return, agency ownership changes, and why the timing matters • Cameron's path from engineering to SEO through referrals and Google Business Profile wins • AI search as a conversation starter with CEOs while fundamentals stay critical • Why brand traffic and last-click attribution mislead decision makers • Cutting low-value traffic through pruning to drive more calls and leads • Agent harness basics using folders, instructions, APIs, and automation • Getting teams into IDE workflows, avoiding chat-only memory limits, and protecting .env keys • Data privacy for regulated industries, self-hosted models, and AI governance policies Guest Contact Information: Website: www.bidviewmarketing.comLinkedIn: www.linkedin.com/cameron-libuttiMore from EWR and Matthew:Leave us a review wherever you listen: Spotify, Apple Podcasts, or Amazon PodcastFree SEO Consultation: www.ewrdigital.com/discovery-callWith over 5 million downloads, The Best SEO Podcast has been the go-to show for digital marketers, business owners, and entrepreneurs wanting real-world strategies to grow online. Now, host Matthew Bertram — creator of the LLM Visibility Stack™, and Lead Strategist at EWR Digital — takes the conversation beyond traditional SEO into the AI era of discoverability. Each week, Matthew dives into the tactics, frameworks, and insights that matter most in a world where search engines, large language models, and answer engines are reshaping how people find, trust, and choose businesses. From SEO and AI-driven marketing to executive-level growth strategy, you'll hear expert interviews, deep-dive discussions, and actionable strategies to help you stay ahead of the curve. Find more episodes here: youtube.com/@BestSEOPodcastbestseopodcast.combestseopodcast.buzzsprout.comFollow us on:Facebook: @bestseopodcastInstagram: @thebestseopodcastTiktok: @bestseopodcastLinkedIn: @bestseopodcastConnect With Matthew Bertram: Website: www.matthewbertram.comInstagram: @matt_bertram_liveLinkedIn: @mattbertramlivePowered by: ewrdigital.comSupport the show

In this episode, Philip Kiely, head of AI education at Baseten, joins us to unpack the fast-evolving discipline of inference engineering. We explore why inference has become the stickiest and most critical workload in AI, how it blends GPU programming, applied research, and large-scale distributed systems, and where the line sits between inference and model serving. Philip shares how research-to-production can move in hours, not months, and why understanding “the knobs” of inference—batching, quantization, speculation, and KV cache reuse—lets teams design better products and SLAs. We trace the inference maturity journey from closed APIs to dedicated deployments and in-house platforms, discuss GPU lifecycles, and survey today's runtime landscape, including vLLM, SGLang, and TensorRT LLM. Finally, we look ahead to agents and multimodality, making the case for specialized, workload-specific runtimes when performance and efficiency matter most. The complete show notes for this episode can be found at https://twimlai.com/go/766.