Enterprise

Built for a fleet, not a demo on one laptop

NIK Agent ships with the things IT actually needs: identities from the directory you already run, deployment through the tooling you already own, centralized management, and an audit trail for the people who ask hard questions.

Centralized user management

One console for every seat

Administrators get an inventory, not a spreadsheet. Seats, sign-in methods, model assignments, usage and retention are in one place, and they follow your directory rather than a separate list you maintain by hand.

Seats and roles

Invite by group, assign roles, and see which users are active. Removing a leaver in your directory removes their access.

Usage by person

Token use per user and per team, so a heavy seat is a conversation rather than a surprise on the invoice.

Policy in one place

Set retention, decide who may add a frontier key, and choose how much autonomy the agent has with payments and outbound sends.

Trace review

Compliance can review the chain of thought behind any action your organization cares about, months later.

Group based rollout

Pilot with one department and extend by group, so the first fifty users prove it before the next five hundred get it.

Offboarding that sticks

When someone leaves, their session, their seat and their traces are handled by policy rather than by memory.
Sign-in

Microsoft and Google, then single sign-on

Your people sign in with the account they already use, and you do not create a second identity store to defend.

  • Microsoft Entra ID sign-in, using the tenant you already own.
  • Google Workspace sign-in for the teams that live in Google.
  • Group based access, so membership in your directory decides who gets a seat.
  • Single sign-on, provisioning by directory group, and automatic deprovisioning for larger rollouts.
  • No passwords for NIK Agent itself, which means nothing new to phish.

The same directory patterns Netarx already supports on the wider platform.

Two clicks for the user
  1. 1Open NIK Agent and choose Microsoft or Google.
  2. 2Approve the organization sign-in you already completed this morning.
  3. 3The agent picks up your role, your model assignment and your policy limits.
Bulk deployment

Push it with the tools you already run

NIK Agent is a signed installer for Windows and macOS with bulk deployment support, so it rides along with your existing management stack instead of adding another one.

Your toolingHow NIK Agent fits
Microsoft IntunePackage the installer as a line of business app and deploy to a device group. Sign-in is the Entra ID account the user already has.
Jamf or another Mac MDMDistribute the macOS package and keep the fleet on the version you have tested.
RMM (if you work with an MSP)Silent install and version reporting, so your provider pushes and updates it the same way they handle the rest of the stack.
Group Policy or a scriptThe installer supports unattended install, so a one-line deployment script is enough for a small fleet.

Deployment guides and the current installer live with support. Read the quick start

Procurement and review

The paperwork your process expects

Security questionnaires, legal review and a pilot that proves value in one department before the fleet rollout.

Pilot in 30 days

One department, 20 to 50 users, and three numbers at the end of it: escapes that got through, false alarms per user per day, and help desk tickets caused by verification.

Security review support

We answer the questionnaire, walk your team through the architecture, and point to Netarx's trust portal rather than inventing a certification.

Commercial flexibility

Volume terms, invoicing and a named contact for rollouts that need them. Smaller teams can simply start on Team pricing.
Enterprise questions

What IT asks in the first meeting

Do we need new infrastructure?
No. The agent installs on the endpoints you already manage, we run the model environment, and sign-in comes from your existing directory.
How long does a rollout take?
One user in minutes, a pilot department in an afternoon, and a fleet rollout on your normal change schedule. Bulk deployment is a supported path, not a custom project.
Can we keep all inference inside our own environment?
The model runs in our environment, hosted domestically. If your requirements call for inference inside your own perimeter, tell us in the first conversation so we can scope it properly rather than promise it on a web page.
What does an administrator control?
Seats, roles, sign-in methods, model assignment, retention of traces, and how much autonomy the agent has with consequential actions. Usage is visible by person.
Can we add a frontier model for some teams only?
Yes. An administrator adds the API key, chooses the users or groups that may use it, and those requests bill to your account with that vendor.
How does this fit with the rest of Netarx?
NIK Agent uses the same identity layer as the wider Netarx platform, so organizations already running NIK on netarx.com can extend the same posture to the agent instead of starting a second program.

Start with one department

Twenty to fifty users, thirty days, and three numbers that tell you whether it survives contact with your organization.