How does building together stay safe?

One writer, so never a conflict

When building together, nothing is ever synchronised between two Mias. The app lives in one place — with the owner — and writing only happens there. Participants send requests, not files. Work can't get overwritten and a half-finished sync can't wreck your app: that situation simply doesn't exist.

The preview is a snapshot

What participants see of the app is a snapshot: an image of how the app looks right now, shown in a shielded frame. It's not a working copy with your real data behind it. Everyone can judge the result without a single byte of your data leaving your environment.

Boundaries are technology, not an agreement

The rules of a build session — only this app, no stored data, no commands on the server — are enforced at the moment Mia executes the work. A request outside the boundaries isn't "discouraged", it's simply impossible. Deliberately switch something on and the wider boundary applies; switch it off and the door is truly closed.

The same hardness applies between users: every Mia runs in its own shielded environment and can't just walk into another Mia. Everything goes through the central point, which checks every request.

Credits and accountability

Build work runs on the owner's Mia and is billed there in credits — so nobody can secretly build elsewhere at your expense. Every executed request also shows who sent it in, so you can always look back at what happened and by whom.