sovereign46 | Sovereign compute for EU + UK
001 · index 41°09′46′′N 8°36′39′′W Private beta

Sovereign coding agents, on metal

The same coding agents. Your code, prompts, and repo context stay inside the EU or UK.

Get access Reply same day, from a founder.
002What it is

A drop-in backend for the coding harness your team already uses

Works with Pi, Claude Code, Codex. Point your tools at our endpoint.

s46
session
HARNESS >>
RUNTIME >>
MODEL >>
~/acme/auth-service — s46 run

                        
harness: pi runtime: javascript model: s46/kimi-k2.6 lane: EU-OPO
003Why

Engineering AI is infrastructure. Own the operating boundary

01 | Sovereignty

Your engineering data stays in lane

Choose an EU or UK lane. Prompts, repo context, logs, and training artifacts stay inside the lane you contract for, on hardware we control.

02 | Continuity

No single point of foundation-lab failure

Keep the harness your teams already use, but avoid making one lab the only path between your engineers and their shipping workflow.

03 | Economics

Predictable capacity after control

Owned metal and open weights make the unit economics legible and under your control.

004What you get

Stop renting your engineering AI

A complete stack: dispatch, training, runtime, mirror. Under a licence you can fork and a jurisdiction you choose.

01 | Long-running agents

Ship while you sleep

Dispatch an agent on Friday, review the PR on Monday. Multi-hour, multi-step work with the full context of your repo, your CI, your review history. Detach from one machine, re-attach from another.

DISPATCH / 04 agents 14:32 GMT Started Deadline AGNT_07 refactor/billing-again Review AGNT_03 fix/works-on-my-machine Implement AGNT_31 feature/final-final-v2 Plan AGNT_36 experimental/do-not-merge Spawn
02 | rl_lab.py

A model trained on your house style.

Open-source gyms wired to your repository: your conventions, your review history. Reward functions you can audit. Delivered with our partner network: certified, EU-resident, working under your DPA. The model lives in your tenant, runs on our metal, and gets sharper by the day.

RL_LAB / policy gym Ep 001 · success 00% · ε 1.00
Sample > action > reward > update Loop · Explore
03 | The only AI coding stack that doesn't care where it runs

Runs where your code runs

The harness, the runtime, the orchestrator: every piece, on your metal. On-prem, air-gapped, on a developer's laptop. One command. Our servers are optional. So is our cloud.

$ s46 mode --set local · stack reconciled in 0.4s.
04 | Push from cloud, pull on-prem

No fast lane, no slow lane

The engineer running agents on our cloud and the engineer running them on a laptop in the SCIF see the same repos, the same agents, the same context, the same reviews. Push from one, pull from the other.

On-prem (you) Repos Agents Context Review Cloud (us) Repos Agents Context Review Push Pull
05 | Licence

Yours to fork. Yours to run. Yours to keep.

BUSL licence. Runtime, orchestrator, deploy scripts. Inspectable, portable, transferable. You keep the stack whether you keep us or not.

Kimi k2.6 Gemma 3 DeepSeek-Coder Mistral Qwen3-Coder sovereign46
005The contract

Your data stays in your sovereign lane

EU and UK lanes are treated as separate operating boundaries.

EU + UK GDPRLane-specific DPA schedule
SOC 2Compliant
DPATraining, retention, deletion
SLAProduction commitments
Audit logsTamper-evident, exportable
SSOSAML / OIDC
006Who it is for

Engineering organisations with sovereign data requirements and 50+ developers using coding agents.

01Teams of 50–250 developersCore
02Teams of 250–1,000Core
03Teams of 1,000+Enterprise
04Regulated industriesCloud & on-prem
05Sovereignty-sensitiveOn-prem
007Get access

Same harness. Sovereign metal. Your rules.