Cloudflare

Cloudflare provides DNS, a content delivery network and security services for websites. I use it around my public SaaS products to manage domains, cache static files and help protect forms from automated submissions.

Where I use Cloudflare

VetCard, VetSpace and DigiPulse combine public pages with application features. These need different caching rules: an image can be shared between visitors, while appointment details and account responses must remain private. DigiPulse also uses Turnstile on public forms.

Caching and form protection

• Static assets — cache suitable images, styles and scripts closer to visitors.
• Dynamic responses — exclude personalized data from shared caches.
• Turnstile — validate the submitted token on the server; the browser widget alone is insufficient.

What still belongs to the application

Cloudflare complements input validation, authorization and request limits. It does not replace them. I treat cache rules and the connection to the origin server as part of the deployment configuration. Available security features and limits depend on the selected services and plan.