Skip to content
Notifications
Clear all

Netskope pricing feedback - anyone feel it's overpriced for small teams?

3 Posts
3 Users
0 Reactions
5 Views
(@cloud_cost_watcher)
Estimable Member
Joined: 5 months ago
Posts: 121
Topic starter   [#847]

Having evaluated numerous cloud security and access solutions from a cost perspective, Netskope's ZTNA offering often surfaces in discussions. While its technical capabilities for secure access are robust, the pricing model appears to be a significant hurdle for smaller teams or startups.

From my analysis and anecdotal reports, the primary concerns are:

* **Entry Threshold:** Licensing is typically structured for enterprise-scale deployments. The minimum commit or user count can be prohibitively high for teams under 100-150 users, forcing small teams to pay for a footprint they cannot utilize.
* **Bundle Complexity:** True security value often requires adopting more than just the ZTNA component (e.g., SWG, CASB). This can lead to a bundled pricing model where you are effectively paying for a suite, making it difficult to achieve a lean, cost-effective ZTNA-only deployment.
* **Lack of Granularity:** Compared to a pure consumption-based cloud service, the per-user, per-year licensing lacks the flexibility that small teams need to scale precisely with unpredictable growth.

In a cloud cost paradigm, we look for linear scaling and clear unit economics. Does Netskope's model align with this for a small team, or does it impose an enterprise tax from the outset?

I'm keen to hear from teams with under 200 users. Have you found workable pricing tiers, or did you ultimately seek alternatives due to cost? Specifically:

* What was the effective per-user, per-month cost you were quoted?
* Were you able to negotiate a package that was truly proportionate to your size?
* Did the bundled features provide tangible value, or were they shelfware you were forced to fund?

Optimize or die.


CloudCostHawk


   
Quote
(@tom_s)
Active Member
Joined: 3 months ago
Posts: 10
 

You're hitting on the exact pain point I ran into last year. That "minimum commit or user count" isn't just theoretical, it's a hard floor in the sales conversation. We're a DevOps team of about 30, and the quote effectively bundled in features we had zero intention of using, just to meet their minimum revenue threshold.

What really stung was comparing it to the operational cost of running a more modular setup ourselves. We ended up using a combination of Cloudflare Tunnel for the ZTNA piece and some baked-in Kubernetes network policies, and our annual cost is a fraction of what that single-vendor quote was. It's more toil on our end, sure, but for a small, tech-heavy team, the trade-off made sense.

It feels like their pricing is optimized for companies where the decision-maker is far removed from the actual bill. Have you found any other vendors that manage to offer a leaner package, or is this just the state of the market?


automate everything


   
ReplyQuote
(@cloud_watcher_99)
Reputable Member
Joined: 1 month ago
Posts: 172
 

Yeah, that "minimum commit" is a killer for startups. It forces you into a totally different cost category than your actual usage, which breaks the cloud scaling mindset.

I've seen teams get around it by pushing hard for a proof-of-concept agreement that lets them start small, but it's a real negotiation fight. Sometimes the sales rep can bend the rules if they think you'll grow fast.

The bundling you mentioned is spot on too. We looked at it for just the CASB piece, and the quote basically included the whole platform. Ended up with a lighter tool and ate the visibility gap, which isn't ideal but kept costs sane. Makes you wonder if they'll ever offer a truly modular SKU.


cost first, then scale


   
ReplyQuote