What Is Stripe's Tech Stack? Languages, Databases, and Cloud
Stripe's core backend is written mostly in Ruby, and it runs on Amazon Web Services. Its main data store is a document database built on MongoDB.
Other languages sit around that core. Scala handles large data and streaming jobs. Go and Java appear in infrastructure services. JavaScript and TypeScript run the dashboard and the client libraries.
Stripe's engineers publish talks, blog posts and open source projects. Most of the list below comes from that public material, not from guesswork.
Stripe Tech Stack by Layer
| Layer | What Stripe uses |
|---|---|
| Main API backend | Ruby |
| Type safety for Ruby | Sorbet, built and open sourced by Stripe |
| Data and streaming | Scala, Apache Kafka |
| Infrastructure services | Go, Java |
| Web and dashboard | JavaScript, TypeScript, React |
| Main data store | Document database built on MongoDB |
| Cache and search | Redis, Elasticsearch |
| Cloud | Amazon Web Services |
| Packaging | Docker containers, Kubernetes |
| Public interface | REST API and webhooks |
Why Ruby Is Stripe's Main Language
Stripe chose Ruby very early and never moved off it. The payments API is a large Ruby codebase.
Ruby is easy to read and quick to change. That matters when one product serves millions of businesses.
Ruby is also loosely typed, which gets risky in a large codebase. Stripe solved that by building Sorbet, a type checker for Ruby. Sorbet is open source, and Stripe uses it across its own code.
So the honest answer to "what language is Stripe written in" is Ruby first, then Scala, Go, Java, and TypeScript.
What Database Does Stripe Use
Stripe's main store is a document database. Stripe built it on top of MongoDB and runs it themselves.
Their engineering team has written about this system in public. It holds hundreds of billions of documents and stays available during data moves.
Some older write-ups say Stripe runs on PostgreSQL as its primary database. That is not accurate for the core payments path. Stripe does use relational databases in places, but the transactional core is document based.
Around that core sit the usual supporting stores. Redis is used for caching. Elasticsearch supports search. Apache Kafka carries event streams between services.
Cloud and Infrastructure
Stripe runs on Amazon Web Services. Amazon has published Stripe as a customer, so this one is not a guess.
Services are packaged in containers and scheduled with Kubernetes. Stripe has also open sourced infrastructure tools, such as Veneur for metrics.
The public surface is a REST API with webhooks for callbacks. Stripe keeps a set of official client libraries in Ruby, Python, PHP, Java, Node.js, Go and .NET. That is why people see so many languages in Stripe's GitHub account.
Stripes Framework Is a Different Thing
Some searches mix up two names. Stripes Framework is an open source Java web framework. It has no connection to Stripe the payments company.
If you are looking for release dates of that Java framework, you want its own project site.
What This Means for a Stripe Interview
You do not need to write Ruby to pass a Stripe interview. Candidates report that you may use the language you know best.
The stack matters in a different way. Stripe interviews lean toward practical work: build a small working feature, handle errors, and think about money correctness. Idempotency, retries and exactly-once handling come up often.
For the round by round layout, read what the Stripe interview process is like.
How to Prepare
- Know the shape, not the trivia. Nobody will ask you to name Stripe's cache. They will ask you to design a payment flow that never charges twice.
- Practice practical coding. Stripe's rounds favor working code over puzzles. Grokking the Coding Interview gives you the patterns that keep showing up.
- Learn payment system design. Ledgers, idempotency keys, webhooks and retries are the core topics. Start with Grokking the System Design Interview, then read what to expect in the Stripe system design interview.
- Check the algorithm bar. Stripe is lighter on puzzles than most large companies. See whether Stripe asks LeetCode questions.
- Have one good API story ready. Pick a service you built and explain its interface, its failure modes, and what you would change.
- Plan the wait. Timelines vary by team. Here is how long it takes to hear back after a Stripe interview.
GET YOUR FREE
Coding Questions Catalog
$99
$197
$72
