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.

Team viewers see only their people and devices. They can request a decision without making it themselves.

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.

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.

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.

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.

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.

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.