What is VaultCrux?
VaultCrux is the documentation and evidence plane. It is where the Crux Daemon and CueCrux are documented, and where the benchmark results for the system are published. You are reading it now.
This page is explanation. It exists because the name has meant three different things over two years, and one of them is still stamped on files you will encounter.
1. What it is today
Two jobs, and they are the same job seen from two sides.
Documentation. Every system in the family is written down here: the daemon you can install and read the source of, the hosted plane, the substrate underneath it, the extension surface, the operations manual. The set is organised into groups on the docs home, and you can filter it to the human track or the agent track.
Evidence. The benchmark results live at Bench results, under one rule: a number carries the corpus it was measured on and the revision it was measured at, or it does not appear. That page also states what we hold and deliberately do not publish, and why. The same posture runs through the rest of the set: Assurance and compliance is the disclosure page, and it lists controls that are built but not enforced in those words.
The two belong together. Documentation that cannot be checked is marketing with headings, and evidence nobody can find is not evidence.
2. What it is not
It is not a separate hosted product, and it is not an API you call. VaultCrux was once a hosted private-RAG service. That product was retired and its code was consolidated into CruxEngine, the hosted platform service. There is no VaultCrux endpoint to integrate against. If you are looking for the hosted API, it is Crux Engine; if you are looking for something to run locally, it is the Crux Daemon.
It is not the trust machinery itself. Receipts are produced by the daemon and by the hosted plane, and verification is a public unauthenticated endpoint on the hosted side. VaultCrux publishes and explains those guarantees; it does not implement them.
The name has not been scrubbed from the internals. Plenty of identifiers still carry it. The OpenAPI document served at /docs/openapi.json is still titled "VaultCrux API", and it describes the hosted plane. Treat every surviving "VaultCrux" identifier as history rather than architecture, and read the system it actually belongs to from the chapter you are in.
3. Where it sits in the family
| What it is | Read more | |
|---|---|---|
| Crux Daemon | The free, local, open-source binary. The thing you install. | Crux Daemon internals |
| CueCrux | The hosted platform and the commercial product. | The platform |
| CruxEngine | The hosted plane. Closed source. | 1. Crux Engine |
| CoreCrux | The retrieval and event-storage substrate. Closed source. | 2. CoreCrux |
| WikiCrux | The public corpus and citation surface. | The Crux family |
| VaultCrux | This: the documentation and evidence plane. | You are here |
The Crux family is the full introduction to each member, including which are open and which are closed. How they fit together draws the data flow and states what stays yours in each deployment shape.
4. Read next
- The Crux family, what each system is for and what its posture is.
- Bench results, the numbers with their corpora and revisions.
- Plans, the capability matrix across the free daemon and the commercial tiers.