You have just landed a contract with a Manchester-based client who insists the website must be "hosted in the UK". The wording feels vague, but the client expects a real answer, not marketing fluff.
What "UK hosted" actually means
TrueCore's data lives on three nodes we call ember, spark, and litespeed. The ember node runs in a Netcup facility in Nuremberg, Germany. The spark node sits in Sofia, Bulgaria, and litespeed is in Dallas, USA. All three run Alpine Linux and our custom flame-bubble containers. The company behind them — contracts, billing, support — is UK-registered.
When we say "hosted in the UK", we refer to jurisdiction, not metal. Your files and databases stay under UK law because the contract, support tickets, and all personal-data handling are processed by our UK-registered company. The underlying servers may be a few hops away, but the legal relationship is UK-centric.
Why data residency matters for SMEs
GDPR and UK GDPR
The UK GDPR requires personal data about UK residents to stay in a jurisdiction with adequate protection. If your site collects names, emails, or payment details, you must either keep the data in the UK or rely on a recognised adequacy mechanism. Hosting with a provider that stores data outside the UK forces you to add Standard Contractual Clauses or the UK-EU Data Privacy Framework to every contract. That adds paperwork and cost.
Sector-specific rules
Finance, health, and education sectors often carry extra contractual clauses about where client records may live. If your client imposes one, read it carefully: some require UK-or-EEA storage (which a German node satisfies), others demand UK soil specifically. Know which one you signed before you pick a host — ours included.
Trust and perception
Your clients see a UK address on the contract, a UK-based support email, and a UK-registered company number. That builds confidence, especially for local businesses that value domestic data handling.
What you get in practice
Latency that feels local
A server in Nuremberg adds roughly 20-25 ms round-trip to a visitor in London. In a typical WordPress page that makes 20 requests, the extra time is under 200 ms total. As we showed in our "UK vs US Hosting" post, a London-to-London round-trip is 5-15 ms. The difference is measurable but rarely noticeable for standard page loads. If you need sub-10 ms first-byte, you would need a true London node, which we do not currently offer.
UK-focused support
Support is handled during UK business hours by the engineer who runs the platform — no offshore tier-1 queue. We do not promise 24/7 phone support, but urgent incidents trigger our flame-sentinel heartbeat that alerts us via Discord.
Backups under UK law
Backups are taken with restic, encrypted before leaving the node, and stored in Backblaze B2 buckets that we access from the UK. The backup interval you choose (daily, 12-hourly, 6-hourly, or 30-minute) follows the same jurisdictional rules because the encryption key never leaves our control.
Database and software versions
Plans that include databases give you a private PostgreSQL 16 instance. All PHP sites run PHP 8.3 under PHP-FPM. These versions are current as of today and receive security updates directly from the upstream projects.
DNS that respects UK ownership
Our custom DNS daemon, flame-dnsd, runs on all three nodes. The authoritative nameservers are ember.truecorehosting.com, spark.truecorehosting.com, and litespeed.truecorehosting.com. You can query one directly with a simple command:
dig @ember.truecorehosting.com example.com A +shortThe answer comes back in milliseconds because our DNS fleet propagates changes in under five seconds via inotify and WireGuard rsync. As we explained in the "How DNS Works" post, the low TTL (default 3600 s, reduced to 300 s for quick changes) keeps resolvers up to date.
Cost that matches the promise
Our plans start at £10 / mo for a single site with 4 GB storage and daily backups. The Flameling plan includes SQLite only, while the Ember plan (£20 / mo) gives you three sites, PostgreSQL 16, and 12-hourly backups. Annual price rises are capped at 2.5 % with a 30-day notice, and you can try any plan for £1 for 14 days before committing to a full month.
When "UK hosted" isn't the right choice
If your audience is primarily overseas, the latency benefit of a UK node disappears. If you rely on US-based APIs that enforce IP-based allow-lists, keeping data close to those services can simplify networking. In those cases, a US or EU node may be more convenient, and you can still keep contracts and support in the UK.
Bottom line for SME owners
- Legal certainty - Your data stays under UK law, reducing paperwork.
- Reasonable performance - A 20-25 ms extra hop is invisible for most sites.
- Local support - Tickets are answered from the UK, during UK business hours, by the engineer who runs the platform.
- Transparent pricing - No hidden fees, clear backup intervals, and capped price rises.
If the contract you just signed asks for "hosting in the UK", TrueCore gives you exactly that: UK jurisdiction, UK-focused support, and a hosting stack that balances cost, performance, and compliance. The metal may sit in Germany, but the legal relationship stays firmly British.