Cloud Studio
Compute · 1 record · JSON
Cloud Studio Compute
trialany-phone?card?phoneRretention-clamped
| Free tier | reported: a user accumulated more than 2,000 machine-hours of Tencent Cloud Studio credit from a platform bug, with the highest usable shape reported as an L40 GPU, and asked the forum what to do with it. unit none; metered on wall-clock; one-time-credit |
|---|---|
| Price | none stated |
| Per-object cap | not applicable |
| Retention | the 2,000 hours came from a defect and not from the offer, so it is unreproducible by design, and the same thread's earlier reports show the standing grant falling from 50,000 minutes a month in 2024 to 20 to 50 hours in 2026. |
| Egress | not stated |
| Identity | any-phone (placeholder) unverified: no page stating the signup requirement was read; the record's evidence covers the machine-hour grants and the trial-only verdict (a 20 machine-hour pack 'after binding a Tencent Cloud account', 2 machine hours a day on login) but not what that account requires. No evidence row names a phone, a card, an email or an ID document, so the stored any-phone kind is unsupported by this record's own evidence. |
| Limits |
the 2,000 hours came from a defect and not from the offer, so it is unreproducible by design, and the same thread's earlier reports show the standing grant falling from 50,000 minutes a month in 2024 to 20 to 50 hours in 2026. |
| Binding | retention-clamped the 2,000 hours came from a defect and not from the offer, so it is unreproducible by design, and the same thread's earlier reports show the standing grant falling from 50,000 minutes a month in 2024 to 20 to 50 hours in 2026. |
| Interface | unknown inferred from the tooling the provider documents; not probed |
| Tooling | not stated |
| Composes with | 2,000 L40 hours is about 200 hours of a 10-GPU job, which would be the largest free GPU allowance in the corpus if it were an offer rather than a defect; as a chain element it is a windfall and not a resource. |
| Reliability | no reliability event recorded |
| Notes | Recorded to stop a future session chasing it: the number is real and the route is not. ⚠ A defect grant is not a free tier and must not be counted as one, which is why this is trial-only with the defect named in the offer. The useful signal is the trend it sits in: Tencent's standing grant fell by roughly two orders of magnitude between 2024 and 2026 while users kept finding temporary surplus. |
| Evidence rung | reported |
| Checked | 2026-10-22 (live); stale on 2026-11-05 |
| Parsed numbers |
|
Evidence (3)
| date | source | what it proved |
|---|---|---|
| 2026-09-14 | linux.do/t/topic/2902157 | the post, translated: 'earlier Cloud Studio had a bug and I got 2,000-plus machine-hours free, I do not know what to do with them'; the highest configuration available is described as an L40 GPU [re-read 2026-10-22: fetch exit 0, token overlap 0.21; the original capture stands] |
| 2026-07-22 | linux.do/t/topic/2635751 | the standing offer for comparison, translated: 50 machine-hours on registration and 2 a day for checking in, with replies reporting only 20 [re-read 2026-10-22: fetch exit 0, token overlap 0.0; the original capture stands] |
| 2026-10-22 | cloud.tencent.com/document/product/1039/131773 | quoted, translated from the vendor's machine-hour FAQ: 'first binding grant: after binding a Tencent Cloud account, a 20 machine-hour resource pack is granted' and 'daily login: after logging in each day, 2 machine hours can be claimed from the profile card (valid for 7 days)'. A new account therefore starts with tens of hours and accumulates at 2 a day, which supports the trial-only verdict and the top of the stored 20-to-50-hour range; it does not support the 2,000-hour windfall, which stays a forum report and is not repeated by any vendor page |
More fields (1)
{
"wave2": {
"class": "cloud-ide",
"free_tier_kind": "one-time-credit",
"shape": {
"vcpu": null,
"ram_gib": null,
"gpu_class": "L40",
"gpu_count": 1,
"vram_gib": 48
}
}
}Unknown or withheld values (9)
$.egress.meteredegress-unknown$.egress.termsnot-stated$.identity_cost.kindidentity-defaulted$.interfaceinterface-unknown$.per_object_cap.notesprocess$.per_object_cap.statednot-applicable$.reliability_notenone-observed$.retention.notesprocess$.toolingnot-stated