Beta codes

[amay-patel]

Do not merge in, not a P0 issue; we will review later

Description

• every person who joins our waitlist will have a waitlist code generated that we will distribute out later to each individual email address on waitlist (when we are ready for release).
• frontend changes include new component to direct to /beta-code and hooks.server.ts changes to protect certain routes when we release
• backend changes are just simple checkers for input passed from frontend.

Type of change

• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Considerations

• ci/cd needs to have waitlist table hosted and we need a migration script to move entries in old table to this table and generate unique beta codes

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
indeq	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 22, 2025 8:38am