Static Practice Security
Open source · Built in house

The security we run, set up for you.

We built our own protection for staticpractice.com and our games: hardened headers, account sign-in, email authentication and edge protection. We set up the same open-source setups for you, and hand you every config, so you own it outright.

Everything we set up is open source or standard configuration you can read, change and keep. No proprietary agent, no lock-in, no licence fees from us. When we're done, you get the files and the notes to run it yourself.

What we set up

Website hardening

Security headers and a Content-Security-Policy written for your site, HTTPS everywhere with HSTS, and safe framing and referrer rules.

  • CSP, HSTS, Permissions-Policy, COOP
  • Removal of files that should not be public
  • A before/after report

Sign-in and accounts

An account system you host: OAuth 2.0 with PKCE, signed tokens with published keys, hashed passwords, rate limits, and sign-in with Google, Discord or GitHub.

  • Single sign-on across your apps or games
  • Self-service: password change, sign-out everywhere, account deletion

Email and domain security

SPF, DKIM and DMARC so your domain can't be spoofed, plus address routing so every role inbox reaches the right person.

  • DNS records checked and documented
  • Routing for addresses like support@ and security@

Edge protection

Firewall rules, rate limiting and bot filtering at the edge, in front of your site or API, tuned so real users get through.

  • Cloudflare WAF and rate-limit rules
  • Protection for login and API endpoints

Privacy-first analytics

Visit counts without cookies or tracking, and event counts that store nothing about the person, with a privacy page that says exactly what is kept.

  • Cookieless analytics
  • A plain-language privacy page

Security review

A review of an existing setup: headers, sign-in, secrets, DNS and exposed files, with a written list of fixes in order of risk.

  • Findings ranked by risk
  • Fixes you can apply, or we apply them

How it works

  1. Get in touchUse the form below. Tell us what you run and what worries you.
  2. ScopeWe reply to agree what is covered and what access we need.
  3. Set upWe set it up and test it, with as little change to your day as possible.
  4. Hand overYou get every config, a written summary and the notes to run it yourself.

Get in touch

Tell us what you need. The form writes the email for you; it opens in your own email app, and nothing is sent until you press send there.

Keep [SP-SEC] at the start of the subject, in your first email and in every reply. It's how security requests are kept apart from everything else we receive, so a message without it may sit in the wrong queue.

Prefer to write it yourself? Email [email protected] and start the subject with [SP-SEC].