MDM rollout
Deploy the LLM gateway to larger teams in your organization through your MDM. When you're ready to move past a local installer evaluation, contact support to get an MDM bundle for your organization.
How it works
On each supported platform, the MDM setup:
- Installs the
mintivebinary, which handles each employee's auth state and policy selection. - Sets up a daemon process that writes a small set of keys into each harness's managed settings files.
- Optionally, merges Mintive's settings into any configuration profiles you already have. This enforces that harnesses talk only through the gateway, but it can make rollout less straightforward.
The setup works alongside any harness configuration your teams already set, because Mintive only writes its own keys and you keep setting yours in the managed settings files mintive doesn't own.
Using MDM usually means you can't use server-side managed settings from Claude or Codex, so your configuration must be set through MDM in the on-device managed settings files. Claude Desktop is the exception: its Admin Console configuration keeps working.
Updates
Mintive releases a new MDM bundle when configurations need to change. The bundle packages rollout management into a single application, so replacing that one package through your MDM updates every device.
Supported harnesses
The MDM setup supports Codex, Claude Code, Claude Desktop, OpenCode, pi, and omp. Since pi and omp have no managed settings layer, the setup configures them in user-space settings instead.
Next steps
- Agent SDKs: point your own agents at the gateway from managed devices
- Access control: grant teams access to the policies they'll select
- Monitoring and analysis: review inference calls across your rollout