fshy

Home / Compute

SF Tensor

sf-tensor.comGPU cloudcompute/sf-tensorJSONcomparereport an errorprovider JSON

Free allowance
No per-GPU hourly price is listed on the page: pricing is by engagement, 'every engagement is scoped to your goals and priced around the outcome you care about'.
Verdict
paidno free allowance; listed for its price
Cost
no price stated
Identity
email?placeholder, not evidence; card unknown, phone unknown
Binding limit
write-gatedengagement is a fixed contract with compute billed separately; there is no self-serve plan and no free tier
Evidence
documented4 sources; a first-party page was read and the sentence quoted
Freshness
stale on 2026-12-04checked 2026-11-03 (live); stale on 2026-12-04
Free tierNo per-GPU hourly price is listed on the page: pricing is by engagement, 'every engagement is scoped to your goals and priced around the outcome you care about'. No H100, A100, L40S, RTX4090 or L4 is listed.
unit none; metered on wall-clock
Pricenone stated
Limits
  • write-gated (binding) engagement is a fixed contract with compute billed separately; there is no self-serve plan and no free tier source
not stated
Identityemail (placeholder) not published
Egressnot stated
Per-object capnot stated
Retentionnot stated
Interfaceunknown
Reliabilityno reliability event recorded
Evidence notedocumented the site was read on 2026-10-22 and states a fixed engagement with compute billed separately. No free tier exists and none is claimed; the compute is a user's, which confirms paid-only
Parsed numbers
  • has-free-tier 0
Evidence 4
datesourcewhat it proved
2026-10-02sf-tensor.comnot published
2026-10-22sf-tensor.com'Our researchers embed with your team for a fixed engagement, with compute billed separately. You get a production model in about six weeks, then take it over or keep us running it.' with '1 to 10,000 GPUs' and '24/7 white-glove support', quoted
2026-11-03sf-tensor.compricing is scoped to the engagement and priced around its outcome, with no per-GPU rate
2026-11-03sf-tensor.comengagement is fixed and compute is billed separately
More fields 5
keep rate basisno field in the source
billing modelunclassified
session cap{"wall_clock_min": null,"idle_reap_s": null,"restart_required": false,"note": "a six-week engagement rather than a session; the compute runs on a user's own quota"}
free tier kindnone
reclassified fromdead
Unknown values 10
  • chaining: a source was read and is silent on this field
  • egress metered: egress metering was not published
  • egress terms: a source was read and is silent on this field
  • interface: the access interface was not established
  • limits note: a source was read and is silent on this field
  • per object cap stated: a source was read and is silent on this field
  • reliability note: nothing of this kind was observed
  • retention notes: the field may be stated in a source that was not read
  • retention stated: a source was read and is silent on this field
  • tooling: a source was read and is silent on this field