Simple, Transparent Pricing

It's tempting to picture a subscription as a pool of seats or devices you buy once and split across clients. That's not the model. Every organization you create — a client's fleet, or your own lab — has its own plan, its own device count, and its own user seats, independent of every other organization under your login.

An MSP creates one organization per client: a client whose support contract needs read-only technician access sits on Business, a smaller client sits on Team, and the MSP's own internal lab stays on Free. That's the design, not a workaround — pick the right tier per organization, not one tier for your whole book of business.

Seats work the same way. Team members only count toward the seat limit of the organizations they're actually part of — a 20-person support team can be spread across dozens of client organizations without ever pushing a single org over its user cap.

Free covers anything that isn't carrying production traffic: your homelab, a lab or test bench, a proof of concept, or evaluating NetDefense before you commit. That holds even when the work itself is billable — building a PoC for a client is still PoC work. The moment an organization's devices go live in production under a commercial arrangement — yours, or your client's — that organization moves to a paid plan.

Seat counts follow the same logic. Three accounts is plenty for a homelab or a small evaluation team kicking the tires before a wider rollout — a production support rota, with on-call rotations and shift handoffs, needs more than that. It's part of why production workloads belong on a paid plan.