Editions

AI visibility.Governance at your scale.

Choose the foundation for discovering AI use, or extend it with the controls to manage decisions across your organisation. Nyxus is built on Shadow AI Guard, so everything in the open-source edition is included.

Explore the live demo Compare in detail
Layer 02·Enterprise · built on topNyxusLicensedOne key per deployment

For organisations managing ongoing governance, multiple teams and separate companies.

Everything in Shadow AI Guard, plus
  • Daily estate history and change tracking
  • Decision rules and console-managed exceptions
  • Company separation and team-scoped access
  • Signed evidence across five frameworks
  • Campaigns, Jira and scheduled reports
  • Encrypted backups and scoped API tokens
Explore the live demo
Layer 01·Open source · the foundationShadow AI GuardFreeOpen-source foundation

For teams getting visibility into AI use and establishing a governance baseline.

Core capabilities
  • Discovery across seven surfaces
  • Tools, people, devices and account context
  • AI register and personal-account lifecycle
  • Paid seats against observed usage
  • Owner, admin and viewer roles with SSO
  • ISO 42001 evidence snapshot
Get Shadow AI Guard
The difference in practice

Compare editions.Line by line.

30 capabilities in five groups. Nyxus includes everything in Shadow AI Guard; a dot marks the 20 rows where the two differ.

Find the right level of controlOpen sourceShadow AI GuardGet started ↗EnterpriseNyxusExplore demo ↗
Browser, CLI, IDE, desktop, network, cloud and MCPIncludedIncluded
Account context and personal-account discoveryIncludedIncluded
Identity map and coverage gapsIncludedIncluded
Unattended AI activityIncludedIncluded
Daily estate history and first-seen datesNot includedIncluded
Weekly change list and past-date estate viewsNot includedIncluded
AI register, owner and review dateIncludedIncluded
Personal-account lifecycle and audit trailIncludedIncluded
Automatic decision rulesNot includedIncluded
Expiring exceptionsIn the governance fileGranted and revoked in the console, with an audit trail
Approval conditions checked against the estateNot includedIncluded
Finding ownership and due datesStatus trackingOwner, due date and escalation
Reminders before a finding is overdueNot includedTwo days before
Personalised campaigns and Jira ticketsNot includedIncluded
Framework coverageISO/IEC 42001EU AI Act · ISO/IEC 42001 · NIST AI RMF · ISO/IEC 27001 · SOC 2
Evidence exportsManual, read-only snapshotSigned, verifiable packs
EU AI Act use-case inventoryNot includedIncluded
Scheduled company reports and access reviewsNot includedIncluded
CSV exportsIdentity mapSeven export areas
Owner, admin and viewer roles with SSOIncludedIncluded
Separate companies in one deploymentNot includedIncluded
Teams and team-scoped viewersNot includedIncluded
Paid seats compared with observed useIncludedIncluded
Recorded seat decisions and team chargebackNot includedIncluded
Setup wizard and detection-source configurationIncludedIncluded
Enrollment tokens and revocable device credentialsIncludedIncluded
Notification destinationsOne webhook + emailMultiple destinations
Destination retry, catch-up and response testingNot includedIncluded
Scheduled encrypted backupsNot includedIncluded
Scoped read-API tokensNot includedIncluded

Framework mapping and evidence exports support your governance work. They do not themselves confer certification or establish compliance.

Only in Nyxus

Built for ongoing governance.Eight things it adds.

What the enterprise layer adds on top of Shadow AI Guard, for organisations running governance as a standing process rather than a one-off audit.

01
Several companies. One deployment.Separate devices, findings, decisions, exceptions, rules, teams, identities, budget, history, campaigns, Jira connections, accounts, SSO and email. Archive, export or delete companies; start new ones from a baseline of rules and decisions.
02
Give each team its own view.Team viewers see only their people and devices. They can request a decision without making it themselves.
03
Record the use, not just the tool.An EU AI Act inventory records and classifies uses. Drafting an email and shortlisting applicants are different activities, even when the tool is the same.
04
A monthly pack, delivered.Schedule a company-specific email with signed evidence, a signed EU AI Act inventory, a spreadsheet inventory and an access review. Includes checksums, a delivery record and retry.
05
Reach the people behind findings.Turn personal-account findings into a coordinated follow-up. Nyxus resolves addresses from the identity map, sign-in names or Budget member lists and shows where each address came from. Sending stays blocked until every recipient is resolved. After a personalised message is sent, see who was reached and whether the activity has been observed again.
06
Connect the work to a ticket.Raise a Jira ticket directly from a finding, so the work can continue in the system your team already uses. Track the ticket back to its originating finding to keep the action connected to the evidence that prompted it.
07
Keep a way back.Schedule backups of the data that cannot be rebuilt from observations. Each backup is sealed with a key you hold and sent to storage you own. Restore from your own machine, keeping control of both the recovery material and the credentials needed to use it.
08
Build your own automation.Use scoped API tokens to connect your own automation to the read API. Give an integration the access it needs to retrieve data without treating it as an interactive user. Deployment licensing stays separate: one key per deployment, with a portal to see where it is held and move it.
Next step

See how it fitsyour estate.