Redcloud is a powerful and user-friendly toolbox for deploying a fully featured Red Team Infrastructure using Docker. Harness the cloud's speed for your tools. Deploys in minutes. Use and manage it with its polished web interface.

Self-host your attack infrastructure painlessly, deploy your very own live, scalable and resilient offensive infrastructure in a matter of minutes.


The following demo showcases deployment of Redcloud through ssh, followed by Metasploit. We then look at Traefik and a live volume attached to Metasploit. Finally, we check that Metasploit's DB is functional with the web terminal, delete the container, and terminate Redcloud.


  • Deploy Redcloud locally or remotely using the built-in SSH functions, and even docker-machine.
  • Deploy Metasploit, Empire, GoPhish, vulnerable targets, a fully stacked Kali, and many more with a few clicks.
  • Monitor and manage your infrastructure with a beautiful web interface.
  • Deploy redirections, socks or Tor proxy for all your tools.
  • Painless network management and volume sharing.
  • User and password management.
  • Web terminal
  • Overall very comfy :hatching_chick:

Quick Start


# If deploying using ssh
> cat ~/.ssh/ | ssh root@your-deploy-target-ip 'cat >> .ssh/authorized_keys'

# If deploying using docker-machine, and using a machine named "default"
> eval (docker-machine env default)

# Check your Python version
# Use python3 if default python version is 2.x
> python --version


> git clone
> cd redcloud
> python

Redcloud uses PyYAML to print the list of available templates. It's installed by default on most systems.
If not, simply run:

# Use pip3 if default python version is 2.x
> pip install -r requirements.txt

Redcloud has 3 different deployment methods:

  1. Locally
  2. Remotely, using ssh. Requires having your public key in your target's authorized_keys file.
  3. Remotely, using docker-machine. Run the eval (docker-machine env deploy_target) line to preload your env with your docker-machine, and run Redcloud should automatically detect your docker-machine, and highlight menu items relevant to a docker-machine deployment.


Briefly, deploys a Portainer stack, preloaded with many tool templates for your offensive engagements, powered by Docker. Once deployed, control Redcloud with the web interface. Uses Traefik as reverse-proxy. Easy remote deploy to your target server using the system ssh or docker-machine.

  • :rocket: Ever wanted to spin up a Kali in a cloud with just a few clicks?
  • :package: Have clean silos between your tools, technics and stages?
  • :ambulance: Monitor the health of your scans and C2?
  • :fire: Skip those sysadmin tasks for setting up a phishing campaign and get pwning faster?
  • :smiling_imp: Curious how you would build the ideal attack infrastructure?

Use the web UI to monitor, manage, and interact with each container. Use the snappy web terminal just as you would with yours. Create volumes, networks and port forwards using Portainer's simple UI.

Deploy and handle all your favorite tools and technics with the power of data-center-grade internet :rocket:

In the following section, we'll be going more in-depth inside Redcloud's design concepts. You can get started without having to dive inside though.


Redcloud Architecture

  • Starts/Stops the Web interface and App Templates, using Docker and Portainer.
  • portainer: Portainer web interface.
  • traefik: Traefik reverse-proxy container to the web interface, api and files containers. Some templates have pre-configured routes for convenience. See the templates.yml.
  • templates: python3 http.server container that feeds the App Templates. Lives in an "inside" network.
  • cert_gen: The omgwtfssl container that generates the SSL certificates using common best practices.
  • https://your-server-ip/portainer: Redcloud Web interface once deployed.
  • https://your-server-ip/files: Redcloud redcloud_files volume. You can also access the redcloud_log container content, protected by the same .htpasswd as Traefik. Default credentials: admin:Redcloud
  • https://your-server-ip/api: Traefik reverse-proxy health monitoring page. Shows live stats about routes, backends, return codes. Will also show reverse-callback implant data if configured through Traefik.

Deployment workflow

Redcloud deployment workflow is as follows:

  1. Clone/Download Redcloud repository.
  2. Launch
  3. Choose deployment candidate from the menu (local, ssh, docker-machine).
  4. automatically:
    • checks for docker & docker-compose on target machine.
    • installs docker & docker-compose if absent.
    • deploys the web stack on target using docker-compose.
  5. Once deployment is complete, will output the URL. Head over to https://your-deploy-machine-ip/portainer.
  6. Set username/password from the web interface.
  7. Select the endpoint (the only one on the list).
  8. Access the templates using the "App Templates" menu item on the left :rocket:

App Template deployment is as follows:

  1. Choose template.
  2. If you wish to add additional options, select "+ Show advanced options".
  3. Add port mapping, networking options, and volume mapping as you see fit.
  4. Select "Deploy the container".
  5. Portainer will launch the container. It may take a few minutes if it needs to fetch the image. If your server is in a data center, this step will be very fast.
  6. Container should be running :rocket:
  7. Portainer will redirect you to the "Containers" page. From there, you can:
    a. View live container logs.
    b. Inspect container details (docker inspect).
    c. View live container stats (memory/cpu/network/processes).
    d. Use a web shell to interact with your container.
    e. Depending on the App Template, use either bash or sh. Choose accordingly from the drop-down menu.


Redcloud makes it easy to play around with networks and containers.
You can create additional networks with different drivers, and attach your containers as you see fit. Redcloud comes with 2 networks, redcloud_default and redcloud_inside.


You can share data between containers by sharing volumes. Redcloud comes with 3 volumes:

  • certs: Container with the certificates generated by omgwtfssl.
  • files: Standard file sharing volume. For now, the files are available when browsing https://your-server-ip/files, and are served by the Traefik reverse-proxy container directly from the files volume. A typical use-case is to attach the volume to a Metasploit container, generate your payload directly into the files volume. You can now serve your fresh payload directly through the Traefik to file server route.
  • logs: Available for logs, served by the file-server too. Access requires basic auth. Default is admin:Redcloud.

Accessing containers from the terminal

If you wish to stay in your terminal to work with the deployed containers, its very easy using Docker. Keep these things in mind:

  • Most containers have bash, but some use sh instead
  • All Redcloud App Templates container names start with red_, such as red_msf-postgresql
  • With Docker, you can either use docker exec or attach to interact with a container
    • exec is preferred as it creates a new process
    • attach lands you straight on the running process, potentially killing your running container
  • If running Redcloud:
    • Locally or using docker-machine, simply type these in your local shell
    • Using ssh, first ssh into your deployment target to run the following commands

To start interacting with the desired deployed container:

> docker exec -it red_container-name /bin/bash

If you see the following message, it means bash is not installed. In that case simply replace /bin/bash with /bin/sh:

> docker exec -it red_container-name /bin/bash
OCI runtime exec failed: exec failed: container_linux.go:344: starting container process caused "exec: \"/bin/bash\": stat /bin/bash: no such file or directory": unknown

> docker exec -it red_container-name /bin/sh

To use docker attach, simply run:

> docker attach red_container-name

If using attach, the container needs to be started in interactive mode, so as to land in a interactive shell.

Accessing files

Point your browser to https://your-redcloud-ip/files.
Please refer to the files volume for more information.

SSL Certificates

Redcloud generates a new unsigned SSL certificate when deploying.
The certificate is generated by omgwtfssl, implementing most best practices.
Once generated:

It will dump the certificates it generated into /certs by default and will also output them to stdout in a standard YAML form, making them easy to consume in Ansible or other tools that use YAML.

Certificates are stored in a shared docker volume called certs. Your containers can access this volume if you indicate it in "+ Advanced Settings" when deploying it. The Traefik reverse-proxy container fetches the certificates directly from its configuration file. If you wish to replace these certificates with your own, simply replace them on this volume.

It also means you can share the generated certificates into other containers, such Empire or Metasploit for your reverse callbacks, or for a phishing campaign.
Most SSL related configurations can be found in traefik/traefik.toml or the docker-compose.yml file.

Stopping Redcloud

You can stop Redcloud directly from the menu.
Deployed App templates need to be stopped manually before stopping Redcloud. You can stop them using the Portainer web interface, or docker rm -f container-name.
If you wish to force the Portainer containers running Redcloud to stop, simply run docker-compose kill inside the redcloud/ folder.
The local and docker-machine stop option is the same, thus they are combined in the same option.

Portainer App Templates

Redcloud uses Portainer to orchestrate and interface with the Docker engine. Portainer in itself is a fantastic project to manage Docker deployments remotely. Portainer also includes a very convenient template system, which is the major component for our Redcloud deployment.
Templates can be found in ./templates/templates.yml. Portainer fetches the template file from a dedicated container (templates).

Traefik reverse-proxy

Traefik is a wonderful "cloud-native edge router". It has replaced the previous NGINX reverse-proxy setup.
A Traefik image is built during deployment, using the Dockerfile located in traefik/Dockerfile. It adds a .htpasswd with admin:Redcloud credentials.

By default, deployment spawns the following routes:

  • https://your-server-ip/portainer
  • https://your-server-ip/files
  • https://your-server-ip/api

Authentications are based of the .htaccess data.

From the Traefik api web interface, you can view your deployed routes, monitor health, as well as real time metrics. Its very neat.

You can add additional labels that tell Traefik where to route traffic, using either:

  • traefik/traefik.toml file
  • docker-compose.yml file
  • templates.yml file
  • Portainer's web interface

See the official documentation for more information.


Redcloud security considerations

Redcloud deploys with a self-signed https certificate, and proxies all interactions with the web console through it.
However, the default network exposes your containers' ports to the outside world.

You can:

  • Remove exposed ports and access the normal port from a machine inside the docker network
  • Add custom labels to create routes with Traefik. See the docker-compose.yml file for inspiration.
  • Start an Ubuntu or Kali with noVNC (VNC through http) from templates, add it to both an "inside" and "outside" network, and access exposed interfaces from inside.
  • Add .htaccess configurations


  • docker & docker-machine installations require root privileges. You can downgrade privilege requirements following the official documentation.
  • The install script is pulled directly from the official docker repositories.
  • fetches Redcloud's public IP address using

Tested deployment candidates

Deploy Target Status
Ubuntu Bionic ✔️
Ubuntu Xenial ✔️
Debian Strech ✔️


  • Check your default python version with python --version. Redcloud needs python 3+.
  • Use python3 instead of python if on an older system.
  • requires that deployment candidate have the public key in their .ssh/authorized_keys, and handles password-less authentication using the user's public key. This is the default configuration for most VPS workflows.
  • docker-machine deployment requires the user to already have a running docker-machine on a cloud infrastructure (such as AWS, GCP, Linode and many others). Once deployed, simply run the eval command as illustrated above.
  • docker & docker-machine installations require root privileges. You can downgrade privilege requirements following the official documentation
  • If you don't see the "App Templates" menu item right after deploying, refresh the web page and make sure you're not at the endpoint selection menu.
  • If you wish to create a new username/password combo, remove Portainer persistent data on deployment candidate: rm -rf /opt/portainer/data
  • If you're running into python errors, you may need to install the python3-distutils package using apt-get install python3-distutils on debian/ubuntu base.
  • If you get an error when deploying an App Template saying the "container name already exists", it's probably because you're trying to deploy the same App Template without having removed a previously deployed one. Simply remove the old container with the same name, or change the name of your new container.
  • If something seems wrong with your container, the standard procedure is to check the container's logs from the web interface.
  • If running a local deployment on OSX, portainer will be unable to use its default volume location /opt/. To solve this, open the docker-compose.yml file, replace /opt/portainer/data:/data with a folder with write-access, for example: /tmp/portainer/:/data and create the /tmp/portainer directory before running Redcloud.
  • if you're getting issues with the web terminal, try disabling some addons, using private browsing, or try with a different browser. If all else fails, connect to your container through the terminal.


  • Create your personal pentest-lab, and practice your hacking skills with friends and colleagues.
  • Protect your offensive infrastructure using honeypots.
  • Recreate an APT infrastructure with reverse implant load-balancing, geo-stretched servers and multi-layered operations
  • Automate payload generation with Metasploit or Empire, AV bypass with gscript, served instantly through the /files/ URI.
  • Perform your bug-bounty pipelines much faster than your competition.
    • Launch Sniper using Portainer api when a new bug-bounty is posted, fetch logs using /files/ URI.
  • Use the reverse proxy to cover Metasploit or Empire.
  • Launch scans behind your own Tor socks proxy.
  • View .onion site using Tor socks + Ubuntu VNC.
  • Advanced OSINT with Spiderfoot and a Tor container as proxy.


  • Template List

  • Deploying a container

  • Using Metasploit's msfconsole through the web interface

  • Traefik real-time data on reverse-proxy routes

  • Deploying using ssh

Download RedCloud

Automated Red Team Infrastructure deployement using Docker - khast3x/Redcloud