Skip to content
MONO for teams

The collaborative GPT for companies.

A GPT is for working alone. MONO is for your whole team, together.

Everyone opens the same files, the same board and the same conversations, live. MONO works there too: it edits next to you, proposes changes, waits for approvals and keeps the plan moving.

Windows · Mac · Linux — your team's own server comes with it

What is MONO?

MONO is a desktop app for Windows, Mac and Linux that puts a team's conversations, people, files and data, board and browser in one window, with an AI agent working inside. Every account gets its own server — its box — where the files, databases, vault and agent live. MONO picks the best AI model for each task (Claude, GPT, Gemini and others), and it never sends, charges or publishes without a person's approval.

Who is it for?

For teams — agencies, sales, operations and professional firms — that want to work in the same files with AI inside, instead of each person alone in a chat. It also works for one person.

From one to everyone
01

Today: one person, one chat.

A chat assistant is great when you work alone. But the answer stays in your thread: your team doesn't see it, can't fix it, and starts again from zero.

02

MONO: the team in the same place.

Ana, Vero and Joe open the same conversation, the same document and the same board. Everyone sees what the others are doing, while they do it.

03

And MONO works with all of you.

Ask @MONO in the team chat. It edits the sheet next to you with its own cursor, proposes changes you accept or discard, and asks before anything leaves the box.

Cursors and locks

Everyone in the same file, nobody stepping on anyone.

You see who's where, live. When someone is editing a row, a card or a section, it's held with their name — and instead of overwriting each other, you ask for control.

  • Cursors with names on sheets, documents and the board.
  • Locks that expire on their own if someone walks away.
  • Ask for control: the other person hands it over with one click.
Proposals

MONO proposes. You decide.

MONO doesn't rewrite your work behind your back. It splits the card in two: what's there now, and what it proposes. You accept it, or you discard it.

Comments

Comments where the work is.

On a card, a cell or a paragraph. They arrive live for everyone in the room, and MONO reads them too when you ask it to pick up the thread.

A comment from a teammate arriving live on a board card
The board, with the plan

Ask for something big. MONO breaks it down.

MONO turns a request into cards — with who does what — and moves them as the work moves. What needs a person lands in «Waiting for you».

Meetings

Meetings that end in tasks.

Any call, no bot joins. Live transcript, ask MONO mid-meeting, and when you hang up: summary, agreements and tasks on the board, with owners.

A live meeting transcript with the panel to ask MONO
Approvals

Sending, charging, publishing: a person says OK.

MONO can draft the email and prepare the charge, but it stops in «Waiting for you» — with why, who asked and from where. Your team works fast; nothing leaves without someone deciding.

How security works

The «Waiting for your OK» screen: each request with its reason, who asked and when
Levels

Invite your team with the right level.

Each person gets what they need, and the box enforces it — not the honor system.

Can look

Asks your data and sees what already happened. Changes nothing.

Can work

Edits the board, sheets and documents of your projects, runs what already exists and writes to your databases. Can't spend, publish, send out of the box or invite.

Partner

Can do everything you can. Give it only to someone who already decides with you.

Guest

Someone outside your team who reaches only the app you share with them.

Measured, not promised

What server your team needs — 3, 10, 25 people.

We put 3, 10 and 25 people typing in a document, moving cards and editing rows non-stop, with cursors moving 20 times a second. The worst case of collaboration — and this is what the box did.

3people
CPU peak17.6 %
cursor p95, same region8 ms
changes lost
0
log vs. what was done
73/73
10people
CPU peak30 %
cursor p95, same region9 ms
changes lost
0
log vs. what was done
178/178
25people
CPU peak59 %
cursor p95, same region51 ms
changes lost
0
log vs. what was done
403/403
TeamServerWhy
1–33 vCPU · 4 GBCollaborating doesn't show (<20% CPU). What weighs here is the rest: browser, video, workers.
4–104 vCPU · 8 GB30% peak with 10 typing at once; room for the browser and workers at the same time.
11–258 vCPU · 16 GB · two tunnels25 fit in 4 cores (59%), but the tunnel hits one core's limit: it has to be split in two.

Measured on 10 Oct 2026 with 4 shared vCPU in Virginia. From Mexico the floor is distance (~100 ms p95). Today every box starts at the 1–3 size.

Pick the size when you sign up Two tunnels for teams over 20
Measured with 25 people

25 people in the same sheet. 0 changes lost.

Everyone typing at once for a minute, MONO suggesting in the middle: no change lost, someone else's cursor in 51 ms (p95, same region), and all 403 actions in the log.

See the whole measured table A team bigger than 25? Talk to us

Put your whole team to work. Together.

Download MONO, invite your team, and ask for the first thing.