Podcasts about Envoy

Hayao Miyazaki est sans conteste l'une des figures majeures du film d'animation. Le 1er novembre 2023 est sorti en France, son dernier film Le garçon et le héron, déjà décrit par la critique comme un excellent cru. La sagesse et la plénitude qui se dégagent de ses réalisations ont tendance à déteindre sur l'image de son créateur, vu comme un bon papy souriant et pacifique. Mais vous connaissez le dicton, les apparences sont trompeuses. En effet, le studio sait où il veut aller et ne recule devant rien. Cette détermination a valu quelques accrochages, notamment avec un producteur très célèbre d'Hollywood. Que s'est-il passé ? Et comment le producteur a-t-il réagi ? Écoutez la suite de cet épisode de "Maintenant Vous Savez - Culture". Un podcast Bababam Originals, écrit et réalisé par Jonathan Aupart. À écouter aussi : ⁠Qui a été le premier artiste de l'histoire ?⁠ ⁠Quelle est la formule magique de Toledano et Nakache ?⁠ ⁠Pourquoi dit-on que le tableau « Le garçon qui pleure » de Bruno Amadio est une œuvre maudite ?⁠ Retrouvez tous les épisodes de ⁠"Maintenant vous savez - Culture"⁠. Suivez Bababam sur ⁠Instagram⁠. Learn more about your ad choices. Visit megaphone.fm/adchoices

AP correspondent Ed Donahue reports protesters are clashing with police in Italy over a US ambassador's luxury yacht tour.

Listen to the latest SBS Hindi news from India. 15/07/2026

Jean-Marie BOCKEL, ancien maire de Mulhouse, ancien secrétaire d'État chargé de la Défense et des anciens combattants, colonel de réserveMaire de Mulhouse pendant 21 ans, ancien député et sénateur socialiste du Haut-Rhin, Jean-Marie Bockel est aussi le fondateur de la Gauche moderne. À 76 ans, son nom représente encore cette troisième voie à l'anglaise, réformiste et libérale, une troisième gauche qui se cherche peut-être dans le crépuscule du macronisme, même si l'homme est retiré de la vie politique. Né dans une famille catholique alsacienne, son oncle Mgr Pierre Bockel était archiprêtre de la cathédrale de Strasbourg, résistant et « Juste parmi les nations ». Attaché aux questions sécuritaires dans sa ville de Mulhouse, Jean-Marie Bockel fut aussi ministre sous Nicolas Sarkozy en 2008-2009, précisément secrétaire d'État chargé de la Défense et des anciens combattants. Colonel de réserve, il a un lien et surtout une histoire avec l'institution militaire. Une histoire tragique, familiale. Son plus jeune fils, lieutenant au 5e régiment d'hélicoptères de combat de Pau, meurt en 2019 dans le cadre de l'opération Barkhane au Mali. Depuis 2020, Jean-Marie Bockel préside l'Association Solidarité Défense qui vient en aide et soutien aux blessés et aux familles des soldats tués. « Envoyé personnel » d'Emmanuel Macron en Afrique en 2024/2025, il œuvra à la reconfiguration du dispositif militaire français en Afrique de l'Ouest et au Sahel. Il prône un partenariat « renouvelé » avec les pays africains. Dans cet entretien, il analyse le sens que l'exécutif donne à ce défilé du 14 juillet, dominé par la volonté de réveiller stratégiquement l'Europe face à la Russie et au moindre soutien de l'Amérique. Hébergé par Audiomeans. Visitez audiomeans.fr/politique-de-confidentialite pour plus d'informations.

Réforme des pensions : les observateurs politiques analysent le message envoyé au gouvernement by TOPFM MAURITIUS

Indian Prime Minister Narendra Modi is set to arrive in Melbourne on 8 July. Ahead of the trip, SBS Hindi sat down with Indian High Commissioner to Australia Nagesh Singh to discuss what the visit is expected to deliver, the key objectives and the agreements that could be announced. We also spoke about calls for Australia to raise human rights concerns with the visiting Prime Minister, whether pro-Khalistan activism remains a concern, and what the visit means for the Indian diaspora in Australia.

A 10h, ce mardi 7 juillet 2026, les GG : Flora Ghebali, entrepreneure dans la transition écologique, Emmanuel de Villiers, chef d'entreprise, et Zohra Bitan, fonctionnaire, débattent de : "300 CV envoyés et aucune réponse : la galère des jeune".

In this episode, recorded live at KubeCon, Ronald and Jan talk with Jannis Relakis and Michael Seiwald-McCarty, both senior platform engineers at Celonis. Celonis manages over 150 Kubernetes clusters across GKE, AKS, and EKS, but it wasn't always that clean. They started with six different Kubernetes flavors, including Gardener, K-Ops, and OpenShift (both Rosa and ARO), spread across multiple cloud providers.In their KubeCon talk "No Shame in Just Paying," they shared how they tackled this consolidation project: migrating all workloads to three standardized, fully managed Kubernetes distributions. Key topics include their self-built cross-cluster connectivity tool called "Wormhole" (powered by Envoy's dynamic forward proxy), RabbitMQ federation for seamless message queue migration, and how they used Karpenter and Cilium to align node and network management across clouds.They also get candid about what went wrong: an accidental ArgoCD sync that caused a 10-minute full environment outage, the pain of "snowflake" environments (including one requiring full HIPAA compliance with Istio mTLS), and the constant fight against scope creep that threatened to derail the entire project.The episode closes with a forward-looking discussion on FinOps, resource rightsizing, the future of VPA, and whether Kubernetes and serverless can ever truly converge.Powered by ACC ICTStuur ons een bericht.ACC ICT Specialist in IT-CONTINUÏTEIT Bedrijfskritische applicaties én data veilig beschikbaar, onafhankelijk van derden, altijd en overalSupport the showLike and subscribe! It helps out a lot.You can also find us on:De Nederlandse Kubernetes Podcast - YouTubeNederlandse Kubernetes Podcast (@k8spodcast.nl) | TikTokDe Nederlandse Kubernetes PodcastWhere can you meet us:EventsThis Podcast is powered by:ACC ICT - IT-Continuïteit voor Bedrijfskritische Applicaties | ACC ICT

.entry-img img{ display:none !important; } .single .hentry .entry-img{ display:none !important; } https://open.spotify.com/episode/6raW3lf3gJuwTrYNbdkf0F Too many organisations are pouring time and money into AI only to find that the promised efficiency gains and cost savings never materialise, leaving CFOs struggling to justify the investment. Understanding why most AI projects fail to deliver ROI, and what finance leaders can do differently, is now a critical skill for anyone responsible for steering strategy, systems, and spend. In this GrowCFO Show episode, host Kevin Appleby sits down with Sinohe Terrero, CFO and COO of Envoy, to explore why so many AI initiatives fall short and how finance leaders can change the outcome. Drawing on his experience as a serial startup CFO and operator in high-growth tech companies, Sinohe reframes AI as a practical toolkit for augmentation, task automation, and application development, and explains how confusion between these use cases leads to poor deployment and weak returns. Throughout the conversation, Sinohe shares real examples from Envoy's finance function, from AI-powered reconciliations and automated interview workflows to custom dashboards that bring data together in one place. He also dives into AI governance, describing the AI council he leads and the data policies that allow innovation while protecting sensitive information, ultimately positioning the CFO as a hands-on AI leader focused on both value creation and risk management. Key topics covered: Companies misunderstand what AI can do, deploy it inappropriately (e.g., trying to “fully automate everything”), and often lack in-house application developers who can tailor solutions to their actual workflows. Sinohe breaks AI use into augmentation, task automation, and application development, arguing that most ROI today comes from targeted task automation and small, purpose-built tools, not sweeping end-to-end automation projects. Envoy's finance team used AI to automate health insurance and other reconciliations, identifying about $40,000 in recoveries and turning tedious, quarterly work into a largely automated process. Sinohe personally builds AI-powered applications to reconcile accounts, summarize emails and Slack, prep and debrief interviews, and create a “morning coffee” dashboard that consolidates operational and financial insights into a single pane of glass. As head of Envoy's AI council, Sinohe has helped design a data governance matrix that clarifies what data can be used in which tools, allowing experimentation and creativity while strictly protecting company and customer data. Sinohe is bullish on increased data accessibility (e.g., via banks and platforms like Salesforce) and predicts a shift toward custom, CFO‑designed dashboards and tools, with legacy point solutions being displaced by in‑house applications that do exactly what the business needs. Links Sinohe Terrero on LinkedIn Kevin Appleby on LinkedIn GrowCFO Mentoring Timestamps:  0:01:36 – Sinohe explains Envoy as a workplace technology platform focused on managing physical spaces (visitor check-in, security, emergency notifications, desk allocation) with 6,000+ global customers and around 250 employees. 0:03:35 – He shares how timing, a tight investor story, and demonstrating strong cash flow and operational discipline were critical to a successful Series C raise during a turbulent market. 0:04:47 – Sinohe lays out the core reasons AI fails in many organizations and introduces his three-part framework: augmentation, task automation, and application development. 0:07:11 – He describes teaching himself to build AI-powered applications, including an asset-account reconciliation tool that cut a two-hour monthly process down to about two minutes. 0:12:21 – Using tools like Scribe to document workflows, Envoy's finance team identifies automation candidates; a payroll-led AI skill for health insurance reconciliations surfaced roughly $40,000 owed to the company. 0:17:53 – Sinohe explains Envoy's AI council, clear AI policies, and a data governance matrix that defines what data can be used where, enabling safe experimentation at scale. 0:21:17 – He details his personal AI setup: automated interview briefing/debriefing via Granola + Claude, daily digests of emails/Slack/meetings, and automated summaries of operational metrics and customer activity. 0:24:58 – Sinohe predicts job disruption in large teams (e.g., 100 accountants potentially shrinking to 60) but sees smaller teams using AI to focus on higher-value, advisory work rather than basic reconciliations. 0:26:30 – He describes replacing tools like Flowcast, Asana/Monday, and other SaaS products with custom AI-enabled applications that do 75% of what generic tools do—but 100% of what Envoy actually needs. 0:33:36 – Sinohe forecasts greater bank and platform data accessibility, more automated reconciliations, and a shift that frees CFOs from operational drudgery so they can focus on higher‑value strategic work. Find out more about GrowCFO If you enjoyed this podcast, you can subscribe to the GrowCFO Show with your favorite podcast app. The GrowCFO show is listed in the Apple podcast directory, Spotify and many others. Why not subscribe there today? That way, you never miss an episode. GrowCFO is a great place to extend your professional network. Join GrowCFO as a free member today and participate in our regular networking events and webinars. Premium members can also access our extensive training center and CFO Digital Toolkit. You can enroll in our flagship Future CFO or Finance Leader programs here. You can find out more and join today at growcfo.net

Bongani Bingwa speaks with former diplomat and international relations expert Dr Kingsley Makhubela about the controversy surrounding former president Jacob Zuma's visit to the Gupta brothers in India last month, despite the brothers remaining fugitives from South African justice. 702 Breakfast with Bongani Bingwa is broadcast on 702, a Johannesburg-based talk radio station. Bongani makes sense of the news, interviews the key newsmakers of the day, and holds those in power to account on your behalf. The team brings you all you need to know to start your day Thank you for listening. Listen live on Primedia+ weekdays from 6 am to 9 am (SA Time) https://buff.ly/gk3y0Kj For more from the show and catch-up podcasts, visit Primedia+ here https://buff.ly/zEcM35T Subscribe to the 702 Daily and Weekly Newsletters https://buff.ly/v5mfetc Let’s keep the conversation going online: 702 on Facebook: https://www.facebook.com/TalkRadio702 702 on TikTok: https://www.tiktok.com/@talkradio702 702 on Instagram: https://www.instagram.com/talkradio702/ 702 on X: https://x.com/Radio702 702 on YouTube: https://www.youtube.com/@radio702See omnystudio.com/listener for privacy information.

Sinohe Terrero still remembers the timing. He joined Envoy in January, only to see the workplace transformed just two months later as offices around the world shut down because of COVID. The company had been building products for offices, but suddenly, almost no one was going to the office, Terrero tells us.That abrupt shift forced Envoy to rethink its future. The company quickly introduced a product called Protect to help organizations safely welcome employees and visitors back into their facilities. From there, it expanded into desk management, room scheduling, deliveries, analytics, and ultimately a broader suite of workplace security solutions.Today, that evolution has reshaped the business. Envoy now helps organizations across industries such as aerospace, defense, biopharma, and manufacturing secure their physical workplaces. Emergency notifications, visitor management, identity verification, and real-time visibility into who is inside a facility have become central capabilities, Terrero tells us.Looking back, Terrero sees a different challenge driving the company's growth. During the pandemic and the inflationary period that followed, organizations struggled to determine whether they would operate remotely, in hybrid environments, or fully in person. Now that most companies have settled on their workplace strategies, the demand for operational data has increased significantly, he tells us.That demand extends beyond simply managing office attendance. Organizations want software that can verify identities, monitor facility access, manage security risks, and provide real-time information rather than relying on manual logs or random sampling. For Terrero, Envoy's journey reflects how quickly a company can evolve when changing customer needs require an entirely new way of thinking about the workplace.

New Zealand's special agricultural envoy says the first steps have already been taken in securing new trade agreements. Chris Luxon's promising to attempt seven new deals in five years, if re-elected. These are Brazil, Switzerland, Argentina, Bangladesh, Nigeria, Uruguay and the European Free Trade Association. Meat Industry Association Independent Chair Nathan Guy told Ryan Bridge Bangladesh is a very big dairy market - and he reckons it will be the first deal secured. LISTEN ABOVESee omnystudio.com/listener for privacy information.

Avec : Pierre Rondeau, économiste. Élise Goldfarb, entrepreneure. Et Frédéric Hermel, journaliste RMC. - Accompagnée de Charles Magnien et sa bande, Estelle Denis s'invite à la table des français pour traiter des sujets qui font leur quotidien. Société, conso, actualité, débats, coup de gueule, coups de cœurs… En simultané sur RMC Story.

Tonight on The Last Word: Donald Trump doubles down on voter-ID bill after his Supreme Court loss. Also, Black voters respond to Republican redistricting efforts. Plus, the Supreme Court will hear the Arizona proof-of-citizenship voting case. New Jersey Gov. Mikie Sherrill endorses Rebecca Bennett for Congress. And North Carolina Republicans override Gov. Josh Stein's vetoes on DEI bans. Rep. Madeleine Dean, Lisa Rubin, Rep. James Clyburn, California Attorney General Rob Bonta, Rebecca Bennett, and Anderson Clayton join Jonathan Capehart. To listen to this show and other MS podcasts without ads, sign up for MS NOW Premium on Apple Podcasts. Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

The coordinated global response to climate change-driven displacement is relatively new. Just a few decades ago, virtually no governments were paying attention to the ways in which people were being displaced by extreme weather, sea-level rise, and other climate events. Although the international response remains a work in progress, significant strides have been made to bring the world together. One of the people responsible for that coordination is Walter Kälin, a longtime humanitarian expert and legal scholar who is now the Envoy of the Chair of the Platform on Disaster Displacement, a country-led initiative that works to protect people at risk of climate-related displacement. In this discussion, he breaks down where things stand today in terms of a coordinated response and how things might evolve in the future. Subscribe and please leave us a review on your podcast service of choice.   Chapters 01:15 Evolution of Global Displacement Policy 06:45 Climate Change Enters the Displacement Agenda (2004–2010) 10:28 The Nansen Initiative and the Birth of the Platform on Disaster Displacement 17:55 Lessons Learned: Bottom-Up Over Top-Down Approaches 19:58 Navigating Declining Funding and Political Fragmentation 24:30 Advice for the Next Generation

The coordinated global response to climate change-driven displacement is relatively new. Just a few decades ago, virtually no governments were paying attention to the ways in which people were being displaced by extreme weather, sea-level rise, and other climate events. Although the international response remains a work in progress, significant strides have been made to bring the world together. One of the people responsible for that coordination is Walter Kälin, a longtime humanitarian expert and legal scholar who is now the Envoy of the Chair of the Platform on Disaster Displacement, a country-led initiative that works to protect people at risk of climate-related displacement. In this discussion, he breaks down where things stand today in terms of a coordinated response and how things might evolve in the future. Subscribe and please leave us a review on your podcast service of choice.   Chapters 01:15 Evolution of Global Displacement Policy 06:45 Climate Change Enters the Displacement Agenda (2004–2010) 10:28 The Nansen Initiative and the Birth of the Platform on Disaster Displacement 17:55 Lessons Learned: Bottom-Up Over Top-Down Approaches 19:58 Navigating Declining Funding and Political Fragmentation 24:30 Advice for the Next Generation

A dangerous prisoner needs to be escorted across country, a mysterious package needs to be delivered overseas…and Special Agent Chet Phillips is wandering the halls.Written byPaige KlanieckiDirected byPete BarryStarringChris Klaniecki as Skip GrangerNazli Sarpkaya as Mackenzie McGrath and Mini-McGrathDave Stanger as Bowden MontcreifPaige Klaniecki as Gloria KovakFaith Dowgin as Section Chief Zelda Anderswith Kirk White as Chet Phillipsand Katerina McGrath as The Mission VoiceAlso StarringAshley Banks as Athena O'BrienJill Ivey as Finleyand Bob Killion as Security Guy and Guy St. LeFevreGuest StarringJohn Dowgin as Dr. Biff Studebaker, Bartender, and Rowdy FanPete Barry as the Bystander, Rowdy Fan, and RaiderDave Serfass as RockfistJ. Michael DeAngelis as the Envoy, TSA Agent, and Train BartenderDavid S. Dear as Terry MillionaireMusic by Pete BarrySound editing and mixing by John DowginA complete transcript of this episode can be found here.Created and produced byPete Barry & J. Michael DeAngelis & John DowginAssociate Producer: Paige KlanieckiFor a complete list of credits and full sound effect attributions, please visit the episode webpage.

The applications to talk at SkeptiCamp in October are now open, don't be shy! In TWISH we hear about how the jesuit priest Angelo Secchi unwittingly became the origin of tales about green men on Mars. Then, it's time for the news:EUROPE / WORLD: European heatwave / El Niño officially under wayAUSTRIA: Study links authoritarian attitudes to belief in Anthroposophic medicineEUROPE / WORLD: Is EU falling for the great replacement theory?The European Commission gets today's award for being Really Right since they finally are easing the rules for CRISPR crops in the EU.In Who's Quacking? we feature Paulo Zampolli, sel-appointed “Envoy to Italy” who has tried to sneak Italy back into the World Cup, even though they clearly did not qualify.Enjoy!https://theesp.eu/podcast_archive/theesp-ep-537.htmlSegments:0:00:27 Intro0:00:51 Greetings0:03:25 TWISH0:10:38 News0:30:06 Really Right0:33:48 Who's Quacking?0:39:31 Quote0:40:57 Outro0:42:20 Outtakes Hosted on Acast. See acast.com/privacy for more information.

In this episode of Everything is Logistics, Blythe talks with Michelle McBride, Head of Product at Envoy AI, about how AI is being used inside freight brokerages to reduce operational drag and help carrier sales teams move faster.Envoy AI builds Ellie, an AI-driven orchestration layer for logistics operations. Ellie connects into the tools brokerages already use, including TMS, compliance platforms, load boards, and communication workflows, so reps can take action without jumping between several different screens.They cover:Why carrier sales reps are still dealing with too many disconnected systemsHow Ellie helps with carrier outreach, compliance, load coverage, and exception handlingWhy master data and SOPs matter before rolling out AIHow brokerages should think about change management during implementationWhy trust is one of the biggest adoption challenges for AI in freightHow human-in-the-loop workflows should have a clear path toward autonomyWhy AI in freight is not about humans versus AIThis conversation is part of the CargoRex AI Use Cases in Logistics guide, featuring real examples of how logistics companies are using AI across freight, warehousing, procurement, visibility, and operations.Read the full guide here:https://cargorex.io/research/ai-use-cases-in-logistics/LINKS:Envoy AI:https://tryonvoy.aiCargoRex AI Use Cases in Logistics Guide:https://cargorex.io/research/ai-use-cases-in-logistics/ -----------------------------------------THANK YOU TO OUR SPONSORS!SPI Logistics has been a Day 1 supporter of this podcast which is why we're proud to promote them in every episode. During that time, we've gotten to know the team and their agents to confidently say they are the best home for freight agents in North America for 40 years and counting. Listen to past episodes to hear why.CargoRex is the search engine for the logistics industry—connecting LSPs with the right tools, services, events, and creators to explore, discover, and evolve.Digital Dispatch maximizes and manages your #1 sales tool with a website that establishes trust and builds rock-solid relationships with your leads and customers. 

Canada's top trade envoy in Taipei, Marie-Louise Hannan, reflects on four decades of Canada-Taiwan ties, growing LNG and offshore wind cooperation, and why Prime Minister Mark Carney's case for middle-power democracies resonates with Taiwan's own search for agency in a fractured world.Episode highlights:00:00 Launching a new diplomat interview series02:44 Arriving in China in 1989, before the Tiananmen incident09:31 Dr. Mackay and the roots of Canada-Taiwan ties12:26 Taiwan as a top Indo-Pacific trade partner15:05 Energy dependence and the case for Canadian LNG20:37 Inside Canada's first ever Indo-Pacific Strategy26:59 Carney's Davos speech and middle-power democracies31:00 Life in Taipei: food, family, and safetyHost: Kwangyin Liu, Deputy Managing Editor, CommonWealth MagazineGuest: Marie-Louise Hannan, Executive Director of Canadian Trade Office in Taipei Producers: Yayuan Chang, Weiru Wang＊Read more：https://english.cw.com.tw＊Share your thoughts：bill@cw.com.tw Powered by Firstory Hosting

Les attaques par déni de service, ou DDoS, font partie des méthodes les plus connues de la cybersécurité offensive. Leur principe est simple : envoyer tellement de requêtes vers un site ou un service en ligne que ses serveurs finissent par saturer. Résultat, la page ne répond plus, l'application tombe, et les utilisateurs légitimes ne peuvent plus accéder au service.Traditionnellement, ce type d'attaque nécessite un botnet, c'est-à-dire un vaste réseau de machines compromises : ordinateurs, routeurs, caméras connectées ou objets mal protégés. Mais des chercheurs de la société californienne Calif viennent de documenter une méthode beaucoup plus inquiétante : une attaque DDoS capable de fonctionner depuis un seul ordinateur. Cette technique, baptisée « HTTP/2 Bomb », doit être présentée lors de la conférence Real World AI Security, organisée à Stanford du 23 au 25 juin. Les chercheurs expliquent avoir utilisé Codex, l'IA d'OpenAI, pour les aider à détecter cette faille.Le cœur du problème vient de HTTP/2, une version moderne du protocole qui permet à un navigateur et à un serveur web de communiquer. HTTP/2 a été conçu pour accélérer les sites, notamment grâce à la compression des en-têtes et à l'envoi de plusieurs requêtes sur une même connexion. Mais ces optimisations peuvent être détournées. L'attaque exploite notamment HPACK, le système chargé de compresser certaines informations échangées entre le client et le serveur. En manipulant ce mécanisme, un attaquant peut forcer le serveur à reconstruire en mémoire de très grandes quantités de données pour un trafic en apparence limité. La seconde étape consiste à empêcher cette mémoire d'être libérée rapidement, en jouant sur les mécanismes de contrôle du flux.Selon Calif, un simple ordinateur connecté à 100 Mbps peut ainsi épuiser des dizaines de gigaoctets de mémoire vive en quelques secondes. Lors des tests, un serveur Envoy est tombé en une dizaine de secondes, Apache a saturé 32 Go de mémoire en 18 secondes, tandis que nginx et Microsoft IIS ont cédé en moins d'une minute. La menace est sérieuse, mais pas universelle. Tous les serveurs ne sont pas vulnérables, et certains correctifs existent déjà. En attendant, les experts recommandent de limiter strictement les en-têtes, de passer par des CDN ou proxys inverses, et de désactiver HTTP/2 lorsque c'est possible. Hébergé par Acast. Visitez acast.com/privacy pour plus d'informations.

Trump tells Iran to make an agreement or else. This as talks between the two countries are once again derailed after more fighting. Plus, Italy slams Trump after he claimed she begged him for a photo.  Learn more about your ad choices. Visit podcastchoices.com/adchoices

What are the prospects that the Israeli-Hezbollah ceasefire will hold and for how long? For insight, Amna Nawaz spoke with Rob Malley. He was the U.S. Special Envoy for Iran during the Biden administration and was part of the team that negotiated the nuclear agreement with Iran during the Obama administration. PBS News is supported by - https://www.pbs.org/newshour/about/funders. Hosted on Acast. See acast.com/privacy

À Nantes, au cœur de l'hiver 1793, la Loire a été transformée en instrument de mort. Envoyé pour sauver la République dans l'Ouest, Jean-Baptiste Carrier est devenu le visage le plus effroyable de la Terreur.Dans le Paris fiévreux de l'an II de la République, s'ouvre un procès politique hors du commun : celui des 132 Nantais, arrêtés et accusés de trahison envers la Révolution. Mais ce qui devait être une formalité se transforme en un déballage glaçant des exactions commises dans la ville de Nantes sous la férule du représentant en mission Jean-Baptiste Carrier.Franck Ferrand nous plonge dans les sombres heures de la Terreur, lorsque la ville de Nantes, assiégée par les insurgés vendéens, a sombré dans un climat de paranoïa révolutionnaire. Carrier, envoyé pour ravitailler et discipliner les troupes de la République, s'est rapidement mué en bourreau, orchestrant une véritable purge sanglante de tous ceux qu'il jugeait suspects.Des prisons regorgeant de détenus aux noyades massives dans la Loire, en passant par les exécutions sommaires, le récit de Franck Ferrand nous fait frissonner. Comment cet homme a-t-il pu se laisser emporter dans une telle furie meurtrière ? Quel rôle ont joué ses complices dans ces atrocités ? Le procès des 132 Nantais marque un tournant, où la Terreur commence à être remise en cause, ouvrant la voie à la chute de Robespierre et de ses partisans les plus radicaux.Plongez au cœur de cette sombre page de l'Histoire, à la découverte d'un épisode qui a profondément marqué la Révolution française.

À Nantes, au cœur de l'hiver 1793, la Loire a été transformée en instrument de mort. Envoyé pour sauver la République dans l'Ouest, Jean-Baptiste Carrier est devenu le visage le plus effroyable de la Terreur.Dans le Paris fiévreux de l'an II de la République, s'ouvre un procès politique hors du commun : celui des 132 Nantais, arrêtés et accusés de trahison envers la Révolution. Mais ce qui devait être une formalité se transforme en un déballage glaçant des exactions commises dans la ville de Nantes sous la férule du représentant en mission Jean-Baptiste Carrier.Franck Ferrand nous plonge dans les sombres heures de la Terreur, lorsque la ville de Nantes, assiégée par les insurgés vendéens, a sombré dans un climat de paranoïa révolutionnaire. Carrier, envoyé pour ravitailler et discipliner les troupes de la République, s'est rapidement mué en bourreau, orchestrant une véritable purge sanglante de tous ceux qu'il jugeait suspects.Des prisons regorgeant de détenus aux noyades massives dans la Loire, en passant par les exécutions sommaires, le récit de Franck Ferrand nous fait frissonner. Comment cet homme a-t-il pu se laisser emporter dans une telle furie meurtrière ? Quel rôle ont joué ses complices dans ces atrocités ? Le procès des 132 Nantais marque un tournant, où la Terreur commence à être remise en cause, ouvrant la voie à la chute de Robespierre et de ses partisans les plus radicaux.Plongez au cœur de cette sombre page de l'Histoire, à la découverte d'un épisode qui a profondément marqué la Révolution française.

The Dazai no Sochi--the head of the Yamato government in Kyushu--was a powerful position, with a lot of autonomy with lucrative opportunities.  The people in this position were often powerful members of the court capable of representing the sovereign.  They would often go on to become quite powerful in their own right.  So who were the movers and shakers that held this prestigious position during Uno no Sarara's reign?  This episode, we take a look at those who held the position and those who supported them. For more, check out our blogpost:  https://sengokudaimyo.com/podcast/episode-151 PS:  Hang around to the end (or check the end of the transcript) for information on some possible updates coming to the show. Rough Transcript Welcome to Sengoku Daimyo's Chronicles of Japan.  My name is Joshua and this is Episode 151: The Dazai no Sochi of the late 7th century   Tsukushi no Masaru was busy.  A new boss was coming in, and he wanted to make sure everything was prepared.  The Dazai may have been about as far as one could get from the capital and still be in Yamato, but it was also the first—and sometimes only—encounter some would have with the archipelago, so there was no excuse to be slacking off.  Of course, this was hardly his first new boss, though for as long as he'd been on the job, each one could well be his last.  He was getting a bit long in the tooth, after all.  Twenty-nine years was a long time to be working in the same position.  As Masaru paused, he thought back on some of the people he'd served.  There was Soga no Akae—he was ambitious.  Apparently he'd been in some rather compromising positions before coming out, but he'd done well enough when he went back.  Shame that he backed the wrong horse. That did bring a chuckle to old Masaru's throat, though.  He remembered when Prince Kurikuma had come out there, to the the Dazai, , and there were still people around who told stories of him.  When those Afumi court stooges had showed up to try and conscript the barrier guards, Prince Kurikuma and his sons just stared them down.  Everyone had been afraid that it would end in bloodshed, or at least that there would be consequences for defying the court, but Kurikuma was adamant, and the messenger had left with his tail firmly between his legs. Then there was Shima. By the time he came, Masaru already knew how everything was supposed to work. He may not have been in charge, but that wasn't his ambition.  It was enough for him to be good at what he did.  He didn't need to go all the way to the Palace and deal with the politics there—there were enough politics out here already.  Shima, though, he was clearly suited for that Palace life.  He was a capable administrator, but Masaru could tell he was ambitious.  When he left, everyone knew that he would be going on to bigger and better things. And now there was another Prince coming out. So they would get the government offices prepared and greet him with proper fanfare.  They'd bring him in and hold the ceremonies, and then they would get down to work.  A stream of officers would present him with what they were working on and what had to happen.  Masaru would be there to help make sure that everything was running smoothly and nothing got too out of hand.  And that was the way things worked out on the edge of the realm.   Welcome back to Sengoku Daimyo.  We are still covering the reign of Uno no Sarara, and, similar to last episode, we are going to continue to talk about the people who made up Yamato at this time.  This episode, more specifically, we are going to be turning away from the capital, in Asuka, and looking all the way over to Tsukushi—modern Kyushu—and at the people who served as Dazai no Sochi, or head of the local government out there, as well as the bureaucrats and staff that worked for them—at least as far we know.  Many of them went on to have considerable careers that took them well beyond Kyushu.  At the same time, we'll take a look at some of the things that happened under their rule as what Aston translates as the "Viceroy of Tsukushi". After that, I have a special announcement about the podcast at the end of the episode, so if you are interested in learning more about what we plan on doing, please listen all the way to the end to hear about some plans for the future. And with that out of the way, let's begin. So we are talking about the position of Dazai no Sochi or the Viceroy of Tsukushi.  Often these people are referred to only as being of the "Tsukushi no Dazai" or the "Tsukushi no Ohomochi".  The term "Sochi" appears later, and we first see this term applied to Prince Kawachi, in 689.  It seems to show up with two different characters, which might be a term from the later Taihou code that was retroactively applied or may refer to an evolution of the position over time.  I'm honestly not sure.  There is still plenty of confusion over what was meant in some of the references. We've discussed this position before on the podcast: This was the sovereign's representative to the world outside of the archipelago.  Not only did the Dazai no Sochi  oversee all of Tsukushi—all of Kyushu— and extensive defensive forces stationed there and in the outlying islands, but they oversaw all diplomatic and trade missions to and from the archipelago.  Envoy missions would come to Tsushima, where they would get a local pilot and send word ahead.  They would then be received at the government center, the Dazai, near modern Fukuoka and Hakata bay.  For most envoys, this was as close as they would ever get to Yamato proper.  They would offload their goods there and be put up at the government supplied quarters in Wogohori.  They would be wined and dined there, entertained as appropriate to their status, while word was sent on to the capital.  In rare cases, envoys would be sent on another journey through the inland sea to Naniwa, and then on to Asuka, but otherwise their journey would end at the Dazaifu.  Any return gifts would come back with the correspondence from the capital, and thus be handed out to the envoys and their escorts before the mission was sent back home to Silla, Tamna, or wherever they had come from. Being the middle man in this operation offered a lot of power and authority, but it also would have been quite lucrative.  While diplomatic missions brought gifts for the court, they also brought  trade goods, of which the Dazai no Sochi could have first  pick.  This is on top of the fact that this position often came with a stipend equaling the labor of hundreds of individuals.  Many of the Dazai no Sochi would serve limited terms, eventually returning to Asuka, where we see them take on powerful positions. Take, for example, our first Dazai no Sochi, Tajihi no Mabito no Shima. Tajihi no Shima was born, we are told, in or around 624 to Tajihi no Maro and a daughter of Ohotomo no Hirafu.  Tajihi no Maro, Shima's father was a powerful noble in the court of Ohoama, aka Temmu Tennou, and he had enough standing that he was one of the named individuals who provided eulogies for Ohoama on the occasion of his passing.   The Tajihi family were quite well placed: they were descendants of Hinokuma no Takata no Miko, aka Senka Tennou, Shima's great-grandfather.  This earned them the kabane of "Mabito", or "True Person" because of their royal lineage.   Tajihi no Shima was placed in charge of the Dazai from at least 682.  His predecessor that we know about is Prince Yagaki, who was dismissed around 676, and we don't know who filled the gap between him and Shima. Shima had quite the run.  We don't know exactly when he returned to the court in Asuka, but it cannot have been later than 689, when we see Awada no Mahito in the position.  A year later, in 690, Shima was made Udaijin, or minister of the right.  That's a huge deal and we will talk about that in a bit, but what did Shima actually oversee during his tenure as Dazai no Sochi? We have quite a few events attributed to him, this reign.  In 686, we see the Tsukushi no Dazai sending tribute in the form of human beings:  Common men and women of Goguryeo, Baekje, and Silla, along with 62 priests and nuns.  We aren't told where these men and women came from, but I suspect that they were refugees or captives from all the fighting on the peninsula.  That they were given as tribute suggests to me that they were enslaved—or at the very least they were not free.  If they were uneducated, they were likely put to work as labor, perhaps building out the new capital or opening new farmlands.  Later we see the various missions from Silla around the death of Ohoama, and the back and forth that went on, there, and in 688 the Tsukushi no Dazai entertained Kara, a Minister of Tamna, aka modern Jeju island, who had been sent by the king of that small country.  You may recall that Tamna, while late to the game, may have been one of the last holdouts of an early Japonic speaking people outside of the archipelago. Being the Tsukushi no Dazai, Shima would not have only been concerned with foreign envoys, but also with two other groups of Hayato—specifically the Ohosumi no Hayato and the Ata no Hayato.  Little is known about them, other than that Yamato considered them to be distinct ethnic and cultural groups living in the far south of Kyushu.  We've talked before about how southern Kyushu maintained a significantly different material culture through Kofun period until more recent times.  We also have indication that they had a distinctive shield and even art style—the famous "Hayato shields" appear to have been appropriated by the court, along with a contingent of Hayato men that were expected to act as an exotic guard for the sovereign and the court.  The earliest reliable evidence we have for them is a record from 682.  There are some questions as to whether or not they were related to the groups previously called Kumaso or even the Tsuchigumo, but there is no clear historical or archaeological  evidence linking them other than the common cultural finds in Kyushu more generally. The Ata and Ohosumi Hayato may have been distinct clans or lineage groups living in Ohosumi and the area of modern Satsuma.  We have a record in 687 of the Ata no Hayato attending Ohoama's funeral and presenting a eulogy.  The chiefs who came brought 337 others—a sizeable contingent—and they were all given presents by the court.  Later, we would see presents given out to 174 Hayato by Shima's successor in the Dazai, Awada no Mahito, and then in 692 we know that the court sent priests to preach Buddhism to Ata and Ohosumi.    In 695, Hayato of Ohosumi were entertained in the capital, and they even held a wrestling match for the Queen and her attendants in the area west of Asukadera, by the site of the famous Tsuki tree. So the Hayato would have been another group that Shima no doubt dealt with on a somewhat regular basis in his capacity as Dazi no Sochi—and then later on when he returned to Asuka and took up his new role as Udaijin.   And as I mentioned, that appointment was a Big Deal.  The position of Udaijin had been vacant since Nakatomi no Kane, one of the infamous leaders of the Afumi court, was non-consensually removed from the position—and this plane of existence—when he was executed in 672, at the closure of the Jinshin no Ran.  After that, Ohoama appears to have been gun-shy about sharing power with anyone outside the royal family.  The position had been left vacant for about 18 years.  So what made Uno no Sarara take up Shima as Minister of the Right?  And what about the Minister of the Left, or the Sadaijin? Well, we don't have a Sadaijin, but we do have a Dajodaijin in the form of Prince Takechi, Ohoama's first-born son.  The Dajodaijin was the Prime Minister in charge of the entire Dajokan, the Council of State, made up of the ministers of the left and right and the 8 bureaus of the government.  The Sadaijin and Udaijin served under the Dajodaijin, in that hierarchical order, with the Sadaijin generally being considered higher in precedence.  So it looks like, in this case, they had the Dajodaijin, Prince Takechi to run the Council and Shima, as Udaijin would have been responsible for ensuring the administration of the eight bureaus was properly carried out. That Shima was appointed just under Prince Takechi again shows the power and influence he likely had and the trust he must have had from Uno no Sarara.  Remember, the Crown Prince, Kusakabe, had died before he could take the throne.  Uno was enthroned as Queen, while the Crown Prince, Karu, was still a minor.  Whereas Ohoama had his wife and many sons to help him run things, Uno no Sarara was running thin.  As had been seen with Prince Ohotsu, there was always the threat that one of Ohoama's other sons could be propped up on the throne.  Uno had to look after Karu's birthright, but there was no guarantee that he would make it to adulthood in times before modern medicine.  It appears that Prince Takechi was actually considered the next in line, just in case something happened to Karu before he could ascend the throne, which makes sense that Prince Takechi was also trusted as Dajo Daijin.  Shima's place as Udaijin must have been indicative of similar trust that he would look after the royal family's interests.  This was no doubt helped by the role he played as Dazai no Sochi. As Udajin, Tajihi no Shima went on to have a rather incredible career.  He was given 4 cho of land for his residence.  This appears to be around 10 acres or so—a not inconsiderable amount of land, and it probably refers to the amount of land he was granted in the new Fujiwara capital city.  Later, in the Nara capital of Heijo-kyo, Prince Nagaya's residence was about that size and Fujiwara no Nakamaro's residence is thought to have been about twice that.  This would have given Shima space for multiple buildings, sprawling gardens, servants quarters, quarters for his wives and children, and much more. Tajihi no Shima would continue in his role as Udaijin, and would eventually, be promoted to the position of Sadaijin, a post he held only briefly, as he passed away almost a year later. He was not forgotten, however.  It is thought that he was the model for one of the suitors of Kaguya Hime in the famous story of Taketori Monogatari—the tale of the Bamboo Cutter.  Taketori Monogatari, also known as Kaguya Hime Monogatari, is considered the oldest known story in the Monogatari form.  It was probably written in the late 9th or early 10th century, with references to it appearing in works as early as 909 CE.  This suggests that Tajihi no Shima and others were still remembered, at least in part, over a century later. Shima is also thought to have been the patron of the famous poet, Kakinomoto no Hitomaro, one of the famous 36 immortal poets.  We'll have to include Hitomaro in a later episode, though we might come back to him after this reign, as he isn't mentioned in the Chronicles, but we do have some fragmentary biographical information thanks to his inclusion in the Man'yoshu.  In fact, he's probably one of the most famous poets in the Man'yoshu who is not otherwise mentioned.  We are told that he was the court poet during the reign of Uno no Sarara, so it makes sense that Shima may have very well been his patron and helped him get his start. Now while Shima was back in Asuka, making it big in the court, the position of Tsukushi no Dazai had to be filled, and we are told that the mantle was taken up by Awada no Mahito no Ason.  This name is a bit tricky, as it seems to have two kabane:  Mahito and Ason.  Since his father is said to have been Kasuga no Awada no Omi no Kudara, the assumption seems to be that "Mahito" was his name, rather than his kabane.  Although it was likely pronounced "Mabito" at the time, I'm going to go with the modern pronunciation of "Mahito" in part to distinguish it from the kabane.  A quick side note:  When reading names from this period, we usually see the kabane coming right after the family name, as the kabane is basically a rank for the family and not the individual.  But we do occasionally see the kabane tacked on at the end of a name, as in Awada no Mahito's case.  I would also like to quickly draw your attention to his father's name:  Kudara.  That can also be read as Baekje.  Was this an indication that his father or an ancestor came from the continent, perhaps from Baekje?  Or just that he had close ties to that kingdom?  I couldn't find anything specific, but it seems interesting that he was put in place at the Dazai, where dealing with the continent would have been an important part of his duties. Awada no Mahito was not just a noble of the court, and even if his father was of Baekje descent, that may not have been the main thing that gained him the position.  It may have also had to do with an earlier incident.  We are told that in 653 Mahito was one of those who traveled with the 2nd envoy to the Tang court as a scholar monk.  He would later return to secular life, but that experience must have been a big feather in his cap, helping him land a good position at court.  In fact, in 685, we are told that he was Jikikwoushi rank—a fairly respectable position for anyone at the time—and he apparently tried to get his father raised to the same rank as he was.  Aston translates the record as saying he was willing to give his rank to his father, but it is unclear to me if this means he was offering to give up his rank altogether.  At the very least it seems that he felt awkward outranking his father—a good, filial attitude, it would seem.  However, Ohoama didn't care.  In the past, rank may have been given to entire families, but now the court was giving rank to individuals, and the rank Mahito had earned was his, not his father's.  And so his request was denied. Four years later, Ohoama was gone and Awada no Mahito was sent to the Tsukushi no Dazai.  We are told that he was in that position as of 689.  If that was the position of Dazai no Sochi, however, he didn't hold it for long, as Prince Kawachi was raised up to that position that same year, and here we have a bit of a conundrum.  Mahito is only mentioned as "Tsukushi no Dazai" while Prince Kawachi is specifically mentioned, at least twice, as Tsukushi no Dazai no Sochi.  There are some who suggest that Mahito may have been the Dazai Daini, an assistant to the Dazai no Sochi—effectively the second-in-command it would appear.  This makes some sense, when you consider it, and he may even have been acting Dazai no Sochi until Prince Kawachi was appointed. Of course, because our records are quite lackluster, and we are never actually told when Tajihi no Shima left the position, it is possible that Awada no Mahito was actually the Dazai Sochi for many years leading up to 689, and that Shima had returned to Asuka some time ago.  This is the problem with the way things are written—sometimes they mention a name and sometimes just a position, and rarely do they mention when someone stepped down. Still, Mahito oversaw a few things that we can be somewhat sure about as they happened after he is first mentioned in the position, though it was all in the same year.  For one thing, he is the one who presented gifts to the 174 Hayato in the first month of 689.  This included cloth, ox hides, and deerskins.  He was also there when the Queen sent relief to the Barrier Wardens whose terms were up.  These were the Sakimori, a position set up to defend the archipelago and repel any potential invasions.  I would assume they were regularly rotated out, especially if they were expected to man the fortifications out on some of the islands.  It is interesting that we don't often see them referenced, so it isn't clear to me why the reference was made here—it may have just been a note in one of the sources the Chroniclers were using. Later that same year, we also see garments being given out—likely meaning official court clothing—to the Tsukushi Dazai and others.  This was probably to bring them all in line with the latest formal wear being used in the court in Asuka.  We also know that in the 6th month of that year they entertained the Silla envoys, who were given various presents. And then, two months later, Mahito is out and Prince Kawachi comes in.  At the same time that Prince Kawachi is being made the Dazai no Sochi, our previous Dazai no Sochi, Tajihi no Shima, had his rank and fief increased.   I doubt this was a coincidence, and it is one of the things that, for me, lends credence to the idea that Shima had just then returned to Asuka and Prince Kawachi was his replacement, suggesting that Mahito had really just been in an acting capacity while the change over was taking place. Unfortunately, if we were looking for more information about Prince Kawachi's background, we would be disappointed.  Although he is a prince, probably descended from Nunakura, aka Bidatsu Tennou, we don't have a lot about him.  He—or someone with the same name, since we do see these Princely titles get reused, it seems—is found in the reign of Ohoama traveling with Ohotomo no Yasumaro and Fujiwara no Ohoshima to go entertain Gim Jisyang of Silla.  Later we see a Prince Kawachi delivering eulogies during Ohoama's funeral.  That suggests he held an important position, and that he was somewhat familiar with the continent, but we don't get a whole lot more.  Our next evidence is when he was appointed to the post of Dazai no Sochi in 689, a position he would hold until his death in 694—which may also explain why we just don't see too much of him in the record.  A promising career may have been cut short, as happened all too often back in that day and age. Still, as Dazai no Sochi, he had plenty to keep him busy.  Not a month after he arrived, Isonokami no Maro and Ishikawa no Mishina arrived at the head of a delegation.  They were there to deliver patents of rank to members of the Tsukushi government and to inspect the fortifications at the edge of the archipelago.  These were the same fortifications being manned by the newly arrived Sakimori. Speaking of the members of the Tsukushi government, it took a lot of people to make the Dazaifu work, not just the Sochi giving people orders about what they should do.  There were numerous assistants helping to keep everything running.  Some of them would have just been dealing with the Sochi's own residence, while others were clerks, guards, and more.  It really was a miniature version of the court in Asuka, and would have required a lot of people to tend to it.  And we know of at least one of them:  Tsukushi no Fubito no Masaru, whose imagined thoughts we heard at the top of the episode.  In 691, Masaru was recognized for 29 years of service as a secretary to the Tsuksuhi no Dazai.  Twenty-nine years in place suggests to me that he would have likely been one of the longest serving members of the Tsukushi government center.  He would have known where all the bodies were buried—perhaps quite literally.  While the Dazai no Sochi was often a temporary appointment, sometimes just for a few years, they would have likely leaned on Masaru for his expertise.  This is just like how modern government appointees like ambassadors may come and go, including for political reasons, but they rely on permanent staff, including a lot of locals, to provide the institutional knowledge they need to do their jobs.  One can assume that if Masaru had been successful for 29 years he knew how things were supposed to work.  And so I hope that his superiors made sure to remember that when Secretary's day rolled around. Prince Kawachi didn't make it 29 years, but he made it five.  He might have gone even longer, but he died in office in 694 and was posthumously raised in rank for his service.  History is full of stories, but in real life, the stories don't always follow the expected narratives.  As much as we'd like to think otherwise, good, moral people do not always triumph and sometimes those who do awful things are never punished.  And some times stories come to abrupt ends.  Of course, looking back, it just is what it is.  Prince Kawachi's life becomes little more than a footnote.  And yet, what if he had gone on?  Would he have followed Tajihi no Shima to help become one of the grand ministers of the court?  Unfortunately, we will never know.  He could have been a rising star, but we just know about his passing. Five months after Prince Kawachi's untimely death, he was followed in the post by Prince Mino.  Prince Mino would continue in the position, it seems, through the end of the reign in 697—or at least nobody else was appointed until 700, when Isonokami no Maro—apparently the same one who had previously come out to inspect the fortifications during Prince Kawachi's tenure—was appointed.  Although he came into the position in the next reign, we'll still touch on him, as he was another notable figure at this time. Looking back at Prince Mino, however, we seem to run into a problem—there are too many Princes Mino in the record.  If you just use the English translations, you'll find several references to Prince Mino, but if you look at the original text, you'll see that there are at least three different spellings.  For one it means "Beautiful Field" and another is just "Three Fields".  A third "Mino" is spelled with characters that don't necessarily create obvious meaning, and may just be a phonetic spelling. It is possible that all of these Princes Mino are the same.  Spelling wasn't standard, and different characters could be used for the same name.  On the other hand, we have one set of characters being used to describe a Prince Mino who supported Ohoama during the Jinshin no Ran, while another, the "Three Fields" Prince Mino, describes one of the sons of Prince Kurikuma, who was with his father in Tsukushi when the Afumi court came calling.  Since travel wasn't necessarily an overnight endeavor—unless you were Ohoama, rushing through the mountains to the east—it would seem that the Prince Mino in Tsukushi is unlikely to be the same one as the Prince Mino who joined Ohoama's forces back in the Home Provinces. So let's make the assumption that Prince Mino—Prince "Three Fields" Mino—is one person and the others are separate.  What do we know about him? Well, he appears to have had experience with Tsukushi and the government out  there, since he would be the son of Prince Kurikuma, a former Tsukushi Dazai no Sochi.  We talked about Prince Kurikuma before, back in numerous episodes, but particularly in episodes 128 and Episode 144, as well as references in betweend. Prince Kurikuma was not only a significant factor in the outcome of the Jinshin no Ran, denying the Afumi court the resources of all of the defenders at the Tsukushi fortifications, he shows up in local legends in Tsukushi still today.  So he definitely seems to have had an impact on the region.  It also suggests that Prince Mino had connections in the area through his father. After his father's posting as Dazai no Sochi ended, Prince Mino appears to have returned with him to Asuka.  He is described as a key member in Ohoama's court.  He was one of the Princes mentioned in the audience at the Daigokuden in 681, when Ohoama instituted the commission to bring together the various court sources that we presume would eventually lead to the creation of the Chronicles—the Nihon Shoki and the Kojiki.  Later, he become a daibu, a high official, of the Household Bureau, responsible for the household of the sovereign, the sumera no mikoto.  This meant the upkeep of the palace, the kitchens, and the various servants waiting on the sovereign and his family.  This also means that he was likely close to the movers and shakers of the court. One of the projects under his purview appears to have been the laying out of a new palace and a new capital city.  In 682 he headed up the investigations at the place called Nihiki, determining that it would be a good location for what would eventually become Fujiwara-kyo—a project still underway in Queen Uno's reign.  He was also sent out to Shinano two years later to look for a site for a second capital.  It ended up not happening, but he spent a couple months and eventually came back with a map of the region.  It may be that the Fujiwara-kyo project took up a lot of Mino's time and effort, because we then don't hear from him for another decade, during which Ohama passed away and so much more happened.  Assuming he was still involved with the Fujiwara capital project, however, we see that in 691 there was a ceremony held for the tranquility of the new capital—a Chin-sai or, what we would today call a "Ji-chin-sai".  This is a "land pacification ceremony" done when breaking ground on a new building or other project.  So it looks like planning and land clearing had taken some 10 years, but it was finally ready to get started.  Later that same year we hear of them laying out the residences of high ranking nobles, like the Udaijin, Tajihi no Shima, and we also see the Queen inspecting the roads.  Then, a year later in 692, they were holding the land pacification ceremony for the new palace.  The queen would move into the new palace in the very last months of 694. But by that time, Prince Mino was on to his next assignment.  He had been appointed Tsukushi Dazai no Sochi earlier that year following the death of Prince Kawachi.  Not much more is said of Tsukushi for the next three years of the reign, but we do see the Hayato visiting Asuka, presumably with Prince Mino's assistance. We don't have a clear idea of when Prince Mino retired—it's certainly not in the Nihon Shoki—but we know that he did because he was succeeded in the role by none other than Isonokami no Maro, who would take up the position in 700.  Prince Mino, on the other hand, returned to the court, where he would eventually pass away in the year 708. And that was the last Dazai no Sochi who held the position during this reign, but I do want to talk about the one who came after Prince Mino just a bit—though more because this was an up-and-coming court noble whom we should be watching. Isonokami no Maro was born, by all accounts, in the year 640.  Despite his name he was actually born to a family that we know somewhat well from much earlier on: The Mononobe.  In fact, his father is apparently Mononobe no Muraji no Umaro, and he appears to be descended from the main line of the Mononobe family, which had declined ever since Mononobe no Moriya had been defeated and killed by Soga no Umako and others. And it seems that the Mononobe curse of being on the losing side in a contest for power hit Maro during the Jinshin no Ran, because we see him, at that time referenced as Mononobe no Muraji no Maro, along with two servants, or Toneri, serving Prince Ohotomo—aka Koubun Tennou—up to the very end.  In fact, when Ohotomo fled and the Afumi court deserted him, only Mononobe no Maro and the servants stayed with him when he eventually strangled himself. And one would think that would be it.   You were with the rival for the throne in the most contentious fight in recent memory.  You couldn't protect him and you were on the wrong side.  Sure, Ohoama was going to pardon you because he couldn't just rid himself of half of the court and hope things would still run smoothly—that would be a surefire recipe for disaster, and nobody wanted the government crippled like that.  However, you can't imagine that those on the losing side would be given any position of trust or authority. And yet, in 676, we see that Mononobe no Maro was sent to Silla.  And he wasn't just helping out: he was sent as the chief envoy of Ohoama's court.  That is quite the turnaround in four years, and we don't really know why, but it has been speculated that Ohoama was actually impressed.  While other members of the Afumi court fled and abandoned Ohotomo to his enemies, Maro and the two toneri with him did not, staying with Ohotomo until the bitter end, and likely conveying what had happened to the other side once it was all over.   That kind of loyalty was impressive, especially back then. It is also thought that Maro may have benefited from the fact that Enoi no Okimi, who was also descended from the Mononobe family, fought on the side of Ohoama.  This is a common scenario we see throughout Japanese history, where different members of the same family fight on different sides of a conflict, often meaning that no matter who wins the family can still claim to have been on the winning side.  When Okimi passed away in 676 he was posthumously recognized as the ujigami, or clan head, of the Mononobe, leading some to suspect that a bit of his shine may have rubbed off on Maro as well. In 684, when the various kabane were being rectified by Ohoama's court, the Mononobe no Muraji were included as Ason, or Asaomi.  There is some thought that around this time is when Maro changed his name to Isonokami, which is a name that was previously used by members of the Mononobe, including one of the brothers to Mononobe no Moriya.  We see him mentioned as Isonokami no Maro in 686, as one of those giving a eulogy for Ohoama: specifically he gives the eulogy on behalf of the Houkan, or Nori no Tsukasa, the Judicial officers.  He is mentioned right after Fuse no Miushi, whom we talked about last episode, who would go on to become a Dainagon and, later, Udaijin, or Minister of the Right. The first connection between Isonokami no Maro and Tsukushi was in 689, and we noted it earlier—he came out to inspect the fortifications as well as to hand out patents of rank to the court officials working out there on the edge of the realm.    He would return to Asuka in time to be a part of Uno no Sarara's official enthronement ceremonies.  There he is named Mononobe no Maro, and is in charge of the shields.  Given what we know of the role of the Mononobe as the early soldiers of the court, it makes sense that he would play this role, and that they would use the name Mononobe rather than Isonokami.  In the same way, the ritual was conducted by Fujiwara no Ohoshima, but he is recorded as Nakatomi no Ohoshima, probably because these were roles specifically for the Mononobe and Nakatomi, rather than for the Isonokami and the Fujiwara. This is another thing that can be quite frustrating when researching Japanese history—names can change at the drop of a hat, and people often had various ancestral names and titles that could be pulled out for various political or ceremonial reasons.  If you don't have the history or understand the nuance it can be easy to just think that it is a different person altogether.  And when you don't have much information, sometimes you have to ask yourself which is it? Maro would stay close to Queen Uno, even accompanying her to Ise shrine, and then, in the following reign, he would succeed Prince Mino as Dazai no Sochi in the year 700.  It isn't clear, however, if he left for the Dazaifu immediately, since in 701 he is noted as having been promoted from the office of Chunagon to Dainagon, and in that same year he went with Royal Prince Osakabe to pay respects at the house of the late Udaijin, Tajihi no Shima, who had just passed away.  He then left for Tsukushi in 702—or possibly headed back.  But in 703, he was once again back in Asuka, paying condolences on the death of the next Udaijin, Abe no Miushi—aka Fuse no Miushi, the same one whom Maro had pronounced a Eulogy with during the funeral ceremonies for Ohoama.  Isonokami no Maro would go on to take the mantle of Udaijin, and then eventually Sadaijin as well.  He would be raised up to the second rank, along with the famous Fujiwara no Fubito, who took the vacated position of Udaijin.  This meant that technically Maro was the senior of the two, though many people think that Fujiwara no Fubito held most of the actual power.  Regardless of that, Isonokami no Maro nonetheless would go on to become the highest ranking court noble before his eventual death in 717.  At that point he was 78 years old, by the reckoning of the day, and he had seen multiple sovereigns, several bloody conflicts, and the creation of two permanent capitals—Fujiwara kyo and Heijo kyo, in modern Nara.  He went from being a supporter in the Afumi court, on the wrong side of the Jinshin no Ran to become the highest ranking court noble in the land.  He would be granted the head of the Mononobe family and would continue to prosper as Isonokami.  It was truly a remarkable career over an incredible span of time. And there you have it.  A look at some of those that were sent out to the Dazaifu in Tsukushi.  In later years, the post of Dazai no Sochi would be seen more as a burden than a blessing, but at this point it was still a lucrative and powerful position.  Several of those involved in the Dazaifu or who held the position as Dazai no Sochi would go on to even more powerful positions back in Asuka.  Whilst this posting did move you further away from the politics—perhaps not always a bad thing—it also put you atop a structure where one had considerable power, authority, and autonomy, at least at this point. Next episode we'll get back to the court in Asuka and take a look at a little more of what is going on.  Before I end this, however, a quick administrative note about the podcast.  This creation is a labor of love.  It was started largely as a way to get myself to regularly dive into the Chronicles and really see what was going on.  In particular, I was excited about the Asuka period, because I don't think we really have enough of a sense of what life was like and what was going on back then.  It was clearly a very dynamic time, and yet we tend to see it through the lens of later Nara and Heian court culture, which was still very much evolving.  The stories that I *didn't* know about were what drew me to this project, and I hope that we've all learned a bit more as the project has continued. And we are reaching the end of the area that is covered by the main Chronicles, the Kojiki, the Nihon Shoki, and the Sendai Kuji Hongi, which have been our main guides through this period.  But that doesn't mean we are bringing things to a close. Next we have the Shoku Nihongi and many other grecords, and I am going to keep up with the project and the schedule as best I can.  In fact, it looks like I may be able to devote even more time to it in the near future as some drastic life changes are coming for me, such that I will no longer be working a 9-to-5 job while also trying to get this podcast out like clockwork twice a month—not to mention my other passion, teaching traditional Japanese martial arts here in the DC region at a local not-for-profit dojo.  This is happening as we are also in the process of building a house, traveling, and more.  But it does mean that we are going to be looking into alternative sources of funding beyond just donations.  We are eternally grateful to everyone who has donated, but I may end up doing something that I've been putting off for a while: allowing advertisements.  I want to do this so that we can continue to offer this for podcast for free, but hosting, staying up to date on sources, etc. does cost money.  I'm not looking to make a huge profit, but if we can at least get the podcast paying for itself, that would be a good start. Before I do that I'll look to find a way that we can get subscribers on Patreon and elsewhere ad-free copy.  I just need to figure that out, but once I do, I'll let you all know. So there you have it.  We aren't going to stop the podcast, but we may be adding a bit more to it in the future.  I hope, though, that we can do more beyond the historical chronicles.  For instance, did you know that we have an English translation of a 17th century cookbook up on our website, SengokuDaimyo.com?  I would love to redact those recipes and maybe provide some cooking videos for anyone who would want to try them.  A shoutout to Max Miller of Tasting History, who reached out to us about using a couple of our translations for his episodes on historical Japanese cooking – Max is a great guy and his series and cookbook are well worth following.  But there's a lot more to explore: one of my favorites so far that we've tried is "keiran", or "eggs": doughy balls filled with brown sugar and cooked in a miso based soup.  I don't know if there is anything like that still being served in Japan, but it's a strange and pleasant recipe and I would love to do that again and record it for everyone to try. All of this is in the works, and nothing will change immediately, but I wanted to keep you all in the loop.  Thank you so much for listening, I can't tell you how much it means. And of course, as always, if you like what we are doing, please tell your friends and feel free to rate us wherever you listen to podcasts.  If you feel the need to do more, and want to help us keep this going, we have information about how you can donate on Patreon or through our KoFi site, ko-fi.com/sengokudaimyo, or find the links over at our main website,  SengokuDaimyo.com/Podcast, where we will have some more discussion on topics from this episode. Also, feel free to reach out to our Sengoku Daimyo Facebook page.  You can also email us at the.sengoku.daimyo@gmail.com.  Thank you, also, to Ellen for their work editing the podcast. And that's all for now.  Thank you again, and I'll see you next episode on Sengoku Daimyo's Chronicles of Japan.

Will Garrison started at Thrust Flight with zero time, worked his way through flight training, became a CFI, later became an Assistant Chief Instructor, joined the Envoy cadet program, and now flies the Embraer 175 as a First Officer at Envoy.

A newly disclosed attack called HTTP/2 Bomb can crash major web servers in seconds using a single computer and a modest internet connection. Researchers say the attack combines two known techniques into a powerful memory-exhaustion exploit affecting widely used platforms including Apache, NGINX, Microsoft IIS, and Envoy. The attack also highlights a growing trend in cybersecurity research: the use of artificial intelligence to uncover dangerous combinations of existing vulnerabilities. The episode also examines President Trump's new executive order creating a voluntary framework for reviewing advanced AI models before public release. The administration says the goal is to improve cybersecurity and national security visibility while avoiding mandatory regulation or licensing requirements. Next, a new Cloud Security Alliance report warns that organizations are struggling to keep up with the growing volume of vulnerabilities. Security teams increasingly face difficult choices about which flaws to patch first as cloud environments, containers, APIs, and third-party software continue to expand the attack surface. Finally, CISA warns that attackers are actively exploiting both a newly patched Android vulnerability and a years-old Linux flaw. The contrast highlights a simple reality: cybercriminals do not care whether a vulnerability is new or old. They care whether it remains exploitable. Stories in this episode HTTP/2 Bomb Can Crash Web Servers in Seconds Researchers disclose a denial-of-service technique capable of exhausting server memory in under a minute, while OpenAI's Codex helps uncover a novel attack chain. Trump Creates Voluntary AI Security Reviews as Government Seeks Visibility Into Frontier Models A new executive order establishes voluntary reviews of advanced AI systems before public release, raising questions about visibility, oversight, and national security. The Cybersecurity Industry's Patch-Everything Strategy May Be Breaking Down A Cloud Security Alliance report suggests organizations are overwhelmed by vulnerability volume and increasingly forced to choose which risks to address. CISA Warning Shows Attackers Don't Care Whether a Vulnerability Is New or Old Active exploitation of both a newly patched Android flaw and an older Linux vulnerability demonstrates that attackers focus on opportunities, not disclosure dates. Cybersecurity Today brings you the latest cybersecurity news, threat intelligence, breach reports, vulnerability disclosures, ransomware developments, cybercrime investigations, and security research affecting organizations around the world. #Cybersecurity #CyberSecurityToday #InfoSec #CyberNews #Ransomware #ThreatIntelligence #VulnerabilityManagement #AndroidSecurity #LinuxSecurity #ArtificialIntelligence #HTTP2 #CISA #CloudSecurity #OpenAI #PatchManagement

Arrivals from the country's top 20 overseas markets were down 2.2% in the first four months of this year. America's new tourism envoy, Nick Adams spoke to Cian about how he plans to reverse the declines .

Dans ce jeu du "Qui Qui Express", la règle est simple : à chaque personnalité retrouvée par les Grosses Têtes, l'auditeur ou l'auditrice remporte 50 euros ! Retrouvez tous les jours le meilleur des Grosses Têtes en podcast sur RTL.fr et l'application RTL.Hébergé par Audiomeans. Visitez audiomeans.fr/politique-de-confidentialite pour plus d'informations.

British police, specifically Thames Valley Police, are currently assessing a complaint alleging that Prince Andrew, now Andrew Mountbatten-Windsor, may have shared confidential government and trade information with the late convicted sex offender Jeffrey Epstein. The inquiry was triggered by newly released U.S. Department of Justice documents showing email exchanges from 2010, while Andrew was serving as a UK trade envoy, in which he appears to have forwarded official reports on trade missions — including sensitive commercial and investment data — to Epstein shortly after receiving them. These actions have prompted a complaint from anti-monarchy campaigners alleging misconduct in public office and potential breaches of Britain's Official Secrets Act. Thames Valley Police have confirmed they are “assessing the information in line with our established procedures” and have held discussions with the Crown Prosecution Service to decide whether the case should advance into a full criminal investigation. Meanwhile, Buckingham Palace has stated that King Charles III and the royal family will support and cooperate with any legitimate police inquiry into the matter, and senior royals including Prince William and Princess Catherine have expressed deep concern over the ongoing revelations.The scope of the police inquiry extends beyond the alleged transmission of confidential trade reports: reports suggest authorities are also examining broader aspects of Andrew's relationship with Epstein, including claims regarding how that relationship persisted after Epstein's 2008 conviction. The inquiry remains in its early phases, with no formal charges filed yet, but the involvement of prosecutors and senior investigators underscores its seriousness. Andrew, who was stripped of his royal titles and duties in 2025 amid longstanding criticism over his ties to Epstein, denies wrongdoing, and the police have not committed to a timeline for a decision on whether to launch a formal investigation. The developments have intensified public scrutiny of both the former royal's conduct and the wider implications of the Epstein files for British public figures.to contact me:bobbycapucci@protonmail.comsource:Andrew probed by criminal prosecutors over Epstein scandal as police issue major update after latest file bombshellBecome a supporter of this podcast: https://www.spreaker.com/podcast/the-epstein-chronicles--5003294/support.

The Doug & Don show is sponsored by PrizePicks ➡️ sign up at https://prizepicks.onelink.me/ivHR/BreakingPoint. When you sign up with code BREAKINGPOINT and play $5 in lineups, you'll get $50 in free lineups instantly, win or lose.Timestamps00:00 Intro00:21 JoeDeceives to Paris06:35 Envoy vs Neptune09:54 Traixx to Bush (Bye Abe)17:12 Bush & Stush21:16 How many M8 Red Cards?30:42 Roster Swap Tier List 50:34 Who gets MVP?53:54 A JoeD Dilemma?

On the 241st episode of the Ego Chall Podcast, Justin Binkowski and Preston Byers discuss the one of the greatest nights of Call of Duty League (CDL) RosterMania and in CoD Twitter history, including the beef between Neptune and Envoy, as well as the rumored Toronto KOI, Paris Gentle Mates, and Miami Heretics changes involving JoeDeceives, Neptune, Sib, ReaaL, Traixx, and more.

Children in Ukraine have spent years living with air raid sirens, disrupted education and the daily uncertainty of war. Many are forced to learn online or in underground classrooms as communities adapt to the realities of a prolonged conflict.During recent visits to Ukraine and the Russian Federation, the UN's Special Representative for Children and Armed Conflict, Vanessa Frazier, met children, families, and officials on both sides of the border. Ahead of the International Day of Innocent Children Victims of Aggression, observed on 4 June, she spoke to UN News's Evgeniya Kleshcheva about what she witnessed and why keeping children at the centre of all responses remains essential.

Emails reportedly handed to Buckingham Palace in 2020 appeared to show that Andrew Mountbatten-Windsor shared confidential government information while serving as a UK trade envoy. According to the report, the cache contained more than 30,000 emails, allegedly from the account of British businessman Jonathan Rowland, an associate of Andrew's, and included material connected to Andrew's financial dealings. The emails were reportedly sent to the Lord Chamberlain six years ago, months after Andrew stepped back from royal duties following his disastrous Newsnight interview over his relationship with Jeffrey Epstein. Andrew was later arrested on suspicion of misconduct in public office over allegations that he passed sensitive government information to Epstein while working as a trade envoy; he denies wrongdoing.The most damaging part is the timeline: if these emails were already in Palace hands in 2020, then the question becomes what Buckingham Palace knew, what it did with that information, and whether serious concerns about Andrew's trade envoy conduct were allowed to sit quietly for years. The report also ties the emails to earlier claims that Andrew requested confidential Treasury information about Iceland's financial crisis in 2010 and then passed details to Jonathan Rowland before a business move involving Kaupthing Bank. With police inquiries still ongoing, the Palace declined to comment, citing the investigation, but the story adds another layer to the broader Andrew scandal: Epstein was not the only issue — the allegations now reach into Andrew's official government role, his business contacts, and the possibility that warning signs were sitting inside the royal household years before public accountability caught up.to contact me:bobbycapucci@protonmail.comsource:Palace was given emails about Andrew's trade envoy activities six years ago, report says | UK news | The Guardian

Emails reportedly handed to Buckingham Palace in 2020 appeared to show that Andrew Mountbatten-Windsor shared confidential government information while serving as a UK trade envoy. According to the report, the cache contained more than 30,000 emails, allegedly from the account of British businessman Jonathan Rowland, an associate of Andrew's, and included material connected to Andrew's financial dealings. The emails were reportedly sent to the Lord Chamberlain six years ago, months after Andrew stepped back from royal duties following his disastrous Newsnight interview over his relationship with Jeffrey Epstein. Andrew was later arrested on suspicion of misconduct in public office over allegations that he passed sensitive government information to Epstein while working as a trade envoy; he denies wrongdoing.The most damaging part is the timeline: if these emails were already in Palace hands in 2020, then the question becomes what Buckingham Palace knew, what it did with that information, and whether serious concerns about Andrew's trade envoy conduct were allowed to sit quietly for years. The report also ties the emails to earlier claims that Andrew requested confidential Treasury information about Iceland's financial crisis in 2010 and then passed details to Jonathan Rowland before a business move involving Kaupthing Bank. With police inquiries still ongoing, the Palace declined to comment, citing the investigation, but the story adds another layer to the broader Andrew scandal: Epstein was not the only issue — the allegations now reach into Andrew's official government role, his business contacts, and the possibility that warning signs were sitting inside the royal household years before public accountability caught up.to contact me:bobbycapucci@protonmail.comsource:Palace was given emails about Andrew's trade envoy activities six years ago, report says | UK news | The GuardianBecome a supporter of this podcast: https://www.spreaker.com/podcast/the-moscow-murders-and-more--5852883/support.

Un homme célèbre, adulé par de nombreux fans et bénéficiant d'un succès certain auprès des femmes est accusé d'agression sexuelle, viol ou tentative de viol par plusieurs femmes, les témoignages des unes déclenchant, en cascade, ceux des suivantes. Lui nie les faits ou évoque des relations consenties. L'affaire Patrick Bruel ressemble à beaucoup d'autres affaires de violences sexistes et sexuelles (VSS), comme celles impliquant le journaliste Patrick Poivre d'Arvor ou l'acteur Gérard Depardieu.Patrick Bruel, 67 ans, a cultivé une image de séducteur, porté par le phénomène « Bruelmania » dans les années 1990. Aujourd'hui, le chanteur et comédien est visé en France par au moins quatre enquêtes pour viols et une enquête judiciaire en Belgique pour agression sexuelle. Initialement classée, une plainte pour un viol présumé sur une jeune femme en 2015 vient, quant à elle, d'être rouverte.Dans les affaires de VSS impliquant des célébrités, les schémas de prédation semblent se répéter et les mêmes questions resurgissent : apparemment « tout le monde savait », alors pourquoi l'affaire n'éclate-t-elle que maintenant ? On entend parfois que la multiplication des accusations serait suspecte, mais ne permet-elle pas au contraire d'accréditer la parole des femmes qui les prononcent, aux yeux de la justice ? Comment garantir la présomption d'innocence des hommes accusés sans que celle-ci ne soit brandie pour discréditer la parole des victimes ? Comment prendre en charge judiciairement ces affaires lorsqu'il existe rarement les preuves qu'exige un tribunal ou que les faits sont prescrits ?Toutes ces questions, nous les posons dans cet épisode de « L'Heure du Monde » à Lucie Soullier, journaliste au service société du Monde.Un épisode d'Adélaïde Tenaglia. Réalisation : Florentin Baume, avec l'aide de Quentin Tenaud. Présentation : Claire Leys. Suivi éditorial : Claire Leys et Sophie Larmoyer. Musiques : Amandine Robillard et Epidemic sound. Dans cet épisode : extrait d'une interview de Flavie Flament par Médiapart, le 18 mai 2026 ; d'interviews de l'avocat Christophe Ingrain sur RTL et France 5, le 18 mai 2026 ; d'un document d'« Envoyé spécial » diffusé sur France 2, le 24 octobre 1991.Cet épisode a été publié le 2 juin 2026.---Pour soutenir "L'Heure du Monde" et notre rédaction, abonnez-vous sur abopodcast.lemonde.fr Hébergé par Acast. Visitez acast.com/privacy pour plus d'informations.

Issue de la mode, la photographe Lee Miller est l'une des rares femmes à couvrir la Seconde guerre mondiale. Elle photographie les camps de Buchenwald et Dachau ; elle n'en revient pas indemne.Plongez dans l'incroyable parcours de Lee Miller, une photographe américaine qui a couvert les événements marquants de la fin de la Seconde Guerre mondiale en Europe.

A right-wing political outsider wins the first round of Colombia’s presidential election. Plus: a live interview with Nick Adams, special presidential envoy for American tourism, exceptionalism and values, to discuss his new role and Trump’s plan to boost inbound tourism to 100 million visitors by 2030. See omnystudio.com/listener for privacy information.

Emails reportedly handed to Buckingham Palace in 2020 appeared to show that Andrew Mountbatten-Windsor shared confidential government information while serving as a UK trade envoy. According to the report, the cache contained more than 30,000 emails, allegedly from the account of British businessman Jonathan Rowland, an associate of Andrew's, and included material connected to Andrew's financial dealings. The emails were reportedly sent to the Lord Chamberlain six years ago, months after Andrew stepped back from royal duties following his disastrous Newsnight interview over his relationship with Jeffrey Epstein. Andrew was later arrested on suspicion of misconduct in public office over allegations that he passed sensitive government information to Epstein while working as a trade envoy; he denies wrongdoing.The most damaging part is the timeline: if these emails were already in Palace hands in 2020, then the question becomes what Buckingham Palace knew, what it did with that information, and whether serious concerns about Andrew's trade envoy conduct were allowed to sit quietly for years. The report also ties the emails to earlier claims that Andrew requested confidential Treasury information about Iceland's financial crisis in 2010 and then passed details to Jonathan Rowland before a business move involving Kaupthing Bank. With police inquiries still ongoing, the Palace declined to comment, citing the investigation, but the story adds another layer to the broader Andrew scandal: Epstein was not the only issue — the allegations now reach into Andrew's official government role, his business contacts, and the possibility that warning signs were sitting inside the royal household years before public accountability caught up.to contact me:bobbycapucci@protonmail.comsource:Palace was given emails about Andrew's trade envoy activities six years ago, report says | UK news | The GuardianBecome a supporter of this podcast: https://www.spreaker.com/podcast/the-epstein-chronicles--5003294/support.

Pour notre invitée, le Sénégal n'est pas une destination. C'est une histoire de famille.Ondine Saglio est née à Dakar, a grandi pieds nus sur l'île de Gorée, et a découvert Paris à sept ans avec des poux dans les cheveux et les vêtements de son grand frère sur le dos. Son père, ethnologue et diplomate, voulait que ses enfants soient « des petits Sénégalais ». Sa sœur, elle, avait été envoyée à dix ans garder des chèvres en Casamance. Sa mère a fondé la CSAO dans un garage du 7e arrondissement, devenue aujourd'hui une institution de l'artisanat ouest-africain. À la croisée de ces deux mondes, Ondine a construit toute sa vie.Aujourd'hui, elle dirige la CSAO, fait travailler une cinquantaine de brodeuses à l'Atelier des Rêves à Dakar, collabore avec Sézane, Bonpoint et Christian Louboutin. Une commande Louboutin permet à ces femmes six mois de revenus et, parfois, l'autonomie nécessaire pour quitter une situation violente. Au-dessus de l'atelier vit La Maison Rose : un refuge pour les femmes des rues enceintes, où la broderie est devenue une thérapie après les traumatismes. À cela s'ajoute l'Empire des Enfants, le programme pour enfants des rues que sa mère a porté pendant vingt ans.Dans cet épisode, Ondine nous raconte tout, son enfance hors-normes avec un père qui allait travailler en planche à voile, le retour brutal à Paris dans une école du 7e, la naissance de la CSAO dans un garage, et la manière dont elle a fait dialoguer le luxe et l'engagement social sans jamais s'excuser de l'un ou de l'autre.Elle partage aussi ses meilleures adresses au Sénégal : la maison d'hôtes solidaire de Gorée, le thieboudienne, le bissap, la brochette de lotte au riz de Casamance, et les meilleures périodes pour partir.Un épisode à écouter quand on a envie d'être une meilleure voyageuse. Ou à envoyer à ceux qui rêvent du Sénégal sans savoir vraiment pourquoi.Un podcast produit et réalisé par Sakti Productions & Beau Voyage

durée : 01:02:28 - Les Nuits de France Culture - par : Albane Penaranda - En 2009, dans un numéro des "Lundis de l'histoire" consacré au maintien de l'ordre, Michelle Perrot reçoit Jean-Marc Berlière, historien pionnier dans ce domaine, Geneviève Pruvost, qui publie un ouvrage sur la féminisation de la police et Dominique Kalifa pour "Biribi, les bagnes coloniaux". - réalisation : Mathias Le Gargasson, Antoine Dhulster, Rafik Zénine, Vincent Abouchar, Emily Vallat, Hassane M'Béchour, INA Vous aimez ce podcast ? Pour écouter tous les épisodes sans limite, rendez-vous sur Radio France

" Dieu a envoyé son Fils, pour que, par lui, le monde soit sauvé "Méditation de l'évangile (Jn 3, 16-18) par le père Eric CourtoisChant final : "Revenez à moi" par Soeur AgatheRetrouvez tous nos contenus, articles et épisodes sur rcf.frSi vous avez apprécié cet épisode, participez à sa production en soutenant RCF.Vous pouvez également laisser un commentaire ou une note afin de nous aider à le faire rayonner sur la plateforme.Retrouvez d'autres contenus de vie spirituelle ci-dessous :Halte spirituelle : https://audmns.com/pMJdJHhB. A. -BA du christianisme : https://audmns.com/oiwPyKoLe Saint du Jour : https://audmns.com/yFRfglMEnfin une Bonne Nouvelle : https://audmns.com/afqCkPVConnaître le judaïsme : https://audmns.com/VTjtdyaEnfin, n'hésitez pas à vous abonner pour ne manquer aucun nouvel épisode.À bientôt à l'écoute de RCF sur les ondes ou sur rcf.fr !Hébergé par Audiomeans. Visitez audiomeans.fr/politique-de-confidentialite pour plus d'informations.

“AI can negotiate freight rates” is one of those claims that sounds true until you sit on a real brokerage floor and watch what happens. I'm joined by Robby Nathan, founder of Load Delivered, CEO of Envoy AI, and a longtime freight operator, to break down what separates automation that actually helps from automation that just fires off templated emails and calls it intelligence. We start with the roots: how Robbie went from a philosophy degree to the carrier desk, why he chose temperature-controlled, high-value freight in the 2008 downturn, and what hyper specialization teaches you about SOPs, service, and building a carrier network that can handle high expectations. From there we get into the hard parts of scaling a freight brokerage: capital constraints, enterprise shippers that cap your volume, EDI setup delays, and the leadership shift that hits when the company outgrows your personal operating style. We also tackle the new risk reality after the Supreme Court negligent hiring environment, why inconsistent processes across pods or agents can create major liability, and why carrier vetting and documentation are becoming non-negotiable for brokers and 3PLs who want to stay in business. Then we go deep on logistics AI, adaptive rate negotiation, and the semantic layer needed to move from copilot to safe autopilot. Robby shares what he's building with Envoy around carrier communication, verification filters, and a future where freight operators manage AI workers instead of living on the phone all day. If you care about freight tech, carrier compliance, TMS data quality, and the future of brokerage, this one will challenge how you think about “automation.” Subscribe, share with a teammate, and leave a review. What part of brokerage should never be manual again?Follow The Freight Pod and host Andrew Silver on LinkedIn.Thanks to our sponsors:Stuut Technologies: Your AI coworker that collects your cash automatically.https://www.stuut.ai/Cloneops.ai: Not just AI. Industry-born AI.https://www.cloneops.ai/Rapido Solutions Group: Nearshore solutions for logistics companies.https://www.gorapido.com/GenLogs: Freight Intelligence on every carrier, shipper, and asset via a nationwide sensor networkhttps://www.genlogs.io/

The British government says it has found no evidence that formal security vetting or due diligence was carried out before Andrew Mountbatten-Windsor was appointed as the UK's special representative for international trade and investment in 2001. Newly released historical documents show that Queen Elizabeth II was “very keen” for Andrew to have a prominent role promoting Britain's interests, and officials appear to have treated the appointment as a continuation of the royal family's existing trade-promotion work rather than as a post requiring serious scrutiny. That matters because the job gave Andrew access to senior business and government figures around the world, yet the government now says there is no sign anyone formally examined whether he was fit for that level of access. The documents also reveal a strikingly privileged setup around the role, including notes about the countries Andrew preferred to visit, how his travel should be managed, and the need for careful media handling.The larger significance is that Andrew's trade envoy role is now being reexamined through the lens of the Epstein scandal and later allegations about his conduct in public office. Andrew served in the unpaid post from 2001 to 2011, traveling internationally and moving through elite diplomatic and commercial circles while carrying royal prestige and government access. The lack of evidence of vetting raises obvious questions about how much deference was given to royal status, how little institutional skepticism existed around Andrew's suitability, and whether the government effectively allowed him to operate as a high-level national representative without the checks that would normally apply to someone with comparable reach. In hindsight, the documents make the appointment look less like a carefully controlled public role and more like another example of Andrew being handed power, access, and legitimacy because of who he was, not because anyone had seriously tested whether he should have it.to contact me:bobbycapucci@protonmail.comsource:No evidence of formal security vetting when Andrew became UK trade envoy, minister says | UK news | The Guardian

The boys break down the major roster changes with Paris Gentle Mates involved. Envoy is on his way to G2 with a blockbuster Estreal trade. CDL Tier List of the roster changes so far throws up some surprises.

Hearthstone's leadership team released their first Dev Connect video this morning! and I play Herald Shaman on the ladder. You can find the deck import code below the following contact links.  You can follow me @blisterguy on Twitch, Bluesky, and Youtube. Join our Discord community here or at discord.me/blisterguy. You can support this podcast and my other Hearthstone work at Patreon here. # 2x (0) Static Shock # 2x (0) Witch's Apprentice # 2x (1) Twilight Egg # 1x (1) Voltaic Burst # 2x (2) Primordial Overseer # 2x (2) Ritual of Power # 2x (2) Skywall Sentinel # 2x (2) Thunderquake # 2x (3) Flight of the Firehawk # 1x (3) Healing Rain # 1x (3) Hex # 1x (4) Elise the Navigator # 1x (4) Farseer Wo # 1x (5) Envoy of the End # 1x (5) Muradin, High King # 1x (3) Avatar Form # 1x (6) High King's Hammer # 1x (6) Ultraxion # 1x (8) Al'Akir, Lord of Storms # 2x (9) Muradin's Last Stand # 1x (10) Deathwing, Worldbreaker #  AAECAfGKBwyvnwTTvgaCmAfbpgffpgflpgeGpwePvgfQvweC1Aeb1Afv4wcJ5pYH8KoH9awHvLEHw8AHycAH98AH9sEH5v0HAAA=

The British government says it has found no evidence that formal security vetting or due diligence was carried out before Andrew Mountbatten-Windsor was appointed as the UK's special representative for international trade and investment in 2001. Newly released historical documents show that Queen Elizabeth II was “very keen” for Andrew to have a prominent role promoting Britain's interests, and officials appear to have treated the appointment as a continuation of the royal family's existing trade-promotion work rather than as a post requiring serious scrutiny. That matters because the job gave Andrew access to senior business and government figures around the world, yet the government now says there is no sign anyone formally examined whether he was fit for that level of access. The documents also reveal a strikingly privileged setup around the role, including notes about the countries Andrew preferred to visit, how his travel should be managed, and the need for careful media handling.The larger significance is that Andrew's trade envoy role is now being reexamined through the lens of the Epstein scandal and later allegations about his conduct in public office. Andrew served in the unpaid post from 2001 to 2011, traveling internationally and moving through elite diplomatic and commercial circles while carrying royal prestige and government access. The lack of evidence of vetting raises obvious questions about how much deference was given to royal status, how little institutional skepticism existed around Andrew's suitability, and whether the government effectively allowed him to operate as a high-level national representative without the checks that would normally apply to someone with comparable reach. In hindsight, the documents make the appointment look less like a carefully controlled public role and more like another example of Andrew being handed power, access, and legitimacy because of who he was, not because anyone had seriously tested whether he should have it.to contact me:bobbycapucci@protonmail.comsource:No evidence of formal security vetting when Andrew became UK trade envoy, minister says | UK news | The GuardianBecome a supporter of this podcast: https://www.spreaker.com/podcast/the-epstein-chronicles--5003294/support.

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

Louisiana Governor Jeff Landry is in Greenland as President Trump's special envoy, as the president continues pushing the idea of bringing Greenland under American control. During the trip, Landry reportedly offered Greenlandic children a chance to come to Louisiana, where they could eat all the chocolate chip cookies they want. Are you proud to see Louisiana's governor serving as an envoy to Greenland, or should he be home doing the job of governor?