Auth entry
This entry surface now reflects the real requested and resolved auth posture for the current build, so demo-safe access and unwired external auth stay equally explicit.
Clerk is configured as the external auth provider. Sign in to start a provider-backed session. The trusted destination currently points to dashboard home.
Requested auth
External
The auth mode requested by environment or explicit server-side config.
Resolved auth
External
The actual auth posture resolved by the server for this request.
Provider
Clerk
External auth mode is configured with Clerk. Sign in to start a provider-backed session.
Dashboard home
This destination is being preserved through a trusted local-only return path.
/dashboard
Clerk is configured as the external auth provider. Use the sign-in button to start a provider-backed session.
The auth posture is resolved on the server and the local identity bridge will bootstrap a workspace on first sign-in.
This destination is being preserved through a trusted local-only return path.
Need the future account-creation route? Create an account
These routes intentionally reflect the real server-resolved auth posture instead of fake local forms. That keeps demo access ergonomic while leaving the external-provider gap explicit.
No active session is available for this request.
That is expected while external auth is requested but still unwired. The route stays visible so the provider-backed flow can attach here later without changing the surface contract.
Start a provider-backed sign-in through Clerk. RebirthIQ will resolve or bootstrap a local workspace after the provider callback.
Return to the marketing entry while auth remains unwired.