Run your AI fleet on hardware you own
Nerv is the operating system for NVIDIA GB10 and GB300 machines. For organisations, Nerv Dynamics adds a self-hosted management plane, supported generations that hold still for years, and support from the engineers who build the system.
Community and Enterprise
Nerv is free and open source under Apache-2.0. An Enterprise subscription adds what an organisation needs to run it in production, the management plane among it. Each subscription is shaped to the customer: the size of the fleet, the support it needs and how long each generation is kept.
| Community | Enterprise | |
|---|---|---|
| Nerv Linux, axon, Plexus, S2 | Free, Apache-2.0 | The same code |
| Updates | Rolling release | Rolling release and supported generations |
| Management plane | Not included | Included, on your own hardware or air-gapped |
| Support | Community chat and the handbook | Professional support, with SLAs agreed per customer |
| Security advisories | Public | Early notice, with an assessment of whether each issue affects you |
| Software bill of materials | Published per generation | Signed per generation, with audit support |
| Onboarding | The handbook | Deployment, training and integration with your systems |
Professional support
Support comes from the engineers who build Nerv, and it covers the whole stack: the system and its kernel, the NVIDIA driver integration, axon, Plexus and S2. Response times, hours and channels are agreed in each contract, from business hours for a development fleet to round-the-clock cover for production.
Contact
A named engineer.
One person who knows your fleet, with a ticket queue and a shared chat channel behind them.
Escalation
Straight to the code.
An issue in Nerv is fixed in Nerv, by the people who wrote it, and the fix reaches your supported generation.
Advisories
Early notice.
Security issues are assessed against your fleet before they are public, with the fix ready to roll out.
Reviews
Planned with you.
Regular reviews of the fleet, its generations and what is coming, so upgrades are scheduled rather than discovered.
Supported generations
A supported generation is a frozen, validated release of Nerv, kept patched for an agreed period and tested on your hardware and workloads. It changes only through your change control, while the rolling release keeps moving to the newest kernel, NVIDIA driver and packages. Security fixes are never held back from the rolling release.
| Rolling | Supported generation | |
|---|---|---|
| Updates | Continuous; everything moves forward | Frozen; security and critical fixes backported |
| Length | Always the newest | Agreed per customer, for example 12 to 36 months |
| Validation | Our test suite | Also on your hardware and your workloads |
The management plane
One place to run a fleet of GB10 and GB300 machines under one set of rules: which GPUs and CPUs serve which teams, which machines are enrolled, which generation each one runs, and what they report. It runs on your own hardware, connected or fully air-gapped, and its source is available to customers for audit.
Machines fetch signed generations and signed policy from the plane and report back. The plane sends no commands, so it has no way into a running machine, and signing rejects anything it should not offer. With a customer-held trust root, generations are signed with your key and nothing reaches your fleet without your signature.
Enrolment shipping
One code per machine.
A machine joins the organisation with a code an administrator approves, and keeps its own keys. Revoking one machine touches no other.
Placement building
GPUs assigned, not configured.
Assign GPUs and CPUs to teams, projects and workloads. Through axon, a fleet's accelerators become one pool, and local and remote are the same path.
Quotas building
Shared GPUs, hard limits.
Cap memory and compute per tenant on a shared GPU. A workload that reaches its limit gets an out-of-memory error, and nothing else on the machine is affected.
Generations building
Canary by machine.
Choose which generation each machine runs and roll a new one out to canaries first. Every machine still falls back on its own if a generation fails to boot.
Access building
Single sign-on and an audit log.
Roles, grants that expire, security keys, and a record of who changed what. Remote access runs over your own policy, never weaker.
Reporting design
Evidence an auditor can use.
A software bill of materials and attestation evidence per machine, and offline bundles that carry signed generations into sites with no internet.
Security and compliance
Every Nerv machine starts from the same chain of trust, with nothing to configure: its own Secure Boot keys made at install, a disk encrypted with LUKS2 and sealed to its TPM, SELinux enforcing with no unconfined domain, and a kernel that loads only signed modules. Packages, generations and release files are all signed, and every package records the source commit it was built from.
That gives an organisation most of what European regulation asks of the software it runs. Nerv Dynamics provides the evidence, and helps map it to your own controls.
| Asks for | What Nerv provides |
|---|---|
| Cyber Resilience Act | A software bill of materials per generation, signed updates, a published support period and a vulnerability-handling process |
| NIS2 | Supply-chain provenance down to the source commit, access control with security keys, and support in handling an incident |
| GDPR and data sovereignty | Self-hosted and air-gapped operation, no telemetry, and a vendor inside the EU |
Hardware and OEM
Nerv runs on NVIDIA GB10 today, with RTX Spark and GB300 on the roadmap. It targets those platforms alone, which is how it gets its performance.
A Nerv base can be signed, locked down with Secure Boot and shipped preinstalled without triggering the installation clause in section 6 of GPL-3, because no GPL-3 package is needed to boot it. The core is Apache, MIT, BSD and 0BSD, with the GPL-2 kernel and LGPL-2.1 libraries. Preinstallation on GB10 and GB300 hardware is licensed per unit.
Built in Sweden, held by you
Nerv Dynamics is a Swedish company. Keys are generated on each machine and never leave it, every package is built from source, the source is open to audit, and with a customer-held trust root your key decides what your fleet runs. Licences are signed files, checked offline, naming your organisation, the number of machines and the expiry date. A fleet that outgrows its licence gets a notice, never a shutdown. Nothing in Nerv calls home, and nothing about your fleet passes through anyone else, including us.
Services
Pilot
On your own hardware.
A pilot fleet installed and running on your machines and your workloads, with our engineers alongside yours.
Deployment
From first install to fleet.
Network installation, enrolment, the management plane and your mirror, set up with your team.
Training
For the people who run it.
Generations, recovery, the compute fabric and the management plane, taught on your own fleet.
Engineering
Built for your workload.
Custom generations, integration with your identity and monitoring systems, and inference tuned to your models.
Questions
Is Nerv free to use?
Yes. Nerv and every tool in it are open source under Apache-2.0. A subscription pays for the management plane, supported generations and support, not for the right to run the system.
Can we run it with no internet?
Yes. The management plane runs on your own hardware, offline bundles carry signed generations into an air-gapped site, and licences are checked offline.
What happens when a licence expires?
You get a notice. Nothing shuts down, and the machines keep running what they run.
Can we build it ourselves?
Yes. Every package builds from source with the same tools we use. Only builds signed by Nerv Dynamics carry the Nerv name.
Talk to Nerv Dynamics
Tell us about your fleet and what it needs to run, and we will shape a subscription and a pilot around it.