JumpCloud's terms now allow usage-based pricing

The change

On June 13, 2026, Venpo detected a new version of JumpCloud's Terms of Service, the Directory-as-a-Service Agreement that governs its identity, device, and access management platform. The substantive change is a single new clause, Section 3.11 (Consumption-Based Features), and the only marker at the top of the page is a revised "Last updated" date, moved from October 3, 2025 to June 12, 2026.

JumpCloud is the cloud directory platform many teams use to manage users, devices, and access from one console. Under these terms, a modification takes effect on the earlier of any continued use of the service after it is posted or thirty days after posting, so for an active customer a new clause like this can become binding without a separate signature.

What changed

The new Section 3.11 says certain features may be offered on a "consumption, usage, or metered basis," as described in an Order, the Documentation, or the Site, and that the customer will pay for them based on actual use at JumpCloud's "then-current rates" or as otherwise stated in those same places. It is the only substantive addition in this revision; everything else is the updated date and a reordered list of prior versions.

Two points are worth isolating. First, the price is tied to "then-current rates" that JumpCloud publishes and can change, rather than a number fixed in the agreement. Second, which features are metered, and what each one costs, is defined outside the contract, in the Order, the Documentation, or the Site. The terms establish the billing model while the specifics sit elsewhere and can move.

What this changes about your costs

Until now, a customer's JumpCloud cost scaled with two things: the number of Users and the number of Devices. Billing runs on a High-Water Mark model, where each month is charged on the maximum count reached during that month, and the published pricing is per user, per month, by module. That model is predictable: if you know your headcount and your device count, you can estimate the bill.

Section 3.11 adds a second axis. For any feature JumpCloud designates as consumption-based, cost can scale with how much that feature is used, independent of seat count, at rates the agreement does not fix. A team that budgeted around per-seat pricing now has a variable line item to account for, and the only way to know which features carry it, and at what price, is to read the Order, the Documentation, and the Site, and to keep reading them, since "then-current" means they can change.

Why this matters

A pricing clause is exactly the kind of change that is easy to miss. It arrived inside a Terms of Service update with no figure attached and no separate signature required, and it can take effect through continued use. This is the category of risk covered in our analysis of the hidden risk of vendor legal changes, where the document that moves is not the privacy policy but the commercial terms.

It also matters because the substance lives outside the contract. When pricing is set in the Order, the Documentation, or the Site at "then-current rates," the version a buyer reviewed is not necessarily the version that applies later, which is the same reason teams increasingly treat the Terms of Service as something to monitor on an ongoing basis rather than read once at signing. The same direction shows up elsewhere in the stack, as when Mixpanel added premium overage fees to its plans.

Potential impact for SaaS companies

Companies that use JumpCloud may want to review whether:

• they know which features in their plan are now classified as consumption-based, and which are still covered by their per-user or per-device subscription

• their budget accounts for usage-based charges that can vary month to month, separate from headcount

• they have visibility into JumpCloud's "then-current rates" for those features, given that the prices are not fixed in the agreement

• finance or procurement has a way to be alerted when the rates or the list of metered features change

For teams that resell or build on JumpCloud, such as managed service providers billing across multiple clients, a usage-based cost that is set outside the signed agreement can be harder to forecast and to pass through cleanly. Tracking that kind of change across a full vendor portfolio is where continuous vendor risk monitoring becomes a control rather than a periodic task.

How Venpo detected it

Venpo continuously monitors vendor legal documents and detects changes as they are published. For this update, Venpo:

• detected the new version of JumpCloud's Terms of Service on June 13, 2026

• isolated the single substantive addition, Section 3.11, from the routine date change and the reordered prior-version links

• scored it as negative for customers and explained the billing impact in plain English

• flagged that the metered features and their rates are defined outside the agreement

Instead of discovering a new pricing model during a renewal or a finance review, a team could see it in the same period it was posted, before the clause took effect through continued use. A pricing clause inside a Terms of Service update is too easy to miss by hand and too consequential to ignore, which is the core of our comparison of manual vs automated vendor monitoring.

Business outcome

Companies that caught this change early were able to:

• identify which features in their plan are now consumption-based and confirm what they are charged for

• add a variable, usage-based line to their JumpCloud budget instead of assuming a flat per-seat cost

• set up a way to track JumpCloud's then-current rates and the list of metered features over time

• brief finance and procurement before the next invoice or renewal

Instead of reacting to a larger-than-expected invoice, they adjusted on their own schedule. This is the difference between operating with current information and operating on assumptions from the last review cycle.

Key takeaway

Some of the most consequential vendor changes are not in the privacy policy but in the commercial terms, where the rules for what you pay are set. This revision of JumpCloud's Terms of Service added a single clause that lets certain features be billed by usage, at rates the agreement does not fix and that are defined in the Order, Documentation, or Site. The only signal at the top of the page was a changed date, and the clause can take effect through continued use. A closer look at why scheduled reviews keep missing this kind of change is in our analysis of manual vs automated vendor monitoring.