Vortex is a Java-based Discord moderation bot, licensed under Apache-2.0, that pairs a moderation and logging suite with an auto-moderator so server staff can track members, keep moderators accountable, and filter certain types of behaviour without constant human intervention.
What it is
Vortex is a Discord bot written in Java and built on JDA, the Java Discord API, with the source published on GitHub under the Apache-2.0 licence. It lives in the Discord bot ecosystem and is designed to keep a server safe and its staff team organised. Two systems do most of that work: a moderation and logging suite that tracks members and keeps moderators accountable, and an auto-moderator that acts on certain types of behaviour automatically. The project documents itself primarily through its wiki, which covers an about page, a getting started guide, a moderator guide, strikes, auto-moderation, Vortex Pro, a full command reference, and troubleshooting.
The concrete problem it solves is the staffing cost of running a busy Discord community. Without tooling, moderators handle every incident by hand, leave no consistent record of who did what, and cannot easily show that a decision was justified. Vortex replaces that ad-hoc, human-only workflow: logging turns moderation actions into a record, strikes give repeated offences a place to accumulate, and the auto-moderator absorbs filterable behaviour so staff attention goes to cases that actually need a human. The README frames this directly as lightening the load on the staff team while keeping moderators accountable for what they do.
Key capabilities
- A moderation suite with a documented Full Command Reference in the wiki.
- A logging suite that keeps track of members and keeps moderators accountable, reflected in the
logging and logs topics.
- Auto-moderator capabilities that filter out certain types of behaviour without human intervention, tagged with
auto-moderation, automod, auto-moderator, and automoderator.
- A strikes system, documented on its own Strikes wiki page, for tracking repeated offences.
- A Moderator Guide wiki page aimed at the staff who operate the bot day to day.
- Written in Java against JDA, the Java Discord API.
- A Vortex Pro tier documented in the wiki, alongside the open Apache-2.0 source.
- Placement in the Infrastructure & Operations / Monitoring & Observability category of this registry.
Who uses it and how
- Discord communities with a staff or moderator team that needs an audit trail of moderation actions, using the logging suite to hold moderators accountable.
- Servers where message volume makes manual review impractical, using the auto-moderator to filter behaviour before a human sees it.
- Moderators onboarding onto the bot through the Moderator Guide and the Full Command Reference rather than reading source.
- Server owners evaluating the Vortex Pro tier documented in the wiki alongside the free command set.
- Developers reading the source for transparency about how the primary features work, since the repository is published openly even though self-hosting is not supported.
Getting started
The documented path is the Getting Started page in the project wiki, together with adding the hosted bot, which is listed on discord.bots.gg under bot ID 240254129333731328. Self-hosting is explicitly not recommended and not supported, and the README states that no help will be provided for editing or compiling the code.
How it compares
The provided facts name no other moderation bots or comparable tools, so Vortex stands alone in this registry entry. No list of paid products it replaces is supplied, and the wiki's Vortex Pro page is referenced without terms, so no licence, hosting, or cost comparison can be drawn here.
When to use it — and when not to
Choose Vortex when a hosted Discord moderation bot is acceptable and the team wants logging, strikes, and auto-moderation without maintaining any infrastructure of its own. Do not choose it if a self-hosted, fully supported deployment is a requirement: the README states plainly that self-hosting is not recommended, that running a copy yourself is unsupported, and that no help will be given for editing or compiling the repository. The other caveat is documentation shape; the README itself is thin and largely points at the wiki, and the project carried 44 open issues at the last recorded push on 2025-11-13.
