BytePlus AI Cloud
byteplus.com · Compute · 1 record · JSON
BytePlus AI Cloud Compute
paidemail?card?Rwrite-gated
| Free tier | Serverless microVM sandboxes that the vendor says start in under 150 ms, scale to tens of thousands created concurrently and to millions of vCPUs, support stateful long-running sandboxes, ship preconfigured templates, and bill at millisecond granularity with no charge while nothing is executing. Templates, large-scale image distribution, arbitrary specifications and MCP, API and SDK access are listed. No free tier is published. unit hours; metered on wall-clock; none |
|---|---|
| Price | none stated |
| Per-object cap | not applicable |
| Retention | not applicable |
| Egress | not stated |
| Identity | email (placeholder) unverified: no page stating the signup requirement was read; the record's evidence covers the sandbox mechanics (sub-150 ms starts, millisecond billing with no charge while idle, MCP/API/SDK access), a third-party rate of USD 0.0351 per vCPU-hour and USD 0.0081 per GiB-hour, and a BytePlus billing page that returned only its navigation shell. Whether a personal account can create a sandbox at all was not established. |
| Limits |
The rate card and the signup gate are both behind an account: the public documentation renders as a script shell, so the only published numbers are third-party, and whether a personal account can create a sandbox at all was not established. |
| Binding | write-gated The rate card and the signup gate are both behind an account: the public documentation renders as a script shell, so the only published numbers are third-party, and whether a personal account can create a sandbox at all was not established. |
| Interface | rest inferred from the tooling the provider documents; not probed |
| Tooling | not stated |
| Composes with | A microVM that bills only while executing is the right shape for evaluation fan-out, where a thousand short sandboxes each live a few seconds; it is the wrong shape for a service that must stay up, because the published selling point is that idle costs nothing precisely by not being a persistent host. |
| Reliability | no reliability event recorded |
| Notes | Recorded as reported because the vendor page establishes the product and its mechanics but not a price, and the documentation is a client-rendered shell that the broker could not read past. Routes tried: the product solution page (read, product facts only), docs.byteplus.com/en/docs/faas/Billing_overview (navigation shell, no table), docs.byteplus.com/en/docs/faas/Overview_of_cloud_sandbox (same shell), and a broad search that returned only third-party comparison tables. What would settle it: an account, which would expose the console rate card. Identity is left null rather than guessed: BytePlus sells to enterprises, and whether a personal account can top up without a company was not established. This is the one provider where the door is more likely to be the finding than the price. |
| Evidence rung | reported |
| Checked | 2026-10-22 (live); stale on 2026-11-05 |
Evidence (3)
| date | source | what it proved |
|---|---|---|
| 2026-10-22 | www.byteplus.com/en/solutions/ai-cloud-native-sandbox | 'sandboxes can start within 150ms and can be created concurrently at a scale of tens of thousands'; 'up to millions of vCPUs'; 'millisecond-level billing with no charges when not executing'; each sandbox is a microVM; MCP, API and SDK access |
| 2026-10-22 | boxyard.dev/providers/byteplus-cloud-sandbox | a third-party comparison lists USD 0.0351 per vCPU-hour and USD 0.0081 per GiB-hour with no free tier, which is a claim about a third party and not a reading of BytePlus's own rate card |
| 2026-10-22 | docs.byteplus.com/en/docs/faas/Billing_overview | the billing overview page returns only its navigation shell with no rate table, so the vendor's own numbers could not be read |
More fields (1)
{
"wave2": {
"class": "regional-sandbox-unpriced",
"free_tier_kind": "none",
"shape": {
"vcpu": null,
"ram_gib": null,
"disk_gib": null,
"gpu_class": null,
"gpu_count": null
}
}
}Unknown or withheld values (9)
$.egress.meteredegress-unknown$.egress.termsnot-stated$.identity_cost.kindidentity-defaulted$.per_object_cap.notesprocess$.per_object_cap.statednot-applicable$.reliability_notenone-observed$.retention.notesprocess$.retention.statednot-applicable$.toolingnot-stated