Say yes to the security questionnaire.

The signed-in home screen. Live activity, organization health and pending work for the current tenant, updating in realtime as teammates act.

The reference product domain: projects and tasks scoped to an organization, with roles, plan limits, search, attachments and an audit history. Copy this pattern for your own resources.

Executable documentation. One-click smoke tests prove feature access, workflows, analytics, errors and email against your own deployment, using debug adapters until real keys are set.

Profile, organization switching, invitations, role changes, ownership transfer and sign-in security, in one settings surface every tenant gets.

Every way into your product: email and password, MFA, passkeys, magic links, one-time codes, social login and multi-device sessions, all under Better Auth.

The multi-tenant spine. Personal and team organizations with members, invitations and roles; every product row is keyed to its organization so tenants cannot see each other.

Authenticator-app enrollment with a verification challenge after password sign-in, plus backup codes for when the phone is gone.

Register, list and delete passkeys, then sign in with a fingerprint or face instead of a password. Standard WebAuthn, no extra service.

One-click sign-in links sent by email. Delivery runs through the same transactional email queue as the rest of the product, previewable locally.

Six-digit sign-in codes by email, for people who prefer a code to a link.

SMS verification codes behind an environment flag, with codes logged locally so the flow is testable before an SMS provider exists.

Google and GitHub sign-in that switch on when provider secrets are set, with the matching buttons appearing on the sign-in form.

Optional public handles alongside email identity, for products where people are seen by name.

Guest sessions for demos and trials, off by default, so someone can try the product before creating an account.

Several accounts or devices signed in at once, with a settings screen to review and revoke each session.

Remembers how each person signed in last time and highlights that method on the form next visit.

Google's returning-user prompt for one-tap sign-in, switched on by environment flag when you want it.

Sign-In with Ethereum for crypto-native products: wallet-based identity through the same session authority as every other method.

Point identity at any custom OIDC or OAuth provider. The escape hatch for when a customer brings their own IdP.

Operator tooling over accounts: list users, change roles, ban and unban, and impersonate for support. Separate from tenant-facing roles.

Keep Firebase as the identity source for phone, Google and email sign-in, and exchange its verified token for a session here. A migration path, not a rewrite.

Invite codes with attribution: each user gets a unique code, sign-ups are credited to the referrer, and a reward hook fires.

Instagram Business Login through the generic OAuth path, with the missing-email case handled and a helper for calling the Graph API afterwards.

One chokepoint for every outbound email, with local previews before a provider is set, and Resend delivery, sandbox protection and templates after.

A typed event catalog with redaction and consent state. Events log locally until a PostHog key is present.

A global error boundary and intentional test exceptions. Errors go to the console until a Sentry DSN is set.

Durable multi-step jobs that journal each step and replay after a deploy or crash. The pattern behind exports and every long-running task.

Private file uploads with authorized URLs, attached to product records. Storage on Convex by default, with complete Cloudflare R2 and Amazon S3 paths.

Real multiplayer rich-text editing with tenant-scoped access checks, server-side creation and plain-text search over document content.

The feature policy: plan defaults, kill switches, percentage rollouts, per-organization overrides and usage windows, every decision carrying a reason the UI can show.

The platform control plane: users, organizations, an audit explorer and password step-up before any privileged change.

A translation guide from SQL habits to Convex indexes — joins, unions, distinct, group-by and filters — each with a live demo on real data.

A deep dive on composing query streams: merging, joining, filtering and paginating across indexes without loading whole tables.

A realtime product table with column sorting, global search, filters and pagination. The pattern for every data grid you will build.

Schema-validated create and edit forms wired to server mutations, demonstrated on the same product catalog the tables render.

Transactional rate limits at the function boundary: token buckets for bursts, fixed windows for quotas, per-user keys, already protecting the hot paths.

Resumable, batched backfills that rewrite live tables without downtime. The same machinery this codebase used for its own schema changes.

Retries with exponential backoff for flaky third-party calls, ending in exactly one completion callback.

Named background queues with parallelism caps, so a burst of jobs drains in order instead of stampeding a downstream API.

The written contract for the codebase: authentication versus authorization, ownership planes, tenancy rules and copy-paste examples for each.

The provider matrix: what runs with no keys, what each vendor adds, how to remove one, and the smoke test that proves it.

Subscription billing with Polar as merchant of record behind a provider-agnostic adapter, webhook ingestion, and a bridge from plan to feature entitlements. A debug adapter simulates the whole path offline.

The Stripe path: subscription checkout, the customer portal, signed webhooks and tax collection, feeding the same entitlement bridge as Polar.

Marketplace and platform payments: onboarding sellers, routing charges between parties, and taking a platform fee.

Paddle as merchant of record: hosted checkout, subscriptions and VAT handled for you, mapped into the same feature entitlements.

Lemon Squeezy as merchant of record for indie pricing: overlay or hosted checkout and subscription webhooks into the same entitlement bridge.

Persistent chat threads with real model replies and retrieval over the organization's own documents, with citations. A debug assistant answers offline until a key is set.

Per-user daily usage counters for chat, API calls and exports, with an aggregate path that keeps dashboards and plan limits fast at scale.

Who is online, where, right now: heartbeat-driven presence with away detection, scoped to the organization.

When-this-then-that inside your product: record changes, inbound webhooks, cron ticks and meter thresholds trigger emails, signed webhooks, agent runs or tasks.

Scheduled AI agents that act on the tenant's data — weekly summaries, task triage, anomaly watch — journaled so failed runs replay instead of vanish.

From meter to invoice: immutable usage events, hourly window close, a push to your billing provider, and quotas that warn at 80 percent and block at 100.

An in-app notification center with a live unread badge, per-user preferences, muted types, and daily or weekly email digests.

One command palette over projects, tasks, documents, products and members, always scoped to the organization you are in.

A written specification for module add and remove tooling: the removability contract, module manifests and marked regions, with notifications and search as the pilot scope.

Customer-facing API tokens: generated once, stored only as digests, scoped to an organization and rate limited per key.

Let customers subscribe to your events: signed deliveries, retries with backoff, and dead-letters that stay visible with their last status code.

Password reset and recovery flows plus session review, with credential material living only in the identity layer, never in product tables.

A complete support desk assembled from shipped modules: SLA timers, transactional replies, notifications, search and an audit trail. Three new tables, no new infrastructure.

A complete deal pipeline assembled from shipped modules: a reactive board, bulk stage moves that fire automations, a live table and a computed forecast. Four new tables, no new infrastructure.