Security is built in, not bolted on.

We think about security in three parts: the code we write, the data your software holds, and keeping it available when your team needs it. Here is what that means in practice.

Secure code
Built against the OWASP Top 10
Every change
Reviewed and scanned for vulnerabilities
Your data
Its own database, hosted in your region
Availability
Monitored, with daily backups

The tools and standards behind it

  • Cloudflare WAF

    A web application firewall in front of your software, blocking attacks before they reach it.

  • Semgrep

    Scans every code change for security issues before it ships.

  • OWASP Top 10

    The industry list of web application risks our code is built and reviewed against.

  • Google Cloud

    Failover and redundancy, so your software stays up if part of it fails.

  • Stripe

    Handles every payment. Card details never touch our servers.

Secure code

Security is part of every step of the build, not a check at the end.

  • We follow a secure development lifecycle: security is considered when we design a feature, while we build it, and before it ships.
  • We build and review against the OWASP Top 10, the most common ways web applications are attacked, such as injection and broken access control.
  • Every code change is scanned with Semgrep for vulnerabilities, in our code and in the libraries it uses, before it reaches your software.
  • An engineer reviews every change before it ships.
  • Logins, roles and permissions are checked on the server, not just in the browser.
  • Keys and passwords live in the hosting platform's secret store, never in the code.

Your data

It stays yours, it stays separate, and it stays where it should.

  • Each client's software runs on its own database. It is never shared with another client.
  • We host your software and data in the region you need, so it stays where your obligations say it should.
  • Everything travels over encrypted HTTPS connections.
  • You own your data and can export it at any time. If you leave, you get a full export, and the source code on request.

Availability

Software your team can rely on, and a way back if something breaks.

  • Cloudflare's web application firewall sits in front of your software and blocks common attacks and abusive traffic.
  • Failover and redundancy on Google Cloud, so a single failure doesn't take your software down.
  • Daily automated database backups, so data can be restored after a failure or a mistake.
  • Uptime and error monitoring, so we usually know about a problem before you do.
  • Dependencies are kept up to date, and security patches are applied promptly.
  • Access to live systems is limited to named team members, each with two-factor authentication.

Payments

Handled by Stripe, end to end.

  • Card and bank details are entered on Stripe's own pages and never touch our servers.
  • Payment updates reach the portal through signed messages from Stripe, which are verified before they are used.

Your client portal

The portal you sign in to follows the same rules.

  • Every sign-in needs a code from an authenticator app such as Google Authenticator, as well as your password.
  • Passwords are stored as one-way hashes, never as readable text.
  • Sessions use secure cookies that page scripts cannot read.
  • Repeated failed sign-ins are blocked for a while to stop password guessing.
  • Each client can see only their own projects, tickets and invoices.

If something goes wrong

Fast, honest and on the record.

  • We contain the problem first, then tell affected clients promptly with what we know.
  • We fix it, restore from backup if needed, and confirm with you when it is resolved.
  • You get a written summary of what happened and what we changed.

Have a security question?

Ask us anything about how we would protect your software, or tell us about a vulnerability you have found. We take every report seriously.