Two licenses. Point them where you need them.

One per technician, one per workstation. The technician license covers your operators and everything they administer — servers, Active Directory, Entra ID, Google Workspace. The device license covers the workstations your end users work on. Buy either on its own, or both.

Device licenses only. License the machines you're managing privilege on and you get endpoint privilege and elevation, local credential rotation, just-in-time access to the machine, and discovery and remediation. Your technicians don't need a paid license for any of it — they just need a login.

Technician licenses only. That covers servers, Active Directory, Entra ID and Google Workspace: rotation, just-in-time access, passwordless MFA-enforced login, vaulting, discovery and remediation. You can still deploy the endpoint client to workstations for inventory without licensing a single one.

Buy both, in whatever mix your environment needs. Your discount follows your total monthly spend, so putting both licenses on one agreement works in your favor rather than splitting your volume across two.

No. A server is a machine only your technicians touch, so it sits with the technician license. The endpoint client runs on servers without consuming a device license.

Deploy the endpoint client everywhere, connect your directories, discover every privileged identity across every client, take a full inventory, stage your policies, and read the vault — none of it consumes a license. A license is what lets you act on what you find.

Your subscription begins with your agreement: you commit to a minimum monthly spend, in any mix of license types, and that buys your license pool. Above that commitment, nothing new is charged until a license is assigned and the technician or device is actually using it. Creating a technician login or installing the endpoint client doesn't consume a license on its own.

No. Assigning a license takes an Owner or Super User. A technician who needs a licensed action can request a license and carry on with everything else while it's approved — they can't commit the spend themselves.

No. A platform fee is a charge just to access the platform, with every technician and device license extra on top. Our minimum monthly commitment is satisfied by the licenses themselves, in any mix you choose — there's no separate charge for access, no per-client fee, and no charge for the AI. Onboard a ten-seat client the same way you onboard a thousand-seat one.

No. The Prompt Terminal is included with both license types — no separate module, no per-token charge, no credit pack. We run our own fine-tuned model on our own infrastructure, so there's no third-party inference bill to pass on to you.

There's a minimum monthly commitment, and it's a dollar amount rather than a license count. No minimum number of technicians, workstations or clients. Any mix that clears it works.

Your discount follows your total monthly spend rather than the count of any single license type. As your spend grows you move into a higher partner tier, and the improved rate applies to your licenses. Ask us where the thresholds fall and we'll show you in the quote.

In the product. Your initial agreement sets your commitment and your discount; after that you add paid licenses yourself without coming back to sales for each one.

Not mid-term. Once a paid license is added you're committed to it through the end of your current agreement. Renewal is where the number can come down.

It runs on your own environment — your tenants, your identities, your stack — with our team helping you scope it and stand it up. Discovery runs first, so you see your real privileged-access position before deciding anything, and nothing is feature-gated during the trial. To continue afterward you'll sign an agreement, which is where your commitment and your discount get set. A trial and an unassigned license are two different things: the trial is a one-time evaluation before you sign, and unassigned licenses stay unbilled for as long as you're a customer.