Sovereign AI is not a badge on a landing page. It is five answers — who operates the platform, where the data physically sits, who owns the contracting company, whose courts can compel access, and who is in the next rack. Genesis Grid gives you a demonstrable mechanism for three of them; the other two are answered by your own corporate structure, and we tell you plainly which is which.
Each cluster carries a stated country and operating entity. Your tenants choose where their workloads may run, and the scheduler treats the constraint as a hard limit: a workload that cannot be placed inside it waits rather than moving.
Each of the three mechanisms — partition keys, network segmentation, storage namespaces — is something your buyer's engineers can test, not a sentence in a proposal.
Every placement, every node hand-over and every administrative access is recorded and retained for seven years. You can show a regulator what ran where and under whose account, and hand the same records to a customer who asks.
Organisations, accounts, roles and policies cut to the shape enterprise buyers already run on AWS. Your customer's security team maps controls it already owns onto your platform instead of learning a private scheme.
A sovereignty claim survives exactly as long as the ownership chain behind it. Genesis Cloud GmbH is a German company, independently held: no chip manufacturer, no hyperscaler and no foreign parent owns Genesis or the roadmap. You license software and run it yourself, so you take on no foreign counterparty in your data path along with it.
Genesis-operated components in your production data path
retention for placement, hand-over and administrative access records
No standing access. There is no Genesis account in your control plane and no support tunnel we can open from our side. Where you want us inside an incident, you grant a time-boxed break-glass session that your own IAM issues, your staff observes and your audit log records like any other access. The control plane does not phone home to keep running, and you pull releases rather than having them pushed at you. Ask every vendor you evaluate those two questions in writing, including us.
.svg){kind=small}
Yes, where separation is enforced and demonstrable. Your buyer's regulator reads the audit trail and your buyer's engineers test the mechanism, and both exist here.
Those laws follow the corporate group, not the building. Where no company in your ownership chain or in your data path is subject to U.S. law, that route is closed — and Genesis being your software vendor does not open it, because we neither operate your platform nor hold your customer's contract. Get the ownership chain of every vendor on your list in writing, ours included.
None on its own. Certification attaches to an operator and a facility, and that is you. What the stack contributes is the evidence an audit needs: enforced placement, a documented separation mechanism and a complete access record. ISO 27001 certification covers what Genesis holds as your supplier.
Yes. Placement constraints are part of the tenant agreement and the scheduler treats them as hard limits. There is no cross-site scheduling that could override them, and a workload that cannot be placed inside its constraint waits instead of being relocated to satisfy demand elsewhere.
You sell it to them. Reserved capacity assigns the device whole to one tenant for the term, and it costs what dedicated capacity costs. The price advantage comes from sharing, so it does not follow anyone into single tenancy, and both models bill through the same meter.
