Short answers for launch, auth, data handling, and support questions with current provider scope.
Accounts
- Sign in with email/password, magic link, or GitLab OAuth. GitHub repository integration, Bitbucket, Azure DevOps, and Gitea remain roadmap surfaces.
- Forgot password flows use Supabase email recovery and the existing auth callback route.
- Cloudflare Turnstile protects /login and /signup when NEXT_PUBLIC_TURNSTILE_SITE_KEY and TURNSTILE_SECRET_KEY are configured.
- If auth is unavailable in local development, check NEXT_PUBLIC_SUPABASE_URL and NEXT_PUBLIC_SUPABASE_ANON_KEY.
- Use PREMORTEM_AUTH_DISABLED=1 only in local verification mode, never in production.
Launch
- The public site, docs, and auth pages share the same visual system and branding.
- The product keeps raw repository context transient and stores structured audit artifacts for review.
- Search indexing is supported through robots.txt, sitemap.xml, and social metadata.
- Stripe stays in test mode until live keys and the catalog are configured.
Support
- Use the docs hub for setup, guides, and troubleshooting.
- If a page errors inside the reviewer console, retry from the route-level error view.
- Alert fatigue is reduced by consensus validation and dedupe clustering before reviewer exposure.
- Auth callback errors usually mean the external code exchange failed or the callback host did not match the canonical app URL.
- For product issues, contact the team through the published support email.
Privacy and data
- Premortem uses Supabase for auth and persistence while the rest of the stack keeps domain data in the configured services.
- Organization-scoped access controls and RLS are used to separate tenant data.
- The product documents privacy and terms publicly, and the auth pages link to both before login.
- If your deployment requires a zero data retention or no-training LLM contract, choose a provider plan that explicitly offers it.
Was this article helpful?
