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 →
From the blog

GPU market trends and deployment playbooks.

Infrastructure best practices, hardware comparisons, and industry analysis from the SLYD team.

Read the blog →

Library

Trust · /platform/security

Trust is structural here.

Not a badge wall. SLYD's trust model is built into how deals are structured: you hold title, the lender holds the lien, every event is timestamped in a shared record, and your workloads run on infrastructure you effectively own. Here's exactly how — and an honest read on where compliance certifications stand.

Custody & title

Buyer holds title, lender holds lien, SLYD holds neither. Clear ownership from day one.

Audit trail

Every advance, milestone, and state change timestamped in one shared deal record.

Data control

Workloads run on hardware you own or control. LXD isolation, no shared kernel surprises.

Lender oversight

Institutional lenders get live collateral telemetry and a complete event history.

Custody model

Three parties. Clear lines. No commingling.

The structural reason SLYD is trustworthy isn't a promise — it's that no single party holds conflicting roles. SLYD never takes title and never takes principal, so our incentives can't quietly diverge from yours.

THE BUYER

Holds title.

From close, the buyer owns the cluster outright. You can depreciate it, build equity in it, and operate it under your own control. SLYD has no ownership claim on your hardware.

HOLDS: ASSET TITLE · OPERATIONAL CONTROL
THE LENDER

Holds the lien.

The financing partner holds a security interest in the cluster until the term completes. They get live telemetry and the full audit trail — never an information gap between advance and repayment.

HOLDS: SECURITY INTEREST · OVERSIGHT RIGHTS
SLYD

Holds neither.

SLYD originates, arranges, deploys, and clears the marketplace. We take clearing fees and spreads — never title, never principal, never your data. That's the whole alignment story.

HOLDS: NOTHING ON YOUR BALANCE SHEET

Every event, timestamped & shared.

The shared deal record isn't a SLYD convenience — it's the audit substrate. Every party who touches a deal writes to the same append-only log. Operators, buyers, brokers, lenders, and SLYD ops all read the same history. No private side-ledgers, no reconciliation gaps.

Append-only — events are never edited or deleted, only superseded with a new timestamped entry.
Attributed — every entry carries the actor, role, and a content hash.
Exportable — lenders and auditors can pull the full chain for any deal on demand.
DEAL RECORD · EVENT LOG ILLUSTRATIVE · SAMPLE DATA
14:02:11Z
Offtake commitment recorded · 1.8 MWBROKER A
#a3f9
13:47:55Z
Lender advance · tranche 2LENDER B
#7b2e
11:20:03Z
Cluster burn-in passed · 200 nodesOPERATOR C
#c1d8
09:15:42Z
Title transfer recordedSLYD OPS · ESCROW
#e4a0
08:58:30Z
Hardware shipment confirmedSUPPLIER D
#92bf
Data control

Your workloads. Your hardware. Your perimeter.

Data control isn't a slogan — it's the architecture. Because the buyer owns the cluster, the workloads run on infrastructure under the buyer's control, not on shared multi-tenant cloud you don't see.

LXD isolation

SLYD Cloud runs on LXD system containers — bare-metal-like isolation, native GPU passthrough, no shared-kernel multi-tenant surprises. Zero Kubernetes anywhere in the stack.

On-prem control plane

License SLYD Cloud and the entire control plane runs inside your environment. No customer data leaves your perimeter — only the billing metadata you choose to share.

Regional placement

You choose where the cluster physically sits — jurisdiction, grid, and interconnect. Data residency follows the iron, and the iron is on your site.

Compliance — the honest version

What we have, and what we don't. Yet.

SLYD is an early-stage infrastructure company. We will not claim certifications we don't hold. Here's exactly where formal compliance stands — and what's actively in motion.

SLYD does not currently hold SOC 2, HIPAA, or FedRAMP attestation. We'd rather tell you that plainly than imply otherwise. What we do have is a custody model, audit substrate, and isolation architecture that are built to pass those audits when we pursue them — and an honest roadmap below.

IN PROGRESS

SOC 2 Type I

Controls documentation and readiness assessment underway with a third-party assessor.

PLANNED

SOC 2 Type II

Follows Type I after the observation window. Targeted once the control set is operating.

PLANNED

HIPAA readiness

BAA framework and safeguards for healthcare-adjacent buyers. Scoped, not yet executed.

EVALUATING

FedRAMP path

Assessing the moderate baseline for public-sector workloads. Long horizon, deliberate.

Frequently asked questions

Trust questions, answered straight.

Who holds title to hardware in a SLYD deal?

The buyer holds title to the cluster from close and can depreciate it, build equity in it, and operate it under their own control. The lender holds a security interest until the term completes. SLYD holds neither — it takes clearing fees and spreads, never title, principal, or your data.

How does SLYD's audit trail work?

Every party who touches a deal writes to the same append-only event log. Entries are never edited or deleted — only superseded with a new timestamped entry — and each one carries the actor, role, and a content hash. Lenders and auditors can export the full chain for any deal on demand.

Who controls my data and workloads on SLYD?

Because the buyer owns the cluster, workloads run on infrastructure under the buyer's control rather than on shared multi-tenant cloud. SLYD Cloud uses LXD system containers with native GPU passthrough, a licensed control plane runs inside your environment, and you choose the jurisdiction where the cluster physically sits.

Does SLYD hold SOC 2, HIPAA, or FedRAMP certification?

No. SLYD does not currently hold SOC 2, HIPAA, or FedRAMP attestation and will not claim certifications it doesn't hold. A SOC 2 Type I readiness assessment is underway with a third-party assessor, SOC 2 Type II and HIPAA readiness are planned, and a FedRAMP path is being evaluated.

What oversight do lenders get on SLYD deals?

Institutional lenders hold the lien and receive live collateral telemetry plus the complete event history for the deal. Every advance, milestone, and state change is timestamped in the shared record, so there is never an information gap between advance and repayment — and the full chain is exportable on demand.

Diligence questions? Talk to ops directly.

For lenders, institutional buyers, and counsel — we'll walk you through the custody structure, share a sample audit export, and answer compliance questions straight. No sales theater.

Reconnecting to the server...

Please wait while we restore your connection

An unhandled error has occurred. Reload 🗙