Skip to main content
Use cases

Venon for your server

Seven types of server and what they usually need: useful modules, an example setup, benefits and the first step. Pick the type closest to yours.

The example setups are scenarios showing how modules can be combined — not stories of specific servers. A badge next to a module marks a beta version or monitor-only mode.

Gaming server

Lots of newcomers from server listings, voice channels and a real risk of raids.

Typical needs

  • Filter out bots and throwaway accounts before they see any channel.
  • Spot a sudden wave of accounts and spam quickly.
  • Voice channels for squads without creating them by hand.
  • A reason for players to keep coming back.

Useful modules

What you get

  • New accounts pass verification before they can post anything.
  • AntiRaid alerts the team when joins spike unnaturally — a moderator decides on the lockdown.
  • Players create their own channels, which disappear when the last person leaves.

Example setup

Example scenario
  1. Verify in captcha mode; the “Player” role only after passing verification.
  2. AutoMod with the default detectors — removes spam and flood; you decide on penalties for repeat offenders.
  3. A temporary channel generator in the voice category.
  4. XP levels with a reward role at each threshold.

How to start

Add Venon, go through the starter wizard in the panel and enable Verify. The panel also has a configuration preset for gaming servers — it shows the list of changes before applying them.

Community

A server where people should meet, talk and stay for longer.

Typical needs

  • A warm welcome and clear first steps for newcomers.
  • Self-assigned roles — interests, notifications.
  • A place for members' ideas and visible decisions.
  • Small rituals that build the atmosphere.

Useful modules

What you get

  • A newcomer knows straight away where to start and which roles to pick.
  • Ideas don't get lost in chat — they have votes and a status.
  • Birthdays and best-of messages remind everyone this is a community, not an announcement board.

Example setup

Example scenario
  1. A welcome card in #welcome and a starter role for the new member.
  2. A role panel with buttons: interests and event notifications.
  3. A suggestions channel with voting and a public server roadmap.
  4. Starboard: a message with enough reactions is copied to a separate channel.

How to start

Add Venon and go through the starter wizard in the panel. The community preset enables welcomes, suggestions, birthdays, role panels and the new member journey — it shows the plan of changes first.

Education and study

Groups of pupils, students or course participants who need order and reminders.

Typical needs

  • Channels and roles for subjects, years or groups.
  • Reminders about deadlines, classes and assignments.
  • Private questions to tutors without cluttering the channels.
  • Recognition for people who help others.

Useful modules

What you get

  • Everyone sees only the channels of their own groups.
  • Reminders go out at a fixed time without anyone remembering to send them.
  • Helping others is visible and rewarded.

Example setup

Example scenario
  1. A role panel with a select menu: subjects or class groups.
  2. Schedules: a reminder about the assignment deadline every Monday morning.
  3. Tickets as private questions to tutors, with conversation history.
  4. Reputation: /rep points for a helpful answer and a role at each threshold.

How to start

Add Venon, create a role panel with your groups and add the first reminder in Schedules.

Creator server

A community around a channel, podcast or blog — viewers want to hear about new releases.

Typical needs

  • Automatic announcements of new content.
  • Giveaways for viewers with clear entry rules.
  • Viewer roles, so everyone sees the channels they care about.
  • Server promotion without tracking timers by hand.

Useful modules

What you get

  • New content is announced without pasting links by hand.
  • The bot draws giveaway winners — the winners and rules are in one place.
  • Viewers pick the roles and channels they are interested in themselves.

Example setup

Example scenario
  1. Content Hub: new YouTube videos are posted to #new-content.
  2. A /giveaway with a role requirement and a winner draw.
  3. A role panel with buttons: viewer roles and access to topic channels.
  4. A reminder for the next server bump.

How to start

Add Venon and connect a source in Content Hub: YouTube, Reddit, Bluesky or any RSS/Atom feed.

Support and shop

A server for a product, service or shop where customers look for help.

Typical needs

  • Private requests with history, not threads in public chat.
  • A team with different permissions — not everyone should be able to do everything.
  • A trail of who changed what and who handled a request.

Useful modules

What you get

  • Every request has its own channel, history and a service rating.
  • The team sees only what they work on in the panel.
  • The change log shows who changed the configuration and when.

Example setup

Example scenario
  1. Ticket CRM: request categories (order, payment, other) and a panel with a button.
  2. An HTML transcript saved when a ticket is closed.
  3. Panel access for the support team with a limited scope.
  4. Moderation logs in a channel visible only to the team.

How to start

Add Venon and configure tickets in the panel or with /ticket_crm. The support preset enables tickets and reminders about unanswered requests — it shows the plan of changes first.

Roleplay

A world with characters, jobs and its own economy.

Typical needs

  • Character sheets approved by the team before anyone starts playing.
  • Currency, jobs and promotions that matter in the game.
  • Items and privileges to buy.
  • Ranks and statuses for the duration of events.

Useful modules

What you get

  • Every character goes through the same approval flow.
  • The economy keeps a transaction log — easy to check where someone's money came from.
  • Event roles disappear on their own after the set time.

Example setup

Example scenario
  1. Applications: a character sheet form with a team decision flow.
  2. Economy: server currency, jobs and promotions along a career path.
  3. A shop with roles, e.g. licences or passes to places in the game world.
  4. Temporary roles granted for the duration of a story event.

How to start

Add Venon, enable the economy in the panel (it is off by default) and create an application form. Venon City is in beta.

Developer community

A server for an open-source project, a library or a group of developers.

Typical needs

  • News about new releases and project blog posts.
  • Protection from phishing links, which often target developers.
  • Recognition for people who answer questions.
  • Collecting feature requests from the community.

Useful modules

What you get

  • Releases are announced from the same source the project already publishes.
  • Malicious links disappear before anyone clicks them.
  • People who help others are visible in the reputation ranking.

Example setup

Example scenario
  1. Content Hub: an Atom feed with project releases (e.g. releases.atom from GitHub) → #releases.
  2. LinkShield removes phishing links and invites to other servers.
  3. Reputation: /rep for solving a problem and a “Helper” role at each threshold.
  4. Suggestions as a public list of feature requests with voting.

How to start

Add Venon, enable LinkShield and connect the project's RSS/Atom feed in Content Hub. Workflows let you add your own rules without code.

None of these fit?

Match modules to your problems

The wizard on the modules page asks about your server type and the problems you face, then points you to modules with descriptions. No login and no changes to your server.