# Gatling

> Gatling is an open source, self-hosted load testing tool from Gatling Corp., scripted in Java, Scala, Kotlin.

- Canonical: https://perf.jmeter.ai/tools/gatling/
- Review: https://perf.jmeter.ai/reviews/gatling/
- Official: https://gatling.io/
- Source: https://github.com/gatling/gatling
- Vendor: Gatling Corp.
- Category: Load Testing
- License: Open Source — Free open-source core; commercial platform available.
- Deployment: Self-hosted
- Status: Active
- Scripting: Java, Scala, Kotlin
- Protocols: HTTP, HTTPS, WebSocket, SSE, JMS
- OS support: Windows, macOS, Linux
- First released: 2012
- Latest release: 3.0.2 (July 2026)
- Last verified: 2026-08-11

## What it is
Gatling uses code-based simulations to model traffic and produce HTML reports. The core project supports HTTP, WebSocket, SSE, and JMS workloads.

## Choose it when
- Load Testing scenarios across typical web and service stacks
- Teams that prefer open-source licensing and self-hosting options
- Groups comfortable scripting in Java, Scala, Kotlin

## Look elsewhere when
- Teams unwilling to operate generators, results storage, and scaling

## Architecture
Gatling is commonly operated as self-hosted software with scenario authoring in Java, Scala, Kotlin. Concurrency and distribution depend on how you size workers or injectors.

## Pricing
Gatling offers a free Community Edition. Gatling Enterprise Edition pricing is available via tiered plans including Starter-pack options (e.g., €89/month billed annually) and custom tailormade solutions; contact sales for specific needs.

## Compare
- [JMeter vs Gatling](https://perf.jmeter.ai/vs/apache-jmeter-vs-gatling/) — Choose Gatling for code-first HTTP performance with strong reporting DNA.
- [k6 vs Gatling](https://perf.jmeter.ai/vs/grafana-k6-vs-gatling/) — Prefer k6 if JavaScript/TypeScript is the team default.
- [Gatling vs Artillery](https://perf.jmeter.ai/vs/gatling-vs-artillery/) — The practical split is the authoring language: Java, Scala, Kotlin for Gatling, JavaScript, TypeScript for Artillery.
- [Gatling vs LoadRunner Professional](https://perf.jmeter.ai/vs/gatling-vs-loadrunner-professional/) — The practical split is the cost model: Gatling is open source, LoadRunner Professional is commercial.
- [Gatling vs NeoLoad](https://perf.jmeter.ai/vs/gatling-vs-neoload/) — The practical split is the cost model: Gatling is open source, NeoLoad is commercial.
- [Gatling vs BlazeMeter](https://perf.jmeter.ai/vs/gatling-vs-blazemeter/) — The practical split is the cost model: Gatling is open source, BlazeMeter is commercial.
- [Gatling vs Tsung](https://perf.jmeter.ai/vs/gatling-vs-tsung/) — The practical split is the authoring language: Java, Scala, Kotlin for Gatling, Erlang, XML for Tsung.
- [Gatling vs The Grinder](https://perf.jmeter.ai/vs/gatling-vs-the-grinder/) — The practical split is the authoring language: Java, Scala, Kotlin for Gatling, Jython, Java for The Grinder.
- [Gatling vs Azure Load Testing](https://perf.jmeter.ai/vs/gatling-vs-azure-load-testing/) — The practical split is the cost model: Gatling is open source, Azure Load Testing is commercial.
- [Gatling vs AWS Distributed Load Testing](https://perf.jmeter.ai/vs/gatling-vs-aws-distributed-load-testing/) — The practical split is who runs the load generators: Gatling on your own infrastructure, AWS Distributed Load Testing on the vendor's.
- [Gatling alternatives](https://perf.jmeter.ai/alternatives/gatling/)

## FAQ
### Who is Gatling for?
Gatling is best for engineers designing load, stress, and performance tests for web and service systems. It is open source, so teams can self-host and extend it. Vendor: Gatling Corp.. Deployment model: self-hosted. Free open-source core; commercial platform available. Confirm details against the official site and a short proof-of-concept in your environment.

### How does Gatling differ from Apache JMeter?
Compared with Apache JMeter, scripting centers on Java, Scala, Kotlin rather than Java, Groovy. Gatling lists protocols HTTP, HTTPS, WebSocket, SSE, JMS; Apache JMeter lists HTTP, HTTPS, JDBC, JMS, FTP, TCP. Status is active versus active. Use the Test Rig to compare full specs side by side before a proof-of-concept.

### What scripting language and concurrency model does Gatling use?
Gatling uses Java, Scala, Kotlin for scripting or scenario definition. Runtime model: code-first scenarios where virtual users execute scripted behavior under load. OS support: Windows, macOS, Linux. Protocols: HTTP, HTTPS, WebSocket, SSE, JMS. Match these to how your team already authors tests and which systems you must drive under load.

### What is the cloud or enterprise path for Gatling?
Gatling is primarily self-hosted; teams typically run generators on their own machines, CI runners, or private cloud. Plan for generator capacity, network access to targets, and result storage yourself. As open source, commercial support or hosted siblings may exist separately. Check the official site. Pricing note: Free open-source core; commercial platform available.

### What are known limitations of Gatling?
Gatling limitations to weigh: self-hosted tools require you to provision, scale, and observe load generators yourself. Status: active. Always validate against your target protocols and scale with a proof-of-concept. Confirm details against the official site and a short proof-of-concept in your environment.

---
Curated by NaveenKumar Namachivayam (QAInsights) · methodology: https://perf.jmeter.ai/about/#methodology · corrections: https://github.com/QAInsights/Performance-Testing-Tools/issues/new?title=Tool%20submission%3A%20&body=Tool%20name%3A%20%0AOfficial%20URL%3A%20%0AWhat%20should%20be%20added%20or%20corrected%3F%20%0A