Yes, that's why we call it a hybrid proxy. We designed cside as a hybrid proxy, meaning you have granular control over which scripts get proxied and which don't. Critical scripts like Stripe, PayPal, Google Pay, or Intercom can be set to bypass our proxy entirely with capture-only mode, while newer or less trusted scripts get the full proxy treatment. This flexibility means you can allow the scripts you trust and proxy the scripts you're most concerned about or have not seen before, and expand coverage as you become more comfortable.
Can cside work alongside my existing WAF without conflicts?
We monitor an entirely different dimension of the application stack; hence, there is no interference.
Does cside's JavaScript proxy add latency like a WAF does to all traffic?
cside only adds 8-20 milliseconds to specific dynamic JavaScript files we proxy, with static scripts cached for faster loading.
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.