NyxusSelf-hosted shadow AI discovery

Find the AI tools nobody approved.And the ones signed in with personal accounts.

A FAMILIAR NAME. AN UNFAMILIAR STORY.
Browser · cloud
ChatGPT
PERSONAL ACCOUNToutlook.com · charmander
NOW ASK

Right tool. Right account?

Example findings from a sample estate: the tool, what Nyxus saw, and where

One finding,start to finish.

  1. 01
    The toolbulbasaur signs in to Codex CLI on NIX-BULBA, an Ubuntu machine, with a personal ChatGPT account.
  2. 02
    The surfaceThe Linux collector checks the machine against the tool registry and finds Codex CLI on the cli surface.
  3. 03
    The evidenceThe sign-in left a credential file. Nyxus keeps only the email domain written in it, never the tokens.
  4. 04
    The findingOne finding reaches the receiver. A personal domain makes it warn, on any surface.
  5. 05
    The decisionA person decides in the console. Try it: the decision changes and the severity stays.
Nyxus · Personal accountsSAMPLE ESTATE
Codex CLIbulbasaur · NIX-BULBA · cli
gmail.com● WARN
DECISION · NO DECISION
Nobody has recorded a decision yet. Pick one.
FINDING FIELDSreceiver · stored finding
{
  "tool": "Codex CLI",
  "surface": "cli",
  "os": "linux",
  "user": "bulbasaur",
  "device": "NIX-BULBA",
  "account_domain": "gmail.com",
  "evidence": "~/.codex/auth.json",
  "source": "Linux collector",
  "severity": "warn"
}
TOKENS REDACTEDbulbasaur@NIX-BULBA: ~
bulbasaur@NIX-BULBA:~$ cat ~/.codex/auth.json
{
  "OPENAI_API_KEY": null,
  "tokens": {
    "id_token": "eyJhbGciOiJSUzI1NiIs…",
    "access_token": "••••••••",
    "refresh_token": "••••••••",
    "account_id": "••••••••"
  }
}
↳ id_token email: bulbasaur@gmail.com · domain gmail.com
ILLUSTRATIVE LOGLinux collector · NIX-BULBA · Ubuntu
09:14:02  scan started · host NIX-BULBA · os linux · user bulbasaur
09:14:02  registry loaded · 31 tools
09:14:03  match · Codex CLI · surface cli
09:14:03  evidence · ~/.codex/auth.json
09:14:03  account · gmail.com → personal
09:14:03  finding → receiver · severity warn
ILLUSTRATIVE SESSIONbulbasaur@NIX-BULBA: ~
bulbasaur@NIX-BULBA:~$ codex
Sign in to Codex CLI
  › 1. Sign in with ChatGPT
    2. Provide your own API key
✓ Signed in as bulbasaur@gmail.com
› refactor the parser to stream input
Decision · No decision

Nobody has recorded a decision yet. Pick one.

Open source on one side.Enterprise on the other.

Shadow AI Guard overview: overall posture, discovered AI tools and personal-account exposureNyxus Enterprise overview: findings waiting for review and the signal flow from evidence to decisions
OPEN SOURCE · APACHE-2.0

The same 31-tool catalogue, 18 sources and 7 surfaces, in one console you run yourself.

Read the source ↗
After discovery

Finding it is the start.

What happens after a tool is found: who decided, what it costs, and what you can show for it.

01
Decisions that are kept
Every tool gets an owner, a decision and a review date, and exceptions expire. In Enterprise, an approval can also carry conditions (teams, seats, work accounts only, surfaces) checked against what the estate actually does.
Both editions · conditions in EnterpriseAI register
02
Spend, measured against use
What each plan costs, against what the estate saw being used. Seats nobody is using, renewals coming up and which team pays. Never a vendor’s word for it: a seat nobody can vouch for is said to be exactly that.
Both editions · chargeback in EnterpriseBudget
03
Evidence, mapped to frameworks
The evidence Nyxus already holds, written out control by control for the EU AI Act, ISO/IEC 42001, NIST AI RMF, ISO/IEC 27001 and SOC 2, as signed packs. A suggested mapping for your auditor to confirm, not an assessment.
EnterpriseFrameworks
04
AI that runs on its own
Agents on a schedule or a trigger, MCP servers, and who answers for each one.
Both editionsAgentic AI
Compare what each edition includes →

It runs in your estate.It makes one call home.

Nyxus runs on your own servers, and what it finds stays there. Every 6 hours it checks its subscription with us, and a signed answer comes back. This is the whole request; click a parameter to see what it sends.

GETregistry.nyxus.co.uk/subscription
id · subscription referenceWhich subscription this deployment belongs to.
Never sent:devices · findings · people · tool names
01Self-hostedKubernetes with Helm, or Docker Compose, in your own cloud. There’s no SaaS platform behind it.
02Offline key checkThe licence key carries Ed25519-signed claims, checked against a key compiled into the product.
03Audit trailEvery change to decisions, access and settings, and every sign-in.
04Encrypted backupsAES-256-GCM, to your own S3 bucket or Azure container. The key never leaves you.
05Signed evidenceEvidence packs and snapshots are Ed25519-signed, and you can check them with nyxusctl verify.
BUILT IN THE OPEN

Check it yourself.Before you talk to us.

Nyxus is new, so here is what you can verify today. Nyxus Enterprise is licensed, not open source, but it is built on Shadow AI Guard, which is. Its releases are signed, and its coverage is published.

THE FOUNDATIONShadow AI Guard

Nyxus is built on Shadow AI Guard. Its code and commit history are public under Apache-2.0. Nyxus Enterprise itself is licensed.

Shadow AI Guard on GitHub ↗
LATEST RELEASE0.5.0 · 8 Oct 2026

The current release and the one before it are supported, and security fixes are backported to both.

Read the release notes →
SIGNED RELEASEScosign + SBOM

Every Nyxus Enterprise image and the chart is signed and ships with an SBOM. The chart pins images by digest.

Verify a release →
COVERAGE
31tools18sources7surfaces

One registry generates the extension, collectors, scanner and discovery job, so every part detects the same tools.

See where it looks →
EARLY ACCESS

Become a design partner.

Nyxus Enterprise is coming soon. If you’d like to run it early on your own estate and tell us what works, get in touch.

NyxusSelf-hosted shadow AI discovery

Find the AI tools nobody approved.And the ones signed in with personal accounts.

A FAMILIAR NAME. AN UNFAMILIAR STORY.
Browser · cloud
ChatGPT
PERSONAL ACCOUNToutlook.com · charmander
NOW ASK

Right tool. Right account?

Follow the evidence →Sample findings: the tool, what Nyxus saw, and where

One finding,start to finish.

01 / 05
The toolbulbasaur signs in to Codex CLI on NIX-BULBA, an Ubuntu machine, with a personal ChatGPT account.
Nyxus · Personal accountsSAMPLE
Codex CLIbulbasaur · gmail.com
● WARN
DECISION · NO DECISION
Nobody has recorded a decision yet. Pick one.
receiver · stored finding
{
  "tool": "Codex CLI",
  "surface": "cli",
  "os": "linux",
  "user": "bulbasaur",
  "device": "NIX-BULBA",
  "account_domain": "gmail.com",
  "evidence": "~/.codex/auth.json",
  "severity": "warn"
}
bulbasaur@NIX-BULBA: ~
bulbasaur@NIX-BULBA:~$ cat ~/.codex/auth.json
{
  "tokens": {
    "id_token": "eyJhbGciOiJSUzI1NiIs…",
    "access_token": "••••••••",
    "refresh_token": "••••••••"
  }
}
↳ id_token email: bulbasaur@gmail.com
Linux collector · NIX-BULBA
09:14:02 scan started · os linux
09:14:02 registry loaded · 31 tools
09:14:03 match · Codex CLI · cli
09:14:03 evidence · ~/.codex/auth.json
09:14:03 account · gmail.com → personal
09:14:03 finding → receiver · warn
ILLUSTRATIVEbulbasaur@NIX-BULBA: ~
bulbasaur@NIX-BULBA:~$ codex
Sign in to Codex CLI
  › 1. Sign in with ChatGPT
    2. Provide your own API key
✓ Signed in as bulbasaur@gmail.com
› refactor the parser to stream input
Decision · No decision

Nobody has recorded a decision yet. Pick one.

Open source on one side.Enterprise on the other.

Shadow AI Guard overviewNyxus Enterprise overview
OPEN SOURCE · APACHE-2.0

The same 31-tool catalogue, 18 sources and 7 surfaces, in one console you run yourself.

Read the source ↗
After discovery

Finding it is the start.

What happens after a tool is found: who decided, what it costs, and what you can show for it.

01Decisions that are kept
Every tool gets an owner, a decision and a review date, and exceptions expire. In Enterprise, an approval can also carry conditions (teams, seats, work accounts only, surfaces) checked against what the estate actually does.
Both editions · conditions in EnterpriseAI register
02Spend, measured against use
What each plan costs, against what the estate saw being used. Seats nobody is using, renewals coming up and which team pays. Never a vendor’s word for it: a seat nobody can vouch for is said to be exactly that.
Both editions · chargeback in EnterpriseBudget
03Evidence, mapped to frameworks
The evidence Nyxus already holds, written out control by control for the EU AI Act, ISO/IEC 42001, NIST AI RMF, ISO/IEC 27001 and SOC 2, as signed packs. A suggested mapping for your auditor to confirm, not an assessment.
EnterpriseFrameworks
04AI that runs on its own
Agents on a schedule or a trigger, MCP servers, and who answers for each one.
Both editionsAgentic AI
Compare what each edition includes →

It runs in your estate.It makes one call home.

Nyxus runs on your own servers, and what it finds stays there. Every 6 hours it checks its subscription with us, and a signed answer comes back. This is the whole request; tap a parameter to see what it sends.

GET registry.nyxus.co.uk/subscription
id · subscription referenceWhich subscription this deployment belongs to.
Never sent:devices · findings · people · tool names
01Self-hostedKubernetes with Helm, or Docker Compose, in your own cloud. There’s no SaaS platform behind it.
02Offline key checkThe licence key carries Ed25519-signed claims, checked against a key compiled into the product.
03Audit trailEvery change to decisions, access and settings, and every sign-in.
04Encrypted backupsAES-256-GCM, to your own S3 bucket or Azure container. The key never leaves you.
05Signed evidenceEvidence packs and snapshots are Ed25519-signed, and you can check them with nyxusctl verify.
BUILT IN THE OPEN

Check it yourself.Before you talk to us.

Nyxus is new, so here is what you can verify today. Nyxus Enterprise is licensed, not open source, but it is built on Shadow AI Guard, which is. Its releases are signed, and its coverage is published.

THE FOUNDATIONShadow AI GuardNyxus is built on Shadow AI Guard. Its code and commit history are public under Apache-2.0. Nyxus Enterprise itself is licensed.Shadow AI Guard on GitHub ↗
LATEST RELEASE0.5.0 · 8 Oct 2026The current release and the one before it are supported, and security fixes are backported to both.Read the release notes →
SIGNED RELEASEScosign + SBOMEvery Nyxus Enterprise image and the chart is signed and ships with an SBOM. The chart pins images by digest.Verify a release →
COVERAGE
31tools18sources7surfaces
One registry generates the extension, collectors, scanner and discovery job, so every part detects the same tools.See where it looks →
EARLY ACCESS

Become a design partner.

Nyxus Enterprise is coming soon. If you’d like to run it early on your own estate and tell us what works, get in touch.

Become a design partner →Start with open source ↗

See it onyour estate.

Talk to us →