CUSTOMER STORY – Enterprise Scale
Intuit scaled load testing across 1,000+ teams.
Here's the architecture
behind it.
When you serve 100 million customers and process $105B in tax refunds, performance isn't a nice-to-have. Chaitanya Bhatt, Principal Engineer at Intuit, broke the specialist model, and rebuilt load testing as a platform capability every engineering team owns.
At this volume, every performance failure has a business name on it.
Load testing at Intuit isn't a technical exercise. It's an organizational priority. When your systems are the financial backbone for millions of businesses and consumers, performance directly determines whether payrolls clear, whether refunds arrive, whether invoices get paid. The stakes make testing non-negotiable, and the scale makes it unsolvable without a platform approach.
100M+ customers served
$2T+ in invoices managed
315+ Kubernetes clusters
1,000+ engineering teams
8,000+ engineers
"Any sort of outage means you're potentially disrupting someone's livelihood. On the small business side, an outage might mean payrolls are not going through, payments are not going through. We have no choice — reliability is not an option. It's a feature."
Chaitanya Bhatt
Principal Engineer
INTUIT
The specialist model doesn't scale.
Here's what does.
At Intuit's size, performance testing owned by a small expert group creates exactly the wrong dynamic. Feedback arrives late. Regressions reach production. Release confidence drops. And every team that needs a load test joins a queue.
Chaitanya had seen this pattern before. The tools were fragmented. There were no standards. No visibility into who was testing what, or whether tests were even running. Reinventing the wheel was the norm.
Intuit stopped treating load testing as a specialist function, and rebuilt it as a platform capability. Four decisions made it work.
Embed testing in every repo
Performance test scaffolding ships automatically with every new service repository. No setup. No blank slate. A pre-configured perf-tests/ folder from day one. If your build has a performance test pipeline baked in, the barrier to entry drops to zero, and teams start doing the right thing without being asked.
Automate onboarding via CI/CD
Pipelines enforce standards. New services are onboarded automatically. Tests run on every pull request. No Jira ticket. No specialist required. When a team merges a PR, performance is already part of the gate.
Pre-vended templates and libraries
Developers don't choose a tool or a version. Everything is pre-selected, pre-configured, and maintained centrally. Library versions are managed and rotated automatically. The only job left is writing the payload.
Central governance with full visibility
One platform. Role-based access. Real-time metrics on who is testing, what's failing, and where coverage gaps exist — across every team, every business group. Platform operators can see who's compliant and fix problems transparently, before teams even notice them.
Watch the session
Chaitanya from Intuit walks you
through the full architecture.
45 minutes. No marketing. A principal engineer explains exactly how Intuit built a load testing platform that onboards teams automatically, gates releases on performance, and gives 3,000+ developers real-time test visibility.
Why Intuit chose
Gatling Enterprise Edition
Four reasons a team of 8,000 engineers standardized on one tool.
Intuit runs Java. Gatling runs on the JVM. Developers loaded it in their IDE and immediately understood it. No learning curve, no new runtime, no friction.
Source code, scripts, and proprietary libraries stay inside Intuit's network. Only latency and throughput numbers leave. A hard perimeter with no compromises.
The Gatling Enterprise API is what made automation possible. Team provisioning, simulation creation, RBAC assignment, all triggered programmatically through Intuit's internal developer portal.
250 concurrent tests. 300K requests in flight. 600+ load generators. 2,000+ CI/CD pipelines. Gatling handled it without tuning.
What changed
with Gatling Enterprise Edition
From fewer than 100 developers using Gatling in 2018 to over 3,000 today, without a single specialist bottleneck.
80,000+ load tests run annually
1,400+ services with embedded perf-tests
97% performance test coverage across critical services
3,000+ developers onboarded
30 → 1 fragmented tooling solutions consolidated
100% CI/CD performance integration
"If you wanted to drive hundreds of thousands of transactions per second, it's not a hard thing to achieve in Gatling. You don't have to tune it. You don't have to call in an expert. Any developer getting started would be able to drive that kind of load with ease."
Chaitanya Bhatt
Principal Engineer
INTUIT
Ready to see how this maps to your stack?
Talk to a Gatling expert. No demo script. Just an honest conversation about where you are and what it would take to get there.
Your all-in-one load testing platform
Design complex tests, manage global infrastructure, and turn results into action on one powerful platform.
Need technical references and tutorials?
Minimal features, for local use only
