Hansa — an alliance of trusted operators

A league of towns beat an empire of ships.

In the thirteenth century the merchants of Lübeck, Bergen and Novgorod each had a harbour, a warehouse and a magistrate. None had a navy, a market, or enough cargo to fill a winter. So they wrote a charter instead of a merger.

The Hanseatic League owned few ships. It owned the apparatus of trust — a common weight, a common court, credit that moved between member towns, and a seal that told a buyer in Flanders that a cask loaded in Riga was what the manifest said. It lasted four hundred years.

We hold the fort for the alliance. Anyone can build a fleet.

AI is on the same path. Compute is concentrating in a few vast private harbours, while demand fragments into jurisdictions that will not let their data leave the country — and increasingly will not let it leave the building.

The people who can build in those jurisdictions are already there: a carrier with a substation, a utility with stranded hydro, an industrial group with twenty hectares and a grid connection nobody else can get. They hold the hardest inputs. They lack chip allocation, a capital stack, a buyer who trusts the site, and a way to prove any of it.

Hansa supplies those. Each operator stays independent, owns the site and prices its own capacity. What they adopt is a common standard for how a token is produced, proved and accounted for — and a market that treats every member’s capacity as first-class. Sovereign at every site, liquid across all of them.

One platform. Three capabilities a single operator cannot assemble alone.

AccessEcosystem and relationships

Standing relationships across the AI infrastructure stack — chip allocation and OEM supply, datacentre developers and power, model and token-generating systems, and the local technology operators who run the floor. We turn a site into a supply chain: silicon on a real delivery date, a build partner who has done it before, and demand waiting at the other end.

CapitalFinancing and access to capital

Compute is a financing business wearing an engineering costume. We structure and source it: equity at the project level, GPU-backed and asset-backed debt, vendor and export credit, offtake and prepay against contracted tokens. A member finances the asset against the contract, not against their balance sheet. Standardised hardware, standardised attestation and standardised offtake are what make the paper bankable.

AssuranceCustody and trust technology

Our core engineering. An unbroken chain of custody for every hardware asset — from purchase order and serial number through freight, install, firmware and decommission — bound to the silicon by cryptographic identity. On top of it, software assurance and a hardened operating enclave: attested boot, confidential execution of weights and prompts, customer-held keys, and a signed record of where each request ran. Lenders get collateral they can verify. Buyers get residency they can audit. Neither has to take the operator’s word for it.

Asset policyOwnership is a decision, not a doctrine

We are not obliged to own datacentres or servers, and in most markets the local operator should. Where the operating model calls for it — an anchor site, a strategic market, a position we need on the balance sheet to make the financing work — we will own, build or hold the asset ourselves.

Four articles. Every member signs the same ones.

Tokens stay where they are promised to stay

Data residency is enforced by the router and proven by the attestation, not asserted in a contract annex. A workload pinned to a country executes only on certified nodes physically in that country.

Every asset and every request leaves evidence

Hardware carries a custody record from purchase order to decommission. Each served request records the site, the silicon, the model version, the firmware measurement and the energy drawn, signed by the node and anchored in an append-only log the customer, the lender and the regulator can read.

The operator is accountable to their own law

Members answer to the courts and regulators where they stand. The alliance never asks a member to serve a request that is lawful somewhere else and unlawful at home.

Membership is open, revocable, and exit is a right

Any operator meeting the reference build may apply. Any member failing attestation is suspended automatically, within minutes, without a meeting. A departing member keeps their hardware, their customers and their data; the standard is open and the client libraries are permissively licensed, so leaving costs a migration, not a business.

What an attested hour looks like.

Every member site reports the same fields. Buyers query it by workload, auditors by jurisdiction, lenders by asset. Operators get paid from it.

Member site	Jurisdiction	Model	Tokens served	Attested nodes	Log anchor
Kontor Malmö	SE — EU	Llama 4 70B	412 M	64 / 64	a37f…91c2
Kontor Johor	MY	Qwen3 32B	1.08 B	256 / 256	b0d4…5e77
Kontor Querétaro	MX	Mistral Large	236 M	32 / 32	7c19…ae30
Kontor Tallinn	EE — EU	Llama 4 70B	88 M	16 / 16	4fe8…1b09
Kontor Abu Dhabi	AE	Falcon 3	644 M	128 / 128	d251…c8a4

Illustrative. Site names follow the Hanseatic convention: a kontor was a member town’s own trading house, run under its own roof and the league’s rules.

Three ways in.

Operators

You have power, a site and a licence — or GPUs already racked and half idle. You keep the asset and the customer. You adopt the reference build, pass attestation, and get chip allocation, a financing structure and demand.

Start an application

Buyers

You need inference placed in a named country, on named silicon, with an audit trail your regulator will accept. One endpoint, one contract, one invoice — and the right to name or exclude any site in the league.

Request an endpoint

Capital and jurisdictions

Lenders get collateral with a verifiable custody chain and cash flow tied to contracted tokens. Governments get domestic capacity built by the operators they already regulate, without writing a national champion a blank cheque.

Talk to us

The company is called Yet Another Cloud. That is the point.

The world does not need another cloud, and that is not what we are selling. We registered the most boring, most honest name available so nobody inside the company forgets it.

Hansa is the brand because the product is the league: the relationships, the capital, the custody chain, the seal. The compute belongs to its members — people already on the ground, already regulated, already known to the customers in front of them.

Trust does not scale from a headquarters. It scales from a standard.

Every token should have a return address.