SLYD
This week

5.2 MW of B200 coming online Q2 2027.

Refinery-tail site in Texas. Refundable deposits open. 24% subscribed — earliest deposits priced lowest.

See Lot 0224 →
Live forward book

12.4 MW under refundable deposit.

Six lots, four regions, three quarters of forward delivery. Spot capacity priced and available now.

Open marketplace →
Pre-qualify

Indicative terms in 30 seconds.

Public financing curve. Tell us deal size, structure, and offtake — we'll quote a range without pulling credit.

Open Configure →
Latest case study

Permian Basin → 3.4 MW H200 in 11 weeks.

How one operator turned stranded gas into financed, offtake-matched compute. Public-approved numbers, real timeline.

Read case study →
What's in SLYD Cloud

The whole operating layer. Not a feature shelf.

SLYD Cloud isn't a wrapper around Kubernetes. It's the same stack SLYD uses to run our own marketplace and operator console — battle-tested in production every day.

GPU scheduling

Multi-tenant fair-share. Reservations, spot, fractional GPUs, MIG. Topology-aware.

Billing & metering

Per-second GPU·hour metering. Invoices, credits, tax, partner rev-share — out of the box.

Tenant management

Multi-org, role-based access, quotas, isolation, audit trail. Per-tenant cost ceilings.

Customer dashboards

White-label-ready buyer console. Usage graphs, cluster health, billing, support routing.

Operator console

Cluster ops view. Power telemetry, thermal limits, redundancy, incident playbooks.

Marketplace integration

List capacity on SLYD's spot & forward marketplaces. Auto-priced by your floor; sales handled.

Pricing engine

Dynamic floor pricing. Demand-driven rate adjustments. Override and band controls.

Forward escrow plumbing

Refundable-deposit lots, subscription tracking, delivery-window guarantees, refund mechanics.

Who uses SLYD Cloud

Three customer shapes. Two paths.

License or Connect — the right choice depends on whether you want to own the customer relationship or skip the go-to-market work entirely.

PERSONA 01

The neocloud builder.

Building 3–50 MW of AI compute for sale. Want your own brand, own pricing, own customer support — but don't want to build orchestration, billing, and tenant management from scratch.

→ LICENSE
PERSONA 02

The capacity operator.

You have power, hardware, and the ops team to run it — but selling compute hour-by-hour to AI buyers isn't your business. Plug into SLYD's marketplace and let demand come to you.

→ CONNECT
PERSONA 03

The enterprise / lab.

Building internal AI infra for your own teams. Want multi-team scheduling, billing, audit, governance — without inviting external traffic. License-only path; runs in your perimeter.

→ LICENSE
Where SLYD Cloud sits

Below your customers. Above your iron.

SLYD Cloud is the layer between the buyer's API call and the GPU spinning at your site. Everything above is yours; everything below is hardware. The operating layer in the middle is SLYD's job — if you want it. SLYD Cloud is optional: every cluster SLYD sources and finances is yours to run however you like, including your own stack.

07CUSTOMER
API callsWeb dashboardCLI / SDKPartner integrations
06CUSTOMER UI
Buyer consoleUsage graphsBilling & invoicesSupport routing
05TENANT & AUTH
IdentityRole-based accessQuotas & ceilingsAudit trail
04METER & BILL
Per-second GPU·hrInvoicingRev-share splitsTax
03SCHEDULE & ROUTE
GPU schedulerTopology-awareReservationsSpot / fractional / MIG
02OPERATOR PANE
Cluster healthPower telemetryThermal limitsIncident playbooks
01HARDWARE
GPU nodesNetwork fabricCoolingPower · UPS
Why LXD, not Kubernetes

Built for AI infrastructure, not web services.

Training and inference want the metal — full GPU access, predictable memory, no noisy-neighbor scheduler fighting the job. SLYD Cloud runs on LXD system containers: VM-like isolation, container-like density, native GPU passthrough. Zero Kubernetes anywhere in the stack.

Characteristic
SLYD · LXD
Typical K8s
GPU access path
Passthrough
Plugin layers
Tenant isolation
Kernel-level
Namespace
Runtime overhead
Near-zero
Control plane
Ops surface
Minimal
Large
Built for
AI infrastructure
Web services
Pricing detail

Two paths. Honest pricing.

No "starting from" gotchas. Indicative pricing below — final terms negotiated with ops based on cluster scale, term, and customer profile.

OPTION 01 · LICENSE

SLYD Cloud, your metal.

Pay-as-you-grow or annual flat. White-label optional.

$0.04/GPU·hr
USAGE-BASED · ANNUAL FLAT AVAILABLE
All features of SLYD Cloud included — no add-on tiers.
On-prem control plane — runs entirely in your environment.
White-label option for branded customer experience.
Quarterly updates + 24/7 incident escalation.
Annual flat-fee alternative for predictable budget.
Talk to ops about licensing
OPTION 02 · CONNECT

Your capacity, our cloud.

Zero up-front. Pay only on SLYD-sourced bookings.

Rev-share
CLEARING FEE ONLY ON SLYD-SOURCED BOOKINGS
$0 up-front — no license fee, no minimums.
Direct customers you bring stay 100% yours — no fee, no involvement.
Marketplace exposure on SLYD's spot & forward boards.
SLYD handles discovery, routing, billing, support for SLYD-sourced.
You set your floor — SLYD never books below it.
Talk to ops about connecting
Questions ops gets often

The honest answers.

Can I use License and Connect at the same time?
Yes. Many operators license SLYD Cloud for their own direct customers, then also Connect a portion of their capacity to SLYD's marketplace to absorb spillover demand. Two billing relationships, one operating layer.
What's SLYD Cloud built on?
LXD — system containers, not Kubernetes. The model fits AI infrastructure workloads better: bare-metal-like performance, native GPU passthrough, fewer abstraction layers between your customer's job and the silicon. Zero Kubernetes anywhere in the stack.
What data leaves my environment?
License path: the control plane runs entirely in your environment. No data leaves your perimeter. Connect path: customer data and workloads run on your hardware; only billing metadata and capacity availability surface to SLYD.
What if I outgrow Connect and want to License?
Built for it. The migration moves your operator-side configuration, customer accounts, and billing history into your own SLYD Cloud instance with no service interruption. Ops walks you through it.
How does forward escrow work in SLYD Cloud?
License and Connect both surface forward-escrow lots — operators commit a delivery window and capacity, buyers escrow refundable deposits. SLYD Cloud handles subscription tracking, delivery verification, and refund mechanics if a lot misses its window.
What's the minimum size to license?
Practical floor is around a 1 MW deployment. Below that the per-GPU-hour licensing cost dominates and the math gets harder. Connect has no minimum.

Talk to ops about SLYD Cloud.

Quick conversation. Tell us your scale, who you're selling to, and whether you want to own the customer relationship. We'll come back with a recommendation and indicative pricing.

Reconnecting to the server...

Please wait while we restore your connection

An unhandled error has occurred. Reload 🗙