Cside only adds 8-20 milliseconds (the blink of an eye typically lasts between 100 and 400 milliseconds) of latency to the specific, highly dynamic JavaScript files we proxy. Static scripts are cached at our edge and therefore load faster than the original source, improving the speed of your website. This is completely different from a WAF that adds latency to every single request to your website. Users won't notice any difference.
Can cside work alongside my existing WAF without conflicts?
We monitor an entirely different dimension of the application stack; hence, there is no interference.
How does cside's approach compare to the complexity of managing a WAF?
cside is much simpler because we're only handling JavaScript files, not your entire web infrastructure.
What happens if cside's proxy goes down? Will my website break?
Your website will continue working as intended with our fail-open design and 99.99% uptime SLA.
Will cside's proxy approach break my website like a misconfigured WAF might?
No, your website will continue working normally as we only intercept third-party scripts with fail-open design.