Stop Sharing RCON Passwords
Invite your admin team with proper roles and permissions. Everyone gets their own login. Every action is attributed. No more shared credentials.
4 Built-in Roles
Owner (full control), Admin (manage members and settings), Operator (start/stop servers, RCON, player management), and Viewer (read-only). Each role has clear, limited permissions.
Email Invitations
Invite team members by email. They create their account, accept the invitation, and join your team with the role you assigned. Manage pending invites and resend if needed.
Full Audit Trail
Every action — RCON commands, config changes, plugin installs, wipes — is logged with the user who performed it. Know exactly who did what and when.
Permissions that make sense
An Operator can start and stop servers, execute RCON commands, and manage players — but can't change server settings, modify team membership, or delete instances. A Viewer can see dashboards and metrics but can't take any actions. Permissions match real-world admin team structures.
Shared server templates
Save a server's complete configuration — settings, plugins, schedules, permission groups — as a template that any team member can use to spin up new servers. Standardize your server setup across your community without manual configuration.
Cross-server coordination
All servers in a team share the same ban lists, player notes, and automation history. When an admin bans a player on one server, the ban syncs across the entire team. Player notes written by one admin are visible to everyone.
Multi-team support
Users can belong to multiple teams. Run different communities or game server networks under separate team workspaces, each with their own members, servers, and configuration — all from one account.