Repolode
juice-shop

juice-shop/multi-juicer

Kubernetes-based platform that runs a separate OWASP Juice Shop instance per participant for security trainings and CTF events.

Stars
328
Forks
180
Open issues
13
Last commit
3 hours ago

What is it?

Running security trainings or Capture The Flag events with OWASP Juice Shop is awkward because Juice Shop is not designed for many users at once. MultiJuicer solves this by creating a separate Juice Shop instance for each participant on a central Kubernetes cluster, so attendees do not need to install anything locally.

All instances sit behind a single domain, with a custom load balancer routing each participant's traffic to their own instance. The platform also includes a leaderboard showing team progress, an admin page for managing instances, and backup of challenge progress so it is restored if a container restarts. Old and unused instances are cleaned up automatically.

Installation uses Helm, and the project provides guides for DigitalOcean, AWS, Azure, OpenShift and plain Kubernetes, along with customization options for theming and enabled challenges.

Key features

  • 01Creates a separate Juice Shop instance for each participant on demand.
  • 02Routes all instances through one domain via a custom load balancer.
  • 03Shows a leaderboard of participant progress.
  • 04Provides an admin page for managing instances.
  • 05Backs up and restores challenge progress after container restarts.
  • 06Automatically removes old and unused instances.

Use cases

  • Running a company security training where each developer gets their own vulnerable app.
  • Hosting a Capture The Flag event with many teams on a shared Kubernetes cluster.
  • Teaching web application security without asking participants to install Juice Shop locally.

Quick start

  1. 1

    Install Helm, the Kubernetes package manager, which the README requires

  2. 2

    Install MultiJuicer on your Kubernetes cluster with Helm

    helm install multi-juicer oci://ghcr.io/juice-shop/multi-juicer/helm/multi-juicer
  3. 3

    Review the production notes checklist before running real events

Things to know

  • Requires a running Kubernetes cluster, so it is not a simple local app.
  • Designed for running events with many participants, which needs cluster resources (about 1GB memory and 1 CPU overhead plus about 300MB and 0.2 CPU per team).

Topics

FAQ

What is multi-juicer?
Kubernetes-based platform that runs a separate OWASP Juice Shop instance per participant for security trainings and CTF events. Running security trainings or Capture The Flag events with OWASP Juice Shop is awkward because Juice Shop is not designed for many users at once. MultiJuicer solves this by creating a separate Juice Shop instance for each participant on a central Kubernetes cluster, so attendees do not need to install anything locally.
Is multi-juicer free to use? What license does it have?
multi-juicer is open source under the Apache-2.0 license. Check the license terms before using it in commercial products.
Is multi-juicer still maintained?
Actively maintained. The last commit to multi-juicer was on Oct 21, 2026.
What can I use multi-juicer for?
Running a company security training where each developer gets their own vulnerable app. Hosting a Capture The Flag event with many teams on a shared Kubernetes cluster. Teaching web application security without asking participants to install Juice Shop locally.
How do I install multi-juicer?
Install Helm, the Kubernetes package manager, which the README requires Install MultiJuicer on your Kubernetes cluster with Helm: helm install multi-juicer oci://ghcr.io/juice-shop/multi-juicer/helm/multi-juicer Review the production notes checklist before running real events
Where can I get multi-juicer?
The source code and installation instructions are on GitHub: https://github.com/juice-shop/multi-juicer

Summary generated by AI from the project's README. GitHub stats refresh daily.

Related projects