Skip to content
Security

Your data lives in your box.

MONO uses your keys without seeing them. Nothing goes out without your OK.

Every account gets its own server. Every action passes through one checkpoint with permissions. Charging, sending and publishing wait for a person. And everything that happens is written in a log nobody can quietly rewrite.

Found something? security@mono.vip

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.

Your own box
01

One server per account.

When you sign up, MONO creates a server just for you and your team. Your files, sheets, databases, conversations and keys live there — not in a database shared with other customers.

02

Models get the question, not the keys.

To answer, MONO sends the request to the best model for the task — Claude, GPT, Gemini, Kimi, DeepSeek. Your keys and passwords never travel with it. We don't train models with your content.

03

Our side knows your account, not your work.

MONO's control plane keeps what it needs to run: your account, your billing and your box's health. Since 11 Oct its master key no longer travels to any box.

The sealed vault
01

MONO asks for a key — never in the chat.

When MONO needs a password or an API key, it doesn't ask you to paste it into the conversation. It gives you a one-time link.

02

You paste it. It gets sealed.

The value goes straight into your box's vault, encrypted with AES-256-GCM. The link works once and expires. MONO never gets the text — and neither does the app.

03

MONO uses it without seeing it.

When MONO calls Stripe, your database or any API, it asks for the key by name. The broker in your box puts it into the request — outside the model — and gives MONO only the answer.

04

Seeing it again is up to you.

To read a sealed value, you open another one-time link, as yourself. «Forget» removes it from the vault.

The checkpoint

Every action goes through one door.

Every tool MONO has — and every button in the app — passes through the same checkpoint before it runs. It checks who's asking, their level, and whether the action needs a person. A tool without a declared permission can't even be registered.

The checkpoint
Action Ownerthe accountPartneradmin · decides with youCan workyour teamCan lookread onlyGuestonly the app you share
Ask your data, see what happened Can Can Can Can its app
Edit the board, sheets and documents Can Can Can Can't Can't
Run what exists, write to your databases Can Can Can Can't Can't
Send, charge or publish outside the box Can — when MONO does it, it waits for a person's OK Can — when MONO does it, it waits for a person's OK Can't Can't Can't
Invite people and change levels Can Can Can't Can't Can't

Since 9 Oct, approving needs the app's own credential, issued per person: a coding agent holding the box's token can't approve its own request.

Human approval
01

MONO drafts. It doesn't send.

You asked MONO to email the quote once the totals were right. It writes the email and gets it ready — that's as far as it goes alone.

02

Sending stops at the checkpoint.

Charging, publishing and sending outside your box need a person. The checkpoint stops them and nothing goes out — even if a model was tricked into trying.

03

It waits for you, with its context.

In «Waiting for you» you see what, why in MONO's words, who asked, from which conversation or worker, and when. Approve once, always for that worker, or say no.

04

You say OK. Then it goes — and it's written down.

Approved, the email goes out. The decision, who took it and what happened stay in the log.

The log

Everything that happened. Nothing erased.

Every action in your box — by a person or by MONO — goes into a chained log: each entry carries the fingerprint of the one before. Changing or removing one breaks the chain, and it shows.

  • Who, what, and how it ended — every action, by every person and by MONO.
  • What MONO decided, and why — in its own tab.
  • 403 of 403 actions in the log in the measured 25-person test.
MONO's log: every action in the box, who did it and how it ended
11:11 Ana asked prev 0000… hash a91f3c
11:12 MONO drafted the email prev a91f3c hash 3c07e2
11:42 Joe approved prev 3c07e2 hash 9be410
11:42 Email sent prev 9be410 hash 51d0aa
Encryption

Locked at rest, in transit and per entry.

The names you can check, and what each one protects.

AES-256-GCM

Every value in the vault is encrypted with AES-256 in GCM mode — authenticated: if someone alters it, it won't open.

the vault · at rest

PBKDF2-SHA256 · 600,000 rounds

The vault key is derived from your box's secret with 600,000 rounds: slow on purpose for anyone trying to guess it.

key derivation

HKDF, one key per entry

Sealed conversations get their own key per entry, derived with HKDF: one key opens one thing.

sealed conversations

TLS and an encrypted tunnel

The app reaches your box through an encrypted tunnel. Everything between them travels over TLS.

in transit

Closed by default

If the checkpoint can't confirm a permission, the answer is no. A failure never turns into a yes.

the policy
Coming soon

ML-KEM-768, post-quantum

Post-quantum key exchange (NIST FIPS 203) is already in MONO's code. Wiring it into the link between your box and our control plane comes next.

box ↔ control plane
Prompt injection

A web page can't give MONO orders.

When MONO reads a page, an email or a file, what it reads is treated as text from a stranger — never as instructions. And if a model still gets fooled, the checkpoint doesn't: sending, charging and publishing wait for you, and keys never reach the model.

  • Web content reaches the model wrapped and labeled as untrusted.
  • An injection detector watches what comes in.
  • The box's browser opens only http and https — never your files or the server's metadata.
Security review · 11 Oct 2026

What we closed this week.

We attack our own product. These are the holes the review found — and how each one closed.

Fixed

The box's browser doesn't open files or the metadata.

It could read file:///opt/mono/.env and the server's metadata address. Now it opens only http and https, never link-local addresses, and stops if a redirect leaves.

Fixed

The control plane's master key no longer travels to the box.

New boxes were born with a key they didn't need. It isn't written to any box anymore, and the metadata is readable only by the system.

Fixed

Approving needs the app's credential.

A coding agent with the box's token could approve its own request. Now deciding needs a credential only the app gets — per person, revocable.

Fixed

A payment that arrives twice credits once.

Stripe can deliver the same event more than once. Credits are now checked against that payment before they're added.

Fixed

The browser stops writing to billing fields.

A signed-in user could edit fields of their own account that only billing should touch. The fix (migration 056) is live: those fields are now written only by billing.

If you stop paying

Nothing gets deleted by surprise.

A failed payment doesn't turn off your work, and turning off doesn't delete it. If you cancel, your box goes straight to «off» — with the same days to come back.

  1. Day 0 A payment fails

    Your box keeps working, and we tell you by email and in the app.

  2. Day 7 It turns off — not deleted

    The server stops. We tell you how to take your data out and how to come back.

  3. 30 days off A full backup, first

    We make a complete copy of the disk. Only when it's ready is the server deleted.

  4. Any time Pay again, it comes back

    In grace, it just continues. Off, it turns back on, as you left it.

Who processes what

The services behind MONO, by name.

The same list as our privacy notice — what each one is for and what it receives.

ServiceWhat forWhat it receives
AI models Answer what you ask. MONO AI, our model router, picks the model for each task. The content of the request. Never the vault's keys.
Stripe Charges, subscriptions and coupons. Your plan and payments. Your card goes to Stripe; MONO never sees it.
Supabase The control plane's database. Your account and subscription.
Deployalo The servers where your box lives, its backups, mono.vip and the encrypted tunnel to your box. Your box (United States, Virginia).
Analytics Only if you accept cookies: Google, Meta and PostHog. Visit and campaign data.

Read the privacy notice →

Report a problem

Found something? Tell us.

Write with what you saw and how to reproduce it. We answer, we fix it, and we tell you when it's closed. Please test only against your own box.

security@mono.vip