Just got the renewal quote for our Netskope ZTNA stack, and wow—the DLP add-on price jumped nearly 40%! 😳 We're a small team, and this was the final piece pushing the total cost way beyond our cloud security budget.
I was all-in on their integrated approach. Having ZTNA, SWG, and DLP from a single pane seemed perfect for our limited ops staff. The ZTNA core works well, especially with their clientless access for contractors. But now, the bundled price with the "essential" DLP features feels like we're subsidizing enterprise-heavy use cases we don't need.
For other SMBs evaluating, here's what our intended automation looked like in Terraform (simplified):
```hcl
# This was the dream: provisioning secure access + basic data controls together
resource "netskope_policy" "ztna_smb_app" {
name = "finance-app-policy"
application = "our_saas_finance_tool"
users = ["finance-team"]
action = "allow"
# Wanted to add DLP checks here simply:
# dlp_profile = "internal-data-only"
# Now that's a costly extra module.
}
```
The problem? We can't justify the new DLP cost for just a few simple rules. Alternatives we're now forced to consider:
* Using Netskope for ZTNA only, and handling data loss via our existing cloud app's native controls (less centralized visibility).
* Looking at a more modular stack—maybe pairing a lighter ZTNA provider with a separate, affordable SaaS DLP tool.
* Accepting the cost and cutting back elsewhere, which isn't really an option.
Has anyone else hit this wall? Did you find a workable compromise with Netskope, or did you switch tools entirely? The ZTNA is solid, but this pricing shift on add-ons changes the total value proposition for smaller shops.
~CloudOps
Infrastructure as code is the only way
That 40% jump on a critical add-on is the playbook. They lock you in with the core ZTNA, then ratchet up the price on the pieces you need to make it actually functional.
You're right about subsidizing enterprise features. Those "essential" DLP rules are probably just the old ones they reclassified as premium. Check the revision date on the feature matrix in your contract annex.
Alternatives? Prepare for the sales rep to suddenly discover a "loyalty discount" you magically qualify for once you quote a competitor.
always check the last 6 months of reviews
Exactly. The "loyalty discount" maneuver is predictable, but it doesn't solve the core issue. They've already redefined what "essential" means in the contract annex. Even with a temporary discount, you're now on their new pricing grid for all future renewals. The goal is to normalize the higher price.
Your next quote from a competitor should be for the full stack you need, not just the DLP piece. Otherwise, you're just playing whack-a-mole with add-on pricing across two vendors.
Show me the data.
You're spot on about the pricing grid reset. I saw this same play with a different vendor last year - got a 25% "adjustment" after pushing back, but the baseline for the next renewal was the new, higher list price. It's a quiet contract annex revision.
That "full stack" advice is critical. When you're back in the market, you have to spec out the exact data controls you need, not just the DLP label. Sometimes you can cobble together the core "don't leak our customer list" policies with more basic, and cheaper, CASB features or even API-based rules in your email platform. The integrated pane is nice, but maybe not 40% nice.
The real question is whether your ops team's time saved by that single pane is truly worth the new premium. For some SMBs, it still might be, but you have to run the math with the new numbers.
Another trial, another spreadsheet