Skip to main content
XodUs
LoginSign up

Public workspace creation

Create your AI PM workspace

Name the workspace and organization, verify the Owner account, then continue directly into onboarding with the first project path already prepared.

Account details

The form validates locally first, creates the tenant and organization metadata, requests a Supabase signup session, then exchanges a verified token with XodUs before onboarding starts.

This creates the XodUs tenant and makes this account the first Owner.

Leave this blank to use the workspace name for the organization.

Use the email that should own the first XodUs workspace.

The strength meter updates locally before any network request.

Confirmation is checked before Supabase or XodUs receives a request.

  • Use at least 8 characters for the password.
  • Workspace creation makes the first verified account the tenant Owner.
  • Authenticated signup continues to onboarding without a detached success page.
  • Verification-pending signup returns to sign in with a visible recovery path.
Already have an account? Sign inBack to landing

AI PM runway

Keep the first setup light.

Signup should feel like the first step of activation, not a detached account gate.

Prepared onboarding

Successful signup continues to the five-step activation flow at /onboarding.

Safe verification

Email verification can pause account creation without inventing auth truth.

Workspace continuity

Workspace, organization, project list, and onboarding status checks decide the first authenticated route.

Signup completion proof

Signup trust chain

Account creation keeps provider signup, backend exchange, onboarding handoff, verification recovery, accessibility, and performance evidence visible in one route.

  1. 01Provider session

    POST /auth/v1/signup carries workspace and organization metadata before XodUs accepts a workspace session.

    Review identity
  2. 02Backend token exchange

    POST /api/v1/auth/login exchanges the verified Supabase token, bootstraps the first Owner, then GET /api/v1/projects resolves workspace context.

    Trace exchange
  3. 03Onboarding handoff

    GET /api/v1/onboarding/status decides whether the next route is /onboarding or an already prepared workspace.

    Preview onboarding
  4. 04Verification recovery

    Pending verification returns to sign in with a clear message instead of faking an authenticated state.

    Open sign in
  5. 05Accessibility and performance

    Labels, hints, status regions, keyboard links, CSS layout, and the local strength meter stay visible without route-owned runtime observers.

    Inspect route
XodUs
LoginSign up