Create your external accounts

You can build before you buy

Every feature in this kit first runs with a local stand-in — a built-in adapter that imitates the real service without an account. EMAIL_PROVIDER=local writes messages to a preview page instead of sending them, AI_PROVIDER=fake returns a deterministic fake answer, BILLING_PROVIDER=local completes checkout without a payment provider, JOB_PROVIDER=local queues background jobs in memory without running them, and CAPTCHA_PROVIDER=off keeps public forms open. The .env.example configuration ships this way, so the five-minute tutorial needs zero paid accounts.

Add a real external account only when you ship the feature it powers: a database before real sign-in, an email provider before messages must reach inboxes, a billing provider before charging money. Each guide below names the console page, the values to copy, and where to paste them.

• Set up Amazon SES with AWS SDK or IAM SMTP

The complete account checklist

This table lists every outside service a supastack product can need. Skip any row whose feature you are not shipping — a web-only starter never touches the mobile and desktop rows. The Guide column names the doc that walks that console click-by-click; the actual links are in Where to start at the end of this page.

A sensible creation order

Create accounts in the order features come online. For most web products that means: 1. Postgres database, 2. transactional email, 3. Google and/or GitHub sign-in, 4. billing, 5. an AI provider — then storage, background jobs, observability, and spam protection as the product needs them.

Hosting and a domain come last — a public URL is only useful once a working app exists to point it at. Mobile accounts (Expo, Apple, Google Play, RevenueCat) and desktop signing accounts matter only when you reach those platforms; skip them entirely for a web-only launch.

Keep every secret — OAuth client secrets, API keys, webhook signing secrets, and the password inside DATABASE_URL — in .env.local files or your host's secret manager. Never place them in NEXT_PUBLIC_ or EXPO_PUBLIC_ variables, and never commit them to Git.

Where to start

The detailed guides below walk each console click-by-click. Work top to bottom: the sign-in providers, then the account walkthroughs for payments, email, and the remaining provider keys, then the provider setup references for the services your product ships, then deployment; the platform account guides when you reach mobile or desktop.

• Add Google sign-in
• Add GitHub sign-in
• Add Apple sign-in
• Add Stripe payments
• Add Resend email
• Collect the remaining provider keys
• Set up database
• Set up payments
• Set up email
• Set up OAuth sign-in
• Set up AI
• Set up background jobs
• Set up file storage
• Set up observability
• Spam protection
• Set up custom domains
• Deploy to Google Cloud
• Deployment checklist
• Create mobile accounts
• Create desktop release accounts
• Connect the mobile project to EAS
• Set up RevenueCat purchases
• Sign desktop installers