Your hardware
The image runs on your host, on your network.
Enterprise Licensed and self-hosted
Some companies cannot put their engineering knowledge on somebody else's infrastructure. Enterprise is Hive as a licensed virtual appliance: the same code we run, on your hardware, on your network, with your backups and your keys.
The image runs on your host, on your network.
Generated on your machine and mounted. We never hold it.
A nightly dump, with one restore performed before anything real is stored.
Nothing asks us for permission at request time.
Nothing is compiled on your side, nothing is assembled by your team and nothing phones out to answer a request. There is no discovery phase and no statement of work.
One container image with the server and its database, a compose file and a runbook. Two commands on your side.
Every organisation's data key is wrapped with a master key generated on your machine. We cannot read your memories because we do not have it.
A firewall change on your side can never stop your brain answering. Enterprise contacts us for renewal and updates and for nothing else.
Developers install the ordinary client and point it at your hostname. Session hooks, auto-recall, the CLI, MCP and the web view work exactly as they do everywhere else.
Your hardware, your network and your TLS. Nothing upgrades itself and nothing about a version we ship can reach your database without you running it.
What you need, what your security team asks for and whether hosted would do. If it would, we say so.
Your DPA on your paper if you want it, a negotiated SLA and whatever your questionnaire needs.
We generate the master key with you and watch you put a copy somewhere that is not that machine.
Before anyone stores anything real, the nightly dump runs and we restore one.
Somebody's existing private brain becomes the team's starting point, so the first day is not an empty box.
We publish an image and an advisory. You decide when to apply it.
Not on a handover document. If your security review needs more from us than a call and a questionnaire, that shows up here rather than as a surprise later.
The licence is a signed claim, checked against a key compiled into the binary. Nothing asks us for permission at request time.
It names your organisation and will not start against another.
It refuses to run against a clock wound back behind the latest time it has already seen.
Over the seat count it refuses the next person rather than cutting off the ones already working.
You will have root on that box and the binary in your hands. Somebody determined could patch the verification out. Closing that needs remote attestation, which needs the call home this appliance exists to avoid.
So the signing makes non-compliance deliberate and provable rather than impossible. The one thing that genuinely stops at the end of a term is on our side of the wire: patched images and advisories.
A brain holds the reasoning behind your decisions, distilled. That makes it a dense target. Here is what protects it, with the limits stated rather than discovered.
The master key is generated on your machine and never held by us. Lose it and nobody reads those memories again, including us. That is the one irreversible step and we do it with you.
Memory titles and bodies, their history, events, notes and messages are encrypted with a data key per organisation before they touch disk. Each value is bound to where it lives, so a copied ciphertext stops opening.
The client refuses to send a token to a plain-http server that is not on loopback. The web UI and the MCP endpoint bind to loopback by default.
Grants live on the tree you define: organisation, department, team, project. Agents and CI get their own tokens, scoped to a node rather than a person.
Reads are logged as well as writes. When a review asks which agent read what and when, that is a query rather than an apology.
ns-brain does not call a language model. Your coding agent does that with your own account and the brain never sees the key, the prompt or the completion.
The first code-level audit found four cross-organisation issues. All four are fixed and the tests that reproduced them are in the suite.
The audit itself and what is still open, with the reasoning for each, go to reviewers on request from security@fightclub.pro. A reported vulnerability is answered within one working day.
The search index holds your words in the clear, because an index over ciphertext matches nothing.
Written here rather than in a contract nobody reads, because it is the question every security team asks.
Export keeps working at every point in that sequence and after it. ns-brain hive leave --apply puts every memory back into local brains your developers own outright.
Annual maintenance is a separate line because folding it into a per-person price hides it. It pays for the patch treadmill on the operating system, the database and our server inside the image.
Published with a note saying what moved and how urgent it is. You decide when to apply one.
For the components inside the image, so your own scanner finding something is a conversation rather than an escalation.
From the people who wrote it, on the deployment you actually run.
Each one pays for something specific. Figures come from a conversation rather than a pricing table, because two of the three depend on your headcount and on what your security review needs from us.
A standard DPA is included. Your DPA on your paper, a negotiated SLA and your questionnaire are part of the paperwork step.
| Line | What it buys | If it lapses |
|---|---|---|
| SetupPaid once | Registration, the signed licence file, the image and a working installation on your hardware with us in the room. | Nothing. It is paid once and it is done. |
| MaintenancePaid yearly | Patched images, advisories and support. | Enterprise keeps running. You stop receiving patched images and advisories, a decision you can reverse later. |
| SubscriptionMonthly or yearly | The software and the shared brain, priced per company and never per seat. | The licence stops renewing and the sequence above runs. |
Team size, what your security review needs and whether hosted would do. If it would, we will tell you. An appliance you did not need is a maintenance obligation you did not need.