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

Deployment checklist

Prepare the production dependencies and verify the flow you intend to ship.

Prepare the services

Provision Postgres, apply the repository’s database migrations, and configure the application origin and authentication settings for your host. Configure Stripe web billing, a transactional email provider, and Trigger.dev for the workflows you enable.

Configure the immutable model/price catalog and workspace AI policy before accepting production AI tasks. An empty alias policy should leave those choices unavailable.

Build and deploy the web application

Run the root checks, then build the web workspace. Configure your host to run the built Next.js application with the same server-side environment validation used locally.

pnpm check
pnpm --filter @starterkit/web build
pnpm --filter @starterkit/web start

Verify the deployed boundaries

Verify sign-in and persistence against the deployed database; test workspace isolation; confirm Stripe sandbox webhook processing and entitlement changes; and run a background task through result persistence and transactional delivery.

Read docs/real-provider-smoke.md and docs/production-ai-runtime.md in the repository for the explicit provider acceptance process. A successful build or intercepted browser test does not establish these external outcomes.