Tenant isolation
Tenant ownership is enforced in backend queries and database relationships—not left to browser filtering.
Security architecture
Powerful administration. Deliberate guardrails.
An RMM agent is privileged software. Nizlo is designed around explicit identity, least-privilege technician access, signed and expiring work, encrypted transport, and visible auditability.
Defense in depth
Trust is enforced at more than one layer.
The browser experience, API authorization, durable job protocol, endpoint verification, and deployment architecture each have a defined security responsibility.
Technician access
Roles and action-specific permissions separate viewing endpoints from remote access, scripts, files, patching, and administration.
MFA and passkeys
TOTP MFA is supported, with WebAuthn/passkey registration and session controls built around the permanent application origin.
Signed device jobs
Privileged work carries a device ID, authorization context, nonce, timestamps, expiration, and server signature.
Immutable operational history
Sensitive actions create tenant-scoped audit records containing actor, target, source, result, and bounded metadata.
Unique device identity
Enrollment exchanges a revocable placement token for installation-specific credentials rather than embedding one universal agent secret.
Privileged action path
Every sensitive action has a verifiable route.
Authorize the technician
Validate the session, tenant, MFA state, role, and action-specific permission.
Bind and sign the work
Attach the target device, request context, nonce, issue time, expiration, and an allow-listed payload.
Verify and record
The agent verifies identity and signature before execution; the platform retains state transitions, result, and audit evidence.
Security should make operations clearer—not mysterious.
TLS-only production trafficNo shared agent passwordAudited privileged actions
Start free