Review in the browserSoon
The web app is the same review screen Studio has, in a browser tab, plus the management a desktop app is the wrong place for: projects, builds, branches, campaigns, members and billing. A link to a moment opens it for anyone on the team, with nothing to install.
Not open yetWhere it is
The web app lives at app.mulno.com, which doesn't answer yet. It is built: we signed in through it, played a real session with the browser's own player and reviewed the requests it makes against its content security policy, on a local stack. Until it opens, review in Studio: Review a session.
The web app lives at app.mulno.com, and Sign in on this site goes to it. A session a tester recorded into Mulno Cloud on production has been played in it, with the browser's own player and under its content security policy. Reviewing a Private-bucket project in the browser is Soon (how playback works). Studio stays the place for what only a desktop can do: Review a session.
1. What the browser gives you
- The review screen. Player, timeline, mixer, notes, drawings and the command palette (
Ctrl K), built from the same components as Studio's. The pop-out monitor is a second Studio window, so it stays in Studio. - Management screens. Builds & branches (Set live, Roll back, New branch, a Private project's storage, the campaigns on a branch), Members (roles, pending invites, seats) and Settings (the workspace, plan and billing, the audit log).
- Notes that reviewers share. Every reviewer's notes are in their own file, in one format. A reviewer can also set a note's status (open, in progress, fixed, verified) and reply. For Mulno Cloud a note goes through the api into our own bucket, under the signed-in email. For a Private project it will be written straight from the browser to your bucket with the reviewer's own key, and never touch our servers Soon.
Studio stays the place for what only a desktop can do: folders on your PC and network shares, working offline, live review of a session that is still recording, transcribing a tester's voice, and running mulno mcp on your machine. Across the campaign isn't available in the browser until the api has a route for it.
2. Sign in and make a workspace
- Accounts. New accounts come from the beta waitlist: one is created only for an address we let in, or one invited into a workspace. An existing account signs in from any country.
- No password. You enter an email address and pass a Cloudflare Turnstile check, and Mulno mails a sign-in link. The link opens a confirm page first; nothing is signed in until you confirm.
- Some places are closed. Mulno doesn't create an account for a request from the EEA or the UK for now. Existing accounts and testers aren't affected, and the page tells you in words, without saying whether an address already has an account.
- A workspace has a region: APAC (the default), EU or US, chosen when you make it and never moved. EU is a guaranteed jurisdiction for the workspace's rows, buckets and project indexes; APAC and US are location hints. An EU workspace can't create a campaign yet, because the broker that runs campaigns isn't regional; everything else in it works.
- Testers need no account and never count as seats.
3. How playback works, and who can read what
The browser plays the original recorded segments through Media Source Extensions: there are no proxies to make, and no second copy. It has been measured in Chromium-based browsers only, and not on phones. Whether a reviewer can play a project's sessions depends on the project's storage:
| Project storage | What lets you read a session |
|---|---|
| Mulno Cloud | Being a member. Our servers sign short-lived reads. |
| Private bucket Soon | Your own read key, held by a signer page on its own origin. Without one, the app says You need access to <project>’s bucket and never shows the moment. |
| Private bucket, lent key on Soon | Being a member: our servers sign the reads, and index the session for search and AI. The lent key |
Today the browser reviews Mulno Cloud projects. The signer page for a reviewer's own key is not at launch, so a Private project is not reviewed in the browser yet; Studio plays it from a bucket folder (Review a session).
The web app runs under a strict content security policy that names only the project's own bucket host, and only for a live member of that project. Anyone else gets a policy with no host in it and no hint that the project exists.
4. Links
A moment link is an https link that opens the moment for a signed-in member. Anyone else sees one generic page. See Moment links and trackers. Open in Studio hands the moment to an installed Studio as a mulno:// link.