Skip to content
supastack
Browse documentation

For AI agents: fetch the complete documentation index at /llms.txt, the full documentation corpus at /llms-full.txt, the agent skill at /skill.md, or this page as Markdown at /docs/mobile/entitlements.md (or send Accept: text/markdown).

Mobile entitlements

Configure RevenueCat purchases and keep access decisions on the server.

Understand the access status shown on your phone

An entitlement is permission to use a paid feature. It belongs to the active workspace, the group of account data your team uses. First complete native sign-in, then open the phone app's Settings → Billing. Read the displayed access status; loading or an error does not mean you have a subscription.

With purchases off, the app should not offer store checkout. To sell access, complete the RevenueCat purchase guide below and test in a native development build. After a test purchase, reopen Billing and confirm the server reports active access; after expiry, confirm the feature is locked again. If a purchase succeeds but access does not refresh, use Restore purchases and check the backend connection rather than buying a second time.

Read access from the server

The mobile entitlement client reads server-owned access state. Keep a loading or failed request distinct from an active subscription; the interface must not infer paid access because a request failed.

Use the presentation logic in apps/mobile/src/entitlements to translate that state into the native interface.

Keep the purchase boundary explicit

Native purchases use RevenueCat when configured; web billing is a separate surface. Do not expose Stripe Checkout in the mobile interface or treat a store-side active flag as proof of server access.

The In-app purchases guide documents client keys, manager checks, workspace identity, purchase/restore sync, server verification, and sandbox setup. Real StoreKit or Play Billing acceptance requires an EAS development build; Submit to the app stores covers release.

Check denied and expired access

Test unavailable, inactive, and active entitlement states, plus network failures. Verify that restricted actions remain unavailable when the server denies access, and that signing out clears the previous session’s presentation.

If you want to continue setup, read Create mobile accounts.

Frequently asked questions

14 questions

What is supastack?

supastack is a modular foundation for building AI-powered SaaS products. It brings together common infrastructure so you can focus on product-specific features.

Does it support web and mobile?

Yes. supastack includes Next.js and Expo apps as starting points for web and mobile experiences.

What authentication is included?

Better Auth covers email OTP, magic-link, and social sign-in; email/password stays available at the API layer and through the Auth.js credentials engine for products that need it. Personal workspaces are provisioned with the account so product records stay scoped from day one.

How does it support AI?

supastack includes configurable multi-provider AI, usage tracking, budgets, and encrypted bring-your-own-key support.

How are subscriptions handled?

For products built on the kit, Stripe billing, subscriptions, and entitlements form the paid-access foundation. Provider secrets stay server-only.

Where does my product-specific code live?

Product-specific features remain in a separate codebase while the product configures and integrates supastack’s foundation modules.

How does supastack pricing work?

The kit is a one-time purchase with lifetime updates: One Platform at $249 (temporary launch price, $100 off the regular $349) — your pick of Next.js (Web), Expo (iOS & Android), or Tauri (macOS & Windows Desktop) — or the All Platforms Bundle at $499 (temporary launch price, $100 off the regular $599) with every platform and the full monorepo, plus $75 per extra developer seat. No kit subscription. Checkout on this site delivers your license key by email, with repository access via GitHub invite.

How do workspaces scope my data?

User-owned records are scoped by workspaceId. Identity, entitlements, AI usage, billing events, and audit entries stay inside the personal workspace boundary.

How do background jobs work?

Trigger.dev is the explicit job runtime. The JobRunner contract only promises enqueue, status, and cancel—workflow semantics stay Trigger.dev-specific and explicit.

How is email different from outreach?

Transactional email covers product workflows such as completion notices. Cold outreach and campaigns are product concerns outside this kit’s email module.

How do mobile purchases work?

Mobile includes native purchases and restore through RevenueCat, with access verified by your server. Configure the store accounts and complete device testing before release. Web billing remains separate.

Where do AI provider keys live?

Bring-your-own-key credentials are encrypted and stay server-only. Keys are redacted from logs; usage and budgets remain visible at the workspace level.

Which payment methods does checkout accept?

The Stripe-hosted checkout accepts cards and can also offer Alipay and WeChat Pay once those wallets are enabled on the Stripe account — handy for buyers in China. Wallet authorizations confirm asynchronously, so the license page updates as soon as the payment clears.

Can I get a refund?

After you've got access to the repository, supastack is yours forever, so it cannot be refunded. But rest assured, you get the complete source code with lifetime updates to build and ship unlimited products for yourself or clients. You just cannot resell the code or redistribute the repository as a starter kit or template.

EN
Theme