SPAPS vs SuperTokens
This is a boundary guide, not a feature-parity claim. The SPAPS statements were checked against
Sweet Potato 5b09d3df1194577c5313c865fef1db98f694cdea; verify SuperTokens’ current primary
documentation before making an adoption decision.
SuperTokens is oriented around self-hosted auth, sessions, recipes, and framework integration. SPAPS targets a narrower revenue-aware app backend: identify the application, identify the user, process billing state, project entitlements, and verify the whole path from one local proof.
The comparison is not “which auth system has more identity features?” It is “does this app need self-hosted auth alone, or does it need a governed control plane for auth plus revenue state?”
Quick Comparison
| Question | SuperTokens-shaped answer | SPAPS-shaped answer |
|---|---|---|
| Primary job | Self-hosted auth and sessions | Revenue-aware app control plane |
| Integration shape | Frontend SDK, backend SDK, and SuperTokens core | CLI/runtime, server package, SDKs, and documented app contract |
| Entitlement source | App-defined integration around auth state | Backend-modeled billing, wallet, and entitlement state |
| First proof | Run auth recipe across frontend and backend | Run local mode, quickstart, and verify JSON output |
| Best reader | Team standardizing authentication | Team standardizing app access tied to payment and grants |
Choose SPAPS When
- The business rule is “this paid or granted user can access this app capability.”
- Stripe webhooks, wallet activity, admin grants, and app auth need one auditable path.
- A Solutions Consultant needs a repeatable field demo with a leave-behind artifact.
- A backend maintainer needs explicit middleware and dependency boundaries before changing code.
Choose SuperTokens When
- The main project is a self-hosted auth rollout.
- Recipes and session behavior are the center of the implementation.
- Billing state can stay outside the auth platform without duplicating entitlement logic.
Proof Path
npx spaps local
npx spaps quickstart --json
npx spaps verify --jsonAfter the proof, continue through billing and entitlements, auth and local mode, and the field kit if the comparison is happening in a customer demo.