---
title: Register services
description: Add each service with its checker, pin both image digests, and publish the source teams receive.
---

A service in an attack/defence event is a pair: the **service image** every team's box runs, and the **checker image** that tests it each tick. Teams receive the service and its source, never the checker.

Register every service before you reserve the host. The host pulls exactly the image digests that are recorded when it is allocated, and a box has no route to your registry once the game starts.

## Register a service

Open **Services** in the event dashboard and click **Register a service**.

| Field | What to enter |
|---|---|
| **Name** | Shown to players on the scoreboard and on their box page. Up to 64 characters. |
| **Slug** | Lowercase letters, digits and hyphens, up to 32 characters. It identifies the service in attack info and in flag IDs. |
| **Description** | Optional, up to 4,000 characters. |
| **Service image** | A tag or digest reference, for example `registry.example.com/org/notes-api:1.2.0`. |
| **Checker image** | Your checker, as a tag or digest reference. |
| **Ports** | Up to 8 port and protocol pairs (`tcp` or `udp`). Each pair appears once, and no service may publish port 22. Every enabled service runs in the same box, so no two enabled services may publish the same pair; `tcp/8080` and `udp/8080` are different pairs. |
| **Flag stores** | 1 to 8. Each store is checked and scored separately. |
| **Checker timeout** | **Event default**, or at least 5 seconds for a service that needs its own. |

When you click **Register service**, Athena resolves both references against your registry and records the manifest digest each one points to. A tag is resolved once: pushing a new image under the same tag changes nothing until you record digests again.

### Private registries

If either image is in a private registry, fill in the pull credentials. The password is stored encrypted and delivered only to your event's host so it can pull the images; teams never see it. Leave the fields empty for a public registry.

To change images or credentials later, open the service and choose **Record digests**. Leaving the credentials empty there clears any stored ones, unless you tick **Keep the stored registry credentials**. With that ticked, both new references, tags or digests, are checked against your registry using the credentials already stored for the service, so you can move a private service to a new tag without typing the password again. If the registry refuses them, nothing changes and the error asks you to enter replacement credentials instead.

## Label flag stores

Each store starts unlabelled and shows as **Store 1**, **Store 2** and so on. Give a store a label, such as `notes` or `profile bio`, so players can tell which part of the service lost a flag.

## Publish the source

Click **Attach source archive** on the service and upload an archive of up to 512 MiB. Teams can download it from their **Downloads** page once the network opens.

## Enable, disable and reorder

A disabled service is out of play and the host doesn't run it. **Position** controls the order services appear in on the scoreboard.

A disabled service may hold a port and protocol pair another service publishes. Registering a service, enabling one, or changing an enabled service's ports is refused while another enabled service publishes one of the same pairs; the error names that service and the pair. Change the ports or disable the other service first.

## When services stop changing

Once the host is allocated, it runs exactly the services, images, ports and flag stores it was built with, so those stop changing:

- **After the host is allocated**, registering, deleting, enabling or disabling a service, recording new digests, and changing ports or checker timeouts are refused. To change any of them before the network opens, [replace the host](/organizers/attack-defence/how-to/lock-the-roster-and-reserve-the-host#replace-the-host): the service list reopens until the replacement is reserved.
- **Once the network has opened**, or the game has ended, none of them can change for the rest of the event.

The name, description, store labels, position and source archive stay editable throughout. If someone else saved the service while you were editing it, your save is refused rather than overwriting theirs; reopen the service and make the change again.

The same operations are available from the command line under `athena ad service`; see [athena ad commands](/organizers/attack-defence/reference/cli-commands).
