UK sovereign LLM inference

Original Article ↗ Hacker News Discussion ↗

A new UK-based AI inference service promises OpenAI-compatible APIs, significantly lower token costs, and strict in-country data residency, targeting sectors like healthcare, finance, and government that must keep data under UK jurisdiction. Commenters probe whether “sovereign” is an accurate label given foreign-made chips and models, and scrutinize issues such as privacy policies, pricing transparency (including caching), and comparisons to OpenRouter and US hyperscalers under the CLOUD Act. The exchange reflects growing demand for non-US AI infrastructure alongside skepticism about marketing claims and the UK’s broader ambitions for genuinely sovereign AI capabilities.

Product and Positioning

  • UK-based LLM inference platform with OpenAI-compatible API, targeting cost-sensitive users and those needing UK data residency.
  • Runs open-source / non-US models (e.g., DeepSeek V4 Pro, Kimi, Nemotron, GPT-OSS 120B) on NVIDIA Blackwell GPUs in a UK datacentre.
  • Presented as suitable for regulated sectors (finance, legal, health, defence) and as a Civo spin-out focused on “sovereign inference.”

Pricing and Cost-Savings Claims

  • Claims “up to 80% cheaper per token” vs OpenAI; some commenters challenge this as potentially misleading if not model-for-model comparable.
  • Token prices are listed in GBP; some UK-based users say they still expect USD pricing.
  • Confusion over plans: per-seat “unlimited chat” vs per-token API usage, especially for coding tools.
  • Cache pricing and economics are unclear; one commenter’s back-of-envelope comparison suggests it might be more expensive than a rival when heavy caching is used.

Data Sovereignty and CLOUD Act Concerns

  • Strong interest in avoiding US hyperscalers and US jurisdiction (CLOUD Act).
  • Platform claims fully UK-incorporated ownership, UK-resident leadership, and UK datacentre; no US parent, so CLOUD Act should not apply.
  • Some argue “sovereign” is oversold because chips, models, and energy are imported; others say “sovereign inference” reasonably means no foreign government can directly “pull the plug.”

Privacy, Terms, and Data Usage

  • Privacy policy allows sharing personal data outside the UK; retention periods require emailing for “additional information.”
  • Terms mention a separate Data Processing Agreement that isn’t easily found, raising concerns for serious commercial use.
  • Desire for explicit zero-retention options and clear opt-out of training on paid plans.

Comparisons to Alternatives

  • Compared to OpenAI, Anthropic, OpenRouter, Novita, Doubleword, and LocAI.
  • Value proposition: UK jurisdiction + cost vs US-centric providers and generic model routers.
  • Some see this as compelling for UK public sector / regulated workloads; others say OpenRouter and local deployment already cover their needs.

Model Quality and Technical Capabilities

  • Acknowledgment that GPT-5 / Claude Opus still lead on hardest reasoning tasks.
  • Advocates say open models now match frontier models on 80–90% of real use cases at much lower cost; critics call this optimistic and note heavy optimization and prompt-engineering overhead for OSS in enterprises.
  • Questions raised about prompt/prefix caching support; not clearly documented.
  • Tooling: supports OpenAI-compatible clients and coding assistants (e.g., OpenCode, Claude Code integrations mentioned).

Market Demand for “Sovereign” AI

  • Several commenters report strong demand in the UK for data-resident, non-US infrastructure, especially in government-adjacent sectors.
  • Others are skeptical of “sovereign X” as a buzzword, or note that true sovereignty would require control over chips, models, and energy.
  • Some argue jurisdictions like Switzerland are preferred for privacy, while UK residency is mainly about regulatory compliance.

Branding, UX, and Communication Feedback

  • Mixed reactions to the name “relaxAI” and associated marketing copy; some find it generic or confusing, others think it’s fine.
  • Criticism that the link went straight to docs with weak “About / who we are” context and few navigation links back to the main site.
  • Suggestions to make the UK ownership, datacentre location, and corporate structure more prominent and linkable (e.g., to official registries).