Documentation
Arkanis is a Discord governance platform for communities that need moderation, cases, identity, audit logs, and staff workflows in one place. Pick a lane below to get set up, learn the daily moderation workflow, or integrate with the REST API and MCP server.
Arkanis unifies moderation, cases, player identity, audit trails, and staff workflows into one platform managed from Discord and the web dashboard. If your community also runs game servers, Arkanis can connect those workflows to RCON, Pterodactyl / Pelican, and SFTP logs.
What is this?
A Discord bot plus web dashboard that gives moderation teams a single place to handle strikes, warnings, bans, AutoMod, cases, appeals, modmail, audit logs, and staff permissions. Optional power layer connects Discord workflows to game servers via RCON, Pterodactyl / Pelican, and SFTP log streaming for communities that need it. Replaces the patchwork of separate bots, spreadsheets, and manual processes most staff teams currently juggle.
Why you might want it
Sixty pages of docs is a catalog, not a journey. The three lanes below sequence the pages you actually need in order, so you don't have to guess what to read next. Pick the lane that matches your role today, then follow the "Next →" links on each page.
Pick your path
Setting up Arkanis
Invite the bot, run the setup wizard, and end up with a working Arkanis install in about 30 minutes.
Start here →Moderator daily work
The everyday loop: enforce rules, run AutoMod, handle cases and appeals, and check the audit log when something is off.
Open the playbook →Integrating with API / MCP
Programmatic access via the public REST API or the MCP server. Capability-scoped tokens, the same gates as the dashboard.
Start building →What Arkanis is
Arkanis is a Discord governance platform for communities that need moderation, cases, identity, audit logs, and staff workflows in one place. It is built around the way a real moderation team works, not the way a single bot command works.
Game-server operations are an optional power layer. Communities that run servers can connect their game server to Arkanis via RCON, Pterodactyl / Pelican, and SFTP log streaming, and tie strikes / bans / identity back to in-game actions. Communities that do not run game servers still get the full moderation, cases, identity, audit log, and staff permission stack.
Arkanis ships deeper ready-made integrations for The Isle Evrima and Path of Titans today (structured log parsing, game-specific workflows). Other games still get the core moderation platform plus generic Pterodactyl / Pelican control and SFTP log ingestion.
Everything is managed through two interfaces:
- Discord bot — slash commands, interactive panels, and automated moderation directly in your server.
- Web dashboard — full configuration, member and player management, enforcement tracking, audit logs, and server control from any browser.
What it solves
Strikes, warnings, bans, mutes, AutoMod rules, role panels, and a structured audit log. Issue actions from Discord or the dashboard; both surfaces show the same history, by actor, target, reason, and timestamp.
Case panels for support, bug reports, and ban appeals. Claim, comment, close, and transcript every case. Modmail starts a case from a member DM and keeps the conversation in the Support Inbox, so nothing gets lost in a moderator's personal DMs.
Optionally link Discord accounts to Steam, Xbox, and Alderon Games IDs where relevant. Look up any member or player across platforms. Capability-based staff roles with view-as-role preview so admins can audit who can do what.
Optional RCON, Pterodactyl / Pelican, and SFTP log integration for communities that run game servers. Staff can run game-side commands and read logs from Discord or the dashboard without sharing hosting credentials with the whole team.
Who it's for
Arkanis is a strong fit for:
- Discord communities with active moderation teams
- Servers that need cases, appeals, modmail, and transcripts
- Communities that need audit trails for staff actions
- Teams replacing several bots, spreadsheets, and manual notes
- Game-server communities that want Discord moderation connected to in-game identity or server operations
Typical teams range from solo admins running a single community to moderation teams of 10+ managing multiple Discord servers, multiple game servers, or both.
Arkanis has deeper built-in support for The Isle Evrima and Path of Titans today (game-specific log parsing and workflows). Other games still get the core moderation, cases, identity, dashboard, Pterodactyl / Pelican control, and SFTP log features.
Free and Pro
The free tier covers everything most communities need to get started:
- Member and player identity
- Strikes, warnings, and bans
- Cases and appeals
- Moderation panels and tools
- Audit logging
- Up to 3 AutoMod rules
- Member Portal (optional) — let your community members check their own strikes, cases, and linked accounts without asking staff.
Other entry points
Not in one of the three lanes? Pick the row that matches what you came to do.
How to design a support panel, configure case buttons, and route them to channels. Has presets for general support, bug reports, and ban appeals.
Roles and capabilities — what a moderator can do versus an admin versus a server owner. Includes view-as-role preview so admins can audit role assignments.
Member lookup, identity linking, and how cross-platform IDs (Steam, Alderon, Xbox) tie back to a single Discord user.
RCON, Pterodactyl / Pelican, and SFTP log integration. How the bot reaches your game server and what staff can do from Discord and the dashboard.
One-page glossary defining the terms you'll see across the docs and dashboard. Useful if a docs page assumes a vocabulary you haven't picked up yet.
How to read these docs
- Getting Started pages are minimal-path guides. They show you the fastest way to turn a feature on. They deliberately don't cover every option.
- Feature pages (Moderation, Enforcement, Cases, Members and Players, Infrastructure) cover every option, edge case, and configuration detail for one feature.
- Admin pages cover billing, roles and permissions, the audit log, and other server-wide settings.
- Developers pages target people building against the Arkanis API or MCP server, not server admins.
- Glossary defines the terms used across the platform. Skim it once and the rest of the docs will read smoother.
Docs are maintained in English. Dashboard and bot UI are also English-only today; the marketing site is localised across 11 languages.