ArmA 3 RCON Tool & Admin Panel
CFTools Cloud is an ArmA 3 RCon admin tool for communities that already run an ArmA 3 dedicated server. People also search for it as an Arma 3 RCon tool or an ARMA 3 admin tool. It connects over BattlEye RCon and provides live monitoring, searchable logs, permanent global player profiles with GUID variant handling and Steam lookup, ban sharing, and granular staff roles that do not require handing out the RCON password. Paid plans retain logs for 30 to 180 days. CFTools Architect and GameLabs are not available for ArmA 3.
No credit card required. A free tier is available.
Admin tool highlights
BattlEye RCon for mission servers
ArmA 3 servers often sit idle between operations and then fill for a session. Cloud stays connected over BattlEye RCon the whole time, so staff see who joined, what the server reported, and whether the process is still answering.
Player history across sessions
ArmA 3 players return under new names. Permanent profiles, GUID variant handling, and Steam lookup give moderators a record that outlives a single play session on Altis, Tanoa, or a custom terrain.
Ban lists for public communities
Share an ArmA 3 ban list across your own servers, or join community-wide ban sharing. Whitelist tools sit next to bans when a unit server should stay closed.
Staff roles for Zeus and infantry admins
A mission maker and a ban admin do not need the same access, and neither needs the BattlEye RCON password. Granular roles keep the password with the server owner.
Restarts, messages, and triggers
Schedule restarts and in-game messages around operation times. Triggers can react to events, and name and chat filters cut down on the noise staff would otherwise handle by hand.
Discord alerts and a REST API
Forward selected ArmA 3 events to Discord. Use the REST API when a unit website or bot should read Cloud data. Paid plans keep logs for 30 to 180 days.
How ArmA 3 remote admin works
You keep running the dedicated server wherever it already lives. CFTools Cloud connects over BattlEye RCon from an edge region close to that host. Staff then use the web dashboard for players, bans, logs, and audit history. The server does not have to be joined in-game to kick, ban, or read what RCon reported.
What ArmA 3 does not include
CFTools Architect does not deploy ArmA 3, and GameLabs is DayZ-only. Queue-priority synchronization is a DayZ feature and does not apply here. Live admin depends on BattlEye RCon being enabled and reachable. If a host blocks the RCon port, Cloud cannot see the server.
What staff can do from the dashboard
Typical ArmA 3 work is watching a live slot list during an evening operation, checking whether a player was banned on another server in the same community, posting a restart warning, and reviewing the audit log afterward. VPN detection and geoblocking are optional modules on the same connection.
What an ArmA 3 server needs
Cloud manages an ArmA 3 server you already operate. It does not install the dedicated server for you.
- An ArmA 3 dedicated server reachable on the internet
- BattlEye RCon enabled and correctly configured
- Firewall access for the RCon port
- A CFTools Cloud account to register the server
CFTools Cloud features for ArmA 3
- 24/7 real-time server monitoring
- VAC protection and automated Steam player rules
- VPN detection
- Geoblocking
- Schedule automatic jobs like restarts
- Trigger automatic actions based on specific events
- In-Game commands
- Automated messages for your players
- Player management and history
- Automatically ID to SteamID conversion
- Whitelist management
- Banlist management
- Banlist sharing
- Discord integration
- API access
- Server logs & RCon logs
- Audit logs
- Statistics tracking
- Global player database with over 6,5 million records
- Statistic analysis for automated player risk ratings
- Name filters against unwanted nicknames
- Chat filters
- Localization - Customize to your local language