Payments that can't double-charge or double-enroll.
No angry member, no manual cleanup.
An open-source operations system for course and coaching programs.
Registration, payment tracking, live classes, audience segmentation, and lifecycle email and SMS — in one system that already knows what a cohort, a session, and an enrollment are. Run the hosted demo, or self-host the whole thing.
Your program runs on five tools that don't talk. Anpa is the one that does.
- Course platformLive-class lifecycle, enrollment, and attendance
- CRMContacts with behavioral segments — not hand-kept lists
- Email & SMS toolConsent-safe lifecycle messaging
- Scheduling / ZoomAuto-provisioned classes, reminders, attendance
- SpreadsheetsOne operator worklist with evidence
The back office the course platforms skimp on.
We never message someone who opted out.
Separated email and SMS consent, enforced.
Audiences from real behavior, not hand-kept lists.
Segment by what people actually did.
Automations you can pause and roll back.
Versioned and reversible — no irreversible blast.
See it run a whole business.
A fictional studio, on real software
One breathwork studio, three ways in — its public site, a student’s portal, and the back office running both. Switch between them as you browse.
- 1Start as a visitorThe studio’s public site: its courses, its live practice calendar, and the free course that feeds everything else.
- 2Switch to a studentThe same business from inside: enrolled courses, progress through the lessons, upcoming classes, and past orders.
- 3Switch to the back officeContacts and segments, the course catalog, automations mid-flight, campaign results, and the revenue behind them.
- 4Follow one threadA student who enrolled, the automation that welcomed them, the email that went out, and the class they showed up to — all the same records.
Read-only, with entirely synthetic data — no real contacts, no live customer accounts.
Operations safe enough to delegate.
- Durable, versioned automation — every run is traceable and reversible.
- Idempotent payments — webhooks can't double-apply.
- Consent and suppression enforced before any message sends.
- Human approval before anything touches production.