Sovereignty · UK-only data

Monitoring is surveillance in reverse.

Every uptime monitor in existence generates a continuous record of what your systems do, when they do it, and what they return. That record is a sensitive map of your business. Most monitoring companies keep it in jurisdictions that allow your map to be subpoenaed without your knowledge.

We do not.

II. Residency

Ours doesn't leave.

Every byte of customer data — account records, monitor configurations, credentials (encrypted with AES-256-GCM), check results, incident timelines, audit logs, notification logs, screenshots — lives on servers inside the United Kingdom.

Not in a UK region of a US hyperscaler. Not "EU data residency with fallback." Physical hardware in Contabo's Portsmouth data centre, expanding to London and Manchester. Operated by Skyie Global Technologies Ltd, a UK company registered in England and Wales.

The only data that transits outside the UK is the target URL + check configuration of monitors you've opted in to checking from our Frankfurt probe. Even then: no storage, no cookies, no PII. The result returns to the UK coordinator and is stored here.

Portsmouthprimary region

III. Jurisdiction

The CLOUD Act, in plain English.

Procurement teams know the phrase; most engineers don't. Here is the two-minute version.

What it is

The Clarifying Lawful Overseas Use of Data Act is a 2018 US law. It lets US law enforcement compel any US-based communications provider to hand over data it holds — regardless of where that data physically sits.

If your monitoring vendor is a US company, or if a US company can buy them, or if their UK subsidiary reports to a US parent, that data is reachable by CLOUD Act warrant.

Why it matters

The warrant can include a gag clause preventing the provider from notifying you that your data was requested. Your monitoring telemetry — which contains detailed infrastructure topology, authentication endpoints, and error patterns — is handed over; you don't know.

UK Schrems II assessments, FCA PS21/3 operational resilience requirements, and NHS DSPT all treat CLOUD Act exposure as a material risk.

Why Skyie Uptime isn't touched.

  • We are a UK company (Companies House 15882201), operated from London, with no US parent, subsidiary, or investor.
  • All data storage uses UK-resident infrastructure (Contabo UK). None of our sub-processors are CLOUD-Act-reachable.
  • We are not a communications provider under the UK-US Data Access Agreement. Monitoring telemetry is not "communications data."
  • UK legal requests go through the UK Investigatory Powers Act 2016 — with judicial oversight, proportionality review, and (in most cases) notification.

IV. Ledger

What we are, and what we are not.

The competing claims of every monitoring vendor, side by side. Last updated October 2026.

DimensionSkyie UptimeBetter StackPingdomUptimeRobotDatadog
UK legal entity
UK data residency
Outside US CLOUD Act
ICO-registered DPO
Cyber Essentials
G-Cloud 14 listingPlanned Q3
Per-seat pricing
White-label
Integrated status pages

Competitor rows reflect public information and marketing material at time of publication. If anything here is inaccurate, email [email protected] and we will correct it within 5 working days.

Honesty

We are not monks.

Some of our tooling is American. GitHub hosts our source code. Our CI runners are GitHub-hosted Ubuntu VMs. npm, the JavaScript package registry, is US-based.

None of that touches your customer data. Source code describes the product; it does not contain monitor results, customer accounts, or incident timelines. Our prod database, Redis, object storage, and backups are UK-resident.

When US-resident development tooling creates a real risk — say, a supply-chain compromise of an npm dependency — we mitigate by pinning and signing. Every dependency is lock-filed; every GitHub Action is SHA-pinned; Renovate drives both forward on a verified-digest basis. SBOM shipped per build.

Boring, specific, verifiable. The opposite of marketing.

Your uptime data never leaves the UK.

Period.