No cloud, no telemetry Live
Nothing of yours goes to a cloud model, API or connector. What a server sends out is on a short list and in a log you can read.
Security
Checkable by you, not only by us.
Items that work in a release you can install are marked Live. Items that are built or planned but not in one are marked Coming, with no dates. Ghalixy OS itself is Coming, so most of this page is. For the server's own protections today, see Ghalixy AI's security page.
What does not change
Your data lives on your box, and only there.
We hold no key to your data Coming
Recovery is your printed recovery key, not a call to us. If someone comes to us for your data, we have nothing to give.
No open door Live
A server accepts no connection from the internet by default. Your phone reaches it through an encrypted tunnel, and the server dials out to a relay that forwards packets it can't read.
Support never sees your data Coming
A support session is opened and ended by your administrator, approved with a tap, and shows system state only, with names and content removed. Everything done in it is written down.
The system
How Ghalixy OS is built to protect it.
Secure Boot with Ghalixy's keys Coming
The machine starts only a system signed by Ghalixy. A changed system file stops the boot.
A read-only system Coming
The system can't be altered while it runs, and nothing is installed by hand.
Encrypted data, opened by the chip Coming
Your data disk is encrypted. The security chip opens it only on a system that started as expected. Optionally, in an office, a second machine on the network can hold part of the key.
Updates that roll back Coming
Signed updates go to a second copy and are tried once. A power cut mid-update can't leave the box unusable.
Models with no way out Coming
The models and speech run on a network with no route out and none to the rest of the server, so closed code near your prompts has nowhere to send them.
A log of what leaves Live
Every outgoing request the server makes is in the egress log, in Settings, then Privacy.
Checking a download
Signed twice, and written in public.
Signed releases Live
A Ghalixy release is signed, and a server checks the signature before installing it.
Two signers, keys on hardware Coming
Each release is to be signed by two named people, with keys on hardware devices, and every release names its key so a stolen one can be shut out.
A public log Coming
Each release's fingerprint, and nothing of anyone's, is written into an open log anyone can read and stamped into Bitcoin once a day. No one could slip one server a different update unseen.
Fingerprints beside every file Coming
With the steps to check them on Windows, Mac and Linux, and a reproducible build so anyone can check that the published system comes from the published recipe.
What is not open
We name the closed parts.
Ghalixy prefers open-source software. These are the exceptions, and nothing is hidden behind the word "open".
NVIDIA's driver Coming
Its kernel modules are open source; its CUDA libraries are not, and they run inside the model process, so they could see every prompt and reply. That is the one written exception to Ghalixy's open-source rule, and it comes with conditions: the models get no network at all, the card goes only to Ghalixy's own pinned containers, and the modules are built and signed by Ghalixy in its build system and arrive through signed updates, never compiled on your box. Only the driver ships, none of NVIDIA's other tools. A reproducible build shows the closed files are NVIDIA's own, not what they do.
Graphics card firmware
AMD's drivers are open source, but a card's firmware, AMD's and NVIDIA's, is closed.
Found a problem?
Tell us, and we'll tell you what we did.
Write to admin@ghalixy.com with "Security" in the subject. A formal disclosure policy is Coming.