Skip to main content
Blog
Blog

Why We’re Called cside

We named ourselves after the part of the web that no one else was protecting: the client-side.

Jun 25, 2025 Updated Dec 12, 2025 2 min read
cside-logo
Table of Contents

TL;DR

  • cside = client-side: The company is named after the client-side, the browser layer where third-party scripts run and where traditional server-side security stops; it is pronounced like "seaside."
  • One official spelling: Earlier versions used a slash to mark the line between what developers can and cannot control, but the company's official name is now simply cside.

We named ourselves after the part of the web that no one else was protecting: the client-side.

When we founded our company, we chose a name that reflected exactly where modern web risk lives, and where traditional security tools stop. That name is cside.

cside = client-side. Pronounced like seaside.

Every time someone loads your site or web app, their browser executes dependencies you didn’t write, don’t own, and very often haven’t audited. It all runs on their machine. In the user’s client. And many of those scripts originate from servers you don’t control and can change at any time.

That’s where real risk begins.

Most security tools stop at the server. We start where they left off.

That’s why we built cside.To protect the code that actually touches your users’ browsers.

About the spelling

You may have seen our name written in different ways-cside, cside, and historically, cside. The slash helped express the line between what developers can control and what they can’t. But as we’ve grown, the simpler and more universal spelling has become the right identity for us.

So today, our company’s official name is cside.

You may still encounter cside from our earlier days or see people write it as cside or cside. While we advocate for using the correct spelling, we embrace the others.

And we’re here to put client-side security on the map.

  • Claiming ownership over what your users actually load
  • Making invisible threats visible again
  • Challenging the idea that the client-side protection is out of scope

We're building a platform that doesn't just patch the past, rather protects the present in its truest form. Today, browsers are the new OS, and scripts are the new supply chain.

So call us cside, cside, or cside.

Just know that we exist to protect the part of the web that everyone else forgot.

Simon Wijckmans
Founder & CEO

Founder and CEO of cside. Previously a product manager on Cloudflare Page Shield (now Cloudflare Client-Side Security). Co-chair of the W3C Anti-Fraud Community Group and a Forbes 30 Under 30 honoree. Building accessible security against client-side attacks, web security is not an enterprise-only problem.

Monitor and Secure Your Third-Party Scripts

Gain full visibility and control over every script delivered to your users to enhance site security and performance.

Start free, or try Business with a 14-day trial.

cside dashboard interface showing script monitoring and security analytics
Related Articles
Book a demo

Want to walk through this with an engineer?

Thirty minutes, on your own site. Not a slide deck.

Book a personalized demo to see:

How to achieve PCI DSS requirement 6.4.3 & 11.6.1 compliance in 1 day
Why third-party scripts are a security risk for you and your visitors
Monitoring privacy and consent leakage (GDPR, CCPA) across every third party
Stopping signup abuse, account sharing, and chargeback fraud with device intelligence
Detecting and controlling AI agents and bots hitting your site in real time

Rather just send a question?

Finding open slots…

Real humans only. We'd know.

Having trouble booking? Open scheduler in a new tab

What are you trying to solve?

Tell us in a line and we'll come back with something useful, not a generic pitch.

We usually help with:

Seeing which third-party scripts run on your site
PCI DSS 6.4.3 and 11.6.1 evidence
Bots, AI agents and account takeover

Prefer to just book a time? Pick a slot instead