The Units Consumption Model
Cisco ThousandEyes licensing is a pre-pay annual subscription built on a units consumption model. Rather than buying a fixed number of seats, you commit to a monthly pool of ThousandEyes Units — a minimum of 2,000 — and every monitoring test draws from that pool based on what it is and how often it runs. The monthly plan amount renews against the contract start date, and the contract sets a total usage cap you pay for whether or not you consume it.
This is a fundamentally different shape from the per-device and per-user models elsewhere in the Cisco portfolio. ThousandEyes cost is driven by configuration, not headcount, which makes it both more flexible and harder to forecast — the same monitoring estate can cost wildly different amounts depending on how aggressively the tests are tuned. Understanding that dynamic is the difference between a controlled line and a runaway one, and it sits alongside the per-device discipline of the Cisco Meraki licensing guide.
Agents, Endpoints and Internet Insights
ThousandEyes pricing has four components, each licensed slightly differently.
| Component | What It Monitors | Indicative List |
|---|---|---|
| Cloud & Enterprise Agents | Network and app paths, from the cloud or your own agents | ~$18–$43 per test/month (unit-based) |
| Endpoint Agents | End-user experience from laptops and desktops | ~$14 per agent/month |
| Internet Insights | Outage detection across providers and regions | From ~$50,000 (two packages) |
| Professional Services | Deployment and configuration | Scoped per engagement |
At list, a BGP routing-monitoring test runs around $18 per test per month and a network agent-to-server test around $43, both drawn from the unit pool; Endpoint agents are a flat $14 per agent per month; and Internet Insights starts near $50,000 for two packages. Connected Device Agents, used for last-mile monitoring, carry their own per-device licence with a 250-agent minimum. Each component should be sized to a real use case rather than bought as a bundle, the same right-sizing logic the Cisco Smart Licensing compliance guide applies to entitlement generally.
How Units Are Consumed
A unit is the consumption currency, and three factors decide how many a test burns: the test type, whether it runs from a Cloud or Enterprise agent, and the frequency at which it runs. A simple routing monitor costs far fewer units than a full network test, and an Enterprise-agent test is priced differently from a Cloud-agent one — but frequency is the multiplier that catches buyers out.
Running a test every minute instead of every five minutes consumes roughly five times the units for the same coverage. Across a large test estate, default-aggressive intervals can drain a unit pool months early — and the fix is a configuration review, not a bigger commitment. Tune frequency to the use case before buying more units.
Because units deduct continuously through the month, consumption is easy to lose track of until the pool is nearly exhausted. The discipline is to monitor unit burn against the committed pool the way you would monitor a cloud spend budget — actively, not at renewal. This is the consumption-visibility version of the entitlement tracking that keeps the wider estate honest, as set out in the Cisco Enterprise Agreement and licensing guide.
The Over-Commit Trap
The structural risk in a consumption model with a minimum commit is over-committing the unit pool. The 2,000-unit floor and the contractual cap mean you pay for the committed volume regardless of actual consumption, so a pool sized to an optimistic monitoring roadmap that never materialises is shelfware in a different form. The mirror risk is under-committing and paying overage rates mid-term.
The way through is to model genuine monitoring need first — which applications, which paths, at what frequency — and commit to that, with negotiated headroom rather than an inflated base. Reconciling actual unit consumption against the committed pool before each renewal surfaces both over- and under-sizing, feeding the next commitment with evidence rather than the vendor's growth assumptions, the same evidence-led posture as the Cisco EA negotiation and pricing guide.
ThousandEyes Inside a Cisco EA
Where ThousandEyes sits alongside other Cisco spend, the strongest commercial move is to fold it into the Enterprise Agreement rather than leave it as an isolated subscription. Inside an EA the unit commitment counts toward the committed value that drives the overall discount band, and the True Forward mechanics give some flexibility on consumption that a standalone ThousandEyes contract does not. That integration also aligns the renewal date with the rest of the estate, removing a separate negotiation cycle.
As with the security and collaboration portfolios, the question is whether the monitoring commitment is large enough to move the EA discount — and for most enterprises running ThousandEyes at scale, it is. Structuring that inclusion is part of the broader subscription strategy covered in the Cisco subscription licensing transition guide and the network-side Cisco SD-WAN licensing guide.
Sizing and Negotiating the Commitment
Optimising ThousandEyes is a sizing exercise before it is a discount exercise. Model the real monitoring need, tune test frequency to each use case rather than defaulting to aggressive intervals, choose deliberately between a la carte and packaged units, and reconcile consumption against commitment on a fixed cadence. Then commit the right pool — with headroom you negotiated, not headroom Cisco assumed — and fold it into the wider EA for the discount benefit.
Done this way, the units model becomes an advantage rather than a blind spot: you pay for the visibility you use, sized to evidence and negotiated against the full Cisco relationship. To size and negotiate your ThousandEyes commitment before your next renewal, request a confidential briefing, or download our Cisco EA Playbook.