Foundations
Setup, member join and leave tracking, role signals, community overview, segments, and the weekly digest. This is what pilot servers validate first.
On the homepage →How Genyx works
Genyx pairs Nyx inside your Discord server with a web dashboard your team uses to configure tracking, read community health, and decide what to do next. This page follows that journey from invite to weekly digest.
Flow
From invite to first insights
The flow is deliberately short. You should understand what Nyx tracks, where to read it, and when the first digest arrives without hunting through scattered modules.
Invite Nyx
You add Nyx with the standard Discord OAuth flow. Genyx runs a permission pre-flight, provisions the Nyx Admin area when possible, and points the server owner to the setup wizard in the web app.
Members keep interacting with Nyx in Discord. Admins configure the platform on Genyx.
Complete setup on Genyx
The guided setup covers security, logging, onboarding, and analytics modules you choose to enable. Each step explains what will be recorded and why it matters for community health.
When setup is marked complete, tracking begins in earnest and the dashboard can surface meaningful summaries after a few days of activity.
Read the community overview
The dashboard overview shows growth and activation snapshots, segments that need attention, and the latest weekly digest. It is designed for a one-minute read before your team meeting, not a wall of charts.
You can drill into members by segment when you need names and counts behind the headline numbers.
Act and iterate
Genyx suggests a practical focus for the week ahead, such as welcoming recent joins or re-engaging quiet members. Activation modules and internal campaigns build on the same segments as they roll out.
The weekly digest in Discord keeps owners informed even when they do not open the dashboard daily.
Product layers
Foundations, Activation, Growth Infrastructure
These three layers describe how Genyx ships value over time. Foundations is live today. Activation is expanding with pilot servers. Growth Infrastructure is a consent-based discovery layer on the roadmap.
Activation
Turn segments into action: internal campaigns, nudges, and Engage & Evolve where enabled. The goal is a clear path from insight to something your community team can run this week.
What ships today →Growth Infrastructure
Future opt-in discovery between compatible communities. Transparent matching, no bought audiences, no silent redirects. Target availability early 2027 after Foundations prove out.
Discovery roadmap →Engagement
Engage & Evolve and community rewards
Where gamification is enabled, Engage & Evolve rewards meaningful participation rather than raw message volume. Community rewards are the engagement points inside that program — not cash, but roles, access, and perks you configure. Optional Web3 modules are on the roadmap for teams that need wallet or NFT signals.
Activation data from XP and participation feeds the same community picture as join tracking, so your overview reflects both arrivals and behaviour.
Landscape
How Genyx fits next to other tools
Utility bots excel at commands and logs. Analytics bots describe activity. Genyx targets community operations: see health, act on segments, grow with consent. This table is a snapshot; dedicated comparison pages cover MEE6, Statbot, and Sesh.
| Criterion | Genyx | MEE6 | Statbot | Sesh |
|---|---|---|---|---|
| Community overview and weekly digest | Yes | Limited | Partial | No |
| Operational segments (new, inactive, silent) | Yes | No | No | No |
| Moderation and server utilities | Core modules | Strong | No | Events focus |
| Primary focus | Community OS | Mods + XP | Descriptive stats | Scheduling |
Dedicated pages: Genyx vs MEE6 · Genyx vs Statbot · Genyx vs Sesh · Full compare hub
Glossary
Terms you will see in the product
- Foundations
- The live layer: setup, tracking, overview, digest, and first segments. Everything else builds on this.
- Weekly digest
- A short summary posted to your server or sent to the owner: joins, activation, what to watch, and one suggested focus for the week.
- Segment
- A group of members defined by behaviour, such as recent joins without participation or members quiet for two weeks.
- Consent-based discovery
- The future Growth Infrastructure layer: communities opt in to be matched with compatible servers. Not an ads marketplace.
- Nyx
- The Discord bot members see. Genyx is the platform you configure in the browser.
- Genyx ID
- Optional Web3 identity signals where your plan and policies allow wallet or NFT aware roles.
FAQ
Common questions
How does Genyx install on Discord?
Invite Nyx with OAuth. Complete setup at /setup/your-server-id on Genyx. Nyx begins capturing events you enable during setup.
When will I see useful numbers?
Join tracking is immediate. The overview and digest become more meaningful after a few days of member activity so trends are visible.
Does Genyx replace MEE6 or Statbot?
Not necessarily. Many teams keep a utility or stats bot and add Genyx for community operations. Genyx is complementary when you need segments, digests, and a single cockpit.
Does Genyx buy members from other servers?
No. Genyx does not run cross-server audience redirects or member marketplaces. Future discovery features will require explicit opt-in from communities.
What does Core include?
Core is free and includes moderation, roles, onboarding, broadcasts, live analytics, and Foundations features such as the community overview and weekly digest when enabled.
Where is the API documentation?
See the Documentation hub for OAuth, REST endpoints including /members and community routes, and admin guides.
Ready to pilot Foundations?
Invite Nyx, finish setup, and join the early cohort if you want direct product input.