Skip to content
AlphaBase
HomeDocs

Hosted Multi-Tenant

Hosted organization setup guidance for secure multi-tenant use.

This page is intentionally high-level for public docs.

For hosted AlphaBase organizations:

  • tenant isolation controls are enabled by platform policy
  • workspace access is scoped by org membership and roles
  • security contracts and signing details are kept in private operator runbooks

What Operators Should Do

  1. Create tenant organizations and workspace structure.
  2. Enforce least-privilege role assignments.
  3. Enable audit retention and periodic access reviews.
  4. Run tenant isolation validation before release promotion.

Account Login Branding

For hosted launches, configure social login behind a branded auth domain before enabling Google or GitHub buttons.

Set ALPHABASE_SUPABASE_AUTH_URL to the activated Supabase custom or vanity auth hostname. If this is not configured and the app only has a default Supabase project-ref URL, AlphaBase blocks social OAuth and keeps email/password plus magic-link auth available.

Verification

Run your release verification gates:

Terminal window
npm run test:tenant:isolation
npm run test:launch:gate