Synpute Standard · v0.1 draft
What a financeable compute asset looks like, in one schema.
One open, versioned schema for compute assets, the contracts they earn from and how they perform. A lender, an operator and a buyer describe the same cluster the same way, so it can be verified, compared and financed.
Synpute Standardfront matter
A data schema for financeable compute assets
- Version
- v0.1
- Parts
- 3
- IDs
- 4
draft
schema
prefixes
- Status
- Open for review
- Parts
- Assets · Contracts · Performance
- Identifiers
- Synpute ID
- License
- Free to read and adopt
- Co-authors
- Founding seats open
Why publish it openly
A standard only wins if the market can read it.
Today every GPU deal is described in a bespoke spreadsheet and data room. Older markets solved this with shared data standards; compute doesn't have one yet.
01
Open
02
Versioned
03
Neutral
04
Co-authored
Schema overview
Assets, contracts, performance.
Three parts, each keyed to Synpute IDs. Assets and contracts are registered before financing; performance accrues for the life of the loan.
01§1 · assets
Assets
02§2 · contracts
Contracts
03§3 · performance
Performance
Schema excerpt
One cluster, one contract, one quarter.
A registered record in the draft format. Every object points to a Synpute ID, so the verification, the Credit Profile and the monitoring data all attach to the same record.
- SYN-CL-…
- Cluster. One physical cluster: its hardware, site and power
- SYN-OP-…
- Operator. The company that owns and runs the cluster
- SYN-BY-…
- Buyer. A tenant renting capacity on the cluster
- SYN-CT-…
- Contract. One capacity contract between operator and buyer
1{2"standard": "synpute/v0.1-draft",3"cluster": {4"id": "SYN-CL-7F3A",5"operator": "SYN-OP-21C4",6"assets": {7"hardware": { "gpu": "B200", "count": 1024, "serials_attested": true },8"fabric": { "interconnect": "InfiniBand", "topology": "rail-optimized" },9"site": { "region": "US-East", "lease_term_months": 120 },10"power": { "contracted_mw": 1.8, "contract_term_months": 120 }11}12},13"contracts": [14{15"id": "SYN-CT-4B71",16"buyer": "SYN-BY-0A9E",17"term_months": 36,18"rate": { "unit": "gpu_hour", "currency": "USD" },19"step_in_rights": { "lender_directed": true, "cure_period_days": 30 }20}21],22"performance": {23"period": "2026-Q3",24"uptime_pct": 99.94,25"utilization_pct": 87.2,26"payments": { "due": 3, "received_on_time": 3 }27}28}
Illustrative excerpt from draft v0.1. Field names, units and structure are open for review and will change.
Version history
Where the draft stands.
Each release is numbered, dated when it ships and lists what changed.
| Version | Status | Notes |
|---|---|---|
| v0.1 | Draft · open for review First public draft of the asset, contract and performance schema. Circulating to founding reviewers; comments open. | |
| v1.0 | Planned First stable release, published with founding co-authors, including at least three lenders. |
Co-authors
Founding reviewers: open.
The first version is written with the people who will rely on it. Founding reviewers are named on the published Standard.
Register as a reviewer
Help write the Standard.
Reviewers get each draft before it's published, a say in what changes, and their name on the version they helped write.
What happens next
- 1We confirm your seat within one business day.
- 2You receive the full v0.1 draft and the review timeline.
- 3Your comments are logged against the version history.
Comment on the draft
Send a comment.
Spotted a missing field, a unit that won't work or a right a lender needs? Tell us which section, and what you'd change.
What happens next
- 1Your comment goes straight to the founder.
- 2We reply if we need more detail.
- 3Accepted changes are logged in the next version.
Who it's for
Built for every side of the deal.
One schema is only useful if every side of the market writes to it.
FAQ
Questions we hear
Straight answers to what comes up in the first call. If yours isn't here, ask us directly.
05 questions · reply within one business day
Help define a financeable compute asset.
Version 0.1 is a draft. The seats at the table are open, and the comments shape what v1.0 becomes.