A cloud desktop that many people — and AI agents — can drive at once. Here's why we built it, and what it took.
"Can you see my screen?" is not collaboration. It's narration.
You've lived it. One person drives, four people describe what to click. Files get exported, mailed, re-imported. Control gets "requested".
Developers get the worst of it: environments that drift until "works on my machine" becomes a shrug, bugs that only exist in CI, whole afternoons rebuilding a setup that worked last week.
And it's not just engineers. Support agents describe fixes they could just perform. Back-office teams pass one spreadsheet around a call like a talking stick.
These look like different problems. They're one problem: every computer you've ever used was designed for a single user, and everything built on top inherits that assumption.
So we broke the assumption.
We're developers. We've lived every version of the pain on this page: pairing over screen shares, environment drift, CI failures nobody could reproduce, production ops done over someone's shoulder.
In 2020 we started building the machine we wanted to work on: a real Linux desktop in the cloud where every participant is a first-class user. No host. No guest. No requesting control. Everyone brings their own cursor and keyboard to the same machine.
Then something happened that we didn't plan: people who had never opened a terminal started showing up. Support teams fixing things with customers instead of narrating at them. Teams running their admin work in one shared desktop. Taking turns, it turns out, was everyone's problem.
Today, Cyqle is a cloud computer where collaboration isn't a feature we added. It's the assumption we started from.
A full Linux desktop, live in your browser in seconds. Share one link and your team is inside — each person with their own cursor and keyboard, all acting at once.
Collaboration is on every tier, including the free one. It's not the upsell. It's the point.
An agent trapped in a chat box can only talk about work. Give it a computer and it can do the work: open apps, run commands, browse, manage files.
On Cyqle, every agent gets a real desktop. Boot a clean machine per run. Configure once, snapshot, and clone it for parallel runs. Drop pre-warmed desktops into CI pipelines. Tear it all down when the job is done.
And because the desktop is multiplayer, the agent is just another user at the machine. You watch its cursor move in real time. If it stalls, you grab your own cursor and take over — same session, no ceremony.
Teams already run Factor, our in-house agent, this way — and bring their own agents, too.
None of this exists off the shelf. At every layer there was a shortcut available — and taking it would have broken the promise.
The usual shortcut: Overlay cursors painted on a video stream
What we built: Real input devices for every participant, injected at the operating-system level
The usual shortcut: A relay server in the middle of every session
What we built: Peer-to-peer session streaming — no server in your data path
The usual shortcut: A delete button and a promise
What we built: Every session encrypted with its own key, destroyed on close — cryptographic erasure
The usual shortcut: Isolation the session enforces on itself
What we built: Airtight isolation around every desktop, enforced beyond the session's reach
The usual shortcut: A cold machine and a setup script to wait on
What we built: Fully configured desktops booting in seconds from pre-warmed snapshots
Years of infrastructure so the experience stays one click.
encrypted · running
Every desktop of the last forty years assumed one user. We think the next ones assume many — machines that people and agents share, summon, and discard as easily as a browser tab. We're building toward that:
A desktop in seconds. Invite a teammate, or send in an agent. Free tier. No credit card.