Kit ServiceWorkspaces
A floating, multiplayer operating system inside a browser tab. Arrange terminals, displays, code editors, and dashboards from any number of containers in one layout — and share the whole thing with a URL.
$ bun test
✓ 142 passed
$ _
Compose containers
Drop any Kit service — terminal, display, code, files, sqlite — into a floating window. Mix services from different containers.
Share a URL
The entire layout is encoded in the address bar. Paste the link to a teammate; they see the same arrangement, live.
Orchestrate live
Every window stays connected — terminals stream, displays render, file changes propagate. No page refresh, no glue code.
A workspace is an HTTPS endpoint
No installer, no desktop agent, no VPN tunnel. Everything runs inside a single browser tab and speaks plain HTTP — which is why sharing, embedding, and auditing just work.
Emily Watson
Platform Lead
Michael Lee
Infrastructure
Desktop apps to install
Services per workspace
To share everything
From click to live session
Powerful primitives, seamlessly integrated
A workspace composes the Kit — 14 single-purpose services that each speak HTTP. Drag any of them into a floating window and they interoperate automatically.
Shell
Visual
Automation
Orchestration
From empty tab to shared OS in four moves
Spin up a workspace the same way you open a gist — one URL, no agents, no config files. The moves below run in the order you'd take them in real work.
- step · 0101/04
Open the workspace URL
Navigate to workspace.hoody.com and the floating WebOS boots in the tab. No login prompt, no loading spinner per tool — the shell is static HTML.
https://workspace.hoody.com/?project=abc123 - step · 0202/04
Drag in your services
Open a terminal window, a display for your GUI app, a file manager, a SQLite UI — each is an iframe pointing at a Kit endpoint. Resize and tile freely.
+ terminal · display · code · files · sqlite - step · 0303/04
Send the URL
The layout, the containers, the welcome iframe — all encoded in query params. Your teammate opens the same link and lands in the same arrangement.
?folder=/workspace&id=5&welcome-iframe-url=... - step · 0404/04
Collaborate live
Multiplayer is the default. Cursors, terminal scrollback, and display state sync in real time across everyone connected to the URL.
GET /api/v1/agent/workspace → [ collaborators: 3 ]
What a workspace replaces
Every item below used to need its own browser tab, desktop app, VPN rule, or admin console. Workspaces absorb them into one URL you can email.
Setup
Open a URL vs install, VPN, SSO, agents.
Sharing
Paste the URL vs screen-share software and seat licenses.
Multi-container view
Native — drag-and-drop tile vs N browser tabs or an RDP session.
Multiplayer cursors
Built-in vs nothing in most admin tools.
Audit trail
Every action is an HTTP request vs scattered across 6 systems.
Embed in your app
iframe src=workspace.hoody.com vs not supported anywhere.
Works on a phone
Yes — browser tab vs RDP clients only on macOS / Windows.
Cost per seat
Pay per container, not per user vs tiered per-seat licensing.
24 Endpoints. One WebOS.
Create and manage workspaces, control floating windows, share layouts, take snapshots, and stream live events — all over plain HTTP.
Workspace Management
{count, plural, =1 {# endpoint} other {# endpoints}'}POST /api/v1/workspaces → { id: "ws_abc", name: "Dev" }
Windows & Layout
{count, plural, =1 {# endpoint} other {# endpoints}'}PUT /api/v1/workspaces/:id/layout → { panels: [...] }
Share & Snapshots
{count, plural, =1 {# endpoint} other {# endpoints}'}POST /api/v1/workspaces/:id/share → { url: "..." }
System & Events
{count, plural, =1 {# endpoint} other {# endpoints}'}GET /global/event → SSE stream of workspace events
Put your whole stack in a browser tab
Workspaces is one of 14 Kit services bundled with every Hoody container. There is nothing to install and nothing to configure — the URL is the product.
- Zero installation
- Shareable via URL
- Multiplayer by default
- Works on any browser
- Embed anywhere