---
title: How challenges reach players
description: Static challenges, container instances, and dynamic flags, and when to use each.
---

Athena delivers challenges to players in two forms: **static challenges**, which are pure content, and **container challenges**, which give each team a live target of its own. Understanding what players experience with each, and how dynamic flags fit in, helps you pick the right form for every challenge.

## Static challenges: content only

A static challenge is what players see on its page: the description, downloadable files, hints, and a flag input. Nothing runs anywhere: the "target" travels inside the files or the prompt itself, and the flag is the one string you typed into the editor. This suits crypto, forensics, reversing, OSINT, and any web-less puzzle, and it's the only form available on Extra Small events.

Because one flag is shared by everyone, static challenges rely on your event's rules to discourage flag sharing.

## Container challenges: a live target per team

A container challenge carries a runtime: one or more services built from your [challenge images](/organizers/how-to/build-challenge-images). Players get an instance card on the challenge page instead of just a flag box:

1. A player clicks **Create Instance**; the card shows the instance moving through *pending* and *provisioning* to *running* (or *failed*, with a **Try again** button).
2. Once running, the card shows one connection entry per exposed port: a clickable link for a web port, and for a TCP port a copyable `athena-proxy add <hostname>` line plus the hostname itself for players who drive a TLS client directly. When an instance exposes more than one port, every entry is labeled with its service name and container port.
3. The instance runs until its shown expiry time, or until the team terminates it. Expired or terminated instances offer **Redeploy Instance** for a fresh session.

Two rules shape the experience, and both are worth putting in your event's own rules or FAQ because the platform doesn't explain them in-app:

- **One active instance per team, across all challenges.** When a team starts an instance while another of theirs is running, even on a different challenge, the old one is stopped automatically to make room. Teams juggling two container challenges will see their other instance turn up *terminated*; that's this rule, not a failure.
- **Solved means done.** After a team solves a container challenge, it can no longer deploy or redeploy instances for it; the card says so in place of the button.

## Dynamic flags

Container challenges unlock **dynamic flags**: instead of one shared secret, the platform generates a distinct flag per team and injects it into that team's instance (via the reserved `FLAG` / `FLAG_FULL` environment variables). A team's flag is generated when it first launches an instance for the challenge and stays the same for that team across redeploys, for the whole event.

The point is integrity: a flag lifted from another team simply doesn't validate, which turns flag sharing from "undetectable" into "impossible" for these challenges. Players aren't told their flags are per-team, and the submission flow looks identical to a static challenge, so cross-team submissions just fail as incorrect.

Dynamic flags require a container runtime (the flag has to live somewhere), and the editor enforces exactly that; see the [challenge editor reference](/organizers/reference/challenge-editor).

## Why Extra Small events are static-only

Extra Small is the lightweight tier: it has no image builds, no build minutes, and no instance infrastructure, which is what keeps it free of instance-hour usage ([Usage, credits, and event sizes](/organizers/explanation/usage-and-credits)). No instances also means no dynamic flags: the editor offers static flags only. If your event needs even one container challenge, size it Small or larger from the start: event size is one of the choices [locked at creation](/organizers/reference/event-settings).

## Choosing a form

There are two forms to choose between, a static challenge or a container challenge (which always uses a dynamic flag: there is no static-flag container, since the runtime setup only appears once you pick **Dynamic**):

- **Static**: anything solvable from an artifact, such as files, ciphertexts, images, or binaries to reverse. Cheapest to run, zero moving parts during the event, and the flag is one shared string.
- **Container (dynamic flag)**: any challenge that needs a live target of its own per team, such as exploitation, attack-style web, or anything players connect to. Because the flag is per-team, one lifted from another team never validates. This is the default choice for pwn and attack-style web challenges.
