Umbra status
Whether the services behind Umbra are healthy right now, and a running log of what we have shipped and improved. No account details and no infrastructure — just what is up, and what changed.
Licensing
Activation and plan checks when you sign in to the app.
App updates
Delivery of new desktop versions and the update check.
Sync & backup
Encrypted cloud backup of your Accounts and proxies.
Team relay
Team decision boards and phone-paired remote checkout.
Website & dashboard
This site, sign-in, and your account dashboard.
Recent changes
what we have been building- Oct 2026Improved
Remote checkout: open any Account from your phone
Pick an Account on your phone, paste a link and press Open: the desktop opens it on its own connection, signed in, and your phone drives it. The desktop now reconnects by itself and stays awake while Remote control is on, a link from the phone loads only on the Account’s own connection, and the phone says plainly what went wrong when something does.
- Sept 2026Shipped
Umbra 2.0 — out of beta
The first release outside the beta programme. Since the last public build, every session has been checked end to end for leaving only through its own connection; bot checks inside pages and background workers see the Account rather than your computer; the connection list tells you what each one really is — HTTPS, HTTP, dead, or deleted — and warnings say what actually happens rather than what might. The download page shows which builds are published right now; the macOS build follows once it can be notarised.
- Sept 2026Shipped
Sign in to Ticketmaster with a passkey
A Ticketmaster Account can sign in with your Mac’s passkey instead of a password, on Ticketmaster’s own page inside that Account’s session. The key stays with Ticketmaster and your device — Umbra never sees it, and deleting the Account does not remove it. It needs the signed macOS build; everywhere else the Account shows passkeys as unavailable.
- Sept 2026Shipped
Decide per Account and per site whether a website gets your location and notifications
Location and notifications stay allowed by default, and any Account can now block or allow them for every site or for just one — a blocked site is told no, as a normal browser would tell it. Decisions are kept with the Account and apply in its Umbra sessions to pages opened or reloaded after you choose; the separate external browser keeps asking for itself. The location a site can be given is always the Account’s, never your computer’s.
- Sept 2026Improved
Bot checks inside a page see the Account, and sessions leave only through their proxy
Frames a page embeds from other sites — where bot checks run — and a page’s background workers now present the Account rather than your computer, the window sits on the Account’s screen, and the newer graphics interface names the Account’s chip. A proxy rule that let a page send certain one-word addresses out on the home connection is closed, blocklist checks travel through the proxy being tested rather than your own connection, the app’s own windows fetch nothing on their own, a session says when the hardened engine could not carry it, feedback reports are stripped of credentials, the setup card can complete, and the drop screen no longer warns about payment details it cannot see.
See the full changelog — every change, in more detail.
Seeing something we are not? Contact support — a person reads every message.