Switched from FortiSASE to Perimeter 81 - was it worth it?

So the cost went up after the fix, not just the latency down? That's a really important detail.

>you find out the hard way
That's the part that worries me. It seems like the trade-off isn't just control for simplicity, it's also predictable costs for unpredictable ones. If a performance fix can automatically change your monthly bill, that feels like a different kind of complexity, just a hidden one.

Did they at least warn you about the price change before they resized the gateway?

That's a smart way to handle it. Scheduling the heavy work makes total sense.

It's interesting you mention figuring out what's truly heavy. We're small, so our Figma syncs aren't huge, but I realized our design team's weekly asset dump was the real culprit. It wasn't constant, but it would just hit the gateway all at once. Do you schedule each heavy workflow separately, or just a blanket 'peak' window for everything?

Great point about figuring out the real source. We're still mapping that out ourselves, honestly. For now we just tell the team to avoid big syncs during our core hours.

But a blanket window sounds easier to manage than trying to track every workflow. Do you find it hard to get team buy-in for scheduled syncs? 😅

Blanket windows are easier to manage, right up until marketing needs to push a big campaign asset during the "quiet" time. Then the policy evaporates.

You're trading technical tuning for social engineering. Instead of sizing a gateway, you're herding users. It works until it doesn't.

And honestly, if you're already paying a premium for a managed service, shouldn't it handle the load without making your team play traffic cop? That's the bit that gets me.

That's such a good example of a hidden cost, the "lost opportunity to architect proper access." It's not just about the wasted license quarter, it's that the billing structure forces you into suboptimal design decisions to avoid a penalty.

When your contract tiers are locked to user counts, you're incentivized to keep workflows on legacy systems longer than you should, just to avoid bumping into the next pricing band. It can actually slow down security improvements. I wish more SASE vendors offered a true usage-based model for these transitional phases.