Getting started
Nothing is installed on the game server: no plugin, no mod, no wrapper. Aquilon reaches it over RCON and, for history, reads its log over SFTP.
1. Sign in with Discord
Sign in is Discord, because that is where Squad communities already are. Your admins keep the roles you give them in Aquilon, whatever their Discord roles say. Create an organisation — one per community, however many servers it runs.
2. Add a server
New server in the rail. Give it a name, the RCON host and port, and the RCON password. Aquilon stores the password encrypted, write-only from the browser, and tests the connection at once: within a few seconds the live roster is on screen.
3. Add SFTP for history
Under the server's Setup, rotate credentials and add SFTP: host, port, user, password and the path to SquadGame.log. From then on matches, kills, connections and sessions are read from the log, and Insights fills in.
If your host gives you no SFTP, or no RCON from outside, run the self-hosted node on the box instead: it tails the log locally and dials out to Aquilon, and it replaces SFTP entirely.
4. Invite your admins
Settings → Members & roles. Invite by email or by link, pick a role — Admin, Moderator, Viewer or your own — and the same live view opens for them with exactly the actions their role allows. Every action they take lands in the audit log with their name on it.
What to set up next
- Automod — start the teamkill chain in dry-run, watch what it would do for a day, then let it act.
- Reserved slots — turn seeding into a reward that grants itself. How it works →
- Discord — pair the bot and route a server's status card and alerts to your channels. Discord bot →
- Broadcasts — seeding rules while the server fills, event reminders when it is live.
- Ban network — share your ban list with communities you trust, and receive theirs.