Hyperstellar
Sell compute Access the market

For colocation providers

A compute market inside your facility.

Your customers earn revenue on the hardware already in their cages. You add a revenue line without adding a megawatt, and you have compute to offer again, with nothing on your balance sheet.

Interested? Let's talk.See how it works
1 agreementcovers every tenant in the building. Customers opt in one by one.
1 patch cablein the meet-me room puts a cluster on the market.
~6,000interconnection facilities worldwide offer cross connects.PeeringDB · June 2026

01What you gain

New revenue is already inside the building.

A compute market inside your facilities adds a revenue line to the AI cages that opt in. Interconnection stays your product. Every cluster listed and every buyer connected adds a cross connect.

01
A new revenue lineA share of the fee on every transaction settled inside your facilities, or colocation and interconnection revenue on new footprint.
02
Net interconnection addsEvery listed cluster and every connected buyer adds a cross connect or a metro interconnection to your count.
03
Stickier cages, demand-led footprintCustomers earn on idle accelerators and buy burst in one building. Buyers seeking proximity take footprint beside them.
04
Compute to offer againA compute answer for your customers, sourced from their own hardware, with nothing on your balance sheet.

02What your customers gain

Value for the customers you already have.

AI cages sit idle between runs. The market turns those hours into revenue for their owners and into burst capacity for their neighbors, without leaving your building.

Monetize idle computeSet a price floor and keep control of the hardware.
Rent burst capacityAccess capacity from peers one cross connect away.
Attested deliveryPerformance, availability and settlement recorded on common terms.
No re-platformingHV-OS runs beneath the OS on the servers already in the cage.
Inside your facility by designOwners keep their cages. Buyer workloads stay inside your building.

03Inside the facility

One patch cable puts a cluster on the market.

Carriers, cloud on-ramps and the exchange already terminate in your meet-me room. Cages connect to the frame once. Any two tenants are then one patch apart.

  1. 01
    Sign the facility.One partner agreement covers every tenant in the building. Customers opt in one by one.
  2. 02
    Deploy HV-OS.Your services team installs it in the cage. Hyperstellar runs it remotely. It sits beneath the OS, so nothing on the tenant's servers changes.
  3. 03
    Cross connect the pool.One patch cable in the meet-me room joins buyer and seller. HV-OS orchestrates. A passive layer-1 path with no electronics in the line.
Days, not months Your remote hands, a standard task Your portal, a standard cross-connect order
One facility · data hall Entrance A Entrance B Across the metro your other facilities · the same link Tenant A · seller GPU cluster · runs HV-OS · attested idle hours rented out Tenant B · buyer draws burst on demand workloads stay in your building Meet-me room fiber distribution frame · operator controlled CARRIER A · IP TRANSIT CARRIER B · IP TRANSIT CLOUD ON-RAMP · PORTS IX SWITCH · PEERING tenant panels · cabled back to each cage PANEL 21 · TENANT A PANEL 22 · TENANT B HS-0007 · market link · live a passive layer-1 path · no electronics in the line port in service open port · sellable patch cord · cross connect metro link cabled once
One cord on the meet-me frame joins a seller's cage to a buyer's cage. The same frame already reaches the carriers, the clouds and the exchange.

04The metro

One campus first, then every metro.

One campus goes live first. The metro's other facilities join over your metro interconnection. Remote interconnection then carries demand from every other metro to the pool.

  1. 01
    Anchor campus.Two or three customers with GPU clusters already installed. The pilot clears trades inside the campus first.
  2. 02
    The metro.Customers in your other facilities join the pool over metro interconnection without leaving your footprint.
  3. 03
    Every metro.Remote interconnection carries demand from your other metros to the pool. Each new metro adds liquidity.
Other metro Other metro Metro facility Metro facility Anchor campus pilot · two or three customers metro interconnection remote interconnection Metro radius · within ~50 km
Liquidity starts inside one campus and grows with every facility and metro connected.

05How value flows

Together, we monetize the flow of compute.

Hyperstellar charges a fee each time compute is made available, matched, priced, routed, reserved, verified or settled across the market. Compute flows to buyers. Value flows to owners, net of the fee.

Demand

Buyers pay the market pricefor attested capacity on common terms.

Hyperstellar · the market layer

enable · match · price · route · verify · settleA fee on every settled transaction.

Supply

Owners earn the cleared priceless the fee, on capacity that would otherwise sit idle.

You earn a share of the fee on every transaction settled inside your facilities, or colocation and interconnection revenue on the footprint the market brings. This shows the mechanics only. Terms are set in the definitive agreement.

06Also available

A configuration database that maintains itself.

Network topology discovery replaces the inventory kept beside the facility. Every pool, cross connect and boundary rule becomes a live object with a state, a utilization and an owner.

  1. 01
    Discovered from the network.The estate is parsed from the network itself. No spreadsheet to keep current.
  2. 02
    Cross connects carry utilization.Each circuit shows its panel, ports, media, capacity, peak window and what it serves.
  3. 03
    Boundary rules live in the same graph.Egress limits and holdbacks sit beside the circuits they bound, with an owner and a state.
Standalone for your interconnection teamIncluded with the market
Configuration database DFW-1 facility parsed 16:02Z · demonstration snapshot
Objects · 8 of 212 attestation run ATT-RUN-0914
POD-ADFW1-A · 2,048 accelerators · attested 96%in service
POD-BDFW1-B · 2,304 accelerators · attested 97%in service
POD-CDFW1-C · 2,048 accelerators · attested 95%in service
xc-0142cross-connect · in-building · 2× SMF · 400 Gbpsconstrained
xc-0158cross-connect · in-building · 2× SMF · 100 Gbps · 41%in service
xc-0203cross-connect · metro · 2× SMF · 100 Gbps · 18%in service
BR-08boundary rule · egress ≤ 400 Gbps · DFW1-Bactive
CAGE-14tenant cage · 3 pods · 6,400 acceleratorsin service
Selectedxc-0142
Typecross-connect · in-building
Panel / portsXC-PNL-04 · 17/18
Media2× SMF
Capacity400 Gbps
Utilization87% · peak 14:00 to 18:00Z
ServesAL-99312 · 512 GPU · running
Boundaryegress ≤ 400 Gbps (BR-08)
OwnerTenant A

Cross-connect orders go through your portal. Typical turn-up 24 to 72 hours.

07From conversation to pilot

A bounded pilot proves the value first.

A pilot proves operating value and controls before any commercial commitment. Your partnership and product teams are in the room from the start.

01 · THE NEXT SESSIONWalk the model.The business model, with your partnership and product teams in the room.Output · a one-page scope
02 · TERMSName the pilot.A term sheet drives the structure. Customers with clusters in one anchor metro are named.Output · a named list and a term sheet
03 · THE PILOT · ONE QUARTERRun the pilot.Deploy HV-OS on the named clusters, cross connect them and clear trades over one quarter.Output · go or no-go
A sponsorOne owner on your side to run point.
Two or three customersClusters in one anchor metro, each opting in.
A marketplace listingHyperstellar listed in your partner marketplace, where one exists.
A remote hands installA standard task, ordered by each customer.

Interested? Let's talk.

Operators are onboarding now.

One agreement covers the building. HV-OS runs beneath the OS. One cross connect joins buyer and seller. A settlement dashboard records the revenue earned.

contact@hyperstellar.ai