zsc
dope

Please stow your legacy SWGs for take-off. This is a nonstop flight.

Make the switch from Zscaler ZIA to dope.swg.
[ PREPARE FOR LANDING ]
NO_MEETING_REQUIRED+++WE_PROMISE

|||||||||||||||||||||||||||||||||

Why should you move from Zscaler to dope.swg?

01
01
We’re reliable
Without relying on datacenters allows us to work consistently in every country and network. You’ll never have to worry about datacenter outages again.
02
02
We’re FAST AF
With local SSL inspection, HTTP2 is supported on day one and your connection is never degraded down to HTTP1.1. It’s so smooth, you won’t even notice we’re running in the background.
03
03
We’re PRIVATE
We never do SSL inspection outside of your device’s safe zone. Decryption happens locally, so the only data we save in the cloud are processed transaction records sent to the region of your choice.
ZSC_01

||||||||||||||||||||||||||||||||| STOPOVER DATACENTERS
Wait, are datacenters
really that bad?
Well, why would you use them if you didn’t need to? That’s like unnecessarily booking a stopover in another country when you could fly direct. Choosing a stopover is choosing to inspect SSL outside of your device. It’s a huge (SWG) box of red flags.

Datacenters come at a high cost. If there are any outages or degradations around the world, it can have an impact on you.  And if your closest datacenter goes down, your data could be rerouted to a completely different country—slowing you down in the process.
zsc_02

||||||||||||||||||||||||||||||||| HTTP2 DOWNGRADED
Does ZSCALER SUPPORT HTTP2? It’S inconsistent
Until the 6.2 release, Zscaler forced HTTP1.1 on the server when accessing decrypted traffic. Zscaler states to do SSL inspection now, but it’s very complex and not a simple “Yes” or “No,” per their own community thread. In other words, YMMV.

Why not choose dope.swg and get HTTP2 every time? Leave the “ifs,” “ands,” and “buts” behind.