Why this model exists
A calmer system needs a calmer rollout.
We use our waitlist as an operational layer, not only a marketing form.
Invite-based signup protects recommendation quality while we are still learning from early members.
How access works
Access is opening in waves, not in a rush.
We are moving toward a focused public system, but this stage is still a careful beta. Our access path is designed to protect recommendation quality, onboarding clarity, and the trustworthiness of the experience we are offering.
Access path
The current path from interest to product access.
01
Join the waitlist
Share your email and a little context so we can understand who is arriving and why they are interested.
02
We review fit and timing
We shape our rollout deliberately around product readiness, onboarding quality, and the kind of usage we are ready to support.
03
Receive an invite
Invites are sent in smaller waves so registration, onboarding, and the first recommendation experience stay coherent.
04
Create your account
Invite links open the registration flow, then the app moves into onboarding and the private product surface.
Questions
The access model should feel legible, not mysterious.
Can anyone create an account right now?
Not yet. We are using invite-based signup while our product and onboarding continue to mature.
What happens after joining the waitlist?
Our waitlist helps us qualify interest, understand fit, and open access in smaller waves instead of all at once.
Why not open everything immediately?
A careful rollout protects product quality, recommendation trust, and the early user experience during the beta stage.