---
title: Gatling Reviews
meta_title: 'Gatling Reviews 2026: Details, Pricing, & Features | G2'
meta_description: Filter 119 reviews by the users' company size, role or industry
  to find out how Gatling works for a business like yours.
aggregate_rating:
  rating_value: 4.4
  review_count: 119
  scale: '5'
date_modified: '2026-09-25'
parent_category:
  name: Development
  url: https://www.g2.com/categories/development
---


# Gatling Reviews
**Vendor:** Gatling  
**Category:** [Load Testing Tools](https://www.g2.com/categories/load-testing-tools)  
**Average Rating:** 4.4/5.0  
**Total Reviews:** 119  
**AI Enabled:** This product embeds AI to enhance or extend its core functionality.
## About Gatling
Gatling is a load-testing solution that helps organizations identify bottlenecks and guarantee website stability under traffic load through test automation. Gatling Enterprise includes advanced features for reporting (live reporting, TCP connections metrics, bandwidth usage, injectors' monitoring) and automation (public APIs, new Continuous Integration plugins, clustering mode). With 30,000,000 downloads for more than 300 000 companies worldwide, Gatling’s solution is used in diverse industries such as software, e-commerce, streaming media, banking, insurance, gaming, and finance.



## Gatling Pros & Cons
Pros and Cons are compiled from review feedback and grouped into themes to provide an easy-to-understand summary of user reviews.

**What users like:**

- Users appreciate the **automation capabilities** of Gatling, facilitating seamless integration with CI/CD workflows for efficiency. (2 reviews)
- Users appreciate the **ease of use** in Gatling, enhancing load testing automation within their CI/CD workflows. (2 reviews)
- Users appreciate the **excellent customer support** of Gatling, enhancing their experience and facilitating smoother testing processes. (1 reviews)
- Users highlight the **excellent customer support** from Gatling, enhancing their overall testing experience and satisfaction. (1 reviews)
- Users appreciate the **easy setup** of Gatling, enabling seamless integration with CI/CD tools for efficient performance testing. (1 reviews)
- Flexibility (1 reviews)
- Helpful (1 reviews)
- Load Testing (1 reviews)
- Simulation (1 reviews)
- Time-saving (1 reviews)

**What users dislike:**

- Users find the **complex configuration** of Gatling challenging, particularly non-developers lacking programming experience. (1 reviews)
- Users find **insufficient documentation** and confusing information which may hinder effective use of Gatling. (1 reviews)
- Users note that the **poor documentation** can lead to confusion and hinder effective use of Gatling's features. (1 reviews)
- Users struggle with Gatling’s **poor UI** , finding it difficult to navigate, especially those without programming skills. (1 reviews)

## Gatling Reviews
  ### 1. Gatling Java DSL: Maintainable Load Tests, Excellent Reports, and Seamless CI/CD

**Rating:** 4.0/5.0 stars

**Reviewed by:** Raman B. | Architect, Quality Engineering, Mid-Market (51-1000 emp.)

**Current User:** The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user.

**Validated Reviewer:** Validated through LinkedIn

**Source: Organic:** Organic review. This review was written entirely without invitation or incentive from G2, a seller, or an affiliate.

**Reviewed Date:** September 15, 2026

At G2, we prefer fresh reviews and we like to follow up with reviewers. They may not have updated their review text, but have updated their review.

**What do you like best about Gatling?**

Gatling's Java DSL is the standout feature — writing load test scenarios in code means tests live in Git, get peer-reviewed, and stay maintainable long-term. We built a shared internal library (gatlingcommon) of reusable feeders, load patterns, and helpers that any team can import and use in minutes, which has dramatically reduced onboarding time for new load test projects.

The built-in HTML reports are clean and actionable — per-request percentile breakdowns, throughput charts, and response time distributions are generated out of the box with zero dashboard setup, cutting post-run analysis time significantly.

CI/CD integration is seamless — the Maven plugin fits naturally into Jenkins pipelines, giving fine-grained control over simulation execution and report generation.

Performance-wise, Gatling is exceptionally efficient. A single node can simulate thousands of virtual users with minimal resource consumption.

Pricing is a strong ROI story for open-source users — the core tool is free, and the ecosystem is mature enough to cover most enterprise load testing needs.

The community forum is active, and the documentation is thorough. Onboarding a new team member to write their first simulation takes a day, not a week.

**What do you dislike about Gatling?**

The biggest limitation is distributed load testing: the open-source version offers no supported way to merge binary simulation logs from multiple nodes into a single consolidated report. Starting with Gatling 3.11.x, the simulation log format changed to binary, which makes manual log merging impossible. In 3.10.x, manually merging logs was a workable workaround, but that option is no longer available. As a result, teams running distributed tests are pushed to either stay on older versions or move to Gatling Enterprise.

Support for the open-source version is community-driven only. When you hit critical blockers, the official response is often along the lines of, “this is only supported in Gatling Enterprise.”

Reference: https://community.gatling.io/t/generate-gatling-report-from-multiple-simulation-log-files-with-version-3-13-5/9737

**What problems is Gatling solving and how is that benefiting you?**

Gatling solves the problem of realistic, high-volume load testing in a developer-friendly way. By providing a code-first DSL in Java, it allows us to write load test scenarios that are version-controlled, peer-reviewed, and reusable — treating performance tests as first-class code rather than throwaway scripts.

The biggest benefit has been standardization across teams. We built a shared internal library of reusable load patterns, feeders, and helpers that any team can import, which means a new load test project can be up and running in minutes instead of days.

Gatling also solves the reporting problem — generating detailed HTML reports with per-request percentile breakdowns, throughput, and response time distributions out of the box means we spend less time building dashboards and more time acting on results.

On the CI/CD side, the Maven plugin integrates cleanly into Jenkins pipelines, making it easy to run performance tests as part of our regular release process rather than as a manual afterthought.

Overall, Gatling has shifted load testing from a specialist activity to something any developer on our team can contribute to.

  ### 2. Efficient Load Testing with Informative Reports

**Rating:** 4.0/5.0 stars

**Reviewed by:** Yessinkcharem@gmail.com Y. | software engineer, Mid-Market (51-1000 emp.)

**Current User:** The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user.

**Validated Reviewer:** Validated through a business email account added to their profile

**Source: Organic:** Organic review. This review was written entirely without invitation or incentive from G2, a seller, or an affiliate.

**Reviewed Date:** August 04, 2026

**What do you like best about Gatling?**

I use Gatling for performance tests of my microservices and find it easy to write load scenarios with minimal code. The reports generated are well-written, featuring charts that help quickly identify issues. The charts and reports are especially valuable for analysis, as I can easily see response time distribution and error rates, which makes it easier to pinpoint where the system is slowing down. The initial setup was fast and easy, thanks to the documentation.

**What do you dislike about Gatling?**

I find the learning curve can be slow because I'm not used to the Scala programming language. Things like chaining requests with dynamic data extraction, conditional logic within a scenario, or coordinating multiple users with different behaviors pose challenges for me.

**What problems is Gatling solving and how is that benefiting you?**

I use Gatling for performance tests, validating system capacity against real-world traffic. It helps identify bottlenecks swiftly and the generated reports make analysis easier, allowing quick insights into performance issues.

  ### 3. Reliable, Scalable Load Testing with Code and CI/CD Integration

**Rating:** 4.5/5.0 stars

**Reviewed by:** Sumit D. | QA Engineer, Mid-Market (51-1000 emp.)

**Current User:** The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user.

**Validated Reviewer:** Validated through LinkedIn

**Source: Organic:** Organic review. This review was written entirely without invitation or incentive from G2, a seller, or an affiliate.

**Reviewed Date:** July 15, 2026

**What do you like best about Gatling?**

What I like most about Gatling is its ability to create realistic, scalable load tests using code. Because the test scenarios are written in code, they’re easy to version control, review, and integrate into CI/CD pipelines. As a result, performance testing becomes a natural part of the development process, rather than something that only happens right before a release.

**What do you dislike about Gatling?**

One area where Gatling could improve is the learning curve for new users. While the code-based approach is powerful and flexible, it can feel intimidating for testers without a programming background. More beginner-friendly tutorials, ready-to-use templates, and guided setup options would make onboarding smoother and less time-consuming.

The reporting is comprehensive, but I’d like to see more interactive dashboards and built-in trend analysis to compare performance across multiple test runs without having to rely on external tools. Integration with popular observability platforms is possible, but the setup can sometimes involve extra configuration steps that could be simplified.

From a UI perspective, there’s also room to make navigation and test management more intuitive, especially on larger projects. It would be helpful to add more AI-powered capabilities as well, such as automatic bottleneck detection, test scenario recommendations, or suggestions for optimizing load tests based on previous runs.

Overall, these feel like opportunities for enhancement rather than major drawbacks. Gatling has been reliable and performs well for large-scale load testing, but improvements in usability and analytics would make it even more accessible and productive.

**What problems is Gatling solving and how is that benefiting you?**

Before adopting Gatling, performance testing was largely a manual effort and typically happened late in our release cycle. That timing made it hard to spot scalability issues early, and tracking down performance bottlenecks often required a lot of time and coordination.

With Gatling, we’ve been able to automate load and stress tests and integrate them into our CI/CD pipeline, so we can validate application performance with every major release. This shift has helped us catch performance regressions sooner, improve stability under peak traffic, and go into deployments with more confidence.

The detailed reports and metrics have also cut down the time needed to review and interpret results, which makes it easier for developers and QA engineers to work together on targeted performance improvements. As a result, we’ve shortened our performance testing cycle, lowered the risk of production issues during high-traffic periods, and delivered more reliable applications to our users. Overall, Gatling has made performance testing more consistent, repeatable, and efficient, and it provides a strong return on the time we invest in building automated test scenarios.

  ### 4. Gatling Makes It Easy to Identify Your App’s Load Limits

**Rating:** 5.0/5.0 stars

**Reviewed by:** Leandro M. | Tech Lead | Full Stack Software Engineer (Currently: Node + Angular + GrahpQL + MongoDB), Mid-Market (51-1000 emp.)

**Current User:** The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user.

**Validated Reviewer:** Validated through LinkedIn

**Source: Organic:** Organic review. This review was written entirely without invitation or incentive from G2, a seller, or an affiliate.

**Reviewed Date:** September 06, 2026

**What do you like best about Gatling?**

Using Gatling makes it easier to identify the limits of your applications in terms of their ability to withstand load pressure across distinct scenarios.

**What do you dislike about Gatling?**

Having to learn Scala in order to develop Gatling tests can be challenging if you’re not already familiar with its programming concepts. That said, with the adoption of other popular languages (Java, Kotlin, JavaScript, TypeScript), this is no longer an issue when you’re working with tests written in one of those languages or when you’re creating a new load test from scratch.

**What problems is Gatling solving and how is that benefiting you?**

Understanding how your application behaves under high-pressure scenarios helps you pinpoint the critical areas that need improvement before you encounter them in a real-world production environment.

  ### 5. Effortless Load Testing with Seamless CI Integration

**Rating:** 4.5/5.0 stars

**Reviewed by:** Deepak A. | Senior QA Engineer, Small-Business (50 or fewer emp.)

**Validated Reviewer:** Validated through LinkedIn

**Source: Organic:** Organic review. This review was written entirely without invitation or incentive from G2, a seller, or an affiliate.

**Reviewed Date:** August 26, 2026

**What do you like best about Gatling?**

I really like Gatling's easy maintainable scripts, and I appreciate being able to use the same IDE and project for both my load tests and functional tests. Sharing the same dependencies, logic, and code between functional and load tests makes the learning curve minimal since my tests are in Java. It's great that I can run load tests remotely on CI without requiring an enterprise license. This all helps make delivery faster. Also, Gatling helps me gauge infrastructure requirements for new releases or marketing events and is useful in detecting potential race conditions and memory leaks. The initial setup was so easy, I didn’t even realize I had to do a setup.

**What do you dislike about Gatling?**

I find debugging failures in Gatling frustrating because of its asynchronous execution and fluent DSL—when a request fails, standard output doesn't always tell me why the failure occurred or what the payload looked like. I wish there was a feature to dry run which, if it fails, should print out the request and response on the console with proper exception.

**What problems is Gatling solving and how is that benefiting you?**

I use Gatling for easy maintainable scripts and running tests in the same IDE, which helps gauge infrastructure needs and detect race conditions. Sharing dependencies and logic speeds up delivery, and I can run load tests on CI without an enterprise license.

  ### 6. Developer-Friendly with Room for Improvement

**Rating:** 3.5/5.0 stars

**Reviewed by:** shabarish k. | Performance Engineer, Enterprise (> 1000 emp.)

**Validated Reviewer:** Validated through LinkedIn

**Source: Organic:** Organic review. This review was written entirely without invitation or incentive from G2, a seller, or an affiliate.

**Reviewed Date:** August 26, 2026

**What do you like best about Gatling?**

I use Gatling primarily for performance, load, and stress testing web applications, microservices, and APIs. Gatling stands out for its resource efficiency, as its asynchronous, non-blocking architecture allows simulating thousands of concurrent users from a single machine without taxing memory or CPU. I appreciate the readable, expressive DSL, which makes tests look almost like plain English, and the developer-friendly workflow that integrates seamlessly into CI/CD pipelines. Gatling's ability to simulate realistic traffic patterns and inject dynamic data through Feeders contributes significantly to its effectiveness. I find the automatic generation of visual reports with real-time metrics incredibly useful for catching regressions before they hit production.

**What do you dislike about Gatling?**

While Gatling is great for developer-centric API and HTTP testing, I found the protocol support outside HTTP lacking for our needs. It falls short if I need to load-test legacy enterprise protocols like JDBC/SQL, JMS, MQTT, Kafka, or custom TCP sockets out of the box. I often have to write custom Java/Scala protocol extensions myself. I also miss native browser-based testing because Gatling only tests the protocol layer. For true end-to-end performance metrics, like Frontend DOM rendering times or Core Web Vitals under load, I have to pair it with tools like Playwright or Selenium. Additionally, I found the distributed testing capabilities limited in the free version and often nudging me toward their paid Enterprise offerings. There is a notable correlation friction for dynamic data, which requires manual regex or JSONPath parsing that isn’t as seamless as some GUI recorders. Finally, the initial setup was difficult without proper guidelines for the free version, and the model being 'tests as code' poses a steep learning curve for QA engineers who aren't familiar with programming languages like Java, Kotlin, Scala, or TypeScript.

**What problems is Gatling solving and how is that benefiting you?**

I use Gatling for performance testing, uncovering bottlenecks early, and reducing resource inefficiency. It integrates with CI/CD for regression checks and offers real-time metrics with visual reports.

  ### 7. Robust Load Testing with Gatling, Slight Learning Curve

**Rating:** 4.0/5.0 stars

**Reviewed by:** Sanjeev G. | SDET, Enterprise (> 1000 emp.)

**Validated Reviewer:** Validated through LinkedIn

**Source: Organic:** Organic review. This review was written entirely without invitation or incentive from G2, a seller, or an affiliate.

**Reviewed Date:** August 24, 2026

**What do you like best about Gatling?**

Gatling is a useful tool for performance and load testing, and I found it relatively easy to work with. I like that the tests can be defined and maintained in a structured way, making it easier to reuse and update scenarios. The reporting and performance metrics are helpful for identifying potential bottlenecks and understanding how an application behaves under load. Gatling provides a clear and repeatable approach to performance testing, making it easier to analyze the results after a test run. Additionally, I appreciate how well Gatling fits into CI/CD workflows with its automation capabilities, and how it integrates with existing development and testing workflows, which makes it easier to include performance testing as part of the overall QA process. The initial setup was relatively straightforward, making it easy to get started with creating and running test scenarios.

**What do you dislike about Gatling?**

One area that could be improved is the initial learning curve, especially for users who are new to code-based performance testing. It can take some time to become familiar with the concepts and syntax. The reporting and analysis could also be made a little more intuitive for new users.

**What problems is Gatling solving and how is that benefiting you?**

I find Gatling effective for performance and load testing, helping me solve microservice issues during peak times. It provides me with good visibility into application performance, making it easy for me to create, maintain, and analyze test scenarios.

  ### 8. Code-Based Performance Testing Made Easy with Gatling

**Rating:** 5.0/5.0 stars

**Reviewed by:** Ilija D. | Senior Technical Lead, Enterprise (> 1000 emp.)

**Validated Reviewer:** Validated through LinkedIn

**Source: Organic:** Organic review. This review was written entirely without invitation or incentive from G2, a seller, or an affiliate.

**Reviewed Date:** August 24, 2026

**What do you like best about Gatling?**

What I liked most about Gatling is its code-based approach to performance testing. It makes tests easy to maintain, and integrate into existing CI/CD pipelines (in my case Jenkins). The DSL is clear and flexible, which allows us to create realistic load scenarios and reuse common logic efficiently.
I also appreciate the detailed reports and metrics, which makes it easier to identify performance bottlenecks and understand how the system behaves under different levels of load. Overall, Gatling fits very well into modern QA and development workflows and makes performance testing feel much more like part of the engineering process rather than a separate activity.

**What do you dislike about Gatling?**

One downside if Gatling is that there can be a relatively steep learning curve, especially for people who are new to code-based performance testing. Creating more complex scenarios sometimes requires a good understanding of the DSL and the underlying programming concepts.
Debugging failed or unexpected scenarios can also be less straightforward compared to some GUI-based tools, and advanced reporting or analysis may require additional configuration or external tools. That said, once the initial learning is overcome, these limitations are generally outweighed by Gatling's flexibility and maintainability.

**What problems is Gatling solving and how is that benefiting you?**

Gatling helps us identify performance bottlenecks, scalability issues, and potential system limitations before they impact users in production. It allows us to simulate realistic traffic and validate how APIs and services behave under different levels of load.
The main benefit is that we can detect performance regression earlier in the development release process, which reduces production risk and increases confidence in releases. Because the. tests can also be automated and integrated into CI/CD pipelines, performance testing becomes more repeatable and can be included as part of the regular QA process rather than being performed occasionally.

  ### 9. Gatling Cloud Scales Effortlessly for High-Volume Load Testing

**Rating:** 5.0/5.0 stars

**Reviewed by:** Hitesh P. | Lead Performance Engineer, Small-Business (50 or fewer emp.)

**Validated Reviewer:** Validated through LinkedIn

**Source: Organic:** Organic review. This review was written entirely without invitation or incentive from G2, a seller, or an affiliate.

**Reviewed Date:** August 18, 2026

**What do you like best about Gatling?**

How well it scales for serious load testing. I’ve used it to run performance tests up to 150k RPS without needing to manage my own distributed injector infrastructure, thanks to Gatling Cloud. The Scala/Java DSL gives precise control over realistic load simulations, and the reporting makes it easy to pinpoint bottlenecks and share results with both engineering and non-technical stakeholders.

**What do you dislike about Gatling?**

I don’t have any major dislikes about Gatling. If I had to mention one, the learning curve can be slightly higher for people who are new to code-based performance testing, especially compared with GUI-based tools. But once you get comfortable with Scala/Gatling DSL, it becomes very powerful, maintainable, and flexible.

**What problems is Gatling solving and how is that benefiting you?**

Gatling solves the challenge of creating scalable, maintainable, and code-based performance tests. It makes it easier to model realistic workloads, run tests efficiently, and integrate performance testing into CI/CD pipelines. For me, the biggest benefit is that the scripts are version-controlled, reusable, and easier to maintain than traditional GUI-based performance scripts. It also provides clear performance metrics, which helps me identify bottlenecks and validate application performance quickly.

  ### 10. Efficient Load Testing with Minimal Infrastructure

**Rating:** 4.0/5.0 stars

**Reviewed by:** Harsimranjit S. | Mid-Market (51-1000 emp.)

**Validated Reviewer:** This review contains authentic analysis and has been reviewed by our team

**Source: Organic:** Organic review. This review was written entirely without invitation or incentive from G2, a seller, or an affiliate.

**Reviewed Date:** August 26, 2026

**What do you like best about Gatling?**

I like Gatling for its Java support and the ease of writing scripts. It's quite impressive that I can run 10,000 users with minimal infrastructure. The scripts are lightweight and consume fewer resources, allowing me to efficiently test performance under heavy loads. With a machine having 16 GB RAM, I can run a large number of users without issues. I also appreciate how easy it is to set up Gatling initially, which is a big plus.

**What do you dislike about Gatling?**

If I compare this tool with Jetter, we should also have something called listener, which can be used to inject data of each request response to some data source like InfluxDB in the free version.

**What problems is Gatling solving and how is that benefiting you?**

I use Gatling for performance testing under heavy loads. It's easy for developers to create scripts, supports Java, and can handle 10k users with minimal infrastructure, thanks to lightweight scripts and resource efficiency.

  ### 11. Easy-to-Use Performance Testing Tool for Beginners

**Rating:** 5.0/5.0 stars

**Reviewed by:** Verified User in Gambling & Casinos | Mid-Market (51-1000 emp.)

This reviewer's identity has been verified by our review moderation team. They have asked not to show their 
name, job title, or picture.


**Current User:** The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user.

**Validated Reviewer:** This review contains authentic analysis and has been reviewed by our team

**Source: Organic:** Organic review. This review was written entirely without invitation or incentive from G2, a seller, or an affiliate.

**Reviewed Date:** August 12, 2026

**What do you like best about Gatling?**

I like Gatling because it is easy to use for performance testing and has a clean interface. It helps me create and run load tests without too much complexity. The reports are also easy to understand, which makes it simple for beginners to identify performance issues and check how the application behaves under load.

**What do you dislike about Gatling?**

The main thing I dislike about Gatling is that it can take some time for beginners to understand the setup and scripting. Some features require learning the Gatling syntax, and the documentation can feel a little overwhelming at first. It would be easier if there were more beginner-friendly examples and a simpler setup process.

**What problems is Gatling solving and how is that benefiting you?**

Gatling helps us identify performance and load-related issues before they affect users. It allows us to test how our application performs under different levels of traffic and find slow or unstable areas. This helps us improve application performance, reduce production issues, and feel more confident before releases.

  ### 12. Efficient Load Testing with a Learning Curve

**Rating:** 4.0/5.0 stars

**Reviewed by:** FYPNLP G. | Mid-Market (51-1000 emp.)

**Validated Reviewer:** Validated through LinkedIn

**Source: Organic:** Organic review. This review was written entirely without invitation or incentive from G2, a seller, or an affiliate.

**Reviewed Date:** August 10, 2026

**What do you like best about Gatling?**

I really enjoyed using Gatling for my web/mobile project with an aggressive deadline. It did a fantastic job, letting us simulate thousands of users with ease and without heavy ram or CPU load, which created a quick feedback loop. The excellent recorder tool made it straightforward for load testing, and as an automation tester, I appreciated being able to use JavaScript without needing to learn additional languages. Also, I like the record and playback tool and the fact that I could present the results of testing back to stakeholders quickly.

**What do you dislike about Gatling?**

I found the learning curve challenging due to the project's tight timeline. I would benefit from courses that accommodate different learning styles since I'm a visual learner.

**What problems is Gatling solving and how is that benefiting you?**

Gatling allowed us to simulate thousands of users, providing a quick feedback loop without heavy resource use. Its recorder tool made the process straightforward, and I could use JavaScript, saving time. Presenting results to stakeholders was quick, despite the initial learning curve.

  ### 13. Gatling’s Code-First Performance Testing Fits Perfectly into Our Workflow

**Rating:** 5.0/5.0 stars

**Reviewed by:** Andrii O. | Senior QA Automation Engineer, Enterprise (> 1000 emp.)

**Validated Reviewer:** Validated through LinkedIn

**Source: Organic:** Organic review. This review was written entirely without invitation or incentive from G2, a seller, or an affiliate.

**Reviewed Date:** July 29, 2026

**What do you like best about Gatling?**

I like best about Gatling is its code-first approach to performance testing. Test scenarios are written as maintainable code, which makes them easier to review, version, refactor, and integrate into a regular development workflow.

**What do you dislike about Gatling?**

the initial learning curve. The DSL is elegant once you understand it, but engineers without experience in Scala or functional programming concepts may find the syntax and error messages less approachable than JMeter’s graphical interface. Also we need more steps to set everything up to work with Scala. However, it is possible to choose Kotlin or Java instead.

**What problems is Gatling solving and how is that benefiting you?**

Gatling solves the problem of creating maintainable and repeatable performance tests for APIs and web applications. It allows performance scenarios, workload models, test data, checks, and assertions to be defined as code and stored together with the application or test project.

Compared with GUI-based tools such as JMeter, Gatling makes collaboration through Git more practical. Changes are easier to review, merge, and track, especially when the performance test suite becomes larger and more complex.

It is possible to execute Gatling from Ci CD pipelines and collect the results automatically

  ### 14. Gatling Makes Performance Testing Efficient with Flexible, CI/CD-Friendly Workflows

**Rating:** 5.0/5.0 stars

**Reviewed by:** Muhammed Sameer S. | Automation Tester (QA Engineer), Small-Business (50 or fewer emp.)

**Validated Reviewer:** Validated through a business email account added to their profile

**Source: Organic:** Organic review. This review was written entirely without invitation or incentive from G2, a seller, or an affiliate.

**Reviewed Date:** July 27, 2026

**What do you like best about Gatling?**

What I like most about Gatling is how easy it is to create and maintain performance tests. As an automation tester, I find its code-based approach more flexible than record-and-playback tools. It integrates smoothly with CI/CD pipelines, generates clear and detailed reports, and helps identify performance issues quickly. Overall, it's a reliable tool that makes performance testing efficient and fits well into modern automation workflows.

**What do you dislike about Gatling?**

One thing I dislike about Gatling is that it has a bit of a learning curve, especially if you're new to Scala or its scripting syntax. Creating complex test scenarios can take more effort compared to some GUI-based tools. Also, debugging scripts isn't always straightforward, and some advanced features require extra setup. That said, once you're familiar with it, the flexibility and performance make it worth using.

**What problems is Gatling solving and how is that benefiting you?**

Gatling helps us identify performance bottlenecks before applications go live by simulating real user traffic and measuring how the system behaves under load. As an automation tester, it gives me confidence that new features can handle expected traffic without affecting performance. It also helps catch issues early in the development cycle, supports continuous testing through CI/CD integration, and provides detailed reports that make it easier to analyze results and share insights with the team.

  ### 15. A flexible tool for building complex performance tests

**Rating:** 5.0/5.0 stars

**Reviewed by:** Marek S. | Senior QA Engineer, Mid-Market (51-1000 emp.)

**Validated Reviewer:** Validated through LinkedIn

**Source: Organic:** Organic review. This review was written entirely without invitation or incentive from G2, a seller, or an affiliate.

**Reviewed Date:** July 23, 2026

**What do you like best about Gatling?**

What I like most about Gatling is its flexibility and the ability to build complex performance test scenarios as code. It gives me full control over test flows, dynamic data, request generation, and different load injection models.

I particularly appreciate that Gatling can be extended beyond standard HTTP testing. In my case, I use it for complex SOAP-based scenarios with dynamic request generation, WS-Security signing, custom mock services, and multi-step transaction flows. The Java-based DSL also makes it easier to structure, maintain, and reuse test components compared to traditional GUI-based performance testing tools.

Another strong point is the clear separation between test logic, request generation, and load profiles, which makes the test project easier to develop and integrate into CI/CD pipelines.

**What do you dislike about Gatling?**

There is not much I dislike about Gatling itself. One challenge is that more complex or non-standard use cases can require additional custom development and a deeper understanding of the underlying technologies. For example, working with SOAP, WS-Security, or custom mock services requires building some functionality yourself.

However, this is also a consequence of Gatling's flexibility, as it gives you the freedom to implement scenarios that go beyond typical HTTP/REST performance testing.

**What problems is Gatling solving and how is that benefiting you?**

Gatling helps us validate the performance and stability of our systems under different load conditions before changes reach production. It allows us to simulate realistic, multi-step transaction flows and control how the load is generated, from gradual ramp-up to sustained concurrency and peak-load scenarios.

The main benefit is repeatability and automation. Performance tests can be maintained as code, reused across different scenarios, and integrated into CI/CD processes. This makes it easier to identify performance bottlenecks, compare system behavior between releases, and reproduce specific load conditions when investigating performance issues.

**Official Response from Diego Salinas:**

> Thank you for the thoughtful review, and especially for calling out our CI/CD integrations with Jenkins, GitLab, and GitHub Actions. Helping teams catch performance regressions before they hit production, especially ahead of high-stakes events like Black Friday, is exactly what we're aiming for.

We also appreciate the feedback on the learning curve for non-developers. Since you last reviewed us, we've made this a priority. We launched a Recorder that lets you generate Gatling scripts from recorded actions rather than writing the Scala code by hand, plus AI-powered migration tools to help teams move existing JMeter and LoadRunner test suites into Gatling. We've also rolled out AI-powered documentation to make it easier to get unstuck without needing deep Scala expertise. Together, these are meant to lower exactly the barrier you described.

We'd love for you to try them out and let us know how they compare to your experience so far. Thanks again for using Gatling and for the detailed feedback.

  ### 16. Developer-Friendly with Powerful Graphical Reporting

**Rating:** 4.5/5.0 stars

**Reviewed by:** Rishav . | Assistant System Engineer-trainee, Enterprise (> 1000 emp.)

**Validated Reviewer:** Validated through LinkedIn

**Source: Organic:** Organic review. This review was written entirely without invitation or incentive from G2, a seller, or an affiliate.

**Reviewed Date:** July 22, 2026

**What do you like best about Gatling?**

I used Gatling for load testing REST APIs in one of my projects. I find it very lightweight, which makes handling concurrency from a single machine much easier. Compared to tools like JMeter, Gatling consumes fewer resources, which is beneficial for simulating millions of users, like during a Black Friday sale, saving a chunk of money on resources. It's developer-friendly, which I appreciate since version control with development is easy. I also like its reporting features, especially the graphical representations, as they provide a clear view of performance metrics.

**What do you dislike about Gatling?**

I find it challenging to learn Scala, which can be quite difficult for new folks who need to invest a lot of time. I feel Gatling's free tier is less flexible compared to open-source tools like JMeter that give you more ease to scale in the way you want. Setting up the Scala environment was somewhat difficult.

**What problems is Gatling solving and how is that benefiting you?**

I use Gatling for its lightweight and developer-friendly nature, which eases handling high concurrency with less infrastructure. It's valuable for cost-effective load testing, especially with its graphical reporting that enhances insights.

**Official Response from Diego Salinas:**

> thank you for the detailed review and for sharing how you're using Gatling for high-concurrency load testing!

We're glad the lightweight design and graphical reporting are pulling their weight, especially for something as demanding as a Black Friday-scale simulation. Cost-effective load testing at that volume is exactly the problem we built Gatling to solve, so it's great to hear it's landing that way for you.

On the Scala learning curve: that's fair feedback we hear often, and it's actually already changed. Gatling now supports Java, JavaScript, TypeScript, and Kotlin in addition to Scala, so you (or teammates who'd rather not pick up Scala) can write simulations in a language you already know. Worth a look if that setup friction was the main blocker.

On the free tier: we're always weighing flexibility against sustainability for the open-source project, so I've passed your feedback to the product team.

Thanks again for taking the time to write this up. If you get a chance to try one of the newer language SDKs, we'd love to hear how it goes.


Diego from Gatling

  ### 17. Realistic Load Testing with Rich Metrics and CI/CD-Friendly Scripting

**Rating:** 4.0/5.0 stars

**Reviewed by:** Minaz K. | QA Consultant, Small-Business (50 or fewer emp.)

**Validated Reviewer:** Validated through LinkedIn

**Source: Organic:** Organic review. This review was written entirely without invitation or incentive from G2, a seller, or an affiliate.

**Reviewed Date:** July 22, 2026

**What do you like best about Gatling?**

What I like best about Gatling is its ability to simulate realistic user loads and provide detailed performance metrics. Being code-based, it allows test scripts to be version-controlled and integrated easily into CI/CD pipelines. I also appreciate its rich reports and dashboards, which help quickly identify performance bottlenecks and analyze system behavior under load.

**What do you dislike about Gatling?**

What I dislike about Gatling is that it is less beginner-friendly than GUI-based performance testing tools. Since it is code-centric, it requires programming knowledge and can take more effort to create, debug, and maintain complex test scenarios.

**What problems is Gatling solving and how is that benefiting you?**

Gatling solves the challenge of validating an application's performance, scalability, and stability under different user loads before issues impact production. It helps identify bottlenecks such as slow response times, resource constraints, and throughput limitations by simulating realistic user traffic.
For me, the main benefit is the ability to proactively detect performance issues early in the development lifecycle. This helps improve application reliability, supports performance validation in CI/CD pipelines, and provides valuable insights through detailed reports, enabling teams to deliver a better user experience and reduce production risks.

  ### 18. Effortless Performance Testing with Gatling

**Rating:** 4.5/5.0 stars

**Reviewed by:** Vishal R. | Software Development Engineer in Test II, Enterprise (> 1000 emp.)

**Validated Reviewer:** Validated through LinkedIn

**Source: Organic:** Organic review. This review was written entirely without invitation or incentive from G2, a seller, or an affiliate.

**Reviewed Date:** July 15, 2026

**What do you like best about Gatling?**

I love how Gatling helps us generate different types of load while keeping test scripts maintainable. The Gatling reports are detailed and make it simple to identify performance bottlenecks. I also appreciate that it easily integrates with Jenkins pipelines, which is really useful for our deployment in a Kubernetes environment. Gatling's feature for generating real-time different load scenarios helps us catch performance issues before they reach production. Maintaining scripts in Gatling is easy, it requires minimal infrastructure, and it's straightforward to learn for anyone with programming knowledge. Setting up Gatling was straightforward by following the Gatling documentation.

**What do you dislike about Gatling?**

If we can integrate Gatling reports with application performance management tools like Grafana.

**What problems is Gatling solving and how is that benefiting you?**

I use Gatling to test backend APIs performance under peak load, assess response times, and decide infrastructure for microservices. It generates various load scenarios, helps catch issues before production, keeps scripts maintainable, provides detailed reports for bottlenecks, and integrates easily with Jenkins pipelines.

  ### 19. Reliable and Efficient Load Testing Tool for Modern CI/CD Pipelines

**Rating:** 4.5/5.0 stars

**Reviewed by:** Neema F. | Full Stack Engineer, Small-Business (50 or fewer emp.)

**Validated Reviewer:** Validated through LinkedIn

**Source: Organic:** Organic review. This review was written entirely without invitation or incentive from G2, a seller, or an affiliate.

**Reviewed Date:** July 31, 2026

**What do you like best about Gatling?**

Gatling is how efficiently it handles high-load performance testing without consuming excessive system resources, especially compared to other load testing tools I've used. The Scala-based DSL makes it easy to write clear, maintainable test scenarios. It also integrates smoothly into our CI/CD pipeline, so we can catch performance regressions before they reach production

**What do you dislike about Gatling?**

Scala knowledge required for scripting. Debugging complex scenarios can be tricky

**What problems is Gatling solving and how is that benefiting you?**

Gatling helps us identify performance bottlenecks and validate system stability before releasing new features into production. By simulating realistic load scenarios, we can catch issues like slow response times. This has helped us build more confidence in our releases, reduce the risk of downtime during peak usage, and make more informed decisions about scaling infrastructure. Overall, it's saved us from costly post-release fixes and given the team a clearer picture of how our systems perform under real-world conditions.

  ### 20. Scalable Performance Testing with Easy Maintenance

**Rating:** 5.0/5.0 stars

**Reviewed by:** Numan I. | Small-Business (50 or fewer emp.)

**Validated Reviewer:** Validated through a business email account added to their profile

**Source: Organic:** Organic review. This review was written entirely without invitation or incentive from G2, a seller, or an affiliate.

**Reviewed Date:** September 21, 2026

**What do you like best about Gatling?**

I like Gatling because it provides a scalable performance testing framework that's easy to maintain. The reporting is great, and I appreciate the reusability options for scenarios, which makes testing more efficient. It integrates well across CI/CD pipelines and the initial setup was a breeze. Switching from JMeter to Gatling was smooth due to the user-friendly framework and code.

**What do you dislike about Gatling?**

The documentation could be improved. I'd like to see more examples, especially around authentication, data parameterization, and assertions, as it would make onboarding easier.

**What problems is Gatling solving and how is that benefiting you?**

Gatling provides a scalable performance testing framework for our CI/CD pipelines. It's easy to maintain and offers proper reporting and scenarios reusability, making it a great tool for performance testing.

  ### 21. Scalable, Developer-Friendly Load Testing

**Rating:** 4.5/5.0 stars

**Reviewed by:** Tarang S. | Senior Consultant Testing, Small-Business (50 or fewer emp.)

**Validated Reviewer:** Validated through LinkedIn

**Source: Organic:** Organic review. This review was written entirely without invitation or incentive from G2, a seller, or an affiliate.

**Reviewed Date:** August 31, 2026

**What do you like best about Gatling?**

I like Gatling’s code-based approach, which makes the tests easy to version and maintain. I appreciate the realistic load simulation that closely mimics production traffic. The detailed reports are really helpful in making bottlenecks easy to analyze. Also, Gatling handles high concurrency efficiently, allowing me to test systems at scale without excessive resource usage.

**What do you dislike about Gatling?**

I find the learning curve steep for me as a beginner, I struggle with debugging complex scenarios, and I wish there were more customization options for the reporting/dashboard.

**What problems is Gatling solving and how is that benefiting you?**

I use Gatling to identify performance bottlenecks, validate system scalability, and detect issues under high loads. Its code-based approach makes maintenance easy, and realistic simulations aid in closely mimicking production traffic, with detailed reports simplifying bottleneck analysis.

  ### 22. Ease and Efficient Integration, Explanations Can Improve

**Rating:** 5.0/5.0 stars

**Reviewed by:** Vilson R. | QA Specialist, Small-Business (50 or fewer emp.)

**Validated Reviewer:** Validated through LinkedIn

**Source: Organic:** Organic review. This review was written entirely without invitation or incentive from G2, a seller, or an affiliate.

**AI Translated:** This review has been translated from Portuguese using AI.

**Reviewed Date:** August 17, 2026

**What do you like best about Gatling?**

I really like the ease of coding in Gatling, which helps me a lot in performance testing. The integration with the ecosystem developed by my contractor is another positive point. Furthermore, the understanding in the use and analysis of the results generated by Gatling is very good. I also found the initial setup extremely easy.

**What do you dislike about Gatling?**

The explanation of the results in Gatling could be improved, especially for those who are not specialists in non-functional testing. I have difficulty explaining the results to stakeholders because they are presented in a very technical way, which does not help laypeople to understand easily.

**What problems is Gatling solving and how is that benefiting you?**

I use Gatling for performance testing and it facilitates integration into my contractor's ecosystem. The coding is easy to understand, making it easier to analyze the results.

  ### 23. Flexible, Coding-First Performance Testing with Clear, Intuitive Reports

**Rating:** 4.5/5.0 stars

**Reviewed by:** Verified User in Hospital & Health Care | Mid-Market (51-1000 emp.)

This reviewer's identity has been verified by our review moderation team. They have asked not to show their 
name, job title, or picture.


**Current User:** The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user.

**Validated Reviewer:** This review contains authentic analysis and has been reviewed by our team

**Source: Organic:** Organic review. This review was written entirely without invitation or incentive from G2, a seller, or an affiliate.

**Reviewed Date:** June 21, 2026

**What do you like best about Gatling?**

What I like most about Gatling is the flexibility and freedom it gives you when designing performance tests. It makes it easy to create reusable scenarios, build complex test chains, and structure tests in a maintainable way.

The ability to use a real programming language such as Kotlin is a major advantage, as it allows for advanced logic and customization that would be difficult to achieve with more restrictive tools. This gives me full control over how I design, organize, and execute my tests.

I also appreciate how clear and intuitive the reporting is. The reports are easy to understand and communicate to both technical and non-technical stakeholders. Overall, the coding-first approach and the level of control it provides are what make Gatling stand out for me.

**What do you dislike about Gatling?**

One area where Gatling could improve is troubleshooting and error analysis. The reports do not always provide enough detail about failed requests, which can make investigations more difficult. For example, when a request returns an HTTP 500 error, it would be helpful to see the underlying error message or stack trace directly in the report instead of having to search through application logs. Having more detailed failure information available out of the box would make debugging and root-cause analysis much faster and more efficient.

**What problems is Gatling solving and how is that benefiting you?**

The main problems Gatling solves for me are performance regression control and load testing under realistic conditions. It helps detect whether a new update has negatively impacted API performance, such as increased response times or reduced throughput, which is crucial for maintaining stability in production.

Another key benefit is the ability to simulate different load scenarios on various machine specifications. This makes it possible to evaluate how systems behave under stress and identify potential bottlenecks or scaling issues before they affect real users. Overall, Gatling provides valuable insight into performance trends and system reliability over time.

**Official Response from Diego Salinas:**

> Thanks so much for taking the time to share this.

We’re really happy to hear Gatling is giving you the control and clarity you need in your testing workflow.

Your point on debugging is fair, too. Making failure analysis faster and easier is exactly the kind of feedback that helps us improve the product.

Thanks again for the thoughtful review.

  ### 24. Customizable and Powerful Load Testing

**Rating:** 5.0/5.0 stars

**Reviewed by:** Yago Janos Andrevitch  G. | Mid-level Back-end Software Developer, Mid-Market (51-1000 emp.)

**Validated Reviewer:** Validated through LinkedIn

**Source: Organic:** Organic review. This review was written entirely without invitation or incentive from G2, a seller, or an affiliate.

**Reviewed Date:** August 27, 2026

At G2, we prefer fresh reviews and we like to follow up with reviewers. They may not have updated their review text, but have updated their review.

**What do you like best about Gatling?**

I really like Gatling's flexibility and customization options. It allows me to create different load testing scenarios and adapt them to the specific needs of each application. I also find it useful for testing applications in development and staging environments before they reach production.

**What do you dislike about Gatling?**

I think the initial setup and learning curve could be a little easier, especially for new users. Some configurations can take time to understand, but after some research and practice, the tool becomes much easier to use.

**What problems is Gatling solving and how is that benefiting you?**

Gatling helps me simulate different load and traffic scenarios to evaluate application performance under different levels of usage. This allows me to identify bottlenecks and performance issues before production, helping improve application reliability and stability.

  ### 25. Excellent Documentation and Broad Language Support

**Rating:** 4.5/5.0 stars

**Reviewed by:** Damaso F. | QA Engineer, Small-Business (50 or fewer emp.)

**Current User:** The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user.

**Validated Reviewer:** Validated through LinkedIn

**Source: Organic:** Organic review. This review was written entirely without invitation or incentive from G2, a seller, or an affiliate.

**Reviewed Date:** July 18, 2026

**What do you like best about Gatling?**

I like the documentation and the many languages it supports; it gives me flexibility across multiple projects.

**What do you dislike about Gatling?**

It’s hard to think of something I dislike, but if I had to mention one thing, it would be that the generated reports could be more user-friendly and easier for anyone to understand at first sight.

**What problems is Gatling solving and how is that benefiting you?**

In the project where I used it, it handled the performance-testing part in an easier way by letting us write code. Before, we used other tools like JMeter, but we prefer this one because it integrates what we already know about coding into performance testing.

  ### 26. Effortless Integration and User-Friendly Documentation

**Rating:** 4.5/5.0 stars

**Reviewed by:** pratik r.

**Validated Reviewer:** This review contains authentic analysis and has been reviewed by our team

**Source: Organic:** Organic review. This review was written entirely without invitation or incentive from G2, a seller, or an affiliate.

**Reviewed Date:** July 20, 2026

**What do you like best about Gatling?**

I found Gatling easy to understand and write code in. Even when I joined the project without knowing anything about Gatling, the inbuilt repository with the code and framework was easy to comprehend. The code is in a very readable format, so anyone with some technical knowledge can read, understand, and write it. The documentation on the Gatling site is pretty self-explanatory, making it straightforward to learn anything new and implement Gatling code in services. Working with Gatling was really good because of this easy-to-read and follow documentation. The initial setup was also easy, with top-notch documentation that anyone can follow.

**What do you dislike about Gatling?**

Not anything to say at this stage

**What problems is Gatling solving and how is that benefiting you?**

I use Gatling for performance testing. It's easy to understand and write code, even for newcomers. The documentation is self-explanatory, aiding quick setup and implementation.

  ### 27. Gatling: Simple and Efficient Load Testing to Validate Performance

**Rating:** 4.0/5.0 stars

**Reviewed by:** Verified User in Computer Software | Enterprise (> 1000 emp.)

This reviewer's identity has been verified by our review moderation team. They have asked not to show their 
name, job title, or picture.


**Validated Reviewer:** Validated through LinkedIn

**Source: Organic:** Organic review. This review was written entirely without invitation or incentive from G2, a seller, or an affiliate.

**AI Translated:** This review has been translated from Spanish; Castilian using AI.

**Reviewed Date:** September 24, 2026

**What do you like best about Gatling?**

I like Gatling because it allows for simple and efficient load testing. I have used it in my work to validate application performance in both non-production and production environments, analyzing metrics and detecting bottlenecks to identify improvement opportunities.

**What do you dislike about Gatling?**

One of its main limitations is that it has a steeper learning curve than tools like JMeter, especially due to its code-based approach. Additionally, it can be more complex to simulate complete scenarios and highly varied or dynamic user flows, requiring more effort to model them accurately.

**What problems is Gatling solving and how is that benefiting you?**

Gatling allows for the detection of performance issues before they reach production, such as bottlenecks, high response times, or degradation under load. It benefits me because I can validate application capacity and detect problems early.

  ### 28. Easy Load Testing with Gatling, Needs Better Server-Side Features

**Rating:** 4.5/5.0 stars

**Reviewed by:** dmytro s. | Mid-Market (51-1000 emp.)

**Validated Reviewer:** This review contains authentic analysis and has been reviewed by our team

**Source: Organic:** Organic review. This review was written entirely without invitation or incentive from G2, a seller, or an affiliate.

**Reviewed Date:** July 15, 2026

**What do you like best about Gatling?**

I like Gatling for its usability and simplicity compared to other tools like JMeter. The multithreading and automation capabilities are particularly beneficial, allowing me to set up each thread with ease and perform a lot of actions. It was great for handling load testing without being overly complicated, which made tasks much easier to manage. The initial setup was quite easy and took less than a day.

**What do you dislike about Gatling?**

I don't think Gatling was able to run on the server as a watchdog or for deploying tests for stress and load testing. Also, I don't remember if Gatling had the option to run load tests while deploying on CICD.

**What problems is Gatling solving and how is that benefiting you?**

I use Gatling for blog and API testing to see how applications behave under different load conditions, particularly for stress and load testing.

  ### 29. Highly Customizable DSLs with Strong Community Support

**Rating:** 4.5/5.0 stars

**Reviewed by:** Nilson N. | Ssr Adv Test Automation Enginner, Mid-Market (51-1000 emp.)

**Validated Reviewer:** Validated through LinkedIn

**Source: Organic:** Organic review. This review was written entirely without invitation or incentive from G2, a seller, or an affiliate.

**Reviewed Date:** July 21, 2026

**What do you like best about Gatling?**

The ability to customize the validations and the ability to integrate as a DSL in different programming languages. The broad community is fundamental when it comes to select it since you can find solutions to most of challanges from people in the past already.

**What do you dislike about Gatling?**

The HTML report is hard to modify; we have to depend on a cloud solution, which, for a small project, is not feasible.

**What problems is Gatling solving and how is that benefiting you?**

Ability to customize and create so detailed validations during performance testing, and the ability to incorporate additional programming dependencies to enrich your validation. When it comes to E2E performance testing, we can find so many flavours in user flows, and those features of Gatling give you the ability to adapt the tool to so many user flows and technologies

  ### 30. Customizable Performance Testing as Code with Developer-Friendly Gatling

**Rating:** 4.5/5.0 stars

**Reviewed by:** Verified User in Information Technology and Services | Enterprise (> 1000 emp.)

This reviewer's identity has been verified by our review moderation team. They have asked not to show their 
name, job title, or picture.


**Validated Reviewer:** Validated through LinkedIn

**Source: Organic:** Organic review. This review was written entirely without invitation or incentive from G2, a seller, or an affiliate.

**Reviewed Date:** August 14, 2026

**What do you like best about Gatling?**

The best thing I like is that it supports performance testing and load testing as code, making it very easy to write in Scala. Gatling can be configured as code, which I prefer over JMeter's XML configuration. The initial setup was pretty easy because Gatling works via simple coding scripts. The best part is that it is developer-friendly, which is why it is gaining popularity.

**What do you dislike about Gatling?**

Sometimes it's difficult for me to simulate the exact number of users or to actually have a understanding about count of how the ramp-up of the users is working. If it is more readable or maybe there is better documentation for that, it would help us to understand the number of users.

**What problems is Gatling solving and how is that benefiting you?**

I use Gatling to identify performance issues and memory leaks, enabling fine-tuning of my application. It's great for performance and load testing as code in Scala, which makes it easy to write and customize. The Gatling charts are also offers quite meaningful information.

  ### 31. Flexible Cloud Setup That Fits Every Team

**Rating:** 5.0/5.0 stars

**Reviewed by:** Matt P. | QA Lead, Enterprise (> 1000 emp.)

**Current User:** The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user.

**Validated Reviewer:** Validated through LinkedIn

**Source: Organic:** Organic review. This review was written entirely without invitation or incentive from G2, a seller, or an affiliate.

**Reviewed Date:** March 09, 2026

**What do you like best about Gatling?**

Flexibility. I like to write in Scala, others prefer Kotlin, Frontend and QA colleagues prefer TypeScript or Javascript. All as code, all in cloud. Perfect setup for current times

**What do you dislike about Gatling?**

Setting up the internal network runners is not ideal, but nothing overcomplicated

**What problems is Gatling solving and how is that benefiting you?**

Gatling is helping us solve two main problems.

First, it removes the ceiling we hit with local testing. When we run tests locally, we’re limited by how many users a workstation can handle, which is usually not enough to understand real scaling behavior (at least with Java; with Scala it’s much better). With Gatling Enterprise, we can safely push tests into the thousands of users and see how our systems actually behave under load.

Second, it gives us a controlled way to stress critical user paths so we can validate autoscaling and overall system stability. The biggest benefit isn’t the report itself, but the engineering signal: whether the service stays healthy, whether scaling kicks in correctly, and where it breaks as load increases.

With Gatling cloud, we also have the option to run tests from external networks or private IPs, which is great for validating the end-to-end user journey.

**Official Response from Diego Salinas:**

> Hi Matt, thank you for the detailed review!

We're glad the language flexibility and cloud setup are working well for your team. That polyglot workflow is exactly what we designed for, so it's good to hear it's landing that way in practice. And it's great that Gatling Enterprise is helping you get past the local-testing ceiling and giving your team a clear picture of autoscaling and stability under load. That's the part we care most about.

Thanks for flagging the internal network runner setup, too. Onboarding steps like that are exactly where we're trying to smooth things out, and specific feedback like yours helps us decide where to focus next.

Appreciate you taking the time to write this up in such detail. It's genuinely useful for us, and for other teams weighing up Gatling.

Diego from Gatling

  ### 32. Reliable, resource-efficient stress testing for high-volume booking engines

**Rating:** 4.5/5.0 stars

**Reviewed by:** Verified User in Transportation/Trucking/Railroad | Mid-Market (51-1000 emp.)

This reviewer's identity has been verified by our review moderation team. They have asked not to show their 
name, job title, or picture.


**Validated Reviewer:** Validated through LinkedIn

**Source: Organic:** Organic review. This review was written entirely without invitation or incentive from G2, a seller, or an affiliate.

**Reviewed Date:** August 08, 2026

**What do you like best about Gatling?**

In my QA role, I relied heavily on Gatling to stress-test our core vehicle-booking flows. The standout feature for me was Gatling’s code-as-configuration DSL. Since we could write load tests as code, we kept them in version control right alongside the application code. That shift changed our workflow significantly and saved our QA team hours of manual test maintenance each week, especially compared with UI-heavy legacy tools.

Another benefit I didn’t expect at first was how smoothly Gatling fit into our existing CI/CD pipelines. It didn’t just enable large, concurrent stress tests; it also gave us immediate, automated performance feedback on new deployments. On top of that, the out-of-the-box HTML reporting is excellent—it helped us quickly pinpoint specific database bottlenecks during high-traffic booking simulations without needing to set up external visualization dashboards.

**What do you dislike about Gatling?**

While the code-as-configuration approach is a strength, the steep learning curve of Gatling's Scala-based DSL was our biggest hurdle. During our Europcar booking stress tests, onboarding QA engineers who were used to visual, GUI-based tools (like JMeter) took significantly longer. The impact was a slower initial setup phase for our load-testing framework, as team members had to learn a new language syntax just to write basic tests. A potential improvement would be offering a lightweight, visual test-builder interface for simpler scenarios, which would lower the barrier to entry while keeping the powerful code DSL for complex edge cases.

**What problems is Gatling solving and how is that benefiting you?**

Before using Gatling at Europcar, we struggled to accurately simulate high-volume, concurrent user traffic on our booking engine without consuming massive amounts of hardware resources. Our previous testing tools were difficult to integrate into an automated CI/CD pipeline, making performance testing a slow, manual bottleneck before major releases.

Now, we can write our load tests as code and automatically trigger them within our deployment pipeline, which has resulted in much faster, automated feedback loops. The primary benefit is that we reliably catch database deadlocks and API latency issues early. Quantifiably, this has resulted in a roughly 30% reduction in time spent configuring performance tests, and it has significantly increased the reliability of our booking platform during peak holiday traffic spikes

  ### 33. Easy Jenkins Integration and Detailed Reports for Reliable Performance Testing

**Rating:** 4.0/5.0 stars

**Reviewed by:** Verified User in Events Services | Mid-Market (51-1000 emp.)

This reviewer's identity has been verified by our review moderation team. They have asked not to show their 
name, job title, or picture.


**Validated Reviewer:** Validated through LinkedIn

**Source: Organic:** Organic review. This review was written entirely without invitation or incentive from G2, a seller, or an affiliate.

**Reviewed Date:** August 06, 2026

**What do you like best about Gatling?**

Gatling has been easy to integrate into our Jenkins pipeline, making performance testing an automated part of our release process. I also like the detailed reports, which make it simple to analyze response times and identify bottlenecks. The scripting approach gives us flexibility to maintain and update test scenarios as our application evolves, and overall it has been a reliable tool for our performance testing needs.

**What do you dislike about Gatling?**

The initial learning curve is probably the biggest drawback, especially for team members who are new to Gatling's scripting approach. Creating and maintaining complex test scenarios can take some time to get used to. While the documentation is helpful, I'd appreciate more real-world examples and troubleshooting guides for advanced use cases. Apart from that, the tool has been reliable for our performance testing needs.

**What problems is Gatling solving and how is that benefiting you?**

Gatling helps us validate our application's performance before every release by automating load tests through Jenkins. It enables us to identify performance bottlenecks, detect regressions early, and ensure critical user flows remain stable under load. This has improved our release confidence and made performance testing a consistent part of our CI/CD process.

  ### 34. Reliable Performance Testing for Micro services APIs

**Rating:** 4.5/5.0 stars

**Reviewed by:** Verified User in Retail | Enterprise (> 1000 emp.)

This reviewer's identity has been verified by our review moderation team. They have asked not to show their 
name, job title, or picture.


**Validated Reviewer:** Validated through LinkedIn

**Source: Organic:** Organic review. This review was written entirely without invitation or incentive from G2, a seller, or an affiliate.

**Reviewed Date:** August 04, 2026

**What do you like best about Gatling?**

I was able to handle performance testing at scale while keeping the test scripts clean and maintainable. 
The developer friendly method using code based scenarios made it easier to version, review, and collaborate on tests compared to GUI tools.

**What do you dislike about Gatling?**

We need more beginner friendly documentation, examples, that would make it more accessible for new users.
There can be a learning curve for users who are more familiar with traditional GUI based performance testing tools

**What problems is Gatling solving and how is that benefiting you?**

Gatling helped us validate the performance, scalability, and reliability of our microservice APIs by simulating realistic user loads and identifying potential bottlenecks. We used Gatling along with a BDD approach using Karate to test APIs, including scenarios that interact with the reporting service in a pharmacy management system.

Tested how our sites handle expected traffic, maintain response time targets, and remain stable under load. This helped our team identify issues faster, improve API efficiency, and deliver a more reliable experience for end users.

  ### 35. Developer-Friendly with a Learning Curve

**Rating:** 3.5/5.0 stars

**Reviewed by:** Verified User | Small-Business (50 or fewer emp.)

This reviewer's identity has been verified by our review moderation team. They have asked not to show their 
name, job title, or picture.


**Validated Reviewer:** Validated through LinkedIn

**Source: Organic:** Organic review. This review was written entirely without invitation or incentive from G2, a seller, or an affiliate.

**Reviewed Date:** July 28, 2026

**What do you like best about Gatling?**

I like that Gatling is a non-GUI, developer-centric tool. The fact that scripts can even be AI-generated is pretty cool, and I find the memory footprint per script to be actually minuscule. It's efficient enough that I can use a single VM to run over 500 threads. I also appreciate how Gatling can be integrated into our dev workflows, allowing Claude to auto-generate Gatling scripts as we develop and build APIs. Additionally, AI can go through Postman collections to create a complete Gatling suite of scripts. Setting up Gatling was rather easy, with no problems there.

**What do you dislike about Gatling?**

Since Gatling is non-GUI, I find it has a learning curve for us non-developers. It takes time for us to figure out the functions and features. Also, I face challenges because Gatling requires Scala, and I had to cross-train Java developers to read and understand Scala code.

**What problems is Gatling solving and how is that benefiting you?**

I use Gatling for scripting end-to-end business workflows, creating reusable templates, and scaling our performance testing frameworks. The low memory footprint allows running 500+ threads on a single VM. It integrates with our dev workflows for auto-generating scripts.

  ### 36. Lightweight, Fast, and Accurate Testing with Gatling

**Rating:** 4.5/5.0 stars

**Reviewed by:** Ravindra G. | Senior Test Engineer, Small-Business (50 or fewer emp.)

**Validated Reviewer:** Validated through LinkedIn

**Source: Organic:** Organic review. This review was written entirely without invitation or incentive from G2, a seller, or an affiliate.

**Reviewed Date:** July 21, 2026

**What do you like best about Gatling?**

I like that Gatling is lightweight and easy to use. There are many options available for script preparation, which allows us to work fast and achieve accurate results. The initial setup was smooth, making it easier for us to transition to using Gatling for performance testing activities.

**What do you dislike about Gatling?**

We have an issue with the report file not being generated in Excel format. Instead, Gatling reports are provided in a different file format. It would be better if Gatling could generate reports in Excel format as well.

**What problems is Gatling solving and how is that benefiting you?**

I use Gatling for performance testing to solve production issues. It's lightweight and easy to use, with many script options. We work fast and get accurate results.

  ### 37. Seamless Karate Integration with Rich Performance Insights

**Rating:** 5.0/5.0 stars

**Reviewed by:** Vijaysai M. | Staff Quality Assurance Engineer, Small-Business (50 or fewer emp.)

**Current User:** The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user.

**Validated Reviewer:** Validated through LinkedIn

**Source: Organic:** Organic review. This review was written entirely without invitation or incentive from G2, a seller, or an affiliate.

**Reviewed Date:** August 01, 2026

**What do you like best about Gatling?**

It integrates well with my existing Karate framework. Can easily run load tests and produces reports with rich performance insights.

**What do you dislike about Gatling?**

Nothing much to add, really. It’s one of the best tools I’ve used so far for performance testing, and it has worked well for what I needed.

**What problems is Gatling solving and how is that benefiting you?**

It helps me simulate load on various services in our product, so I can measure performance and identify bottlenecks.

  ### 38. Gatling user since 2016

**Rating:** 5.0/5.0 stars

**Reviewed by:** Boris K. | Senior Automation Engineer, Mid-Market (51-1000 emp.)

**Current User:** The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user.

**Validated Reviewer:** Validated through LinkedIn

**Incentivized:** This reviewer was offered a nominal incentive as thanks for completing this review.

**Source: G2 invite on behalf of seller:** Invitation from G2 on behalf of a seller or affiliate. This reviewer was offered a nominal incentive as thanks for completing this review.

**Reviewed Date:** June 29, 2023

At G2, we prefer fresh reviews and we like to follow up with reviewers. They may not have updated their review text, but have updated their review.

**What do you like best about Gatling?**

Writing performance tests as a code, gradle support.
Very good documentation and a very useful community. 
Great memory management, easy support of tens of thousands of users.

**What do you dislike about Gatling?**

I still haven’t found a perfect way to debug the tests yet.

**What problems is Gatling solving and how is that benefiting you?**

1. Tens of thousands of users simulation
2. Groups of requests, simulating complex browser pages using the BE
3. Good visualization of load/stress test results

  ### 39. Lightweight Load Testing That Delivers High Performance with Fewer Resources

**Rating:** 4.5/5.0 stars

**Reviewed by:** Sarthak M. | Senior Software Architect, Enterprise (> 1000 emp.)

**Validated Reviewer:** Validated through LinkedIn

**Source: Organic:** Organic review. This review was written entirely without invitation or incentive from G2, a seller, or an affiliate.

**Reviewed Date:** August 13, 2026

**What do you like best about Gatling?**

I’ve used multiple tools like JMeter, LR, and NeoLoad, and compared to them, this one feels lightweight. It helps us execute higher loads while using fewer resources.

**What do you dislike about Gatling?**

It needs to improve in terms of protocol support. Market leaders like Jmeter, NL, and LR offer a much wider variety of supported protocols, which Gatling currently doesn’t have.

**What problems is Gatling solving and how is that benefiting you?**

We needed to run a large load test with limited resources, and with JMeter we were feeling constrained. That’s where Gatling helped us. Now, with it available, we can quickly create Scala scripts and execute them.

  ### 40. Great Load & Performance Testing Capabilities for Our Infrastructure

**Rating:** 4.5/5.0 stars

**Reviewed by:** Anurag A. | Engineering Manager, Enterprise (> 1000 emp.)

**Current User:** The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user.

**Validated Reviewer:** Validated through Google using a business email account

**Source: Organic:** Organic review. This review was written entirely without invitation or incentive from G2, a seller, or an affiliate.

**Reviewed Date:** August 07, 2026

**What do you like best about Gatling?**

It has great capabilities and features for measuring load and performance when testing our infrastructure.

**What do you dislike about Gatling?**

Pricing is bit on a higher side and we have less community till date , we can have ways to onboard customer

**What problems is Gatling solving and how is that benefiting you?**

it helps me and my team to access the performance of our Web Applications , API's under immense load .

  ### 41. Robust, Scalable, and Beginner-Friendly Tool

**Rating:** 4.5/5.0 stars

**Reviewed by:** Verified User

This reviewer's identity has been verified by our review moderation team. They have asked not to show their 
name, job title, or picture.


**Validated Reviewer:** This review contains authentic analysis and has been reviewed by our team

**Source: Organic:** Organic review. This review was written entirely without invitation or incentive from G2, a seller, or an affiliate.

**Reviewed Date:** August 17, 2026

**What do you like best about Gatling?**

I love Gatling for its excellent tool features, including great language compatibility, especially with Scala. It's very robust, easy to maintain, and highly scalable. Gatling is a must for beginners because it's effortless to manage code and easy to begin with. I like its multi-language compatibility and the reports generated by Gatling are true gems, providing an entire snapshot of performance tests at a glance. The official documentation is great for setup, which makes it easy to use.

**What do you dislike about Gatling?**

I feel that many professionals don't even know about it, and I think the marketing can be improved.

**What problems is Gatling solving and how is that benefiting you?**

I find Gatling offers effortless code management and multi-language compatibility, and it generates detailed reports for performance testing. It's robust, scalable, and easy for me as a beginner.

  ### 42. Great tool to Boost Legacy App Performance

**Rating:** 4.5/5.0 stars

**Reviewed by:** shivangi j. | Associate Developer, Mid-Market (51-1000 emp.)

**Validated Reviewer:** Validated through LinkedIn

**Source: Organic:** Organic review. This review was written entirely without invitation or incentive from G2, a seller, or an affiliate.

**Reviewed Date:** July 29, 2026

**What do you like best about Gatling?**

Its really good tool for load testing tool i actually use it for my old legacy app and it really helped me to improve the app performance.

**What do you dislike about Gatling?**

It’s difficult for an end user to understand the UI, so it could be improved in that area to make it clearer and easier to use.

**What problems is Gatling solving and how is that benefiting you?**

We were struggling with performance issues in our app. Since the app was live and a legacy application, we were dealing with production issues on a daily basis. To address all of that, we decided to go with Gatling.

  ### 43. Efficient Performance Testing Made Easy

**Rating:** 4.0/5.0 stars

**Reviewed by:** Huzaifa V. | Enterprise (> 1000 emp.)

**Validated Reviewer:** Validated through LinkedIn

**Source: Organic:** Organic review. This review was written entirely without invitation or incentive from G2, a seller, or an affiliate.

**Reviewed Date:** August 03, 2026

**What do you like best about Gatling?**

I like that Gatling made performance testing easy for my Kotlin backend application. It helped us achieve our tier1 project's SLA and identify crucial breaking points under stress testing. The tool's ease of use and the powerful in-built functionalities fit my use case perfectly. I appreciate how exceptionally it works to test systems in bottleneck traffic. Also, the initial setup was very easy and understandable.

**What do you dislike about Gatling?**

Nothing

**What problems is Gatling solving and how is that benefiting you?**

I use Gatling for stress testing, identifying application breaking points, with its ease of use and powerful functionalities helping us handle bottleneck traffic.

  ### 44. Gatling’s Fluent, Readable Test Scripting Is a Joy to Use

**Rating:** 4.0/5.0 stars

**Reviewed by:** Jakub D. | Principal Architect, Small-Business (50 or fewer emp.)

**Current User:** The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user.

**Validated Reviewer:** Validated through LinkedIn

**Source: Organic:** Organic review. This review was written entirely without invitation or incentive from G2, a seller, or an affiliate.

**Reviewed Date:** March 31, 2026

**What do you like best about Gatling?**

Gatling’s biggest strength, in my experience, is the developer experience when building test scripts. A lot of effort has clearly gone into the fluent style of writing tests, and even though the scenarios are written as code, they remain easy for humans to read and understand.

**What do you dislike about Gatling?**

There’s a lack of automatic correlation detection for test scripts, which makes the process more manual than it needs to be.

**What problems is Gatling solving and how is that benefiting you?**

I’ve integrated Gatling into my resilience testing framework, using Kafka along with other messaging protocols. Gatling’s core is highly efficient in terms of memory and overall resource management, which makes it a powerhouse load-testing platform and a strong foundation for expanding support across additional protocols.

**Official Response from Diego Salinas:**

> Thank you so much for the review, Kuba! 

We’re really glad the scripting experience feels clear and readable. That developer experience has always mattered a lot to us.

We also appreciate the feedback on automatic correlation detection. Reducing manual work in script creation is a valuable point, and it’s helpful to hear where the workflow can be smoother.

Thanks again for sharing how you’re using Gatling in resilience testing and messaging-based systems.

  ### 45. Intuitive with Strong Community Support, but Documentation Needs Improvement

**Rating:** 5.0/5.0 stars

**Reviewed by:** Marijana R. | Quality Assurance Engineer, Information Technology and Services, Mid-Market (51-1000 emp.)

**Validated Reviewer:** Validated through LinkedIn

**Source: Organic:** Organic review. This review was written entirely without invitation or incentive from G2, a seller, or an affiliate.

**Reviewed Date:** April 25, 2023

At G2, we prefer fresh reviews and we like to follow up with reviewers. They may not have updated their review text, but have updated their review.

**What do you like best about Gatling?**

I use Gatling for testing in both my previous and current company, and I really like their support. The switch from using Scala to TypeScript for writing tests has been a positive experience for me. The DSL (domain-specific language) that Gatling has is very intuitive, making it easy to use. I appreciate that it's easy to use, especially compared to tools like JMeter, and I like that you have something more tangible in the code form. The fact that developers can easily jump in and manage changes since it's code-based is great. I find the syntax clear, and the reporting feature is very user-friendly, providing a history of load tests that is quite helpful. The support for languages and clear syntax makes writing tests easier, even for people who might have never coded before. I also find the reporting crucial for quickly getting the information I need and spotting bottlenecks or slow requests at a glance. The feature that allows comparisons between different runs is something I appreciate very much. Additionally, the community support is great. I also recommended Gatling at my current company because I liked it. Setup is now easier thanks to moving from Scala to Java and TypeScript support, which I think helps in facilitating the setup. There's also a recording tool that can get you started quickly. I really like Gatling, think it's a great tool, and appreciate the great support from the community.

**What do you dislike about Gatling?**

I think maybe their documentation could be a bit more. It is good, but I think it could be improved. Sometimes, you get confusing information that might not be suitable for your case. I think that could be improved. Before, in my previous company, when I used their reporting, I had some bugs in terms of a layout break. If I have a long endpoint written, then the layout would break and basically make the report not useful to me. So I have to make workarounds there.

**What problems is Gatling solving and how is that benefiting you?**

Gatling is easier to use than tools like JMeter with its clear code form. It supports versioning and lets developers control changes. Its reporting is user-friendly, providing fast insights and helping spot bottlenecks quickly.

  ### 46. Simple to Use for Real user Journey Test Design

**Rating:** 5.0/5.0 stars

**Reviewed by:** Paul C. | Release / Quality Specialist, Mid-Market (51-1000 emp.)

**Validated Reviewer:** Validated through LinkedIn

**Source: Organic:** Organic review. This review was written entirely without invitation or incentive from G2, a seller, or an affiliate.

**Reviewed Date:** September 20, 2026

**What do you like best about Gatling?**

It’s simple to use, and it lets me design tests that follow a real user journey.

**What do you dislike about Gatling?**

Some features are only available in the Enterprise version, while others are genuinely interesting and useful.

**What problems is Gatling solving and how is that benefiting you?**

I’m able to design tests at both large and small scales, and the architecture lets me adapt quickly in either direction.

  ### 47. Rich Data Generators and Powerful Simulation Run Management

**Rating:** 5.0/5.0 stars

**Reviewed by:** Verified User in Computer Software | Mid-Market (51-1000 emp.)

This reviewer's identity has been verified by our review moderation team. They have asked not to show their 
name, job title, or picture.


**Current User:** The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user.

**Validated Reviewer:** Validated through LinkedIn

**Source: Organic:** Organic review. This review was written entirely without invitation or incentive from G2, a seller, or an affiliate.

**Reviewed Date:** April 28, 2026

**What do you like best about Gatling?**

I like the flexibility I get in implementing data generators (feeders). This allows for representative and sufficiently random data that ultimately gives meaningful performance test results.
I also like the simulation run management and history offered by the enterprise product which lets non-engineers to access and use the results directly.
The technical documentation is an ever-evolving artifact but in its current state it is useful and well structured and helps newcomers create effective simulations, not just "hello world" versions.

**What do you dislike about Gatling?**

Some of our integrations (e.g. with Github workflows) are brittle, although I should add that they are improving both the integrations themselves and the relevant documentation.

**What problems is Gatling solving and how is that benefiting you?**

Infrastructure management (minimum viable configuration)
Infrastructure budget projections
Identification of throughput bottlenecks
SLO monitoring
Performance regression

**Official Response from Diego Salinas:**

> Thank you so much for the thoughtful review.

It’s great to hear Gatling is helping your team create more realistic tests, share results more easily, and keep performance work connected to real engineering goals.

We also appreciate your honest note on integrations. CI/CD reliability really matters, and feedback like this helps us keep improving both the product and the documentation.

Thanks again for taking the time to share your experience with Gatling.

  ### 48. Efficient Load Testing with Comprehensive Reports

**Rating:** 5.0/5.0 stars

**Reviewed by:** Yeshwanth V. | Senior Quality Assurance Engineer

**Validated Reviewer:** Validated through LinkedIn

**Source: Organic:** Organic review. This review was written entirely without invitation or incentive from G2, a seller, or an affiliate.

**Reviewed Date:** August 14, 2026

**What do you like best about Gatling?**

Its Async and non blocking architecture make it possible to simulate thousands of concurrent users effectively also reporting capabilities

**What do you dislike about Gatling?**

Some Advance features may require additional time to understand and configure the framework

**What problems is Gatling solving and how is that benefiting you?**

I use Gatling for performance and load testing. It efficiently simulates thousands of users with minimal resources, offers excellent, detailed reports, supports concurrency, and is developer-friendly with easy CI/CD integration.

  ### 49. Gatling Makes CI/CD Performance Testing Easy and Maintainable

**Rating:** 4.0/5.0 stars

**Reviewed by:** Swapnil D. | Automation Engineer, Small-Business (50 or fewer emp.)

**Validated Reviewer:** Validated through a business email account

**Source: Organic:** Organic review. This review was written entirely without invitation or incentive from G2, a seller, or an affiliate.

**Reviewed Date:** August 12, 2026

**What do you like best about Gatling?**

Gatling’s code-based approach makes it easy to create, maintain, and integrate performance tests into CI/CD pipelines.

**What do you dislike about Gatling?**

The initial learning curve can be a bit steep, especially for teams new to code-based performance testing.

**What problems is Gatling solving and how is that benefiting you?**

Gatling helps us automate performance and load testing, identify bottlenecks early, and integrate performance checks into CI/CD, improving release confidence and reducing production performance risks.

  ### 50. Easy, User-Friendly, and Works Great Even Without an IDE

**Rating:** 5.0/5.0 stars

**Reviewed by:** Sarulatha R. | Senior System Engineer, Small-Business (50 or fewer emp.)

**Validated Reviewer:** Validated through LinkedIn

**Source: Organic:** Organic review. This review was written entirely without invitation or incentive from G2, a seller, or an affiliate.

**Reviewed Date:** August 28, 2026

**What do you like best about Gatling?**

It is very easy to use and user-friendly. It can be used even without an IDE, which makes it convenient and accessible.

**What do you dislike about Gatling?**

Nothing to add. It works great and does exactly what I need it to do.

**What problems is Gatling solving and how is that benefiting you?**

It helps me measure my application’s performance at the API level.


## Gatling Discussions
  - [Is Gatling better than JMeter?](https://www.g2.com/discussions/is-gatling-better-than-jmeter) - 1 comment, 4 upvotes
  - [What are the protocols supported by Gatling?](https://www.g2.com/discussions/what-are-the-protocols-supported-by-gatling) - 1 comment

- [View Gatling pricing details and edition comparison](https://www.g2.com/products/gatling/reviews?section=pricing&secure%5Bexpires_at%5D=2026-09-26+01%3A06%3A17+-0500&secure%5Bsession_id%5D=ee10b151-6bab-4a39-9809-312467867448&secure%5Btoken%5D=a1c9d9459cbfa76442cfba7076037aca98301b6b17e9f28fb3372cb915be2cd2&format=llm_user)

## Gatling Features
**Functionality**
- Stress Testing
- Extreme Cases
- Test Variety
- Web Testing
- Regression Testing
- Mobile Testing
- Cloud Load Testing
- UI Testing
- Cross Browser Testing
- Parallel Testing
- Performance Testing

**Functionality**
- Test Repository
- Integration
- Test Diversity

**Functionality **
- Test Feedback
- Test History
- Customization
- Test Variety

**Agentic AI - Software Testing**
- Autonomous Task Execution
- Natural Language Interaction
- Proactive Assistance

**Reporting**
- Reporting
- Uptime Reporting
- Web Traffic Reporting
- Real-Time Reporting

**Management**
- Reporting
- Version Control
- Scaling

**Automation**
- Organization
- Reliability
- Thoroughness

**Additional Functionality**
- API
- Third-Party Integrations
- Secure Data Storage
- Configuration Management
- Trend Analysis
- Real-Time Monitoring
- Reporting/Analytics
- Forecasting
- Data Extraction
- Real-Time Analytics
- Reporting & Statistics
- Engagement Tracking
- Data Synchronization
- Activity Tracking
- Productivity Analysis
- Browser Performance Metrics
- User Management
- Real-Time Data
- Data Transformation
- Performance Management
- Data Import/Export
- Server Monitoring
- Bottleneck Identification
- Alerts/Notifications
- AI Copilot
- Performance Metrics
- Visual Analytics
- Activity Dashboard
- Status Tracking
- Monitoring
- Charting
- Data Storage Management
- Testing Management
- Software Testing Management
- Remote Monitoring & Management
- Testing Scripts
- Generative AI
- Rules-Based Workflow
- Assessment Management
- Scheduling
- Drag & Drop
- Data Visualization
- Website Analytics
- Load Scenarios
- Multiple Data Sources
- Benchmarking
- Debugging
- Predictive Analytics
- Bug Tracking
- Test Performance Metrics
- Issue Tracking
- Desktop/Application Virtualization
- Issue Management
- Continuous Integration

**Additional Functionality**
- Commenting/Notes
- Approval Workflow
- Drag & Drop
- Task Management
- Generative AI
- Test Case Management
- Quality Assurance
- Risk Management
- Access Controls/Permissions
- Testing Scripts
- Templates
- Customizable Fields
- Data Import/Export
- Collaboration Tools
- Audit Trail
- Issue Tracking
- Automated Testing
- Traceability
- Prioritization
- Alerts/Notifications
- Single Sign On
- Milestone Tracking
- Activity Dashboard
- AI Copilot
- Reporting/Analytics
- Repository Management
- Multiple Test Types
- Requirements Management
- Parameterized Testing
- Test Run Tracking
- Defect Tracking
- Screen Capture

**Agentic AI - Automation Testing**
- Autonomous Task Execution
- Natural Language Interaction
- Proactive Assistance
- Supports Parallel Execution

**Additional Functionality**
- Assessment Management
- Reporting & Statistics
- Security Testing
- Parameterized Testing
- Data Visualization
- Data Import/Export
- AI Copilot
- API
- Unicode Compliance
- Monitoring
- Performance Management
- Real-Time Reporting
- Issue Tracking
- Performance Testing
- Bug Tracking
- Compliance Management
- Move & Copy
- Requirements Management
- Hierarchical View
- User Management
- Software Testing Management
- Model-Based Testing
- Activity Dashboard
- Issue Management
- Quality Assurance
- Version Control
- Activity Tracking
- Data Extraction
- Static Analysis
- Requirements-Based Testing
- Real-Time Monitoring
- Customizable Reports
- A/B Testing
- Alerts/Notifications
- Action-Word Testing
- Test Script Reviews
- Data Storage Management
- Workflow Management
- Generative AI
- Collaboration Tools
- Drag & Drop

## Top Gatling Alternatives
  - [Apache JMeter](https://www.g2.com/products/apache-jmeter/reviews) - 4.3/5.0 (151 reviews)
  - [BrowserStack](https://www.g2.com/products/browserstack/reviews) - 4.4/5.0 (3,324 reviews)
  - [Postman](https://www.g2.com/products/postman/reviews) - 4.6/5.0 (1,755 reviews)