Five pieces on the homepage. Six questions here.
Six questions decide a subscription. Each block answers short, shows the screen where it happens, says where it stops — and points to the page with the whole mechanism.
Do I keep selling where I already sell?
The sale stays on your gateway, with no revenue cut. The webhook arrives signed, the product becomes access, the student walks in alone — seven providers, from Hotmart to Stripe, with origin and transaction recorded on every access.
Visitors see the showcase; buying requires an account.
Can I run a class with dates, exams and certificates?
Nine lesson types, tracks with ordering and date-based release, cohorts with a window that opens and closes on its own. Quizzes graded on the server, with passing grade and attempts; on completion, a certificate with a serial number and a public verification page.
Quizzes are server-graded; assignments wait for human review — the product runs the queue.
Can I control who joins, who speaks and who moderates?
Three layers: invites and approval at the door, permissions and moderators per space, and trust levels that promote on real activity — the server refuses posts, polls and images from anyone not there yet.
The feed has two tabs, All and Following — no feeds by rule, tag or segment.
Does the live conversation live here, or does it stay on WhatsApp?
Community chat over WebSocket — presence, reactions, quoted replies, server-enforced slow mode — and direct messages with blocking. Turn on the assistant and it answers the repeated questions with your knowledge base and your model key.
One room per community, no topic channels; search does not cover messages.
Can I see who's disappearing?
Five analytics lenses, each with CSV export. Retention lists who was active and stopped showing up, with the date last seen — a database query, not a model's guess. On the other side, streaks, rankings, challenges and badges call them back.
The lens looks backward — there is no churn prediction.
Is the platform mine, or yours?
Yours on the outside — color, theme, logo, SEO and your own domain, unlocked after a real HTTPS handshake — and inside: every customer starts with their own Postgres database and containers, not a row in a shared table.
Without your own SMTP, transactional email goes out from a platform domain.
The numbers the server enforces.
Six limits per plan, checked on the server: past them, the API refuses. Members are the exception — they grow through add-ons.
| Start | Scale | Dominion | |
|---|---|---|---|
| Members | 1,000 | 3,000 | 10,000 |
| Spaces | 10 | 30 | 100 |
| Courses | 10 | 50 | 100 |
| Storage | 100 GB | 250 GB | 600 GB |
| Moderators | 2 | 10 | 50 |
| AI courses, per month | 3 | 15 | no limit |
Storage is visible before it becomes a surprise: total use, per-media breakdown and real video weight.
Above 10,000 members, each additional block of 10,000 is a paid add-on — up to 1 million.
What the product doesn't do.
Each block's limits are not repeated here. These are the ones without a block.
- No base or content import — entry is invites and gateway-driven access.
- Button exports are metrics only, as CSV. Not members, not content.
- No app to install, no offline use. Runs in the browser.
- No corporate SSO login.
- XP is not a rewards store: it feeds levels, rankings and challenges.
This is not a roadmap; it is the product today.
Two exits.
If your case fits the numbers above, build: the structure comes up on its own.
A base to migrate, a cohort in flight, or contract before card? Then it's a conversation.