Skip to main content
About the bot
Venon is an operational platform for your server, not another bot
Security, the team's workflow, community growth and the web panel tied into one system with one identity — so the server stays protected, orderly and simple to run every day.
38
Slash commands
48
Dashboard screens
5
Command categories
12
Security modules
In short
What sets Venon apart
- VenonSec: verification, anti-raid, automoderation and link filters with automatic setup.
- Five layers: VenonSec, the team workflow, community, the dashboard and the documentation.
- The biggest advantage comes when a server uses Venon as one environment.
What the product is worth
What Venon genuinely brings to a server
Three pillars that separate an operational platform from an ordinary bot with a list of commands.
Security as the foundation
Order and protection first, extras afterwards
Venon starts with what matters most: verification, anti-raid, automoderation, link filters, logs and fast operator actions. The bot is not an add-on to the community, but a real layer of security and control.
The team's workflow
Moderation works to procedures, not to chaos
Tickets, reports, cases, review, warnings, mutes and bans are one environment. Venon puts in order not only the configuration, but also the way the team reacts to problems every day.
The web panel and synchronisation
The bot, the dashboard and the site are the same product
The configuration is not a marketing veneer stuck on top. The dashboard, the documentation, the public statistics and the bot's system use the same modules and the same settings — which makes the rollout predictable.
How it works on a server
Venon covers a server's whole life cycle
From a member's first arrival, through the community's daily work, to the response to an incident.
New members arriving
Onboarding from the first moment: verification, account age, anti-fake, anti-raid and filtering of suspicious behaviour.
- checking new accounts as they arrive and limiting the risk
- an automatic response to join waves and suspicious profiles
- control over a member's first contact with the server
The community's daily work
After the security layer comes growth: levels, reputation, suggestions, reminders, reaction roles, stats and bump.
- modules for member activity and retention
- community mechanics tied to the logs and the panel
- growth tools that do not break the operational order
Operational response and incidents
Venon is at its strongest when something has to be configured, repaired, published or tested — real operator actions, not just forms.
- setup, publishing, testing, syncing and repair
- logs, review and a workflow for the staff
- getting control back faster after an incident
Honestly
What Venon will not do
A list of things no configuration here will solve. Better to know about them now than during an incident.
Venon will not replace a moderation team. Automation takes the repetitive traffic off, but disputed decisions, appeals and conversations with people stay with the staff.
The bot works within Discord's permissions. It will not grant a role or remove someone whose role sits above its own, and it does not see content in channels it has no access to.
Content filters rest on patterns and lists. A single cleverly written message can always get around them — which is why logs and reports matter as much as the detectors themselves.
Backups cover roles, channels and module configuration. They will not restore message history, because Discord gives bots no way to do that.
See for yourself
See what the configuration looks like before you add the bot
The guides give the exact field names from the panel and a way to check the setting took hold. It is the fastest way to judge whether Venon fits your server.
FAQ
Common questions about Venon
I added the bot, but the slash commands do not appear.+
Most often the bot was added without the applications.commands scope. Add it again with the invite link (scope: bot + applications.commands). Global commands can take up to about an hour to update.
The bot is online, but does not react to commands.+
Check the bot permissions in the channel (View Channel, Send Messages, Use Application Commands). Moderation commands additionally need permissions such as Kick / Ban Members and Manage Messages.
Verify, or granting roles, is not working.+
The bot's role has to sit ABOVE the roles it grants in the hierarchy, and the bot needs the Manage Roles permission. Make sure as well that the Verify module is enabled and configured (channel + role) in the dashboard.
AntiRaid / AutoMod reacts too strongly, or too weakly.+
You adjust the thresholds and actions in the dashboard (the AntiRaid / AutoMod sections). Changes apply immediately, with no restart. That is also where you set the allowlist of channels and roles exempt from the filters.
Logs, tickets or panels are not creating channels.+
The bot needs the Manage Channels and View Channel permissions in the target category. The fastest route is the auto-setup button in the module — it creates the structure and sets the permissions itself.
I cannot sign in to the panel through Discord.+
The Redirect URI in the Discord Developer Portal has to match the panel's address, and the browser must not block cookies. Access requires an account with permissions on the server.
How much does Venon cost?+
Nothing. Venon Security is free — every protection, moderation and community module and the whole web panel, with no per-server limits and no premium tier. There is no feature unlocked by a payment and no limit that disappears once you pay.
How do I report a bug or get help?+
Join the Venon support server — that is where you report a bug, ask a question and get help with rolling out or configuring the modules.