Product tour · No sign-up required
See how EmberChamber works.
Three selected screens show the beta web interface from invitation preview to the signed-in workspace. No account, installation, or invitation is needed to view them.
Required onboarding happens between the first and second captures: invite acceptance, self-attested 18+ eligibility, email bootstrap, and device setup. These are product screenshots, not an interactive demo, and may differ from the latest build.
Step 01
Review an invitation
Joining begins with an invitation rather than a public people directory. The preview identifies the invited space, who issued the link, and the access rules before account setup.
- Current state
- A signed-out visitor is reviewing an invitation.
- Primary action
- Choose whether to begin the protected join process.
- What follows
- Accepting continues to eligibility confirmation, email bootstrap, and device setup.

Step 02
Review profile and recovery settings
After onboarding, the signed-in settings workspace keeps profile, privacy, session, and recovery controls together without creating a public identity page.
- Current state
- The account and device are set up, and the profile has been saved.
- Primary action
- Review or update the private profile and account controls.
- What follows
- Return to the workspace to start or continue a conversation.

Step 03
Start a conversation
The web companion provides a conversation workspace alongside the native clients. This capture shows the interface after a first message; it is not a live chat or a test of encryption.
- Current state
- A signed-in member has opened a direct conversation.
- Primary action
- Write and send a message from the browser workspace.
- What follows
- Conversation history and private-content search remain device-local.

Next, look under the hood.
See how device-local state, a delivery relay, and multiple clients fit together. The case study includes source links and the tradeoffs still being worked through.
Before using the beta, review its privacy and recovery boundaries.