About Stripe History

Stripe history

Stripe is private, so its history arrives in pieces: annual letters, tender offers, press reports, interviews, and blog posts. Stripe History gathers those pieces into one dated record, from the founders' first projects in 2005 to today, and links every event to its sources. It publishes a reverse-chronological company timeline covering acquisitions, products, leadership, funding, valuation, expansion, offices, publishing projects, the founders' projects outside Stripe such as grant programs, early history, annual volume, sourced annual net-revenue disclosures, and reviewed long-form appearances by Stripe founders and senior leaders.

Evidence status

Sources and review

Stripe History is a dated record in which every entry links to its sources, and the whole record downloads as YAML. Other Stripe references lists where Wikipedia, Sacra and others serve a reader better.

Every history entry resolves to at least one cataloged source. Review prefers primary material and filings, uses strong contemporaneous reporting where necessary, checks chronology, category placement, source support, and duplicate claims, and preserves uncertainty when a transaction or event was only proposed or reported.

“Citations” counts each link between a timeline entry and a source in the catalog. It is not a count of independently corroborated claims: one source can support more than one entry, and one entry can cite more than one source. The source catalog lists every source.

“Last research run” is the date of the most recent completed research run. Each run covers one research collection, not the whole timeline. The collection definitions and the research-run log, both YAML, show what each run covered.

Publications followed

Weekly discovery reads first-party and Stripe-affiliated publication feeds. The timeline records those publications when they become part of Stripe's editorial history. It does not turn every newsletter essay into its own event.

Followed publications include Stripe Economics, Works in Progress, and Stripe Press. Discovery also reads first-party Stripe Blog and Stripe.dev Blog RSS, and the Cheeky Pint episode feed.

Independence and corrections

Stripe History is not affiliated with, endorsed by, or operated by Stripe, Inc. Stripe names and trademarks belong to their respective owners. Corrections are made in the underlying sourced records so the timeline and its focused category views stay aligned.

To inspect or reuse the current record, export the public YAML. To challenge a date, claim, status, or source, use the public issue tracker and include the affected entry, proposed correction, and supporting source. The contact page keeps those requirements easy to find.

Publisher and contributions

Published and maintained by Hraness. The maintainer, Ben Guo, was an early engineer at Stripe from 2015 to 2023. To suggest a correction, add a source, or improve the project, open an issue or contribution in the Stripe History repository. The same public channels are listed on the contact page.

Other Stripe references

Checked September 28, 2026. Wikipedia is better for a short overview and is cited far more widely. Stripe’s newsroom and annual letters are the primary source for many entries here; this site adds reported events Stripe did not announce and puts everything in one timeline. Crunchbase, PitchBook and Tracxn are better for investor lists and comparing companies, and much of their data is paywalled. Contrary Research and Sacra analyze the business, and Sacra publishes revenue estimates. Stripe History records disclosed and reported figures and makes no revenue estimates. A valuation it derives from reported share prices shows its formula.

Privacy

The site sends anonymous, cookieless pageview events for public pages to PostHog. Each event contains the normalized public page path, its page category, a site identifier, an analytics schema version, and PostHog's cookieless marker. It also carries the host name of the site that linked to the page, such as google.com, but never the full referring address. It excludes query strings, URL fragments, account data, and user content. The browser does not save an analytics cookie or identifier.

The site does not use autocapture, session replay, heatmaps, surveys, feature flags, performance monitoring, or user profiles, and it has no local reader accounts or authentication. Requests are still subject to the ordinary logs and security controls of the hosting provider. The footer offers the general Hraness newsletter and optional support through Hraness Accounts; Stripe History does not create a separate product newsletter subscription.

The dedicated privacy page repeats this policy for agents and other readers who look for /privacy.