Convergence Nexus In development

One door between your machines and the cloud.

Convergence Nexus is the sovereign airlock: the one controlled doorway between your own machines, where local MasiDyn runs, and the cloud. It is being built to decide what may leave, what may enter and which agent may act, to log every crossing and let you undo it, and to leave the keys with you.

convergencenexus.com is an early control plane, not the finished airlock. Nothing on this page is ready to use yet.

The idea

Why an airlock

On a spacecraft, an airlock is a small chamber with two doors that never open at the same time. Nothing moves between the ship and space without passing through it, and someone decides when it does. Convergence Nexus applies the same idea to your data and your AI agents.

Your machines

The computers you own, where MasiDyn Free runs. Models run on your own hardware, and local data stays here unless you let it out.

Distribution notices

The airlock

The single doorway between the two. Every crossing, in either direction, goes through it and is checked against your rules before it happens.

The cloud

Everything outside: hosted AI models, online services and other Massive Dynamic products. Useful, but only reached through the door, on your terms.

How it will work

Every crossing answers to you

This is the design we’re building toward. None of it is a feature you can use today.

What may leave

The door starts shut. Nothing leaves your machines unless a rule you set allows it, or you say yes when asked. You choose which data, and which destinations.

What may enter

Replies, files and updates coming in from the cloud are checked at the door before they reach your machines, not after.

Which agent may act

Each AI agent gets its own permissions. One might be allowed to read a folder and never send anything; another might reach one service and nothing else.

Every crossing logged

Each crossing is recorded: what moved, which way, which agent asked, which rule allowed it, and when. You can read the whole log.

Reversible

Revoke any permission, and roll back what an agent changed through the airlock. A copy that has already reached someone else’s servers can’t be recalled, which is why the door stays shut until you open it.

You hold the keys

The keys that open the door are yours. The airlock is being designed to open on your say-so, not ours.

Privacy statement

An example

One crossing, step by step

Say an agent in your local MasiDyn wants a hosted model’s help with one document. This is how the airlock is meant to handle it.

An illustration of the design, not a recording of a working product.

At the door

  1. The agent asks. It requests to send that one document to that one hosted model.
  2. The airlock checks your rules. Is this agent allowed to send? Is this document allowed out? Is this destination on your list?
  3. If no rule covers it, you’re asked. You see what would leave and where it would go, and you answer yes or no.
  4. It crosses, and it’s logged. Only what you approved goes out, and the reply comes back in through the same door.
  5. You can take it back. Revoke the permission whenever you like, and see in the log exactly what left.

Status

What exists today

Convergence Nexus is in development. There is an early control plane at convergencenexus.com. Everything else on this page is the plan, and we’ll mark each part live only when it is.

convergencenexus.com is an early control plane. It doesn’t yet do everything described here.

Convergence Nexus, part by part

  • Early control planeIn development
  • Rules for what may leave and enterPlanned
  • Permissions for each agentPlanned
  • Crossing logPlanned
  • Revoke and roll backPlanned
  • Keys held by youPlanned
  • Signing in with your MasiDyn accountPlanned

Join the waitlist

We’ll email you when there’s an airlock to try.

In development. Joining the waitlist doesn’t give you access to anything yet. It only means we’ll tell you when there is.

See our privacy statement.