Power for compute.
Translate the tenant equipment schedule into distribution, resilience and metering requirements.
COMPANY INTRODUCTION
AI factory infrastructure, from supply chain to site.
partner@lintelinfra.ai
Approved cooling-array illustration · not an owned or completed Lintel facility.
Site and power planning, equipment sourcing, and electrical, cooling and modular systems.
Record site rights, utility conditions and timing. Utility supply and critical IT load are separate figures.
Coordinate supplier scope, electrical and cooling interfaces, lead times and installation access around the selected equipment.
Agree acceptance tests, record results and unresolved items, then hand over operating and maintenance responsibilities.
Projects are in development. The image is illustrative; no owned facility or available capacity is claimed. Contracts define design, purchase, ownership, payment, delivery and operation.
Buy a development or delivery scope; add contracted facility services where applicable.
Compute operators and enterprises with a defined facility requirement. Site and power owners engage under a development or cooperation mandate.
Development, engineering and integration milestones; facility capacity, colocation and asset-management fees where contracted. Equipment purchases and project capital stay separate.
Lintel focuses on facilities; INTERTIE develops compute and model services. Each project agrees capacity, equipment ownership, acceptance and operating responsibilities.
Repeat specifications, interfaces and acceptance methods. Site rights, utility evidence, approvals and responsibility remain project-specific.
Our work covers site and power planning, equipment sourcing, and the integration of electrical, cooling and modular systems.
Land or building rights, site assessment and utility coordination.
Design, permits, equipment and construction scope.
Power, cooling, space and connectivity for tenant compute.
Commissioning, operating handover and project responsibilities.
Illustrative equipment arrangement, not inventory or a product specification. Projects are in development; each project defines its selected hardware and capacity.
Our development focus includes GB300 liquid-cooled facilities and Vera Rubin infrastructure. Each platform brings a different thermal basis to the power, cooling and building design.
Plan the facility loop, distribution unit and rack interface together. Confirm flow, pressure, temperature and fluid requirements against the selected equipment.
Translate the tenant equipment schedule into distribution, resilience and metering requirements.
For GB300, CPUs and GPUs are liquid-cooled, with air cooling for other components. Vera Rubin's full-liquid architecture changes that design basis.
Coordinate modular electrical and cooling packages, cooling distribution units, pipework and maintenance access with the rack layout.
NVIDIA GB rack hardware guide is the dated equipment reference, not Lintel capacity. Cabinet image is an edited illustration, not a GB300 or Vera Rubin product specification. The selected equipment sets the project design basis.
Clients provide us with a tenant brief that sets out the technical and commercial requirements for their desired facility.
| Requirement | Project specification |
|---|---|
| Location and power | Location, utility supply and critical IT load. |
| Compute environment | Rack density, cooling and connectivity. |
| Delivery | Phasing, installation interfaces and required service date. |
| Commercial | Facility term, service scope and payment structure. |
Utility supply and critical IT load are reported separately.
Project agreements identify who designs, buys, owns, delivers and operates each part. Development, facility services and compute operations have separate scopes.
Each phase produces the evidence and agreements needed for the next. The selected equipment, supplier interfaces and site conditions set the project programme.
Establish the site and power basis.
Phase record:Site assessment · utility information · permit path · open conditions
Define the facility and delivery scope.
Phase record:Design basis · responsibility matrix · cost plan · phased programme
Build and commission the agreed scope.
Phase record:Approved delivery scope · construction progress · commissioning results
Accept, hand over and plan ahead.
Phase record:Acceptance record · operating handover · maintenance and expansion plan
Project capacity is stated with its basis: utility supply, critical IT load and development phase. Service dates depend on the connection, permits, construction and funding programme.
Three ways to start: a tenant brief, a site with power and rights, or a delivery and operating capability.
We welcome enquiries from tenants, landowners and development partners, and delivery and operating partners.
Location, IT load, rack density, service scope and timing.
Site rights, utility information, permits and proposed role.
Specialists in design, permitting, equipment, construction and facility operations.
partner@lintelinfra.ai
Presentation checked against the live websites on 2 November 2026. Original business information remains dated 14–17 October 2026; later page-specific sources retain their dates.
Proposed: scope or terms under discussion, nothing executed. Contracted: executed obligations. Connected: utility connection energized and confirmed. Commissioned: installation tested with accepted commissioning results. Accepted: service or facility acceptance evidenced. Planning targets are not commitments.
It establishes no customer, supplier, capacity or financing commitment. Scope, availability, pricing and legal terms are agreed in individual proposals and contracts.
Page-specific licensing, customer rights, procurement and financing conditions remain next to the relevant content.