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

Privacy

What this covers

This page describes how supastack handles information when you use the public website, create an account, or submit a contact or newsletter form. It is not a certification, audit report, or claim that every product built on the kit follows the same practice.

Account and workspace data

If you sign in, we store the email and name on your account, session data, and records owned by your personal workspace. Product records such as AI usage, entitlements, billing events, and audit entries are scoped by workspaceId. Provider secrets stay on the server and are not written into logs.

Billing

When Stripe is configured for a product built on this kit, customer, subscription, and entitlement records are stored so access can be enforced. Kit license checkout for supastack itself is not connected yet, so this site does not collect card details for a supastack purchase.

Messages you send us

Contact and newsletter forms send the details you type (name where asked, email, and message) to an operator inbox only when delivery is configured. We do not publish a subscriber count. If delivery is not connected, the form says so instead of pretending the message was mailed.

Analytics and cookies

Server error and analytics clients may run in a deployed app when you configure them. The marketing site does not fire client-side analytics unless a browser capture SDK is enabled. If that happens, a consent banner appears first, and capture waits for an explicit accept.

What we do not claim

We do not sell a customer list, invent testimonials, or promise a specific deletion portal beyond what you can do from account settings (name update and sign-out today). Ask via the contact form if you need a record removed from an operator inbox.