Every AI infrastructure project starts with the same question: what do you want to own, and what do you want someone else to run?
The answer decides which engagement model fits. At Neoverse Technologies we offer four: build-to-suit, powered shell, colocation, and design and build. They share the same delivery capability underneath, but they divide ownership, scope and risk very differently. This guide focuses on the two that are most often compared, powered shell and build-to-suit, and shows where the other two fit.
Powered shell: you bring the technical stack
A powered shell is a commissioned building and infrastructure envelope, ready for the client's nominated hardware, network and operating stack.
- Who owns it: the client
- Neoverse scope: site, shell and utility infrastructure
- Outcome: ready for technical fit-out
- Risk allocation: shared at the demarcation point
Powered shell suits organizations that already have strong views on their technical fit-out, or their own operating teams, and mainly need the hardest part done for them: a site with power delivered and a building ready to receive their equipment.
The key to making it work is a clear demarcation. Both sides need to agree exactly where the shell and utility scope ends and the client's fit-out begins, because that line is also where risk changes hands.
Build-to-suit: we deliver the full facility
Build-to-suit is the most complete model. We secure the site, engineer the campus, deliver power and cooling, and construct to the agreed operating specification.
- Who owns it: flexible
- Neoverse scope: the full facility, to the client's specification
- Outcome: lease or handover
- Risk allocation: Neoverse-led development
Build-to-suit suits organizations that know what capacity and performance they need, but do not want to manage land, utilities, engineering and construction themselves. It brings together all three of our capabilities: design and build, host and operate, and procurement.
The other two models
Colocation is for clients who own the hardware and want to deploy into an operating environment. Neoverse provides power, cooling, security and operations, and the client contracts capacity. More on colocation
Design and build is for clients who already control land. We develop a high-density facility on that site, from engineering through commissioning, with optional ongoing operations management. Risk allocation is defined by contract. More on design and build
Side by side
| Powered shell | Build-to-suit | Colocation | Design and build | |
|---|---|---|---|---|
| Ownership | Client | Flexible | Client hardware | Client site |
| Neoverse scope | Site, shell and utility infrastructure | Full facility to client specification | Power, cooling, security and operations | Engineering through commissioning |
| Outcome | Ready for technical fit-out | Lease or handover | Contracted capacity | Turnkey delivery |
| Risk | Shared at demarcation | Neoverse-led development | Infrastructure operated by Neoverse | Contract-defined |
How to choose
Three questions usually settle it:
- Do you control a site already? If yes, design and build is the natural starting point.
- Do you want to run the technical environment yourself? If yes, powered shell gives you the most control. If no, build-to-suit or colocation hands that to us.
- Do you want to own the facility, or contract capacity? Ownership points to build-to-suit or powered shell. Contracted capacity points to colocation.
Whichever model you choose, the risks that matter are the same and are managed before construction starts: power certainty, the thermal envelope, program controls, and operational readiness. Every project moves through the same six decision gates, from feasibility and basis of design through detailed engineering, procurement, construction and commissioning. See our full capabilities.
Not sure which model fits? Request a turnkey RFP and we will map the options against your load plan.