Neural Inverse Govern / Devices
Every machine that runs AI tools, enrolled and accountable.
Device enrolment, the endpoint agent and the signed policy it enforces, device commands, wipe and lost mode, and the AI coding tools each device runs and how each is governed.
- Endpoint agent
- macOS, Windows and Linux
- Policy
- Ed25519-signed, verified on the device
- Releases
- Signed by your installation's own key
- Lost or stolen
- Credential and keys revoked on the server
- Record
- Every lifecycle change audited
Overview
Govern manages the developer machines its endpoint agent is enrolled on, with no vendor MDM involved. Each device has its own credential and signing key, receives agent policy and agent updates signed by your installation, and reports the AI coding tools it runs. Administrators queue commands, put a device in lost mode, wipe it or offboard its person, and the server-side effects happen before the device hears about them.
What it does
What device management covers today.
Only what works today. Device management is still being built out; the rest is listed at the end of this page.
EnrolmentEnrolment tokens stored only as hashes, connect keys, and enrolment by signing in from the agent. Organisations can allow self-enrolment, with requests an administrator approves or denies.
Device credentialEvery device call is authenticated with a server-issued device token. A device can act only as itself, in its own organisation and region.
Signed agent policyThe agent fetches compiled agent policy as an Ed25519-signed manifest, refuses one that does not verify or is older than the one it holds, and denies every action once its offline grace period has passed.
Endpoint rules and kill switchOrganisation rules and the kill switch reach endpoint agents as a signed feed, by polling and over a live connection.
Device commandsRefresh policy, report status, install hooks into newly detected tools, or enter lost mode, for one device or many. Only command types the agent runs can be queued, and each is acknowledged once.
Lost, stolen and wipeMarking a device lost or wiping it revokes its credential, blacklists its hardware identity, flags its person's sessions of the last 24 hours for review and queues a wipe. The device counts as wiped only once it confirms.
UnenrolAdministrators unenrol a device with a reason, revoking its credential and signing keys. Where the organisation allows it, people can unenrol their own devices.
PostureLifecycle state, last seen, the last health report and tamper report, governed and ungoverned tool counts, and pending commands. What the device reports is labelled as reported by the device.
AI coding tools on each deviceThe tools the agent detects and how each is governed there: Govern's hook, the MCP proxy, not installed, vendor audit only or process tracking only. The server derives the mode itself.
Ungoverned tools across the fleetEvery AI coding tool that a live device runs without governance, with the devices that run it, most devices first.
Tamper reportsThe agent reports tampering with itself; the device is marked tampered and each report is kept.
Device signing keysEach device registers its signing key with proof of possession; keys are revoked with unenrol, wipe and offboarding. Your installation countersigns device exports and audit batches, and verifies exports on request.
Signed agent releasesEach installation signs every agent build with its own Ed25519 release key. Agents pin the key set at enrolment and refuse a build signed by another key, a tampered artifact and any downgrade.
Update channelsPer-device update channels and staged releases to a share of the fleet, with the status of each release across devices.
Decommission and offboardingDecommission a device with a reason, or offboard a person and all their devices, by hand or when SCIM deprovisions them. The last Owner cannot be offboarded.
Retention and legal holdsDaily retention of device data per organisation, legal holds that win over it, and erasure of a person from device data with a random pseudonym.
How it works
From enrolment to retirement.
- RequestA person installs the endpoint agent and signs in, or uses an enrolment token.
- ApproveWhere self-enrolment needs approval, an administrator approves the request before the device is enrolled.
- RegisterThe device registers its signing key with proof of possession.
- ReceiveSigned agent policy, rules and releases arrive and are verified on the device.
- ReportHeartbeats carry health, tool coverage and the agent's policy decisions.
- RetireUnenrol, wipe or offboarding revokes the credential and keys on the server.
Who uses it
Built for every role that answers for AI.
IT and endpoint administratorsEnrol devices, approve self-enrolment, queue commands, manage update channels and decommission machines.
Security teamsMark devices lost or stolen, act on tamper reports and close the gaps in the ungoverned tools list.
Privacy officersSet device data retention, place legal holds and erase a person from device data.
EngineersEnrol their own machine by signing in, and unenrol it where the organisation allows.
Enforced and recorded
Decided on the server, never on the device's word.
The endpoint agent's source is public, so Govern treats what a device reports as a report and acts on the server.
Enforced
Only as itselfA device is identified from its token and can write only for itself, in its own organisation.
Lost and wipeCredential and signing key revocation, the hardware blacklist and session flags happen in the request's own transaction, before the agent is told.
CommandsUnknown command types are refused, a command is acknowledged once, and a confirmed wipe cannot be undone by a replay.
ReleasesThe agent installs only builds signed by your installation's key, and never an older version.
Recorded
CommandsEvery queued command and every acknowledgement, recorded as the device's unverified word.
LifecycleWipe requested and confirmed, lost, unenrolled, self-unenrolled, decommissioned and offboarded, in the change's transaction.
Keys and releasesDevice signing key registrations and revocations, and every agent release published.
RetentionEvery retention run and every erasure of a person from device data.
Posture, health and tool coverage are the device's own report, labelled as such. No server decision relies on them.
Desktop platformsSigned agent packages for macOS, Windows and Linux, served by your own installation.
Self-hosted and in your cloudDevices enrol with, and fetch policy and updates from, your installation.
Air-gappedPolicy, releases and their signing keys come from your installation; the agent needs no outside service.
Hosted by usWe run it for you. Devices enrol in the region your organisation lives in.
Get started
Set it up with the documentation.
What's next
Being built now.
These are in development and not part of the product today.
Configuration profilesConfiguration profiles delivered to managed devices, not only stored.
Jamf, Intune and FleetConnectors that carry lifecycle actions to these MDM platforms, instead of completing them by hand.
Neural Inverse trayA tray app for each person: sign in, status, the policy in force, recent decisions, each tool's control level and pause of activity capture.
Staged device rolloutsCanary, beta and stable rollouts of device changes that advance and roll back on their own.
Firmware and machine identityIdentities for hardware and firmware devices that obtain tokens with their own credentials.
Device trust scoringTrust scores and fingerprint checks for devices, used in sign-in decisions.
Talk to our team.
Neural Inverse is available by request. We work with your engineering, security and procurement teams from the first conversation.