# Flood

> Flood is a commercial, vendor-hosted cloud load testing service from Flood IO, scripted in Java, Scala. It is discontinued.

- Canonical: https://perf.jmeter.ai/tools/flood/
- Official: https://www.flood.io/

- Vendor: Flood IO
- Category: Cloud Load Testing
- License: Commercial — Historical commercial service; current availability requires vendor confirmation.
- Deployment: Cloud
- Status: Discontinued (successor: Tricentis NeoLoad)
- Scripting: Java, Scala
- Protocols: HTTP, HTTPS
- OS support: Browser
- First released: Not recorded
- Latest release: "Flood Element 2.0" ("")
- Last verified: 2026-08-15

## What it is
Flood was a hosted platform for distributed performance testing with open-source engines. The original Flood service is no longer presented as an independently active product; verify migration options before use.

## Choose it when
- Teams that want managed load generation without operating injectors
- Organizations budgeting for commercial licenses or subscriptions
- Groups comfortable scripting in Java, Scala

## Look elsewhere when
- New greenfield programs (prefer an active successor or alternative)
- Strictly air-gapped environments with no approved cloud path
- Projects that require a fully free open-source stack only

## Architecture
Flood runs as a cloud service: scenarios use Java, Scala, while generators and orchestration are vendor-managed.

## Pricing
Flood offers free and paid subscription plans, with consumption-based pricing calculated using Virtual User Hours (VUH).

## Compare
- [Flood alternatives](https://perf.jmeter.ai/alternatives/flood/)

## FAQ
### Who is Flood for?
Flood is best for teams that want managed load generation without operating generators themselves. It is commercial software, typically licensed for larger or governed programs. Vendor: Flood IO. Deployment model: cloud. Historical commercial service; current availability requires vendor confirmation. Confirm details against the official site and a short proof-of-concept in your environment.

### How does Flood differ from Apica?
Compared with Apica, scripting centers on Java, Scala rather than JavaScript. Flood lists protocols HTTP, HTTPS; Apica lists HTTP, HTTPS, REST. Status is discontinued versus active. Use the Test Rig to compare full specs side by side before a proof-of-concept.

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

### What is the cloud or enterprise path for Flood?
Flood is cloud-hosted: you run tests on vendor-managed infrastructure without operating load generators yourself. That usually speeds ramp-up for distributed load while shifting capacity planning and data residency to the vendor. Pricing model: Historical commercial service; current availability requires vendor confirmation.

### What are known limitations of Flood?
Flood appears as discontinued in this directory. Prefer Tricentis NeoLoad or another active alternative for new work. Historical references remain so older docs and diagrams still resolve. Verify any remaining commercial support directly with the vendor before depending on it.

---
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