We cannot see inside your tenant unless you let us.
Every RMM vendor has staff who can open a customer. At Nyxie that door is locked from your side, and every time it opens there is a line in a log you can read.
Consent-based support access
This is how a Nyxie engineer gets into your account when you ask for help.
You issue a code
Account settings, Support access, choose how long it lasts (2 to 72 hours, default 8). You read the code to us.
We redeem it
The code plus your access ID unlocks a read-only view of your account for that engineer only. Wrong code, wrong ID, expired or revoked: refused and logged.
Editing needs a second factor
Read-only is the default. Changing anything requires the engineer to pass two-factor again, and that elevation is logged too.
It ends
The code expires or you revoke it, and access ends with it. Your Access history shows every issue, use, refusal and revocation, by name, with the exact time.
Nobody at Nyxie can view your account right now. That sentence is on your Support access page whenever it is true.
Identity and access
Two-factor for everyone
TOTP with recovery codes. Sensitive actions such as running scripts or remote sessions ask for a fresh code even inside a signed-in session.
Single sign-on
Microsoft Entra ID, Google Workspace or any OpenID Connect provider, per account, matched by email domain. Enforce it and password sign-in is refused for your domain.
Roles scoped to organizations
Admin, operator and read-only roles, and operators can be limited to the sites they look after.
Audit log
Sign-ins, support-code events, user changes, script runs, remote sessions and staff actions, searchable and exportable. Customers see their own account's activity in Settings.
API keys
Read or write keys scoped to your account, shown once, revocable. Webhooks are signed with HMAC-SHA256 so your receiver can verify every payload.
Kill switches
Remote commands and automation can be switched off per organization or platform-wide, instantly, and the switch state is visible to you.
Where your data lives
Nyxie runs entirely on Cloudflare: Workers for the services, D1 for data, R2 for agent releases and backups. There are no servers of ours to patch and no third-party analytics in the console.
- Encrypted in transit and at rest by the platform
- Agent updates are signature-verified before they run
- Hourly backups with 48-hour, 30-day and 12-week retention
- Sessions are HttpOnly, Secure cookies bound to nyxie.io
Report a vulnerability
Write to security@nyxie.io. We acknowledge within two business days and will credit you in the fix notes if you want.
Status and incidents
Every product publishes a /health endpoint. Incident notes go to your account admins by email.