A virtual office for remote engineering teams.
Engineers need long stretches of focus and quick answers when they're stuck. TinyFloor gives you both: quiet by default, and a teammate a short walk away.
One price for the whole team · No card needed
By Jitto Joseph
An engineering day on the floor
Engineers need two things that pull against each other: long stretches without interruptions, and a quick answer when they're stuck. A floor gives you both, because you can see who's heads down before you walk over.
- 1.
- 2.
Heads down
10:15
Set yourself busy. You're still on the floor, so people know you're working, and they know to wait.
- 3.
Unblocked
14:30
Stuck on a failing build? See who's available, walk over, share the logs and sort it out in ten minutes instead of tomorrow.
- 4.
Review
16:00
Two or three people in a meeting, one sharing the pull request, talking it through instead of forty comments.
What an engineering team needs, and how the floor covers it
| Need | On TinyFloor | Keep elsewhere |
|---|---|---|
| Focus time | A busy status. Nobody hears you until you start a call, and there's no open microphone. | Your editor and your notification settings. |
| Quick questions | Walk up to whoever knows and tap to call. Voice first, screen share in one click. | — |
| Pairing | A call with a shared window, and a third person turns it into a meeting. | Live Share or Code With Me, if both of you need to type. |
| Standups and demos | The main meeting, always open, with screen sharing. | — |
| Incidents | A meeting named after the incident that anyone can be asked into. | Your alerting and status page. |
| Written decisions | Channels and direct messages that keep their history. | Pull requests, tickets and docs. |
Quiet by default
- No open microphones. Being on the floor doesn't mean being heard. Sound only starts when someone starts a call or you join a meeting.
- Statuses people set themselves. Available, busy or away, chosen by you. Nothing reports how long you've been at your desk or how long you've been idle.
- Cameras that rest. Calls start with voice. A camera left on through ten minutes with nobody talking turns itself off.
- No pings to come back. TinyFloor doesn't send emails or notifications to pull people onto the floor. The tab's title shows unread messages, and that's all.
Running an incident on the floor
- Open a room for it. Start a meeting named after the incident and ask in whoever's on call. Everyone on the floor can see who's in it, so nobody has to ask what's going on.
- Share what you're looking at. Dashboards, logs and the deploy pipeline on screen, so everyone is looking at the same thing.
- Bring people in, then let them go. Ask in the person who wrote the service; when they've answered, they walk back to their desk.
- Write it down. Post the timeline and what you changed in a channel while it's fresh, ready for the write-up.
How it fits beside your tools
TinyFloor runs in a browser tab next to your editor, terminal and chat. It doesn't connect to GitHub, GitLab, Jira or Linear, and it doesn't post into Slack. That's deliberate: it's where the team talks, and the work stays tracked where it already is. Many teams keep Slack for written messages and use TinyFloor for presence, calls and meetings.
Common questions.
Does TinyFloor connect to GitHub or Jira?
No. TinyFloor is where you talk, not where the work is tracked. Share your screen to look at anything together.
Is it good for pair programming?
Yes. Walk up to a teammate, start a call and share your screen. Add a third person and it becomes a meeting.
How big can an engineering team be?
Pro is made for a small team, up to 15 people in one office. Larger organisations give each team an office of its own.
Can we keep Slack?
Yes. Plenty of teams keep Slack for messages and use TinyFloor for presence, calls and meetings.
Still wondering? Try the demo office and see for yourself.
Related guides.
Keep exploring.

Give your teama floor to share.
14 days of Pro for every new office · Runs on Cloudflare
