Product guide
Documentation
Discrofy V2 is a Next.js dashboard, Python AI service, Discord bot, and shared Postgres database. Use these hubs to go from zero to a linked server with real telemetry.
Setup wizard
Connect Discord, link a server, invite the bot — same flow after you are signed in.
ContinueStartCreate an account
Sign up, then you are guided through Discord connection, linking a server, and inviting the bot.
ContinueReturnSign in to the dashboard
Access overview, analytics, content, billing, and settings for your organization.
ContinueSupportHelp Center
FAQs on setup, analytics, AI features, billing, and where to get human support.
ContinueShip logChangelog
What shipped recently across the website, APIs, and operator tooling.
ContinueTechnicalAPIs & integrations
How the AI service, bot HTTP API, and Stripe webhooks fit together — no magic public API key.
ContinueHumansContact the team
Questions, partnerships, or sales — messages are stored for follow-up.
ContinueGetting started
After signup, open the in-app setup wizard (after sign-in: Setup in the sidebar or Integrations). Connect Discord with OAuth, pick a server you manage, link it to your workspace, then use the bot invite link so analytics and automation can write to the same database the dashboard reads.
See Privacy for what we store at a high level, and the operator appendix docs/DATA_COLLECTION_AND_RETENTION.md in the repo clone for table-level detail.
Dashboard areas
- Overview & analyticsTelemetry-driven charts when the bot is on linked guilds.
- AI BuilderGuild-scoped server profile, blueprint generation, apply, and rules posting via the bot.
- ContentAnnouncements and campaigns with review and publish flows.
- Members & notificationsModeration signals and activity when the bot persists them.
- BillingStripe checkout, webhooks, and Customer Portal from the billing page.
- SettingsOrg preferences, security, and integrations entry points.
Uptime & health checks
The marketing site exposes GET /api/health for load balancers (JSON includes a lightweight database check when configured). Pair it with GET /health on the AI service and GET /api/health on the bot — see the operator runbook in the repository for curl examples.
Self-hosting & operators
If you run your own stack, treat migrations → AI → bot → website as the default deploy order and keep DATABASE_URL aligned across services that share Postgres. The repo includes docs/RUNBOOK.md, docs/TO_CONFIGURE.md, and docs/testing/SMOKE_TEST_MANUAL.md for checklists and health probes (including GET /api/health on the website).