Keelah Arma Server Tool (KAST)

---

Badges

GitHub

CI / Quality

Docker

INTRO

After developing FASTER for a few years, I decided to restart the whole project to make a new Architecture from a clean slate. This new Architecture should allow contributors to better participate in the project development.

Big up to all the devs, testers and users. Also, to BI for giving us an awesome game to break.

PREREQUISITES

• Steam account with valid copy of Arma 3.
• Basic understanding of Arma 3 dedicated servers.

FEATURES

• Steam Workshop Integration

  • Install and update Arma 3 Server (Stable, Dev, DLCs, Legacy)
  • Install, update and manage Arma 3 Workshop mods
  • Import Local Mods
  • Supports Steam Guard and Mobile Auth
  • Import mod presets from Arma 3 Launcher
  • Check for mod updates on app launch

• Multiple Server Profiles

  • Save and load multiple server presets
  • Supports all server config options
  • Supports all server command line options
  • Custom mission params
  • Custom difficulty
  • Headless Client support and auto launch
  • Correctly displays mods in Server Browser
  • Load Steam Mod Presets (html presets) to your profiles
  • Manually editable config files

• Local Mod Support

  • Reads local mods from server folder
  • Include additional folders to search

ISSUES and FEEDBACK

As always, best place to report issues is on the GitHub Repo. As for general discussion I'll keep an eye on the BI forum thread but I'll be more active on Discord.

DOCUMENTATION

A complete Documentation is available on the GitHub Wiki

INSTALLATION

KAST is distributed as a self-contained single-file executable — no .NET installation required on the host.

Stable releases

Download the latest release for your platform from the Releases page:

Platform	Archive
Linux x64	kast-linux-x64-v*.tar.gz
Linux arm64	kast-linux-arm64-v*.tar.gz
Windows x64	kast-win-x64-v*.zip
Docker	ghcr.io/foxlider/kast:latest

Extract and run the KAST.UI executable. On Linux you may need to chmod +x KAST.UI first.

Nightly builds

Automated builds from the develop branch are published as a rolling pre-release at
releases/tag/nightly.

The nightly tag always points to the latest development commit. Download URLs are stable:

Platform	File
Linux x64	kast-linux-x64-nightly.tar.gz
Linux arm64	kast-linux-arm64-nightly.tar.gz
Windows x64	kast-win-x64-nightly.zip
Docker	ghcr.io/foxlider/kast:nightly

Nightly builds may be unstable. Use tagged releases for production.

Docker (Compose)

Create a docker-compose.yml file:

services:
  kast:
    image: ghcr.io/foxlider/kast:latest
    ports:
      - "5000:5000"                # KAST Web UI + API (TCP)
      - "2302-2322:2302-2322/udp"  # Arma instance UDP blocks (game + Steam + BattlEye traffic)
      # Optional: BattlEye RCon (UDP). Use a dedicated port configured in BEServer_x64.cfg.
      # - "23150:23150/udp"
    volumes:
      - kast-data:/app/data
      - kast-mods:/app/mods
      - kast-servers:/app/servers
    restart: unless-stopped

volumes:
  kast-data:
  kast-mods:
  kast-servers:

Start KAST and open http://localhost:5000:

docker compose up -d

Arma 3 ports

• Use UDP for Arma ports.
• Publish one UDP range for game instances, for example 2302-2322/udp.
• Each server instance uses 5 consecutive UDP ports.
• BattlEye RCon also uses UDP, but on its own RConPort from BEServer_x64.cfg.
• RConPort must be different from the game instance ports.

Per-instance UDP block (base port n):

Port	Used for
n	Game traffic
n+1	Steam query
n+2	Steam traffic
n+3	Voice over network (VoN)
n+4	BattlEye traffic

Example with default range 2302-2322/udp:

Server	Base port	Reserved UDP ports
1	2302	2302-2306
2	2307	2307-2311
3	2312	2312-2316
4	2317	2317-2321

2322 is unused in this example.

If you need remote RCon, publish the dedicated RCon UDP port separately (example: 23150:23150/udp) and set the same value in BEServer_x64.cfg.

Port 5000/tcp also serves KAST's management API. Do not expose it directly to the public internet; restrict it with a firewall, VPN, or authenticated reverse proxy.

VERSIONING

KAST uses MinVer to derive the version from git tags at build time.

Scenario	Version format
Tagged release v1.2.3	1.2.3
Nightly (develop)	1.2.3-nightly.20260522.abc1234
Local dev build	1.2.3-alpha.0.5

To create a release, push a tag matching v* (e.g. git tag v1.2.3 && git push --tags).
The CI pipeline will run tests, build native binaries for all platforms, push the Docker image, and publish a GitHub Release with all assets attached.