Product / the interaction layer
Your processes stop at the company door.
The work does not.
An order is approved, a delivery checked, a document requested, a decision taken. Your company's process has to work with the other company's.
Open a dossier01 / Today
Working with the outside
means building a dedicated layer.
A portal, an application, a module. Failing that, email. And the other company enters as a guest: it works by your rules, in your system, on your record.
Your tools stop where your company stops.
So do your AI assistants.
02 / What APIs do not settle
APIs and MCP give access to data. They do not say how two companies work together.
Which version was issued? Who approved, rejected or corrected it? Do both parties hold the same record? Access answers none of these questions.
Your system
Your processes, your teams, your agents.
They run at home, with your rights, on your tools.
Their system
Theirs, at their place.
Neither is meant to host the other.
03 / The interaction layer
Companies keep their systems, their teams and their agents.
The parties set their own permissions. The interaction leaves a record both sides can verify. Each party — a company, its teams, its AI assistants — enters with its own rights: it sees only what is meant for it, its assistants act only within those limits, and its systems stay at home.
Your process
Their process
Two companies work the same dossier. Neither opens its system to the other.
04 / What happens there
The dossier,
and nothing else.
01
Documents
Made available, never sent. Access is withdrawn at any time.
02
Questions and answers
Addressed to the party concerned, kept with the dossier.
03
Tasks
Requested, done, backed by documents.
04
Decisions
Proposed, then consented to by the people entitled to.
05
Signatures
Reserved to people. An assistant never signs.
06
Closing
Each entitled party leaves with a complete dossier it can verify.
05 / Three ways in
Use it as is. Plug in your assistant. Integrate it into your flows.
See the developers pageAs is
In the browser, nothing to install, for your teams and the other party's.
With your assistant
From any MCP-compatible client, with the rights you grant it — and can withdraw.
By API and MCP
In your flows, with signed webhooks. The technical reference is on the developers page.
06 / Proof
The record verifies without us.
Each party exports the record and verifies it on its own side, offline, with the VAL verifier — no account with us. Any alteration is detectable.
See the protocol07 / To close
Separate processes.
One shared interaction. One verifiable record.
Not at your place, not at theirs. A shared record and workspace, outside both systems.
Neither host nor guest. RIGA.