SLYD
Read first

The 5-step pipeline.

How energy turns into a deployed, financed, offtake-matched cluster, and what SLYD does at every step.

How SLYD works →
Hardware

New and recovered GPU systems.

NVIDIA and AMD systems through documented manufacturer and qualified channel supply, with financing and deployment coordinated on the same platform.

Explore GPU hardware →
Marketplace

Compute, hardware, and power in one book.

Browse available GPU capacity by accelerator, configuration, region, and price, or bring supply to qualified demand.

Open marketplace →
Pre-qualify

Start with an indicative structure.

Tell us deal size, structure, and offtake. Any range is preliminary and subject to underwriting, diligence, and documentation.

Open Configure →
/configure · energy-backwards

Configure a deployment.

Energy in, compute out. Start from whichever number you actually know: power envelope, accelerator count, budget, or IT load. SLYD sizes a buildable package from its pricing engine.

1Your input

MW
200 kW10 MW20 MW+

2Accelerator

Loading catalog…

3Cooling

4Sourcing

RE-CALCULATING

Save this build. Start the conversation.

Sign in to save this configuration and get a structured proposal from ops, with exact pricing tied to real lots and a delivery timeline. Capacity is held only via deposit.

Talk to us
BANDED PUBLIC ESTIMATE. SIGN IN FOR EXACT-TO-THE-CENT QUOTES TIED TO REAL LOTS
Banded public estimate. Every number below comes from SLYD's published pricing engine, and output is banded (…). Sign in for exact-to-the-cent quotes tied to real lots.

POWER ENVELOPE · ALLOCATION

PUE … · PRICING ENGINE
Compute draw · GPU nodes
IT overhead · network + storage + mgmt
Facility · cooling + UPS + losses
Pick an input to size the envelope. PUE and the IT-overhead ratio come from the published pricing config.
RECOMMENDED BUILD

Sizing…

GPUs
…
Nodes
…
Racks
…
IT load
…
Meter power
…
PUE
…
ALL-IN BUILD COST · BANDED
$… to $…
BANDED
Compute hardwareGPUS · CHASSIS · KIT
…
Electrical$/kW · SITE POWER
…
Cooling plant$/kW · METHOD-DEPENDENT
…
NetworkingTOP-OF-RACK · PER SERVER
…
Install & commissioningPER NODE + FRACTION OF STACK
…
Enclosure & packageREMAINDER OF STACK
…
Shares of the banded total. Dollar line items are quoted lot-by-lot after sign-in.
IF YOU SELL THE CAPACITY

Est. annual revenue $… – $…

…
SLYD CLOUD · OPERATING LAYER

Building a neocloud? Don't reinvent the stack.

If this cluster will serve tenants, SLYD Cloud handles orchestration, billing, tenant isolation, GPU scheduling, and marketplace exposure, so you sell capacity rather than build software.

OPTION 01 · LICENSE

Run SLYD Cloud on your own metal.

Full stack, white-label optional, on-prem control plane, using the same orchestration, billing, and tenant primitives SLYD runs.

PER-GPU-HOUR LICENSE · QUOTED WITH YOUR BUILD
OPTION 02 · CONNECT

Plug into the SLYD marketplace.

Your capacity surfaces as your inventory. Customers find you; you keep the relationship. SLYD takes a clearing fee on bookings it sources.

REV-SHARE · NO LICENSE FEE · SLYD-SOURCED BOOKINGS ONLY
Configurator questions

How the configurator works.

Do I need to sign up to use the configurator?

No. The configurator is public and every output is a banded estimate from SLYD's published pricing engine. Signing in unlocks exact-to-the-cent quotes tied to real lots, lets you save the build, and starts a structured proposal from ops with a delivery timeline.

What does energy-backwards sizing mean?

You start from whichever number you actually know: site power at the meter, accelerator count, build budget, or post-PUE IT load. SLYD sizes a buildable package from it. PUE and the IT-overhead ratio come from the published pricing config, so the power envelope allocation stays consistent with the rest of the estimate.

Why is pricing shown as a band instead of an exact number?

Public output is banded on purpose. Every figure comes from SLYD's published pricing engine, but exact-to-the-cent pricing is tied to a real lot and sits behind sign-in. Dollar line items covering compute, electrical, cooling, networking, and install are quoted lot by lot after you save the build.

Can I compare new and recovered hardware in the same build?

Yes. The sourcing step switches between new hardware and recovered hardware. The cooling choices of air, direct liquid, and immersion each carry their own PUE from the pricing config, so the build cost and power envelope update as you toggle.

What these numbers are, and what they are not

Every figure on this page is calculated from the inputs you set against SLYD's published pricing configuration. None of it is a measurement, none of it is a quote, and none of it is tied to a specific lot of hardware until you save the build and sign in.

How to read each output

  • Accelerator count, nodes, racks, IT load, meter power. Calculated. Derived from your chosen input mode using the accelerator specification and the PUE and IT-overhead ratio in the pricing config.
  • Build cost band and the cost breakdown. Calculated, then deliberately widened into a band. The band is not a confidence interval: it is a disclosure boundary, because exact pricing depends on a real lot.
  • Estimated annual revenue and monthly figures. Estimated, and the most assumption-dependent numbers here. They rest on a utilization assumption from the pricing config and on rates that move with the market.
  • PUE. A configuration value attached to the cooling method you selected, not a measurement of any facility. Your site will differ.

What the estimate does not include

  • Site acquisition, utility interconnection, and the cost or lead time of getting power to the meter
  • Construction, permitting, and any structural work the deployment requires
  • Ongoing energy cost at your tariff, staffing, and operations
  • Taxes, duties, and freight
  • Residual value, financing fees, and any discount rate

Operating cost over time, and the comparison against renting capacity instead, are modelled in the TCO calculator. Facility power and cooling load are worked through in the power and cooling calculator.

Freshness

The numbers are computed on each interaction from the pricing configuration as it stands at that moment. If the pricing engine is unreachable, the page shows a notice and retains the last build it computed rather than filling in defaults. SLYD does not currently publish a version identifier or an effective date for the pricing configuration itself, so this page cannot state which revision produced a given result.

This is planning analysis. It is not a quote, not an offer of finance, and not accounting, tax, credit, or investment advice. Capacity is held only by deposit against a signed order.

Reconnecting to the server...

Please wait while we restore your connection

An unhandled error has occurred. Reload 🗙