Article
Auth and guest mode
Understand login, guest access, account conversion, and where each path should lead users.
The SvelteKit template supports both registered accounts and guest sessions. The goal is to reduce friction before a user commits to sign-up.
Registered account flow
- Public entry:
/auth/login,/auth/register, and/login - Supported modes: email today; Google/GitHub OAuth when configured in later stages
- Post-login destination:
/dashboard
Registered users should land on the activation-oriented dashboard homepage and continue from there into AI, keys, billing, or support.
Guest flow
- Public entry:
/guest-demo - Guest sessions are real authenticated sessions with their own credits and dashboard access
- Guests should be encouraged to upgrade after they validate the workflow
Upgrade guidance
Guest mode is ideal for:
- early product demos
- marketing traffic that is not ready to sign up
- sales conversations where you want a lower-friction proof point
Registered mode is ideal for:
- persistent usage
- billing and subscriptions
- API key management
- long-term project ownership
Product recommendation
Do not treat guest mode as a dead-end sandbox. It should behave like a guided first session that naturally leads into account creation once the user sees value.