Hey, I'm Aim

I help you check your testing maturity, plan a test strategy, set realistic SLOs, choose a load injection shape, set up a testing campaign, or find the right tool for your stack

Tell me what you're working on

Hi, I'm Aim

I help you check your testing maturity, plan a test strategy, set realistic SLOs, choose a load injection shape, set up a testing campaign, or find the right tool for your stack

Tell me what you're working on

+30,000,000 downloads

+300,000 COMPANIES

Your AI load tester

Build, run, and analyze load tests from your coding agent, your CI, or your browser. Know what broke and what to fix before every release.

CheckoutTest.javaYOUR IDECODING AGENTLoad test checkout: 500 users ramping over 60 sWrote CheckoutTest.java from your routesStarted run #318 on Gatling EnterpriseAI RUN SUMMARYp95 on /checkout/pay: 412 ms, +38% vs baselineSLO p95 under 300 ms failed, 502s from payment-apiOpen a Jira issueMatch with infra metrics1ScenarioBuilder checkout = scenario("Checkout")2 .exec(http("Browse").get("/products"))3 .exec(http("Add to cart").post("/cart"))4 .exec(http("Pay").post("/checkout/pay")5 .check(status().is(200)));67setUp(checkout.injectOpen(8 rampUsers(500).during(60)))9 .assertions(global().responseTime()10 .percentile(95).lt(300));Gatling EnterpriseCHECKOUT CAMPAIGN, RUN #318RUNNINGSLO FAILEDRequests/s2,480p95 response time412 msError ratio0.4%Virtual users500Response time percentilesPOST /checkout/payp95 trend, last 6 runsJiraPERF-142Investigate p95 regressionon POST /checkout/payAssignee: Payments teamLinked: Gatling run #318TO DODatadogINFRAdb-primary CPU92% at 14:02Same window as the p95 spikeMATCHED

Plugs into the workflows your teams already run

Run Gatling tests from your CI/CD, send results to your observability stack, and alert your team where it already works.

BuildkiteGitHubGitLabJenkinsGitHub ActionsDynatraceDatadogSlackClaude CodeCodexJiraMS TeamssbtTerraformAWS CodeBuildMavenGradlePostman

Build your new AI load testing workflow

Create load tests with your coding agent.

Gatling Skills give your coding agent the Gatling SDK, so it writes working Gatling tests from your code and recent changes. Already have browser journeys or legacy scripts? Turn them into Gatling tests with AI.

CODING AGENTWhat should we load testbefore release 4.2?Read 42 routes and 3 changed filesCRITICAL JOURNEYS TO COVERPOST /checkout/payCHANGEDPOST /cartHIGH TRAFFICGET /productsHIGH TRAFFICWrote CheckoutTest.javawith Gatling SkillsWorking Gatling test, ready to runCheckoutTest.javaNEWscenario("Checkout") .exec(http("Products") .get("/products")) .exec(http("Cart") .post("/cart")) .exec(http("Pay") .post("/checkout/pay"))setUp(checkout.injectOpen( rampUsers(500) .during(60)))ALSO FROMPlaywright to GatlingJMeter to Gatling converterLoadRunner to Gatling converter

Trigger and run tests automatically.

Run Gatling tests on every merge from your CI pipeline, from your coding agent through the MCP Server, or from the CLI. Group them in campaigns per release and run them at the scale you need.

CI pipelineGitHub Actions, JenkinsMCP Server“Run checkout before merge”CLIgatling enterprise:startCampaign: Release 4.23 GATLING TESTSCheckout ramp500 users over 60 sSearch spike2,000 users in 10 sLogin soak300 users for 2 hRUNNINGQUEUED

Analyze every run and get recommendations.

AI Analysis compares each run with your baseline, checks your SLOs, and recommends what to fix next, in Gatling Enterprise or in your IDE through the MCP Server.

Run #318 vs baselineP95, POST /CHECKOUT/PAYSLO FAILED412 ms, +38%AI RECOMMENDATIONSALSO IN YOUR IDE VIA MCP1Add an index on payments.order_id2Raise the payment-api connection pool3Re-run the checkout ramp to confirmDatadogdb-primary CPU92% at 14:02SAME TIME WINDOW

See Gatling in action

Build, run, and interpret your first load test. A practical session: by the end, you'll know exactly what Enterprise gives you out of the box.

Loading next session...

30 minutes

Live + Q&A

"Gatling let us turn load testing into a company-wide capability - 3,000+ engineers, 80,000 load tests a year."

Chaitanya Bhatt

Principal Software Engineer
Intuit

Build for modern performance needs

Gatling helps you test complex systems under real-world conditions, whether you’re migrating to the cloud, scaling your SaaS, or running AI workloads. Reproduce real traffic. Detect bottlenecks. Release with confidence.

Success stories powered by Gatling

Ready for your biggest
traffic spikes?

Turn peak demand into peak performance, without lost sales or downtime.

Deploy load tests directly from your AI coding agent.
‍

The Gatling MCP Server and Skills connect Claude Code, Cursor, or any MCP-compatible client to your Gatling Enterprise Edition account. Configure, deploy, and start a test without leaving your IDE.

Learn more
Learn more

Track performance compliance on every run
‍

Define Service Level Objectives directly in Gatling Enterprise Edition. Set response time and error ratio targets, then see exactly how compliant your system was after every run.

Learn more
Learn more

Put your AI load tester on your next release

Build, run, and analyze your Gatling tests on one platform, from your coding agent to production-scale load.

Need technical references and tutorials?

Minimal features, for local use only