Know your controls.
Find your orbit.

Getting started

Start by connecting your account, then choose the server you want to manage.

1. Open My servers and sign in with Discord. Complete the Cloudflare check to continue to Discord.
2. Choose a server where you have owner, Administrator, or Manage Server access.
3. If Splash is missing, use Invite Splash. Review the Discord installation permissions before approving.
4. Keep Splash’s role above the roles it needs to manage. Discord role hierarchy still applies; a bot cannot moderate the server owner.
5. Open the server to view its verified identity. Use the separate sample dashboard to experiment with settings.

Anti Nuke

Anti Nuke is the policy for destructive administrator and bot activity. The sample editor groups rules into Channels, Roles, Members, and Integrations.

Open Protection and choose the Anti Nuke card. The master switch controls the module independently of its filters. Basic configuration offers grouped status and a default response; the category selector below opens channel, role, member and integration rules on the same page. Each rule has a mode, threshold, window and trigger action.

Example: Channel deletion at 3 actions within 60 seconds reaches the sample threshold on the third matching action. Use Try this filter to compare counts below and at the limit.

Quarantine is a proposed response in this preview. It does not remove a real member’s roles. Discord permissions, hierarchy, attribution, and runtime availability must be checked before live enforcement.

Anti Raid

Open Protection → Anti Raid. Join-wave rules look at sudden arrivals; account rules look at young accounts and default avatars. Set the minimum account age separately from the wave threshold.

Inspect each signal in context. A new account or default avatar does not by itself establish malicious intent. Start with Observe and tune thresholds against your community’s usual activity.

The sample response choices include requiring verification, locking down joins, quarantining, and alerting moderators. These choices do not execute Discord actions in this dashboard.

AutoMod & filter testing

Open Moderation and choose AutoMod. Its master switch locks or unlocks all dependent settings. Turning the module off retains its filters, thresholds and responses, and turning it on restores editing. The Status panel groups message, mention, and media filters. Auto Timeouts applies a response and duration across the sample filters; individual filter panels can override them.

1. Choose Balanced for default counts, Strict for lower counts, or Observe only to preview logging without a response.
2. Open a filter category. The floating selector switches between Text, Mentions, and Links & media.
3. Set the count and window, then choose a trigger action. Timeout durations apply only when Timeout member is selected.
4. Expand Try this filter and run a sample count. The simulator evaluates the count against that rule; it does not inspect real messages or run a heat algorithm.
5. Use Save changes to retain the sample settings in this browser, or Discard to restore the last saved version.

Drafts remain separate for each sample server and module. A failed browser save retains the draft for the current session.

Exceptions & logs

Use Exceptions & logs inside Protection or Moderation to enter sample member, role, or channel exclusions. Prefer specific exceptions over a global bypass. Store exact IDs or mentions, one per line.

AutoMod also has a blocked-term list. The sample alert channel is a routing preference only: no log messages are sent from this demonstration. The count simulator does not resolve Discord identities, exemptions, or term matches.

Verification & admin safeguards

Connected today: Cloudflare verification protects website sign-in and bot invitations. Its response is validated by the server before proceeding to Discord.

Planned: member-role verification and external administrator safeguards. The dashboard does not enroll passkeys, verify a Discord member, grant roles, or hold real moderation actions.

Completing the website’s Cloudflare check is not the same as verifying membership in a Discord server.

Backups & recovery

The Premium backup preview uses sample server structures. Try backup preview unlocks local sample snapshots, scope selection, JSON export, schedule preferences, and a restore simulation.

There is no live capture, scheduled job, or Discord restore. A sample JSON export is not a backup of your real server. Messages and real member-role assignments are not captured by this preview.

Plans & Premium

Core protection and AutoMod are part of the proposed Free feature set. Premium adds the proposed backup and admin-safeguard capabilities. Community Solution has the same Premium scope across three servers.

• Premium: one server. Current localized prices come from Paddle on the Premium page.
• Community Solution: three servers. Current localized prices come from Paddle on the Premium page.
• Enterprise: scope and pricing by arrangement.
• Custom Branding: optional paid add-on. Current localized price comes from Paddle on the Premium page.

Paddle determines the current amount and billing interval shown before checkout.

See the full comparison ↗

Availability & troubleshooting

What comes next

The reference review identified useful future work: coordinated incident scoring, decaying AutoMod heat, stronger permission and server-identity monitoring, verified member-role flows, and real backup recovery.

These need bot runtime support and validation before the website can offer them. Plan allocation is undecided for incident scoring and adaptive heat. No release date or purchase entitlement is promised.

The current design favors visible rule thresholds, per-rule simulations, explicit saves, and clear availability so admins can understand a configuration before applying it.