Clear answers. No vague promises.

No. Signup is open. Choose Core or Scale, create the owner account, accept the terms, and Nizlo creates the workspace immediately. Technician invitations are only for adding other people to an existing workspace.

No. Every new workspace receives a full 14-day trial without entering payment information. Because no card is collected, the trial cannot silently charge you.

Your existing workspace data is retained, but new endpoint enrollment and technician growth stop until the workspace is placed on an active plan. Continuing will require a deliberate plan and payment choice; there is no automatic charge from the card-free trial.

Core covers everyday monitoring, inventory, remote actions, alerts, scripts, patching, customers, sites, and operational reporting. Scale is intended for teams that need deeper automation, scheduled workflows, expanded reporting, and priority support. You can change the commercial plan later.

Nizlo is a cloud-hosted remote monitoring and management platform for MSPs and internal IT teams. It brings customer organization, endpoint health, inventory, alerts, remote work, automation, reporting, and audit history into one console.

Yes. Public self-service signup creates a 14-day Core or Scale workspace immediately, with no invitation and no credit card required. Windows is available for managed deployment while macOS packaging continues acceptance and Linux remains roadmap work.

The Windows x64 agent is the active acceptance target. A native Apple Silicon and Intel macOS monitoring agent is implemented but awaits its first signed, notarized package and physical Mac validation. Linux remains roadmap work.

The product is being built to cover the high-frequency endpoint workflows an MSP uses every day, but it does not claim feature-for-feature parity. Migration should proceed customer by customer after monitoring, inventory, commands, and remote access pass acceptance.

After signup, the workspace owner creates or selects a customer and optional site, then downloads the scoped installer or copies a silent curl installation command. The endpoint reports its hostname automatically; no separate sales-side provisioning is required.

The short-lived token safely assigns a new installation to the correct tenant, customer, and site. It is exchanged once for a unique device credential and is not the computer’s permanent API password.

The generic installer does not expire. The placement credential used alongside it expires after seven days by default. Generate a fresh command when deploying another batch, or revoke an unused credential sooner.

The Windows agent includes a signed update architecture and reports its version to the platform. Production self-update depends on an approved, signed release package and must pass rollback acceptance before broad rollout.

No. Ordinary workstation disconnects remain visible through availability and last-seen history but do not create alerts by default. Offline alerting can be enabled deliberately for servers or other critical scopes.

Current endpoint data includes heartbeat, availability, CPU, memory, disks, uptime, network throughput, hardware, operating system, interfaces, installed software, services, security posture, patches, and pending reboot state where supported.

Nizlo uses a replaceable provider architecture rather than inventing a proprietary screen transport. The current integration launches an approved self-hosted connection from the endpoint record and keeps the action auditable.

Yes on supported Windows agents. Quick commands and versioned scripts are delivered as authenticated, signed, expiring jobs with output, exit code, duration, requester, and result retained.

Tenant ownership is required in backend queries and database relationships. The interface is not the security boundary; authorization and tenant checks happen before tenant-owned data or actions are returned.

No. Each installation creates its own identity and receives a device-specific credential after enrollment. Privileged jobs are bound to the device and carry signatures, nonces, timestamps, expirations, and authorization context.

Yes. Technician security includes TOTP authenticator support, recovery handling, session management, and WebAuthn/passkey architecture for the permanent application domain.

The selected plan starts with one technician. Additional technician access is managed from the workspace and remains subject to the plan's seat allowance. Invitations are for teammates joining your workspace—not for creating the original owner account.

Core is $59 per month, Scale is $79 per month, and Suite is $99 per month. Every plan includes unlimited RMM endpoints, one technician, and additional technicians at $15 per month each. Suite also includes five protected backup endpoints and 1 TB of pooled cloud storage. Core and Scale signups start with a 14-day trial and no credit card is required.

No. Open signup does not collect a card. A paid subscription begins only after an authorized workspace owner deliberately selects a plan and completes checkout. The billing screen then provides invoices, card updates, plan changes, and cancellation controls.

The current private deployment uses a self-hosted remote transport behind a replaceable provider architecture. Commercial redistribution and open-source obligations are reviewed separately; customers are not offered a separate remote-access checkout.

The live application uses a production container topology behind trusted HTTPS. PostgreSQL, Redis, API, worker, and web services have separate responsibilities, while public application and remote-transport endpoints remain intentionally separated.