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 / Getting started

Local setup

Install the workspace and run the local reference flow.

Prerequisites

Use Node.js 22 or newer and the pnpm version declared in the root package.json (currently 11.19.0). Run the following commands from your supastack repository root. Keep the generated .env file local; it must not be committed.

Prepare the workspace

Copy the example environment file, then install the workspace dependencies. On Windows PowerShell, use Copy-Item .env.example .env for the first command. If .env already exists, review it instead of overwriting your configuration.

cp .env.example .env
pnpm install

Run the local checks

The local verification command runs lint, types, deterministic tests, builds, and the browser suites. PR tests use fake/local adapters and do not call billable providers.

pnpm verify:local
pnpm dev

Explore the web app

Use the local URL printed by Next.js. The public homepage is at /. Open /dashboard for the reference interface, /auth for sign-in, and /settings for profile settings.

A production-style reference environment needs migrated Postgres and configured integrations. If a check requires external infrastructure, report that gate separately rather than substituting a local result for it.