Book a Technology Review

Home/Security & infrastructure

Trust

How it is hosted, backed up and secured.

Hosting, backups, authentication, deployment and security — answered properly, because “it is on the cloud” is not an answer.

How the systems we build are hosted, backed up, secured and released. This page exists because “it is on the cloud” is not an answer, and because the questions below are the ones your IT team, your insurer and your auditor will ask.

Hosting

Systems run on Microsoft Azure or AWS, chosen per project — usually whichever your business already has a commercial relationship and a security review for. Infrastructure is defined in configuration rather than clicked together by hand, so the environment can be rebuilt from scratch and staging genuinely matches production.

Where a system holds personal data of UK residents, our default is a UK or EEA region. Static marketing sites sit behind a CDN; applications sit behind the cloud provider’s own load balancing and WAF.

  • Azure
  • AWS
  • Load & uptime monitoring
  • Observability
  • Caching layer

Backups

Databases are backed up automatically with point-in-time recovery, so a restore can target the moment before a bad deployment or a mistaken delete rather than last night. Retention is set per system against how far back an error could plausibly go unnoticed — a finance integration needs a longer window than a brochure site.

A backup nobody has restored is a hope, not a backup. Restores are rehearsed into a scratch environment, and the rehearsal is what we report on, not the fact that the job ran.

Authentication and access

Wherever your business already has an identity provider — Microsoft Entra, Google Workspace, Okta — applications federate to it over OAuth 2.0 or SAML. That matters for one practical reason: when HR disables a leaver, access to the system goes with it, instead of depending on someone remembering a separate user list.

Where there is no identity provider, accounts carry multi-factor authentication and role-based permissions. Reporting is enforced at the row level, so a regional manager querying the same dashboard as the board sees their own region.

  • SSO & MFA
  • OAuth 2.0 / SAML
  • Row-level security
  • MDM & biometrics

Deployment

Every change reaches production the same way: committed to version control, reviewed, run through an automated test suite, then released by pipeline. Nobody edits a file on a live server, and nothing ships that the pipeline has not built.

Releases are reversible. Database migrations are written so the previous version of the application still runs against the new schema, which is what makes a rollback a decision rather than an incident.

  • CI/CD pipelines
  • Automated test suites
  • Run monitoring
  • Scheduled jobs

Security

Traffic is HTTPS only. Secrets live in the cloud provider’s secret store, never in source control. Dependencies are monitored for published vulnerabilities and patched on a schedule rather than on alarm. Input is validated server-side on the assumption that the client can be lied to, and database access is parameterised throughout.

Integrations authenticate per system with scoped credentials, so a compromised key for one connection cannot be replayed against another. Where a system handles payments we use a provider’s hosted flow — card details do not touch our infrastructure.

Monitoring and what happens at 2am

Uptime, error rates and the health of every scheduled job are monitored, with alerting on thresholds rather than on a human noticing. Integration runs are logged with an audit trail, so when a nightly posting into Sage or Business Central fails the question is which record and why, answered from the log, not reconstructed from memory.

Your code is yours

Source code lives in your repository, under your organisation, from the first commit. There is no proprietary runtime between you and your own data, and no part of the system requires us to keep operating for it to keep running. If you want to take it in-house or to another supplier, the handover is a transfer of access, not a negotiation.

This website

For completeness, since it is the system you are looking at: static HTML served over HTTPS behind Cloudflare, with one server-side form handler. It sets no tracking cookies — see the cookie policy and the privacy policy. The stack we build client systems with is listed on technology stack.

Next step

Start with a technology review, not a proposal.

A short, structured conversation about where your systems are costing you time, margin or growth — and what the realistic options are. No pitch deck.