# Flood Element

> Flood Element is an open source, vendor-hosted browser and real-user monitoring tool from Flood, scripted in JavaScript, TypeScript.

- Canonical: https://perf.jmeter.ai/tools/flood-element/
- Official: https://flood-io.gitbook.io/flood-chrome
- Source: https://www.npmjs.com/package/@flood/element
- Vendor: Flood
- Category: Browser/RUM
- License: Open Source — Free source code; Flood cloud execution is priced separately.
- Deployment: Cloud
- Status: Active
- Scripting: JavaScript, TypeScript
- Protocols: HTTP, HTTPS, WebSocket
- OS support: Browser
- First released: 2018

- Last verified: 2026-08-12

## What it is
Flood Element let teams author browser-level load tests with a JavaScript and TypeScript API driving real Chrome instances, executed at scale through the Flood platform. The original GitHub repository is no longer available and the project is not actively maintained.

## Choose it when
- Browser/RUM scenarios across typical web and service stacks
- Teams that prefer open-source licensing and self-hosting options
- Groups comfortable scripting in JavaScript, TypeScript

## Look elsewhere when
- Strictly air-gapped environments with no approved cloud path

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

## Pricing
Free source code; Flood cloud execution is priced separately.

## Compare

## FAQ
### Who is Flood Element for?
Flood Element is best for teams validating real-browser or end-user experience under load. It is open source, so teams can self-host and extend it. Vendor: Flood. Deployment model: cloud. Free source code; Flood cloud execution is priced separately. Confirm details against the official site and a short proof-of-concept in your environment.

### How does Flood Element differ from Grafana k6 browser?
Compared with Grafana k6 browser, deployment is cloud versus hybrid for Grafana k6 browser. Flood Element lists protocols HTTP, HTTPS, WebSocket; Grafana k6 browser lists HTTP, HTTPS. Status is active 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 Element use?
Flood Element uses JavaScript, TypeScript for scripting or scenario definition. Runtime model: code-first scenarios where virtual users execute scripted behavior under load. OS support: Browser. Protocols: HTTP, HTTPS, WebSocket. 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 Element?
Flood Element 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. As open source, commercial support or hosted siblings may exist separately. Check the official site. Pricing note: Free source code; Flood cloud execution is priced separately.

### What are known limitations of Flood Element?
Flood Element limitations to weigh: cloud services trade operational simplicity for vendor pricing, data residency, and network path differences versus your production topology. Status: active. Always validate against your target protocols and scale with a proof-of-concept. Confirm details against the official site and a short proof-of-concept in your environment.

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