Skip to content
supastack
Browse documentation
WebNext.js

For AI agents: fetch the complete documentation index at /llms.txt, the full documentation corpus at /llms-full.txt, the agent skill at /skill.md, or this page as Markdown at /docs/web/glossary.md (or send Accept: text/markdown).

Words you will see

Plain-language definitions for the terms the setup guides, error messages and the product itself use.

Files and folders

These words describe the code you downloaded. The setup guides name them whenever they ask you to open or edit a file.

  • Repository — the project folder plus its full change history, hosted on GitHub and copied to your computer.
  • Clone — your own copy of a repository on your computer; the git clone command creates it.
  • Monorepo — one repository holding several apps and shared packages; the All Platforms bundle is one.
  • package.json — the file in every app or package that lists its name, its commands and the libraries it needs.
  • pnpm-workspace.yaml — the file at the monorepo root listing which folders belong to the workspace.
  • Lockfile — the file recording the exact version of every installed library, so each install matches.

Tools on your computer

Programs you install once before the first run. The guides name them in commands such as node --version.

  • Terminal — the window where you type commands, such as PowerShell on Windows or Terminal on macOS.
  • Node.js — the program that runs JavaScript outside a browser; the kit's server and scripts run on it.
  • npm — the library installer bundled with Node.js; in this kit you mainly use it to reach Corepack.
  • Corepack — the tool that switches on the exact package-manager version the project pins.
  • pnpm — the package manager that downloads libraries and runs project scripts; reach it as corepack pnpm.
  • Git — the tool that downloads your repository and records every change you make to it.
  • Editor or IDE — the app where you open folders and edit files; the guides use Visual Studio Code.

Configuration words

Settings live in files, not in the terminal. These words cover where they sit and what they are called.

  • Environment variable — a named setting such as EMAIL_PROVIDER=local that changes how the app behaves.
  • .env — the file at the repository root holding settings for commands such as database migrations.
  • .env.local — the settings file for one app, such as apps/web/.env.local for the web server.
  • Secret — a value that must stay private, such as a password or signing key; never commit it or paste it into chats.
  • API key — a secret string an outside service gives you so it recognizes your app as an allowed caller.
  • Provider — an outside service the kit can use for AI, email, billing, storage and similar jobs.

Words the product uses

The running app and its settings screens use these terms. Workspace appears with two different meanings — check the context.

  • Workspace — in the product, one team's separate users, data and settings; in pnpm commands, one package folder inside the monorepo, selected with --filter.
  • Entitlement — the server's record that a workspace is allowed to use a paid feature.
  • Migration — a versioned database change that creates or updates tables; you apply migrations with a command.
  • Session — the signed-in state that tells the server who is asking, until it expires or you sign out.
  • Webhook — a message an outside service sends to your app's URL when something happens, such as a paid invoice.
  • Account vs organization — an account is one person's sign-in; an organization is the shared team space members join, also called a workspace.

Web development words

Terms the run, build and deploy guides use when you open the app in a browser.

Ctrl + C means press and hold Ctrl, tap C, then release — it stops the running command in a terminal.

  • localhost — the name for this computer in a browser address; your app runs there during development.
  • Port — the numbered door after localhost, such as :3000; each running app uses a different one.
  • Dev server — the command that keeps rebuilding and serving the app while you work; stop it with Ctrl + C.
  • Build — the step that turns your source code into the optimized files a server deploys.
  • Server rendering (SSR) — pages the server assembles before sending them, so the first view arrives complete.

Frequently asked questions

14 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 OTP, magic-link, and social sign-in; email/password stays available at the API layer and through the Auth.js credentials engine for products that need it. 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 Platform at $249 (temporary launch price, $100 off the regular $349) — your pick of Next.js (Web), Expo (iOS & Android), or Tauri (macOS & Windows Desktop) — or the All Platforms Bundle at $499 (temporary launch price, $100 off the regular $599) with every platform and the full monorepo, plus $75 per extra developer seat. No kit subscription. Checkout on this site delivers your license key by email, with repository access via GitHub invite.

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.

How do mobile purchases work?

Mobile includes native purchases and restore through RevenueCat, with access verified by your server. Configure the store accounts and complete device testing before release. Web billing remains separate.

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.

Which payment methods does checkout accept?

The Stripe-hosted checkout accepts cards and can also offer Alipay and WeChat Pay once those wallets are enabled on the Stripe account — handy for buyers in China. Wallet authorizations confirm asynchronously, so the license page updates as soon as the payment clears.

Can I get a refund?

After you've got access to the repository, supastack is yours forever, so it cannot be refunded. But rest assured, you get the complete source code with lifetime updates to build and ship unlimited products for yourself or clients. You just cannot resell the code or redistribute the repository as a starter kit or template.

EN
Theme