Everything in this sub-section applies to running the PurpleTeam CLI (purpleteam) configured for the cloud environment. (AKA BinaryMist PurpleTeam)

PurpleTeam cloud Architecture

The following diagram shows how the PurpleTeam components communicate. In the cloud environment all you need to be concerned with is the PurpleTeam CLI and of course making sure your System Under Test (SUT) is listening, in a clean state, and reachable from the Cloud:

cloud architecture
Cloud Architecture (click to enlarge)

Your System Under Test (SUT)

Make sure the Web application or API (SUT) that you wish to target is up and responding to requests.

If your SUT is not yet ready, an option may be to use what the PurpleTeam-Labs development team uses for their SUTs (purpleteam-iac-sut). PurpleTeam-Labs use purpleteam-iac-sut for both local and cloud testing.

PurpleTeam (CLI)

Details on installing the PurpleTeam CLI, configuring and running can be found here

Once you have the CLI running and if you want or need to debug it, details can be found here.

Release Strategies

Customers can choose one of the following release cycle cadences to be on:

  • dev - Latest and greatest (bleeding edge)
    • When we make updates to the CLI, the customer needs to update the CLI before their next Test Run
    • Only source code is pushed to Github, new releases of the CLI are not guaranteed to be published to NPM
  • 2w - Stay on your version for at least two weeks. This approach allows you to plan for your updates. There may or may not be a release on the specified date, we will let you know if we are planning on creating a release near the end of the previous week
    • CLI source is released (tagged) and published to NPM if changes have been made
    • CLI resources (, Job file if updated) is published to your customer specific file share that PurpleTeam-Labs provides you

New Zealand dates:

Release Cadence 25 Jan 08 Feb 22 Feb 08 Mar 22 Mar 05 Apr 19 Apr
(2w) Fortnightly