Skip to content

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

Modules / Foundation

Module overview

Small contracts that make the infrastructure easier to understand and reuse.

Compose the capabilities you need

The shared packages provide identity, workspace persistence, billing, AI, background jobs, transactional email, and observability. Applications compose these modules; product domain logic stays outside Starter Core.

Prefer the existing contract when integrating a feature. If it cannot describe the behavior you need, make that limitation explicit before expanding it.

Follow ownership through the flow

A session identifies a user. A workspace scopes their records. Entitlements authorize capabilities. A background task carries trusted context into execution. Usage and audit records let the application account for the work afterward.

Use local adapters for deterministic checks

Fake/local adapters support repeatable tests without paid provider requests. Real providers are verified through a separately configured smoke path. An adapter test is evidence about the contract, not proof of real delivery or persistence.