Distributed teams
Teams spread across time zones
See who is around before you ask, walk into a room to talk, and leave a written trail in chat and docs for the people who are asleep.
Features
One place to meet, build, and ship
Everything here flows from one idea: your team should have somewhere to be. Below is the whole catalog, from the floor people sit on to the audit log your security team will ask about.
The office
A real place your team shows up to, not a list of green dots.
Floor Editor
Draw your own office. Place rooms, seats, desks, walls, and furniture on a grid, set who may enter each room, and publish. Overlapping rooms resolve themselves as you drag.
Game Room
A built-in room with a console, an arcade cabinet, and bean bags. Start a party, invite the floor, play head to head. The social bit of an office that video calls delete.
Attendance
Room visits recorded as they happen, scoped to your organisation: who was on the floor, in which room, and for how long.
Meet and present
Talk, share, and record with everyone seated in the same room.
Collaborate
Think together on a canvas, a doc, a file, or a thread. All native.
File Storage
A drive with folders, moves, and per-organisation scoping, plus a registry that tracks every upload from every module in one place. Nothing gets lost because it was attached to a task instead of a doc.
Notices
Organisation-wide announcements that every member sees. For the messages that should not be a chat post scrolling away by lunchtime.
Plan and track work
Turn decisions into tracked work, logged time, and clear ownership.
Teams
Group people once and use that group everywhere: project membership, tracker assignment, and room access all read from the same team.
Daily Operations Report
One document each night covering hours logged, work shipped, and AI spend across the organisation, built at 01:00 in your own timezone and emailed to the owner as a PDF.
AI built in
An assistant in the room, a workspace at your desk, and an API for your agents.
Deskly Assistant
A floating assistant that can do the things you would otherwise click: create the task, find the doc, log the time. Pick the character that sits at your desk.
Platform and trust
The parts a security review asks about, shipped rather than promised.
Organisations
Run several organisations from one account and switch between them. Each brings its own members, roles, floors, and its own choice of which modules are switched on.
Roles and Permissions
Permission-based access, not an admin flag. Built-in roles, custom roles per organisation, and a per-person grant and deny matrix on top of them.
Audit Log
Every consequential action recorded with its actor, target, and time, queryable per organisation and exportable when someone asks you to prove it.
Notifications
One notification system delivering in app, by email, by SMS, and by push, through a queue that retries rather than dropping the message when a provider hiccups.
Admin Console
A separate operations panel for staff: users, workspaces, files, security, incidents with a status banner, runtime configuration, and live logs.
Solutions
Who it's for
The same office serves very different teams. Here is where to start, depending on yours.
Product & engineering
Product and engineering teams
Plan sprints on the tracker, sketch on the whiteboard, write the spec in docs, and talk it through in the room where the team already sits.
Meeting-heavy teams
Teams whose day is meetings
Schedule a meeting in a room, join it with one click, share a screen, record it, and read the minutes afterwards instead of taking notes.
AI-assisted teams
Teams working with AI
Use the AI workspace at your desk, and connect an assistant such as Claude over MCP so it can read your docs and update the tracker with your permissions.
Self-hosted teams
Teams that must keep data in-house
Run the app, the database and your own LiveKit media server with Docker Compose, behind two-factor sign-in, revocable sessions and an audit log.
Floor editor
Draw your own office
Admins build floors in a visual editor: rooms, seats, desks and furniture on a grid, and who may enter each room.
- 1
Draw rooms like furniture, not config
Drag rooms onto the grid, resize and rename them. Overlapping rooms push each other out of the way as you drag, and the floor is data, so nothing is permanent.
Floor editor · HQ Floor 2DraftRoomSeatDeskWallDecorDesign ReviewEngineeringLeadership - 2
Place seats where conversations should happen
Seats decide where people can sit, and every seat belongs to one room, so sitting down puts you in that room's call. Cluster them around a table or spread them along a quiet wall.
Floor editor · HQ Floor 2DraftRoomSeatDeskWallDecorDesign ReviewEngineeringLeadership - 3
Decide who may come in, then publish
Each room is open to everyone, shared with chosen people or teams, or private. Publish the floor and the new layout reaches everyone on it.
Floor editor · HQ Floor 2PublishRoomSeatDeskWallDecorDesign ReviewEngineeringLeadershipLeadership · access
Open
Shared
Private
Allowed
Scheduled calls versus a place
Video calls are good at scheduled meetings. They are poor at everything that happens between them, which is most of how work actually moves.
| Dimension | Scheduled-call tools | Remote Desk |
|---|---|---|
| Starting a conversation | Find a slot, send an invite, wait for the link | Walk into the room and unmute |
| Knowing who's available | A green dot that has been green since Tuesday | Who is in which room, on a floor you can see |
| Side conversations | Everyone in one call, or breakout-room admin | Separate rooms, each its own call. Walk between them |
| Cameras | Often on by default when you join | Off until you turn yours on, in every room |
| Your data | Their cloud, their terms | Hosted, or fully self-hosted on your own server |
Give your team somewhere to be
Every capability on this page is in the same workspace, behind one sign-in. It's free to start.