Skip to content
supastack
English
Get Access

Menu

English
Get Access

Frequently asked questions

12 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/password, OTP, and social sign-in. 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 Framework at $249 or All Frameworks (Next.js, iOS, Android) at $499, plus $75 per extra developer seat. No kit subscription. Checkout on this site is not connected yet.

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.

Can mobile expose Stripe Checkout?

Not yet. Mobile must not present Stripe Checkout until RevenueCat exists. Web can use Stripe for subscriptions and entitlements when billing is configured.

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.

Open full FAQ page
Documentation
Browse documentation

Web / Development

Troubleshooting

Diagnose setup problems at the boundary that actually failed.

Setup and configuration

Read the failing command and first relevant error before changing configuration. Determine whether the failure is dependency installation, compilation, environment validation, database access, provider dispatch, or browser behavior.

pnpm --filter @starterkit/web typecheck
pnpm --filter @starterkit/web build
pnpm test

Implementation workflow

For missing API access, verify the server is running and the configured origin matches the client. For unavailable AI choices, inspect AI_MODEL_POLICY and enabled catalogue rows. For an uncertain queued task, use the saved recovery flow instead of starting another submission.

For browser layout issues, inspect computed styles and reproduce the exact viewport. Product chrome tokens live in app-theme.css (packs from catalog.ts); marketing brand lock lives in theme.css. Component overrides can still win through specificity. Check the rendered radius rather than only the token declaration.

Verification and troubleshooting

Do not solve a failing check by disabling authorization, logging secrets, or treating skipped infrastructure checks as passed. Capture a small reproduction and the relevant non-secret configuration. Re-run the failing check after the fix, then the affected regression tests.