Why BrowserUp?

BrowserUp offers a fresh approach to load testing.

See our manifesto for more about why we think this is the right approach to load testing.

How is it different?

BrowserUp is a DRY (Don’t Repeat Yourself) Load Testing Tool

BrowserUp uses your code, libraries, page objects, binaries, and PostMan definitions for load tests. Why maintain two implementations of “how to talk to your app” when you can maintain one?

Don’t Repeat Yourself!

BrowserUp uses the cloud to “scale the thing that makes the requests.” With traditional load testing, you scale a script that makes requests that are kinda like the real ones, or at least kinda like how the real thing worked at the moment you hard-code it.

Those tools force you to maintain a second implementation of your request-logic for API’s, or page-walking logic for UI tests within their language, UI or IDE.

BrowserUp uses assets you already have, so you can test earlier in the release cycle and shift your load testing left.

  • BrowserUp stays out of your way–work in your repo, in your IDE, in your language of choice
  • Built-in multi-region cloud run capability
  • Your data stays in your EC2 account


  • BrowserUp runs your code in our “magic” traffic-capturing containers. This means logic and condition-handling code just works
  • BrowserUp containerizes your stuff (automatically) and scale containers running your code to generate load
  • BrowserUp captures the traffic and provides rich reporting

You might be thinking “what scripting language do I use to create the script?” The answer is: anything you like that drives traffic!

Java and Selenium?


Your PostMan script?

Python script?

Ruby Script?

Some binary or command-line app you compiled yourself?

Any other thing, yes, probably!

…So do I have to worry about containers now?

Probably not! BrowserUp has a standard container with Java, Javascript, Ruby, Python, Bash, Postman and Curl and some other things ready to go. It has Chromium installed and ready for each of these languages. This image is the browserup/standard image and you get it, plus your assets by default. It should just work, and you won’t need to consider about containers.

If your needs are off the beaten path, the browserup/custom-base container option gives you an escape valve where you can install more or less anything you want to drive load.