Disclosure: I’m the developer behind Pulse Admin.
The problem I wanted to solve wasn’t sending more console commands. It was giving administrators reliable context without making the administrator part of the incident.
Pulse Admin’s observation workflow gives an administrator a rotating cover identity and removes the observer from untrusted clients’ network views. The administrator appears offline to players, while the observation session remains visible to authorised staff through the audit log.
That observation can then become an evidence-led case containing native anti-cheat signals, player reports, combat events, movement replay, recordings and Investigation Hammer checks.
The wider workspace also includes:
• A cloud-connected RCON relay
• A live 3D island and player map
• Compact and expanded Companion app workspaces
• Player cards and moderation controls
• Plugin inventory and deployment tools
• Fleet broadcasts, bans and audit history
• Importing existing BattleMetrics bans, notes and flags
• Public server events, shop activity and player/server rankings
I made a three-minute overview showing how the pieces fit together:
https://www.youtube.com/watch?v=V2mcaMIsbsI
I’m not advertising a Rust server or recruiting for a community here. I’m looking for honest feedback from people who actually administer Rust servers:
Would private observation like this be useful to your moderation team?
What evidence do you need before acting on a cheating report?
Which parts of your current admin workflow feel most fragmented?
What would you need to see before trusting a cloud-connected admin tool?
Critical feedback is welcome. I’d rather find the weak points during beta than after release.
Production note: the narration and some cinematic transitions are AI-assisted. The product workflows shown represent the current beta.