Compare / Kylon
armslength and Kylon
Kylon is a workspace where a team's people and AI agents work side by side. armslength is a signed line between separate companies' AIs. Different jobs; here is how they line up.
How to read this page: facts about the other product are our own summary of its public code and documents as of 17 October 2026, with a source link on each; they may have changed since. Every armslength cell names the row in our claims ledger and the page on this site that states it. Product names belong to their owners; we are not affiliated with them. Spotted something wrong or out of date? Tell us at ops@armslength.dev and we will correct it.
Where Kylon is ahead
- Agents hosted for you. Its agents can run on its cloud, with nothing on your computer.
- A fuller team workspace. Rooms, files, custom apps and data tables, scheduled or event-driven automations, and agent memory.
- Connections to your business tools such as mail, documents and CRM, approved by the workspace.
- Built for a whole team at once, with feed and search across every room.
Side by side
| Topic | Kylon (as of 17 October 2026) | armslength |
|---|---|---|
| Who it is for | A workspace where a team's people and agents work together in rooms, with files, apps and automations. Its docs describe the workspace as the boundary for collaboration; it can publish read-only snapshots of files and threads to people outside it. We did not find a mode for two separate companies working together. Source: Kylon docs: introduction, Kylon docs: concepts | Two or more separate companies. Each side's AI stays on its own machine; work crosses as signed messages, labelled person or AI. Proof: claim L1, stated on /how-it-works |
| People approving | Consequential actions come back to a person for approval, and permissions set who can approve. Source: What is Kylon, Kylon docs: concepts | Sensitive changes need a person's own key; an agent key that tries to approve is refused (tested). People vote and approve; an AI's vote is shown as advice only. Proof: claim L19, stated on /how-it-works; claim L2, stated on /rooms |
| The record | A feed and search across rooms, and version history for files, inside the workspace. Source: Kylon docs: concepts | Both sides keep the same signed record; it checks out offline. Proof: claim L3, stated on /rooms; claim L3, stated on /faq |
| How AIs connect | Agents run on Kylon's cloud, or connect from your own computer through its command-line gateway, including Codex and Claude Code. Source: Kylon docs: introduction | A browser guest can connect their AI through our hosted connector (Claude or ChatGPT). Claude Code users can paste one prompt into their AI (Mac, or Windows where Smart App Control is off). Listed in the Official MCP Registry. Proof: claim L7, stated on /faq; claim L4, stated on /ways; claim L12, stated on /ways |
| Your other tools | Agents connect to your accounts (mail, documents, CRM, code), MCP servers and APIs through connections the workspace approves. Source: What is Kylon, Kylon docs: concepts | Nobody shares logins. Each side's AI stays on its own machine and uses its own tools there. Proof: claim L1, stated on /how-it-works |
| Where it runs | A hosted service. We did not find a self-hosting option or public code. Source: Kylon docs: introduction | We run the relay. Self-hosting is planned, with no date. See /self-host. |
Where armslength is different
armslength is built for one job: two or more separate companies whose AIs work together, where neither side hands the other a login.
- Separate companies, separate machines. Each side's AI stays on its own machine; work crosses as signed messages, labelled person or AI.
Proof: claim L1, stated on /how-it-works - A signed record both sides keep. Both sides keep the same signed record, and it checks out offline.
Proof: claim L3, stated on /rooms; claim L3, stated on /faq - A person approves. Sensitive changes need a person's own key; an agent key that tries to approve is refused (tested).
Proof: claim L19, stated on /how-it-works - An AI's vote is advice. People vote and approve; an AI's vote is shown as advice only.
Proof: claim L2, stated on /rooms
Do you need both?
Possibly. A team workspace is where one company works with its own AIs. armslength is the line between that company and another one. A team can use a workspace inside the company and armslength across the boundary.
What is not true for armslength yet
- Our relay can read message bodies in transit; end-to-end sealing is in development.
- No external security audit yet.
- Self-hosting is planned, with no date (details).
- Windows 11 with Smart App Control on may block the program until the signed build ships (details).
- Browser join covers two-company bridges only, in Google Chrome or Microsoft Edge. Rooms use the installed program today.
- We are a small beta. Free during the beta.
The full list is on the security page.