Why Arkanis

When your community outgrows the moderation-bot starter pack.

Generic moderation bots are fine when you have 50 members and a single staff role. They start hurting when your community grows past that. Staff turn over. Bans need to follow players across alts. Appeals need a paper trail. AutoMod actions need to feed something. Arkanis is built for that moment.

Section 01

Built for staff workflows, not isolated commands

Generic bots give you a command. Arkanis gives you a workflow.

  • Issuing a strike doesn't just log the strike. It updates the player's composite risk score, evaluates against your auto-ban threshold, surfaces the player on the Enforcement Board for senior review, and DMs the player with the reference ID and reason.
  • Closing a support case writes the transcript, archives the channel, fires the post-close DM, and saves the workspace so future appeals reuse it. Staff don't reconstruct context two months later.
  • An appeal isn't a separate ticket type sitting in a different bot. It's the same case workspace with the original enforcement action attached, and the deliberating staff sees the full history before they decide.
Section 02

One audit trail, not five

Stitch five bots together and you get five logs that disagree about what happened. Arkanis writes one timeline.

  • Every staff action lands in one audit log: strikes, bans, mutes, warnings, AutoMod hits, RCON commands, dashboard edits, API calls. Same schema, same timestamps, same actor attribution.
  • Filter by actor (everything one staff member did), target (everything that ever happened to one user), or action type (every ban issued this week). Export as CSV for compliance or legal review.
  • When an external API token or Claude Control runs an action, it shows up with the same actor schema as a human staff member, including which token, which scopes, and what was confirmed.
Section 03

Built to run from both Discord and the dashboard

Most "Discord platforms" make you live in the dashboard. Arkanis treats Discord as a first-class surface.

  • Most core staff workflows have a Discord panel equivalent. Strikes, cases, role panels, AutoMod toggles, identity verification: all of it works from buttons inside Discord. Setup, billing, and some admin surfaces stay dashboard-only.
  • Reply to a support case from the dashboard, the member sees it in Discord. Open a case in Discord, it appears in the Support Inbox in real time. The two surfaces stay in sync because they read the same database.
  • Staff who prefer Discord never have to log into the dashboard. Staff who prefer the dashboard never have to use Discord buttons. Either path works; the audit trail looks identical from either side.
Section 04

Built to be automated, not just operated

When your community gets large enough, governance becomes code. Arkanis Pro gives you the surfaces to write that code.

  • Scoped REST API tokens follow the same capability gates as the dashboard. A token mapped to a "moderation" role can issue strikes; it can't touch billing. Same trust boundary, programmatic access.
  • Issue strikes, query risk scores, manage cases, link identities, run RCON commands. All via REST. Every API action is audit-logged with the token name, scopes used, and (for dangerous actions) the sentinel confirmation.
  • Claude Control through the Arkanis MCP server (Pro Labs) means an LLM can do real governance work with the same trust boundary as a human staff member. Capability-gated, scoped, audit-attributed.
Section 05

Game-server depth, when you need it

Most platforms see Discord. Arkanis sees Discord and the server you run alongside it.

  • RCON commands, Pterodactyl and Pelican panel control, SFTP log streaming. Every action audited and capability-gated, just like Discord moderation.
  • Identity linking across Discord, Steam, Xbox, and Alderon. Bans follow the player, not the Discord account. An alt rejoining gets matched by Steam ID.
  • In-game events (kills, chat, admin commands) parsed and streamed into dedicated Discord channels in real time. The Isle Evrima and Path of Titans get structured parsing; everything else gets raw streaming.
Section 06

When you don't need Arkanis

Arkanis isn't the right tool for every Discord community. Honest about that.

  • You run a 50-member friend group with two admins. A generic moderation bot like MEE6 or Dyno is fine. Arkanis is overkill for that size and the audit-trail discipline is value you won't use.
  • You want music, leveling, mini-games, or economy features. Sapphire, MEE6, and most popular general-purpose bots are entertainment-first. Arkanis is governance-first; we don't ship those features and won't.
  • You only need basic word-filter AutoMod and nothing else. Discord's native AutoMod is free, fast, and excellent at exactly that. Use it directly; come back to Arkanis when you need actions on top of the detection.

Most communities that hit Arkanis-shaped needs realise it because something broke. A repeat-offender came back on an alt and nothing caught it. A staff member left and their decisions weren't documented. A case got lost between two ticket bots. If any of that sounds familiar, you've outgrown the starter pack.

Comparing to other bots?

Honest side-by-side, not a sales pitch.

We are upfront about where another bot is the better fit and where Arkanis is. Each page acknowledges the competitor's strengths and our own gaps.

Pilot Arkanis on the Free tier

Moderation, AutoMod, support cases, and identity linking work without Pro. Try the platform on Discord before deciding whether you need the Pro layer.