Models 14,200+ · day one
Open weights from the major labs, mirrored across every continental operator, every version content-addressed. No git, no LFS, no surprises.
- Open-source LLM weights
- Diffusion / vision / audio
- LoRA and adapter packs
A federated registry for machine-learning artifacts. Six continental operators, each incorporated under its own law, share one open content-addressed protocol. Where your weights live is where your regulator sits.
Same workflow as the registries you already use, with one essential difference: every artifact is hosted by an entity that answers to your law, not to a single foreign cloud.
Open weights from the major labs, mirrored across every continental operator, every version content-addressed. No git, no LFS, no surprises.
Federated dataset registry. Residency-aware by default — a dataset stamped EU-only never leaves the European operator's jurisdiction without an explicit, logged export.
Hosted inference and demos, deployed in the operator of your choosing. Pin your evaluation to a single jurisdiction — useful for audits, procurement, and reproducible disclosures.
Indexed, signed, content-addressed. Each card carries the operator that holds it, the license, the residency clause, and the manifest digest.
Illustrative previews. Exact catalogue and metadata subject to the operator's regional residency policy at launch.
Each continental entity is independently incorporated under the law of its seat, with its own board, treasury, and audit obligations. None can compel the others. None can be quietly acquired.
stichting-concord-europa
Dutch foundation. Operates 11 sites across Amsterdam, Frankfurt, Stockholm, Madrid, and Warsaw. Custodian of EU/EEA residency manifests.
concord-boréal-société
Québec non-profit society. Nine sites across Montréal, Toronto, Vancouver, Calgary, Ottawa, Halifax, and Yellowknife. Subject to Canadian federal and Québec civil law.
asociación-concord-del-sur
Uruguayan civil association. Five sites across Montevideo, Buenos Aires, São Paulo, and Santiago. LATAM residency custodian.
concord-afrika-trust
South African public-benefit trust. Six sites across Cape Town, Lagos, Nairobi, Johannesburg, and Casablanca. Pan-African residency custodian.
concord-asia-foundation
Singapore company limited by guarantee. Fourteen sites across SG, Tokyo, Seoul, Mumbai, Jakarta, Taipei, and Bangkok. Subject to PDPA and APEC CBPR.
concord-pacific-foundation
New Zealand charitable incorporated society. Four sites across Wellington, Auckland, Sydney, and Perth. Pacific and Antarctic residency custodian.
One spec. Reference clients in Rust, Python, and Go. Protocol-compatible with the existing HuggingFace Hub HTTP surface — point your tooling at the operator of your jurisdiction by changing one URL.
A version is a short signed manifest naming a handful of shards — weights, tokenizer, config — each given as a merkle root. Chunks exist below the line, fixed-boundary blake3 leaves the protocol uses for dedup but the manifest never enumerates.
No git, no LFS, no commit history. A version exists if and only if its manifest is signed by an operator key. Reverting a release means signing a prior manifest.
Identical tokenizer shards or LoRA bases are stored once per region — never six times. A typical pull on Concordfaces transfers 6–10% of the wire bytes of an equivalent HF pull.
Clients pull from their continental operator. Cross-border fetch is opt-in, logged per manifest, and observes the residency clause of the requesting jurisdiction.
Names resolve through gossip between operators. Any one operator may delist for legal cause within its jurisdiction without affecting the others.
# A version = a signed manifest. Shards are merkle-rooted # over fixed-boundary blake3 chunks (impl detail, not here). [manifest] name = "mistral/mixtral-8x22b" version = "v0.3.1" protocol = "concord/1" issuer = "eu:stichting-concord-europa" issued_at = 2026-05-13T09:14:22Z [license] spdx = "Apache-2.0" residency = "any" # eu|na|sa|af|as|oc|any export = "unrestricted" # Shards are the addressable unit. Each is a merkle root over # the chunks beneath it — the manifest never lists chunks. [[shard]] role = "weights" format = "safetensors" parts = 56 size = 90_172_948_480 merkle = "b3:7a4e…9c2f" [[shard]] role = "tokenizer" format = "tokenizers.json" size = 2_412_904 merkle = "b3:88a0…f0e1" [[shard]] role = "config" format = "json" size = 1_847 merkle = "b3:c911…02de" [signature] alg = "ed25519" key = "eu:europa:k/2026-01" sig = "5f3c…d091"
$ concord pull mistral/mixtral-8x22b:v0.3 resolving via eu:stichting-concord-europa manifest b3:7a4e…9c2f signed ed25519 license Apache-2.0 residency=eu [1/188] weights/0 cache-hit [2/188] weights/1 eu:ams-3 … [188/188] tokenizer eu:ams-1 ✓ 91.4 GiB · 6.2 GiB on the wire (dedup 93.2%) ✓ residency observed: EU → EU $ _
Bytes don't recognise borders. Residency in Concordfaces is a legal & audit construct, backed by routing and L7 refusal — not a cryptographic guarantee. Here is what each layer stops, and where its limits sit. We would rather be specific than be quoted later.
/v1/pull endpoint without an explicit cross-border manifest. Refusal is signed and logged.
VPN egressing inside the region, residential proxies inside the region, mis-tagged corporate NAT.
concord CLI) refuse to fetch cross-border unless the manifest's residency clause permits and the user has supplied a signed cross-border token.
An attacker controlling their own client. Bytes once received cannot be recalled.
Each continental operator advertises its own anycast prefix (e.g. eu.concordfaces.org) from its in-region ASes only, with BGP communities scoping propagation to local IXPs and continental transit. This is a performance and soft-gating optimisation. It is not a fence. We say so plainly.
There is no single anycasted concordfaces.org that resolves to the nearest operator. That would break residency semantics — BGP picks shortest path, not jurisdiction-correct path. Clients resolve through the federation gossip layer and a jurisdiction hint, not through routing.
Not "no foreigner ever saw them." Rather: "if an auditor asks where the weights are, the answer is here, with this signed proof — and any cross-border fetch is named, dated, and admissible." The product is provenance, not impossibility.
Each operator answers to the law of its seat. A subpoena issued in one capital is not a subpoena in another. Your data resides where its regulator sits — by default, not by exception.
Six independent treasuries. Six legal forms. Six failure domains. The collapse, capture, or sanction of any one entity leaves the protocol — and your weights — intact.
Council seats rotate annually. Protocol changes require four of six. No single operator may both author and ratify. The economics of hosting cannot consolidate into a hyperscaler-shaped chokepoint.
Three accession waves. Every operator is incorporated before it ingests its first chunk.
RFC 0001 ratified by all six operators. Public draft of the specification published. Reference clients in private alpha.
Stichting Concord Europa and Concord Boréal Société open to the public. Models, signed manifests, residency clauses live. CLI v1.0.
Latin American and African operators come online. Federated datasets enter public beta. First cross-continental residency audits published.
Singapore and Wellington open, completing the federation. Spaces (hosted inference) enter alpha. Training receipts for reproducible evaluations.
If a single foreign cloud is a non-starter, you are who this is for.
Get a single email when the operator of your jurisdiction enters public mainnet. No marketing, no list-rental, no third-party trackers.
// One notice per operator · unsubscribe in one click · no analytics