Skip to content
Enterprise

A big team, one MONO.

Talk to us. We size it with you.

With many people, what changes isn't the app — it's the server under it, who can do what, and who answers when you write. Tell us about your team and we'll tell you, with numbers, what you'd need.

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.

What changes with many people

Same app. A server and rules your size.

A server your team's size

Every account has its own server. For a big team it's sized from the measured test below — and above 25 people, we measure again with you before promising anything.

Security that doesn't depend on the model

Keys sealed in the vault, never in the chat. MONO uses them by name; the model never sees them. Sending, charging and publishing always wait for a person.

Five levels of permissions

Owner, partner, can work, can look and guest. Each person sees only what you share, and every tool passes through the same checkpoint that checks their level.

A log nobody can rewrite

Every action, by a person or by MONO, in a chained log: each entry carries the fingerprint of the one before. 403 of 403 in the 25-person test.

Deployment

Your box is set up by Deployalo in Virginia. Your files, databases and conversations live there, not in a database shared with other customers.

People, not a ticket queue

You talk to the team that builds MONO, by email, in English or Spanish. We set it up with you and stay on the thread.

How security works

Measured, not promised

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

Everyone typing in a document, moving cards and editing rows non-stop for about a minute, cursors moving 20 times a second, the owner watching and MONO suggesting. The worst case: a real team doesn't type all at once all the time.

Measure 3 people10 people25 people
Server CPU, peak (4 cores) 17.6 %30 %59 %
Someone else's cursor, p95, same region 8 ms9 ms51 ms
Someone else's cursor, p95, from Mexico City 116 ms107 ms131 ms
Changes lost 000
Log vs. what was done 73/73178/178403/403
TeamServerWhy
1–33 vCPU · 4 GBCollaborating doesn't show (under 20% CPU). What matters 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 tops out one core: more cores alone don't fix it. It gets split in two before going past ~25.
25+we measure againNot measured yet. First the two tunnels, then the test with 50 — with your team in mind.

Test box: 4 shared vCPU, 7.6 GB, Virginia, 10 Oct 2026. Not included: conversations with MONO, the box's browser, video and workers — they depend on how much they're used, not on how many people collaborate.

Not yet

So nobody finds out later:

  • No external security audit or certification yet.
  • No single sign-on (SSO) yet.
  • One region today (Virginia); from Mexico the floor is ~100 ms of distance.
Talk to us

Tell us about your team. We answer by email.

A person from the team reads it and answers by email, in your language.

Or write directly to hola@mono.vip

Try it first with a few people.

Download MONO, invite two people and open the same sheet. Then we talk about the rest.