Gatling review
A broad performance-testing platform with code, no-code, and distributed load options.
Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026
Gatling is a performance-testing platform for developers, QA teams, and enterprises testing web applications, APIs, microservices, and cloud infrastructure. Its open-source Community Edition runs code-based scenarios locally, while the broader platform combines SDKs, browser-session recording, Postman imports, and no-code capacity, stress, and soak profiles. Test scenarios can use Java, JavaScript, TypeScript, Scala, or Kotlin, with support for HTTP and HTTPS alongside WebSocket, SSE, JMS, MQTT, and gRPC.
The published plans show a freemium model with a free plan and a 14-day free trial. Basic costs €89 per month when billed annually and includes up to 60,000 virtual users, 1 hour of testing, 1 load generator, 2 seats, and community support. Team costs €356 per month when billed annually and raises capacity to 180,000 virtual users, 5 hours of testing, 3 load generators, 10 seats, distributed testing, and professional support. Enterprise uses custom limits for virtual users, testing hours, and load generators, with all features and integrations plus premium support. The plans give smaller teams a defined entry point while reserving greater scale and support for higher tiers.
Gatling fits teams that want performance testing embedded in delivery workflows. Integrations include GitHub Actions, GitLab CI/CD, Jenkins, Azure DevOps Pipelines, TeamCity, Bamboo, Datadog, Dynatrace, InfluxDB, New Relic, OpenTelemetry, Postman, Jira Cloud, Slack, and Microsoft Teams. It also provides configuration as code, a public API, real-time dashboards, and private load-generator locations on customer infrastructure. The main boundary is browser coverage: recorded browser sessions produce HTTP-based scenarios, but the HTTP engine does not execute JavaScript like a real browser. Choose Gatling for broad protocol coverage, API testing, distributed load, and code-oriented workflows; choose an alternative when real-browser JavaScript execution is central.
Gatling pros and cons
- Where it wins
- Supports HTTP, WebSocket, SSE, JMS, MQTT, and gRPC testing
- Distributed testing supports up to 60,000 virtual users on Basic
- Integrates with major CI/CD, observability, and collaboration tools
- Where it doesn't
- Browser sessions generate HTTP scenarios rather than executing JavaScript
- Basic limits testing to 1 hour and one load generator
- Advanced limits and support require higher-tier or custom plans
Gatling fact sheet, pricing and score →
Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.
Last updated · How we research and update
