G
G
Guides
Go to Dashboard
Search…
G
G
Guides
Getting started with Flood
Overview of Flood
Scripting and Tools
Choosing a tool
Test Builder
JMeter
Gatling
Flood Element
Selenium
Default tool versions
Test data
Accessing the file system
Saving custom results
Custom libraries
Supported SSL ciphers
Infrastructure
Infrastructure overview
Demand infrastructure
Host Your Own infrastructure
Standalone Infrastructure: Flood Agent
Flood's network topology
Grid management
How to get the IP address of your grid node
Static IP addresses
Test Execution
Infrastructure
Test parameters
Advanced parameters
Environment variables
Baselining
Using the Flood API
Overriding DNS
Planning for a large-scale test
Troubleshooting: Test Execution
Results Analysis
Metrics during test
Flood options
Service Level Objectives
Archived Results
Sharing results
CSV Results
Insights
Troubleshooting: Results Analysis
Continuous Integration
Continuous Integration with Flood
Travis CI
Circle CI
Jenkins
APM Tools
Account Management
Managing account members
Managing account resources
Single Sign On (SSO)
Reset your password
Troubleshooting: Account Management
Pricing
How much does it cost?
What is a VUH?
Billing page
Usage page
Pricing FAQ
Why don't I see a VUH estimate?
Minimizing costs on Flood
Tosca
Using Tosca with Flood
Ebooks
API Load Testing: A Beginner's Guide
Powered By GitBook
Infrastructure overview
At Flood, we believe you should be able to run your load tests from anywhere, so we provide a few different options for using Flood to scale up your testing.
First, you'll need to decide whether you need to run your tests from the cloud or from your on-premise infrastructure. Then, follow the links below to find out more options.
As long as you have a subscription with Flood, you'll be able to make use of any or all of these options.
Nicole explains the different options for running floods

On the cloud

Load testing on the cloud means that we will be starting virtual machines for you to run your scripts from using one of our cloud providers, either AWS or Azure.

Option 1: Demand infrastructure

This is the easiest way to get started, because they require the least set up from your end. Floods on team plans are executed from our own AWS account, but all of that happens in the background. All you'll need to do is run floods from the Flood UI and we'll take care of the rest.

Option 2: Host Your Own infrastructure

This is a step up in complexity from Option 1. Option 2 allows you to run floods using your own cloud accounts, whether that's with AWS or Azure. You'll need to integrate Flood with AWS or Azure and allow Flood to start virtual machines on those accounts on your behalf.

On-premise

Option 3: On-premise

To generate load using infrastructure you already have on-premise or in a data center, you can use Flood Agent. Flood Agent allows Flood to start load tests using machines that you specify.

Frequently Asked Questions

Should I run on the cloud or on-premise?

Good question! We've gone through this in more detail in this article.

I don't know which one to choose!

Here's a summary to help you decide.
If you want the least amount of set up: Option 1 - Cloud: Demand If you already have an AWS/ Azure account: Option 2 - Cloud: Host Your Own If your company already has load generators or a data centre: Option 3 - On-Premise

How much does each option cost?

You can check out the pricing for our plans on our Pricing page and our pricing help articles.
Flood Agent (on-premise testing) is currently available for free for anyone with a Flood subscription.
​ ​
Scripting and Tools - Previous
Supported SSL ciphers
Next - Infrastructure
Demand infrastructure
Last modified 1yr ago
Copy link
Contents
On the cloud
Option 1: Demand infrastructure
Option 2: Host Your Own infrastructure
On-premise
Option 3: On-premise
Frequently Asked Questions
Should I run on the cloud or on-premise?
I don't know which one to choose!
How much does each option cost?