A whole crew. One bot.

Moderation, support, roles, automation, and recovery in one dashboard your staff can read.

Axon dashboard with example data showing server health and modules
Server dashboard · example data

One server dashboard

Versioned settings

Discord-aware permissions

Restart-safe jobs

Pick a job. Axon has a specialist.

Each character maps to work Axon handles today, with permission checks and recovery guidance kept close to the action.

Available now

Moderation and cases

Warn, timeout, kick, or ban while Axon keeps reasons, evidence, staff notes, reversals, and member history together.

Axon dressed as a ninja for moderation work
Tickets shipped

Tickets and staff support

Open private support spaces, claim requests, manage participants, keep transcripts, and recover ticket records after Discord changes.

Axon working at a support desk
Available now

Welcome, roles, and onboarding

Greet new members, assign safe starting roles, and publish button or select menus without handing out roles Axon cannot manage.

Axon dressed as a pirate with a parrot for community roles
Available now

AutoMod and protection

Build message rules, test matches, contain raids, and keep a recovery route when Discord refuses an action.

Axon dressed as a wizard for AutoMod and protection rules
Available now

Schedules and events

Schedule messages, log server events, and run giveaways or birthdays with saved recovery state.

Axon dressed as a scientist for scheduled and event-driven work
Available now

Configuration and recovery

Draft settings, publish a revision, inspect what changed, and restore an earlier version without rebuilding the module.

Axon in a hard hat holding tools for configuration work
Axon carrying the configuration and audit record

One record behind every costume.

The crew shares authorization, configuration history, audit records, and recovery behavior. Staff do not have to piece the story together across bot websites.

Permissions checked against Discord

Axon checks the staff member, its own role, and Discord hierarchy before sensitive work.

Every publish keeps its history

Revisions record who changed a setting, when it changed, and what the bot received.

Failed work keeps a recovery path

Queues, leases, retries, and receipts let staff recover work without guessing what Discord accepted.

Commands and dashboard share one record

Discord actions and dashboard changes land in the same redacted audit history.

Axon waving

Bring the crew into one test server.

Invite Axon, run the setup check, and choose the modules your staff needs.

Invite Axon