JumpCloud Deployment Options & Rollout 2026
JumpCloud is a multi-region cloud directory plus device management. Your only footprint is a 5-7 MB Go agent, or MDM enrollment for devices that cannot run it.
JumpCloud Deployment verdict
JumpCloud is a cloud directory unified with cross-OS device management.
The control plane is a multi-region SaaS. Your only footprint is a lightweight Go agent, a native binary using roughly 5 to 7 MB of RAM, that contacts JumpCloud over a long HTTPS poll.
Plan JumpCloud as a fleet onboarding exercise. Decide, per device class, whether to distribute the Go agent to Windows, Mac, Linux servers and laptops, or enroll Apple, Windows, Android devices through MDM. Then associate devices to your org with Connect Keys, choosing whether users can self-install with one-hour keys or you use never-expiring admin keys. Point your apps and network at the directory protocols: LDAP and SAML for SSO, RADIUS for secure Wi-Fi, REST for automation. Automate bulk user, system, group operations with the open-source PowerShell module rather than the console. Use agent policies for device-level controls, such as local accounts, FileVault, SSH MFA, and Directory Insights for audit. Operationally, account for the agent's offline-queueing update model and the chance of a manual fix when updates fail repeatedly. Start with the 30-day trial on one feature, then expand. It is strongest when you are consolidating a mixed-OS fleet that Active Directory alone could not cover.
- The control plane is JumpCloud's multi-region SaaS. The customer footprint is a lightweight Go agent on endpoints, with MDM as the agentless path.
- Devices associate to your org with a Connect Key. Admin keys never expire, user-generated keys last one hour.
- Agent updates are pushed to active devices and queued for offline ones, which matters for large or distributed fleets.
- Model
- Cloud directory + device mgmt
- Footprint
- Go agent, ~5-7MB
- Agentless
- MDM by device type
- Onboarding
- Connect Key
- As code
- PowerShell module + REST
This page covers how JumpCloud deploys and is administered. Its compliance posture and pricing live on their own pages.
Deploy JumpCloud: commands and config
Install the open-source JumpCloud PowerShell module and authenticate once with your org API key.
# install the open-source JumpCloud PowerShell module
Install-Module -Name JumpCloud -Scope CurrentUser
Connect-JCOnline -JumpCloudApiKey $env:JC_API_KEY- The PowerShell module and API examples are open source at github.com/TheJumpCloud/support
- The REST API base is https://console.jumpcloud.com/api with an x-api-key header
- Bind users to systems to have the agent provision local accounts on the device
Real JumpCloud commands from the official docs. Pick a task to see what it does, then copy the command.
What you run at each JumpCloud layer
| Aspect | What you run | Notes |
|---|---|---|
| Control plane | Cloud SaaS directory | Multi-AZ, multi-region, replicated services |
| Endpoint footprint | Go agent, native binary | ~5-7MB RAM; Windows, Mac, Linux |
| Agent transport | Long HTTPS poll | Near real-time work requests; TLS 1.2+ |
| Agentless path | MDM protocols | Apple, Windows, Android by device type |
| Onboarding | Connect Key | Admin keys never expire; user keys valid 1 hour |
| Protocols | LDAP / RADIUS / SAML / REST | SSO, secure Wi-Fi, directory from one hub |
| As code | REST API + open-source PowerShell module | Bulk user, system and group management |
JumpCloud connectors and integration surface
| Integration | Type | Capabilities | Setup |
|---|---|---|---|
| JumpCloud agent | Endpoint agent | Local account mgmt · Run commands · Policies and telemetry | Install on device |
| MDM | Agentless management | Apple / Windows / Android · Profile and policy · Enrollment by device type | Enroll via MDM |
| LDAP | Directory protocol | Cloud LDAP directory · App and infra auth | Point apps |
| RADIUS | Network auth | Secure Wi-Fi onboarding · Network access | Configure |
| SAML / SSO | Federation | Single sign-on · App federation | Connect apps |
| REST API / SCIM | Automation | Programmatic management · User provisioning | Code |
| Directory Insights | Audit / logging | Event audit trail · Install attribution | Built-in |
| PowerShell module | Open-source tooling | Bulk user and system ops · CSV import · Inspectable on GitHub | Install module |
JumpCloud rollout plan and risk points
- After installing the agent, admins manage device access and apply profile requirements, with a common pattern of installing the agent, adding users, and applying profiles.
- Updates are pushed to devices with an active agent; if a device is offline, the update is queued and applied the next time it is active.
- If an update fails repeatedly, manual intervention may be required, which matters for large fleets, and agent log files have known locations for troubleshooting.
- A 30-day trial lets teams fully evaluate the directory platform, and resilience is built on multi-region replication with a degradation-before-disruption philosophy.
JumpCloud Deployment FAQ
How is JumpCloud deployed?
As a cloud directory plus device management. JumpCloud hosts the directory as a multi-region SaaS, and on your side you install a lightweight Go agent on machines or enroll devices through MDM by device type. You associate devices to your organization with a Connect Key from the Admin Portal, then manage Windows, Mac, Linux, plus Android under common policies. The agent is a native binary using about 5 to 7 MB of RAM and talks to JumpCloud over a long HTTPS poll.
What is the JumpCloud agent and how does it work?
It is a small native binary written in Go, with some C++ on Windows, that you install on managed machines. It uses roughly 5 to 7 MB of RAM and contacts JumpCloud's servers over a long HTTPS poll in near real time, then downloading and running work requests when they appear. Once installed, it can add, modify, delete local accounts, run commands, manage local groups, control FileVault on Mac and enable SSH MFA on Linux.
Can I manage JumpCloud as code?
Yes. JumpCloud publishes an open-source PowerShell module and API example scripts on GitHub, plus a REST API at console.jumpcloud.com/api authenticated with an x-api-key header. With the PowerShell module you connect once using Connect-JCOnline, then create users, groups, bindings or bulk-import from CSV. The REST API covers the same operations for any language. This makes user, system, group provisioning scriptable rather than manual in the console.
What is a Connect Key?
It is how devices associate to your JumpCloud organization. The Connect Key lives in the Admin Portal and is unique to each admin. It is explicitly not treated as a secret, and any key can connect the agent to a device. Admin-generated keys never expire, while user-generated keys, when admins allow self-install, are valid for one hour. Directory Insights attributes agent installations to the admin who owns the key, regardless of who ran the install.
How complex is a JumpCloud rollout for different company sizes?
It scales with fleet diversity more than platform complexity. Small teams install a tiny agent and start from a 30-day trial. Larger or mixed estates use MDM enrollment, RADIUS for Wi-Fi and SSO across apps, and automate onboarding with the PowerShell module. It is aimed at heterogeneous fleets that outgrew Active Directory, combining Windows, Mac, Linux under one platform, and MSPs run it across multiple customer organizations. Plan for the agent's offline-queueing update model and the possibility of manual intervention when updates repeatedly fail.
Sources & verification
| Source | What was checked | Last checked |
|---|---|---|
| JumpCloud Official | Official product page | July 10, 2026 |
| GitHub TheJumpCloud Support | TheJumpCloud Support | July 10, 2026 |
| JumpCloud Cloud Device Management | Platform Cloud Device Management | July 10, 2026 |
| JumpCloud Security | Security and compliance | July 10, 2026 |
| JumpCloud Support Understand The Agent | Support Understand The Agent | July 10, 2026 |
Every fact on this JumpCloud page is tied to a named source and a verification date. Freshness-sensitive figures trace to the sources above; verify against the vendor before relying on them.
Explore JumpCloud
Every page on JumpCloud in one place, you are on deployment.
Snapshot, score and verdict
Frameworks covered and what a security review will ask
You are here
Every tier and the entry price
Compared and ranked vs peers
Price and feature change history
Browse the full Identity & Access Management category