GCN.ONE on your own servers
Your documents never leave your building.
GCN.ONE runs on your own servers. Your people send to clients, counterparties and each other exactly as they do on gcn.one - but nothing you send ever touches infrastructure you don't control.
The same three promises, enforced by your own instance
Only the named person can open it
Inside your organisation or outside it. Keys are derived on the sender's device and unwrapped on the recipient's, so your instance holds ciphertext it cannot read.
Gone on your schedule
Expiry and revoke are enforced by your own deployment. When something expires it is deleted from storage you own, on a retention policy you set.
You know the moment
Every open and every download is recorded on your side, in a tamper-evident audit trail your own team can verify.
What you get
The full platform, inside your environment
The same control plane, storage nodes and clients that run gcn.one, deployed on hardware you choose - on your premises or in your own private cloud.
An annual licence
Support and updates are included for the term. One line on the budget, renewed once a year.
Deployment by our engineering team
Our engineers install it, adapt it to your environment and hand it over working. The team behind GCN.ONE is 100 Programmers.
Documentation for your risk review
The encryption model, the data lifecycle, a Data Processing Agreement, and our NIS2 and DORA mappings - written for the people whose job is to say no.
Before you ask your risk team
Everything a reviewer needs is written down and public. The important part is structural rather than contractual: encryption happens on the sender's device, so the instance - even one you run yourself - stores only ciphertext.
Start with a pilot in one department
Tell us what you would send with it and we will come back with a deployment plan and a price. One department first is usually the fastest way to find out whether it fits.