Explore Venon. No sign-in needed.
Monitor mode
Notice a signal. Make an informed decision.
Follow a sample wave of joins. AntiRaid detects and reports; an administrator decides whether to lock down.
New accounts join
Example: six accounts arrive within a short window. This is a signal to review, not proof of abuse on its own.

Try configuring Verify
Choose a sample channel and role. Build a message, then try it locally. Nothing is published to Discord.
Set up real verificationChoose a channel, role and button text to build your preview.
Explore the security workflow in detail
For readers who want to understand signals, incidents and restoring permissions.
Workflow
Five stages, each with a visible record
Join
AntiFakeEvent
A new account joins the server. The account module assesses its age, avatar, name pattern and how it joined. A risk score is an observation, not yet an incident.
Example: An account created 40 minutes earlier, with no avatar and a randomly suffixed name.
Signals
SecuritySignal
Each observation is recorded as a signal with a type, confidence, source and privacy class. A single signal has little meaning; several appearing together tell a clearer story.
Example: Six joins in 90 seconds, all with the same name pattern and using the same invite.
Incident
SecurityIncident
Signals of the same type within one time window form an incident with a severity and operating mode. The incident records its window, signal count and recommended action, which has not yet been executed.
Example: A join-wave incident: HIGH severity, 6 signals, a 90-second window and a recommendation to raise the verification level.
Action
ShieldSession / SecurityAction
New servers start in SHADOW mode: incidents are recorded and reported, but no action happens automatically. Execution requires the administrator to explicitly enable manual mode or limited automation.
Example: The administrator approves the action in the dashboard. The actor, time and grounds for the decision are recorded.
Recovery
ChannelPermissionSnapshot
Before permissions change, their previous state is saved. Lifting a lockdown can then restore the exact previous configuration.
Example: The wave ends after 12 minutes. Lifting the lockdown restores 14 channels’ permissions from the snapshot.
The flow is one-way up to stage 4: an observation cannot trigger an action without an incident, and an incident cannot bypass the mode chosen by the administrator. Stage 5 reverses the effects using the saved permission snapshot.
Security Operations Center
What the incident queue looks like
| Type | Severity | Mode | State | Signals | Window | Notes |
|---|---|---|---|---|---|---|
| Join wave | HIGH | MANUAL | OPEN | 6 | 90 s | Six accounts with the same name pattern, using one invite. |
| Link spam | MEDIUM | SHADOW | OPEN | 3 | 4 min | The same shortened link posted in three channels. |
| Mass mentions | LOW | SHADOW | CLOSED | 2 | 2 min | Closed without action — the threshold was not reached. |
SHADOW mode means that an incident was recorded and reported without taking action. Every server starts this way. Automation begins only when the administrator explicitly allows it and sets its limits.
MSIoU dossier
What administrators can and cannot see
przyklad_alfa · 100000000000000001
- Lookup scope
- 2 network servers out of 3 publishing servers
- Activity window
- 30 days
- Messages in the window
- 412
- Minutes in voice channels
- 1180
- Lookups for this person
- 3
- WARN2Both on a server publishing to the network
- MUTE1Expired
- BAN0None
Passport: Enabled by the user — server counts are visible, server names are hidden
What a dossier never contains
- Server names. Neither dossiers nor passports disclose where a person spends time, regardless of configuration.
- Message content. Only aggregate figures from a 30-day window are included.
- Data from servers outside the network. A server that does not publish contributes nothing to another server’s dossier, even when it uses the same bot.
- Cross-server disciplinary history after an opt-out. An opt-out restricts the view to the server where the lookup was made.
- Anonymous requesters. Every lookup records who requested it. That would also apply to this demonstration if it were performed in the product.
Details and source files: Trust Center .