Publisher
Engineering case studies and developer guides from Stripe.
Minions: Stripe’s one-shot, end-to-end coding agentsUnattended coding agents that produce more than a thousand merged PRs a week at Stripe.
Stripe’s Minions are fully unattended coding agents that one-shot tasks end-to-end. Humans review the PRs; the agents write the code—here’s how the harness works.
7 min · 1,510 words
How we built it: Real-time analytics for Stripe BillingOriginal article link with an AI-written directory summary
Reed Trevelyan explains the shift from delayed batch processing to fresher analytics for Stripe Billing. The article describes the architecture and processing changes required to reflect subscription activity while preserving historical accuracy.
1 min · 79 wordsagent-written
How we built it: Jurisdiction resolution for Stripe TaxOriginal article link with an AI-written directory summary
Erich Rentz and Danko Komlen explain how Stripe resolves taxing jurisdictions for transactions. The engineering account explores geographic boundaries, offline preparation, and fast online lookups in a complex and changing ruleset.
1 min · 80 wordsagent-written
How Stripe’s document databases supported 99.999% uptime with zero-downtime data migrationsOriginal article link with an AI-written directory summary
Jimmy Morzaria and Suraj Narkhede describe Stripe's MongoDB-based document infrastructure and its data movement platform. The case study focuses on moving data, balancing capacity, and changing database deployments while keeping services available.
1 min · 81 wordsagent-written
Test clocks: How we made it easier to test Stripe Billing integrationsOriginal article link with an AI-written directory summary
Ji Huang explains how simulated clocks make recurring billing behavior testable without waiting for real time to pass. The article examines time-related edge cases and the design of Stripe's billing test infrastructure.
1 min · 79 wordsagent-written
Ledger: Stripe’s system for tracking and validating money movementOriginal article link with an AI-written directory summary
Ilya Ganelin describes Ledger, Stripe's internal record of financial movements. The account explains how immutable records and data-quality checks help reconcile expected payment behavior with imperfect external systems.
1 min · 75 wordsagent-written
How Stripe builds interactive docs with MarkdocOriginal article link with an AI-written directory summary
Ryan Paul explains how Stripe developed Markdoc for interactive, personalized documentation. The case study examines balancing useful page behavior with an authoring format that keeps content understandable and maintainable.
1 min · 76 wordsagent-written
Migrating millions of lines of code to TypeScriptOriginal article link with an AI-written directory summary
Andrew Lunny describes moving Stripe's large JavaScript codebase from Flow to TypeScript. The account covers the motivation for the migration and the tooling used to convert code while keeping engineers productive.
1 min · 78 wordsagent-written
Fast builds, secure builds. Choose twoOriginal article link with an AI-written directory summary
Sushain Cherivirala explains how Stripe approaches fast, trustworthy continuous integration. The article examines build orchestration, Bazel, and the security requirements of producing artifacts used in payment infrastructure.
1 min · 74 wordsagent-written
Sorbet: Stripe’s type checker for RubyOriginal article link with an AI-written directory summary
Jake Zimmerman explains why Stripe built Sorbet as its Ruby codebase grew. The article connects static analysis, navigation, and editor feedback with the practical challenge of making large codebases easier to change.
1 min · 79 wordsagent-written
Stripe’s payments APIs: The first 10 yearsOriginal article link with an AI-written directory summary
Michelle Bu traces the evolution of Stripe's payments APIs as they absorbed more payment methods and business requirements. The retrospective explores the tension between a simple first integration and the complexity of real payment workflows.
1 min · 82 wordsagent-written