New Here
See how EmberChamber works
Start with the trust model, current scope, and where your data actually lives.
Best when you are evaluatingTrust model firstDownload status stays visible
Start Here
Pick the quickest correct path.
Start with the trust model if you're evaluating EmberChamber. If you already have access or an invite, take the shortest route from here.
Invite-only access
Adults-only beta
Evaluate
Review the trust model, relay boundary, and current beta scope in one pass.
Join
Invite-only onboarding and sign-in both start here without public discovery.
Continue
Check the posted Android and desktop builds when you want a longer-session client.
Have An Invite
Join the beta
Bring the invite token and the private email that will stay tied to access and recovery.
Best when your invite is already liveInvite token + private emailShort staged onboarding
Already Have Access
Sign in with the same private email
Use the email tied to this account so the right sessions and recovery path follow you.
Best when the account already existsSame private emailSupport remains available if state drifts
Need A Client Build
Check the posted clients
See what is posted for Android, Windows, and Ubuntu when you want an installed client.
Best when you want an installed clientAndroid build statusWindows and Ubuntu releases
Typical Path
Most people only need three moves.
01
Start in web
Review the boundary, confirm access, and get the first session running without an install.
02
Keep the same private email
Use one inbox for invite, sign-in, and recovery so the account state stays consistent.
03
Install a daily-use client when you want one
Android and desktop builds are there when the browser stops being enough.
Keep It Simple
Keep the account state clean.
Keep the same private email attached to invite, sign-in, and recovery.
Give every device a readable name before you add it.
If something feels unclear, ask support early instead of forcing the wrong flow.