On this page
Overview
Gatling is a code-first load-testing and performance-engineering platform. Teams can write simulations in Java, JavaScript/TypeScript, Kotlin, or Scala and exercise HTTP, WebSocket, SSE, JMS, gRPC, MQTT, and other supported workloads for regression and release-gate checks.
Features and best fit
Based on official documentation; not hands-on tested · Content checked:
Key features
Manage performance tests as version-controlled code in multiple languages
The README documents SDKs for Java, JavaScript, TypeScript, Kotlin, and Scala, allowing simulations to be reviewed and automated with the rest of the source code.
Sources: [1]
Exercise HTTP, WebSocket, SSE, JMS, gRPC, and MQTT workloads
Official protocol support spans web/API traffic and messaging/event workloads, enabling simulations that approximate different production traffic patterns.
Sources: [1]
Generate load with a non-blocking asynchronous architecture
Gatling contrasts its non-blocking asynchronous design with one-thread-per-user tools and focuses on resource efficiency and scalability per load-generator node.
Sources: [1]
Best fit
Fits teams running performance tests in the same delivery workflow as application code
It is useful when simulations should be automated in CI/CD for regression detection and performance gates rather than operated as isolated GUI test assets.
Sources: [1]
Before adoption
Run load tests only against systems you are authorized to test
Because Gatling can intentionally generate substantial traffic, tests should target dedicated or explicitly authorized environments with known capacity, cost, and rate-limit boundaries and should ramp load gradually.
Sources: [1]
Separate Enterprise features from the open-source core
The README describes real-time dashboards, trend and SLO monitoring, AI-assisted summaries, RBAC, and related capabilities under Gatling Enterprise Edition. Evaluate the OSS repository on its open-source test-as-code and local execution capabilities.
Official sources
- [1]Gatling v3.16.0 README(2026-10-04)
- [2]Gatling v3.16.0 build definition(2026-10-04)
- [3]Gatling v3.16.0 release(2026-10-04)
- [4]Gatling Apache 2.0 license(2026-10-04)
Supplemental curator note
Run load tests only against explicitly authorized targets and ramp traffic gradually. Features described in the README under Gatling Enterprise Edition, such as advanced dashboards, SLO monitoring, and AI-assisted summaries, should be evaluated separately from the OSS core.
Try it in 3 steps
- 1
Download the official Gatling 3.16.0 bundle
Pin the download to the official GitHub release bundle. No load test is started.
curl -L -o gatling-bundle-3.16.0.zip https://github.com/gatling/gatling/releases/download/v3.16.0/gatling-bundle-3.16.0.zip - 2
Extract the Maven-wrapper-based bundle
The standalone bundle has been Maven-wrapper-based since Gatling 3.11. Inspect only the wrapper and project structure after extraction.
rm -rf gatling-3.16 && mkdir gatling-3.16 && unzip -q gatling-bundle-3.16.0.zip -d gatling-3.16 && find gatling-3.16 -maxdepth 3 -type f \( -name mvnw -o -name mvnw.cmd \) -print - 3
Display Gatling plugin help without generating load
Do not launch a simulation. Run actual load tests only against explicitly authorized test environments.
GATLING_DIR=$(find gatling-3.16 -type f -name mvnw -print -quit | xargs dirname); test -n "$GATLING_DIR" && cd "$GATLING_DIR" && ./mvnw gatling:help
Growth
Growth trends · Last 30 days
6,956 Stars
Trend data is still being collected.
Development activity
Last 90 days · weekly
- Commits (last 30 days)
- 48
- Open PRs
- 2
Development activity is still being collected.
Built with
Categories and tags
Categories
GitHub data
GitHub dataView detailed GitHub data
GitHub Topics
- netty
- scala
- loadtesting
- automation
- gatling
- load-testing
- java
- cicd
- javascript
- kotlin
- load-test
- load-tests
- Stars
- 6,956
- Forks
- 1,207
- Watchers
- 226
- Open issues
- 16
- Contributors
- 193
- Owner type
- Organization
- Primary language
- Scala
- License
- Apache-2.0
- Repository last updated
- Sep 29, 2026
Related information
Write a related articleShare a guide or use case for this OSS in Markdown. Articles are published after administrator approval.
Explore next
- Kotest4,789 Stars
2 shared tag(s) · 1 shared category(s)
combine spec styles, assertions, and property testing across Kotlin projects
Kotlin - fake-indexeddb695 Stars
2 shared tag(s) · 1 shared category(s)
recreate the IndexedDB API in memory for Node.js tests
JavaScript - Argos636 Stars
2 shared tag(s) · 1 shared category(s)
review UI changes by comparing visual diffs for each pull request
TypeScript - Markuplint623 Stars
2 shared tag(s) · 1 shared category(s)
lint markup against HTML and ARIA rules across HTML, React, Vue, Svelte, and other templates
TypeScript - Apache Spark44,112 Stars
2 shared tag(s) · Same language
Process SQL, DataFrames, streams, and machine learning on one distributed engine
Scala - Play Framework12,615 Stars
2 shared tag(s) · Same language
Build stateless, non-blocking JVM web applications with REST, JSON, and WebSockets in Java or Scala
Scala
Report incorrect information
Tell us if any listing information is incorrect or outdated.