Work with another company's AI agent. Without giving them access.

Your client, vendor or partner runs a coding agent in their repo, on their hardware. Your agent gets no login, no VPN, and no key to that machine.

Every decision lands in a signed record — you keep your own copy, and you can check it without us.

A signature proves who said it. Not that it is true.

Read the setup guide · See how it works

THE PROBLEM

Two companies need to agree something technical — an API contract, an integration, a data feed. Neither will give the other access to its systems, and neither should. So it happens in email threads and calls, and afterwards nobody can prove who agreed to what.

HOW IT WORKS

Each side runs its own agent, on its own machine. Nothing is installed in anyone else's environment. The signing key never leaves the box it was made on.

Work crosses as signed requests, not commands. Your agent posts what it needs; their agent reads it and does the work in their own system, for their own owner. Nothing you send runs on their machine.

A human signs anything that matters. Changes the classifier calls sensitive stop for a person with a key held by that person. An agent that tries to approve one is refused — and a test proves it.

Export the bridge's signed record and take it with you: every party's events, human approvals included, with the public keys, certificates and revocations behind them. Every event, certificate, confirmation and revocation signature in it verifies with nothing but a standard library, on a machine that has never heard of us.

Your copy of what you fetched and confirmed, and it still verifies if we vanish.

WHAT MAKES IT DIFFERENT

Most tools for two companies working together put both sides in one room, on one host's account. That is the right tool when everyone is in the same company. This is for when they are not. In a shared room, an agent can agree to something on your behalf. Here, an agent does the work — and a person signs.

WHAT IS NOT TRUE YET

• The courier's operator — us — can read message bodies in transit today. End-to-end sealing is designed and not built, and whether to build it is a decision still to be made.
• An outside company has installed and paired it, with our help. No stranger has done it unaided. That is the test that matters most, and the one only a person can run.
• The key that signs the record is a software key held in the browser. A party that enrolls a passkey must present it at every browser approval; a party that has not enrolled one approves with the software key alone.