---
title: Host your first CTF
description: Create an account and take a small event from sign-up to a live player-facing site.
---

In this tutorial you'll create an organizer account, set up a small event on the free plan, watch the platform build it, and open the finished player-facing site. No prior setup is needed. By the end, you'll have a live event URL you can share with players.

:::warning[A few choices are locked at creation]
Most of the form can be changed later from the event's **Settings** page, but a few choices can't: the **slug**, **flag prefix**, **event size**, **team mode**, the **email-verification requirement**, your **sign-in (OAuth)** providers, and the **retry cooldown**. Decide those before you submit. See [Event settings](/organizers/reference/event-settings) for the full breakdown of what's locked versus editable.
:::

1. **Create your account**

    Open the control panel at [app.athena-ctf.com](https://app.athena-ctf.com)
    and go to the sign-up page. You can **Continue with Google** or **Continue
    with GitHub**, or sign up with email by filling in your name, email, and a
    password (at least 8 characters).

    If you sign up with email, Athena sends you a verification link. Open it
    before signing in, or the login page will ask you to verify first.

    Your personal workspace is created for you automatically, and you start on
    the free **Hobby** plan. You'll land on the dashboard, which shows
    **No events yet. Create your first event to get started.**

2. **Start a new event**

    Click **Create Event** on the dashboard. This opens the **Create a new
    event** form.

3. **Name and schedule the event**

    Under **Basic details**:

    - **Event Name**: 3–32 characters, for example `November 2025 CTF`. As
      you type, Athena auto-fills the slug and flag prefix from the name; both
      stay editable.
    - **Start date (UTC)** and **Start hour (UTC)**: everything on Athena
      runs on UTC, and the hour picker makes that explicit (`18:00 UTC`). The
      default is the next full hour. The start time must be in the future.
    - **Duration (in hours)**: how long play lasts; the default is 48 hours,
      and the maximum is 720 hours (30 days).
    - **Wind-down (in hours)**: how long the event stays up after the freeze;
      the default is 24 hours, and the range is 1 to 72 hours.

    Below the schedule, a live preview shows when the event will **Freeze**
    and **End**. Play runs from the start until the freeze (start + duration).
    The event then stays up for the wind-down you chose before ending. After
    the freeze, submissions close and players use that window for feedback and
    writeups.

4. **Pick a slug and flag prefix**

    - **Slug**: the short identifier your event's web address is built from.
      It must be 3–32 characters of lowercase letters, digits, and dashes. As
      you type, an indicator at the end of the field shows whether the slug is
      available: a spinner while checking, a green check when it's free, a red
      X when it's taken. If it's taken, a **Try:** row offers clickable
      alternatives, and you can't submit until you pick an available slug.
    - **Flag format prefix**: the wrapper for every flag in your event, up to
      8 letters or numbers. A live sample shows the resulting format, for
      example `athena{s0me_s3cr3t_fl4g}`.

5. **Choose an event size**

    **Event size** determines your event's capacity and storage. The dropdown
    only lists sizes your plan includes. On the free Hobby plan, that's
    **Extra Small** and **Small**.

    :::note
    Extra Small events are for static challenges only: no container
    challenges. If you plan to follow the [container challenge
    tutorial](/organizers/tutorials/run-a-container-challenge) with this
    event, pick **Small**.
    :::

    Below the size, an **Estimated credit hold** panel shows what creating
    the event will reserve from your wallet: the hours of play at the size's
    hold rate (quoted per 24 hours and prorated to your duration), the
    wind-down after the freeze at the same rate, the wait between creating the
    event and its start at half that rate, and your current balance. If the balance can't cover it, the panel says how much
    more you need and **Create event** stays disabled until you top up.

    **Enable team mode** sits just below, still under **Basic details**, and
    is off by default, so players compete individually. Turn it on to have
    players create and join teams, optionally with a **Max team size**. Like
    the size and slug, team mode is fixed once the event exists.

6. **Review the remaining sections**

    The rest of the form is fine on its defaults for a first event:

    - **Branding** and **Marketing**: landing-page copy, logo, theme, prize
      pool, and footer links. You can leave the defaults for now and refine
      them later in **Settings**.
    - **Rules &amp; FAQ**: a rich-text rules editor and an FAQ list shown to
      players. Fine to leave empty for a first event; you can author both
      anytime in **Settings**.
    - **Integrations**: the Discord integration toggle. Turn it on to let
      players link their Discord account and to run the Athena bot on your
      server; connect the server itself from the event overview afterwards.
    - **Sign-in**: email verification (on by default) and optional Google,
      GitHub, and CTFtime sign-in for players. Remember these are
      create-time choices, so decide how players will sign in before you
      submit.
    - **Limits**: the **Retry cooldown (minutes)** between a team's
      challenge-instance deployment attempts, plus the wrong-flag
      submission throttle.

7. **Create the event**

    Click **Create event**. The button stays disabled until the name is
    valid, the slug is confirmed available, and your wallet balance covers
    the estimated credit hold from the previous step.

    One more limit can stop you here: the Hobby plan allows one running event
    at a time: *"You have reached your plan limit for concurrent events."*
    And if your balance changes between filling the form and submitting,
    you'll see *"Not enough wallet credits to create this event. Add credits
    and try again."* with an **Add credits** shortcut to your usage page.

8. **Watch the setup**

    After submitting you land on the event's setup page, badged **Setting
    up**, with a **Setup progress** checklist, an elapsed timer, and a
    **Technical log** streaming the detail.

    You don't have to sit and watch it. The page says so: *"Setup continues
    without keeping this page open."* Close the tab and come back whenever
    you like.

    Two things are worth knowing about the checklist. It runs from *Request
    received* and *Preparing setup* through to *Finished*, but not every step
    reports progress as it happens, so rows can sit unticked while work is
    genuinely happening behind them. The elapsed timer is the better signal
    that things are moving. And if nothing reports for a few minutes you'll
    see *"Setup is taking longer than usual. Athena is still receiving
    updates."*, which is a nudge rather than
    an error.

    Setup is done when the status badge turns green and reads **Complete**,
    and you're moved into the event workspace automatically.

    If it shows **Failed** instead, the credits reserved at creation are
    released back to your wallet. The event stays in your events list as a
    **Failed** record until you delete it, which you can do from that list.
    Contact support if setup keeps failing.

9. **Open your event**

    Head back to the dashboard. Your event's row now shows **Upcoming**
    (it flips to a green **Live** once the start time arrives), and its
    **Player site** column has an **Open** link. On the event's overview
    page you'll find the same address under **Event URL** with an **Open
    event** button.

    That's your live, player-facing site. Share the URL with players and
    they can register, form teams (if you enabled team mode), and wait for
    the countdown to your start time.

## Next steps

Your event site is live, but it has no challenges yet. Continue with
[Publish your first challenge](/organizers/tutorials/publish-your-first-challenge)
to give your players something to solve.
