Because it runs on your hardware, not ours. We sell hardware — the Access line, and CEC's custom builds — and two services: a real technician's time by the minute, and a Private Line for people who want relay servers of their own. The app, the mesh, and the always-on 1 Mbps relay cost us almost nothing per user, so we don't bill for them.
Same itch, different animal. A VPN answers "how do my machines reach each other?" by building a network — a subnet with IPs, ports, and rules to manage. This mesh answers it with routes: your devices carry capabilities (a screen, a shell, a folder), and the graph connects exactly the pairs you've granted, for exactly as long as a route is live. The Private Line runs that introduction layer on servers of your own — VPN-grade exclusivity, on a mesh that was already private by design. See how the layers fit together →
Streams travel directly between your devices, encrypted end to end — keys live on your machines, not on a server. When a relay has to carry traffic, it passes data it can't decrypt. A Concierge session starts with your approval, shows only what you approved, and we can see that a session happened (for billing), not what was on it.
Your devices are on your local network, so they keep talking to each other — consoles, terminals, files, all of it. Discovery stays local too: peers on the same LAN find each other over mDNS, no server involved, so you can even claim a new device with the internet down. You lose reach from outside the house and you lose Summon, and both come back the moment the internet does.
It announces itself over mDNS on a claim channel that never leaves your LAN — no IPs to type, no cloud round-trip, and it works before the device even has the right time. It appears in your app's claim sheet, you tap Claim, and it joins your fleet. Claiming over the internet is off by default; if you turn it on for a device, it uses a rotating, hard-to-guess code instead of an open door. The same-room shortcut, explained →
No. The code is MIT-licensed, the introduction servers are settings you can point at your own box, and any hardware you buy keeps working without us. Cancel everything and every device keeps running the app. Your data never lived on our side to begin with.
The software needs a live OS to run on. The Access line is for the days there isn't one — crashed, frozen, stuck in BIOS, or refusing to boot. A witness watches the machine's video signal and presses its buttons, so it stays on your graph with its OS gone. Watch it save a machine.
Yes. Each one runs AllMyKVM — CEC's open firmware fork — and stands on its own as an out-of-band console. The app is what puts it on the same graph as everything else you own — but no subscription, account, or cloud is ever required to use hardware you bought.
Only what you approve, only while you allow it. A session starts with your explicit yes, shows just what you approved, is logged end to end, and you can watch live or pull the plug mid-session. $25 per 15 minutes, $20 with a plan — by invitation while we grow the team. The three ways to pay.
Normally your mesh calls out at a shared, public venue, with a free 1 Mbps relay when a direct path is blocked. The Private Line is a venue of your own: your own signaling, STUN, and TURN at 1 Gbps with unlimited bandwidth, serving your devices and nobody else's — like calling them home instead of meeting in public. $10 a month, cancel anytime, and the free shared venue is always there underneath. Compare it to the free layer.
Yes — that's the Private Line's free, do-it-yourself twin. AllMyStuff already runs the open-source MyOwnMesh daemon under the hood; put that same daemon on a box you keep online, switch on its signaling / STUN / TURN roles, and point the app's Settings → Networks → Servers at it. Your introductions then run on hardware only you own. We wrote the whole thing down, step by step. Self-host it free →
Still curious? The code answers everything the copy doesn't.