A CLOSED ROOM
One place, where the raise becomes its own proof.
On Exedra Gate the issuer and its investors speak inside the system, not in an inbox:
before the raise, during it, and afterwards, when the relationship actually begins.
Identity verification, the data room, contracts, signatures, deadlines, reports and
multi-language document management run in one flow. Everything that happens becomes proof
automatically: sent, opened, read, signed and independently timestamped under RFC 3161. Nobody writes the protocol afterwards. It is a byproduct of the work.
Read against the six situations above: every investor who was approached, invited or
admitted is an entry with a date, which is what turns the perimeter question and the
threshold arithmetic from an argument into a count. A disclosure sent from the room comes
back with opened and read receipts per recipient, which is what the investor dispute
actually turns on. Documents are generated on the rail and independently timestamped when they are signed,
so there is one version rather than final_v7. Obligations carry their deadline alongside
the artefact that proves each one was met, which is how a duty that runs until complete
repayment survives the departure of the person who knew about it. And certified
translations are delivered beside the original rather than instead of it.
A signature is given on the phone in the counterparty's pocket, wherever he happens to
be. The Exedra Gate app is arriving, and will carry the same room onto the device itself.
The rail does not wait for a raise. Neither do the questions.
Audits, due-diligence requests and disputes arrive on their own schedule, and usually
about things that happened years earlier. Everything the rail records during a raise, it
records between raises too: contracts signed on the engine, the data room and who opened
what inside it, identity checks on the people being onboarded, certification screening.
Each closes into the same record a third party can check offline, years later, with free
standard tools.
Buying the rail for the compliance work alone is a normal way to run it, not an edge
case. And if a raise opens later, it starts on a rail the company already runs, with the
record already accumulating.
Sovereignty, and what it replaces
The answer to fragmented storage is not another vendor. It is one place with one legal
basis, deployed where the company's obligations point: as a managed service, as a
white-label deployment on a server of the company's choosing, in Germany, in
Switzerland, or inside the company's own data centre. Where four vendors meant four
legal bases, four processor agreements and four registers to search, one place means
one.
Deployment models, stated.