Your community, in focus.
A clear view of the players, matches and moments that matter.
A good night.
A community that stays.
IRONCLAD / EU 01 · London, Europe
96 / 100 players
A pulse on your community
Player population · last 7d
Leading the way
Ranked by kills in this period
Every match has a story
Open a report to explore the result and player scoreboard.
Make it feel like your community
Edit the fields to update your public-page preview instantly.
IRONCLAD / EU 01
Tactical warfare. Good company. A server worth coming back to.
An owner workspace, with clear boundaries
How access works in the current product
Provisioned server access
Owners can grant server admin and moderator accounts. Sessions use HTTP-only cookies, with secure cookies in production.
Server-scoped permissions
Each configuration change checks that the signed-in user has access to that server.
Protected credentials
RCON passwords are encrypted before storage and never appear on public pages or moderator forms.
Everything is flowing
The simulated game RCON listener is reachable. Live players, population, and observed round summaries are being recorded.
Test the unexpected
Choose a scenario to explore how connection health behaves.
Recent ingestion activity
A readable trail of accepted data and connection events
Population snapshot accepted · 96 players1 minutes ago · sample event
Observed round saved · unique local round ID2 minutes ago · sample event
RCON player list refreshed · authenticated request3 minutes ago · sample event
Connection details
A representative configuration, with no real credentials
- Connection
- Direct WARDOGS RCON
- Listener address
- http://192.0.2.10:7776 · example
- RCON password
- Demo placeholder · masked
- Read access
- Status and player list checked
- Moderation
- Server-scoped kick, ban and unban with audit history
What can flow into WarTrack?
Population & observed roundsDirect RCON polls record population, named faction scores and observed player totals. Polling history can be incomplete.
Live moderationAuthorized server moderators can kick, ban or unban players. Kick and ban reasons are sent to the game.
Individual kill eventsNo supported receiver is enabled. Weapon and headshot analysis remain concepts.
Tune the trade-off
Move the controls to see how retention changes the estimate.
Concept only. No individual kill-event receiver is enabled.
Know where the space goes
Projected year-one database footprint
- Match & participant summaries
- 61.22 MiB
- Recent population samples
- 0.12 MiB
- Hourly + daily aggregates
- 0.23 MiB
- Estimated index & row overhead
- 36.94 MiB
Warning begins at 70%. At 85%, optional raw-event writes are suspended by policy.
Watch retention do its job
Run an illustrative cleanup on an isolated sample backlog.
The scenario contains expired samples and hourly rows. Cleanup leaves durable summaries available.
Small footprint, clear limits
Expired rows are deleted in small batches to keep maintenance predictable.
PostgreSQL holds transactional data, summaries and job state.
This model excludes WAL, backups, images and container logs. Aggregate history still grows over time.
Your community, one command away
Try the four commands implemented by the optional WarTrack bot.
Switch off to try the bot’s setup-required response.
Your next conversation starter.
Select a command and run it to see the sample reply.
“Why did everyone leave?”
Investigate a drop without confusing correlation with cause.
Sample rotation moved from Ozeti to Bakurani.
A simultaneous decline may relate to the match ending, time of day, or other causes.
Use multiple matched time windows before drawing a conclusion about a map.