# Gatling vs Tsung

> Gatling is an open source, self-hosted load testing tool from Gatling Corp., scripted in Java, Scala, Kotlin. Tsung is an open source, self-hosted protocol and API load tool from Tsung community, scripted in Erlang, XML. The practical split is the authoring language: Java, Scala, Kotlin for Gatling, Erlang, XML for Tsung.

- Canonical: https://perf.jmeter.ai/vs/gatling-vs-tsung/
- Compared: [Gatling](https://perf.jmeter.ai/tools/gatling/) · [Tsung](https://perf.jmeter.ai/tools/tsung/)

## Verdict
Both cover HTTP, HTTPS. Recorded protocol coverage is the same width on both sides (5 protocols), so breadth is not the deciding factor here. Team language and existing tooling usually settle Gatling against Tsung. Run the same scenario on both before you standardize; the rows below only tell you what is true on paper.

## Specs
| Field | Gatling | Tsung |
| --- | --- | --- |
| Vendor | Gatling Corp. | Tsung community |
| Category | Load Testing | Protocol/API Load |
| License | Open Source | Open Source |
| Deployment | Self-hosted | Self-hosted |
| Status | Active | Active |
| First released | 2012 | 2001 |
| Pricing | Free open-source core; commercial platform available. | Free; GPL-2.0 license. |
| Scripting | Java, Scala, Kotlin | Erlang, XML |
| Protocols | HTTP, HTTPS, WebSocket, SSE, JMS | HTTP, HTTPS, WebDAV, LDAP, XMPP |
| OS support | Windows, macOS, Linux | Linux, macOS |

## How to choose
- Only Gatling records support for WebSocket, SSE, JMS — one hard requirement there decides the pair on its own.
- Only Tsung records support for WebDAV, LDAP, XMPP — one hard requirement there decides the pair on its own.
- Match the authoring language to the team: Gatling means Java, Scala, Kotlin, Tsung means Erlang, XML.
- Open the Test Rig to compare license, deployment, protocol and OS rows side by side.

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