Launch a cloud, not a platform organisation

You have the hardware, the power contract and the customers in the pipeline. Genesis Grid supplies what sits between them — portal, tenancy, quotas, metering, identity — under your own brand, so your engineers stop building a cloud and start selling one. You still run the platform, with a smaller and less specialised team than a stack of your own would need.

The build-versus-buy clock

Your real competitor is your own roadmap

Nobody loses this race to another vendor. They lose it to the control plane, the tenancy model, the metering pipeline and the portal their own team has to build first, while the accelerators depreciate in the rack. Genesis Grid is eight years and two complete rewrites of that work. What the capacity is then worth still depends on demand you can reach: the stack makes capacity sellable, not sold.

2 weeks

from signed contract to first invoice, pilot and cluster onboarding included

2 days

to stand the stack up on a further cluster

Day one

Live on day one, under your brand

Arrow
White-label portal and API: Your logo, colours, domain and product names, and the surfaces that usually leak with them: API hostnames and error strings, CLI and SDK package names, TLS certificates on your domain, transactional mail from your sender, your status page. Where something still carries our name it is listed in the contract before you sign, rather than found by a tenant in a stack trace.
Arrow
Self-service onboarding: Tenants register, verify and reach working capacity without a ticket or an engineer from your side. That is what keeps small orders profitable and keeps capacity selling outside your office hours.
Arrow
Accounts, projects and roles: An identity and organisation model cut to the shape buyers already know from AWS: accounts under an organisation, projects, roles, policies and per-tenant credentials. Enterprise buyers map their own structure onto it on day one instead of asking you for a feature.
Arrow
Isolation you can put in a contract: InfiniBand partition keys on the fabric, per-tenant network segmentation, and namespaces with per-tenant credentials and quotas in Ceph and VAST. One cluster serves many tenants at once and each one stays inside its own boundary.
Arrow
Quotas, metering and invoicing: Per-tenant limits and a meter that runs from the first call, feeding invoices on demand, reserved, per node or per token — whichever way you sell. You add a billing shape rather than lose the deal that needed it.
Arrow
Operator tooling: Your team sees tenants, adjusts quotas, drains nodes and handles incidents from one place, without shelling into machines.
How operators start

Start on what you already own

One cluster first
Point Genesis Grid at a single cluster and sell the capacity that has no contract against it today. The accelerators and the fabric stay as they are. What you add is control-plane and management nodes, out-of-band reachability on every node, and VAST hardware only if you want to sell shared file.
Arrow
More clusters as you grow
Each site you run is its own cluster with its own tenants, and the stack is hardware-agnostic, so mixed vendors and mixed generations are normal rather than a migration project. Multi-tenancy is enforced inside a cluster, which is where your tenants run.
Arrow
Both books from day one
Sell committed capacity at a fixed term to underwrite the site, and let short-lived on-demand buyers fill the space around it at a far better price per hour. The same cluster carries both books.
Arrow
Svg

Questions before you build it yourself

Why not build this in-house?
Substrack Icon

Because the build is not the portal, it is everything under it: scheduling, isolation, quotas, metering, invoicing and upgrades. That is twenty to thirty engineers permanently, against four to six to run Genesis Grid under a licence. It is also work with few finished answers in the open: we stripped Kubernetes back until it orchestrates virtual machines instead of containers, made InfiniBand multi-tenant over partition keys in a way that surprised NVIDIA's own engineers, and run VPP and SPDK in user space to hold line rate from 200 to 800G.

Can we promise performance when tenants share a cluster?
Plus Icon

Yes, and the mechanism is specific rather than a policy — partition keys on the fabric, segmentation on the network, namespaces in storage, all listed above. Each tenant runs against the service level you sold it rather than a best-effort share of whatever is free. What a tenant environment is available for rests on your building and your hardware, so that number is yours to set. What Genesis commits to is the control plane, the portal and the meter at 99.9 %.

Does our existing hardware qualify?
Plus Icon

Mixed vendors and mixed generations are workable, and so are facilities below the top topology class — with one honest limit. Uptime Institute's Tier I to IV describe redundancy and what can be maintained while the site keeps running, not availability percentages. Software resilience shifts how much redundancy the building must carry for a given class of tenant; it does not replace it. A deployment is one cluster in one building: if that building loses power, the cluster goes down. We say so before you put a number in a contract.

Who runs the platform, and who runs what?
Plus Icon

You keep the facility, the hardware, the commercial terms and the tenant, and you run the platform yourself in both contract forms. Genesis backs your team with escalation support: 30 minutes on severity one, 24/7, with escalation to the engineers who build the stack. The split is written down line by line before anything is signed.

Has anyone else built on this?
Plus Icon

Volta licensed Genesis Grid and is building its platform on it. On 5 August 2026 Volta raised USD 300 million at a USD 2.4 billion valuation, co-led by Andreessen Horowitz and Altimeter with NVIDIA and Michael Dell participating, alongside USD 5 billion of customer financing and a six-year, USD 10 billion cloud contract delivered with Bitdeer from a 133 MW data centre in Norway. Founders Ricard Boada and Sofia Gumuzio came from Brookfield. Volta is the licensee we are allowed to name.

Do you compete with us for our own tenants?
Plus Icon

No. Genesis Cloud is a software company today: we license the stack and sell no capacity, so there is no rate card of ours to bid against yours. We were the operator before that — on the market since 2018, more than 20,000 users, and demanding buyers chose the cluster we ran. Photoroom took 256 H100s, and its co-founder Eliot Andres wrote up the decision publicly on 8 July 2024, describing Genesis Cloud as "a German provider that offers an Infiniband cluster that runs on CO2-free hydroelectricity". He states plainly that it is not an endorsement, which is what makes it worth reading.

Your hardware, your brand
Map your route to the first invoice
Arrow
Close Cookie Popup
Cookie Preferences
By clicking “Accept All”, you agree to the storing of cookies on your device to enhance site navigation, analyze site usage and assist in our marketing efforts as outlined in our cookie policy.
Strictly Necessary (Always Active)
Cookies required to enable basic website functionality.
Cookies helping us understand how this website performs, how visitors interact with the site, and whether there may be technical issues.
Cookies used to deliver advertising that is more relevant to you and your interests.
Cookies allowing the website to remember choices you make (such as your user name, language, or the region you are in).