Home / Compute
Ubicloud
www.ubicloud.com/docs/about/pricingCloud VMcompute/ubicloudJSONcomparereport an errorprovider JSON
- Free allowance
- No free tier: billed by the minute on provisioned resources, with GitHub Actions runners from $0.00125 a minute for 2 vCPU and 8 GB and burstable VMs from $10.47 a month
- Verdict
- paidno free allowance; listed for its price
- Cost
- USD 22.46/monthparsed from the record, in USD
- Identity
- email?placeholder, not evidence; card unknown, phone unknown
- Binding limit
- request-ratebilled per minute on provisioned resources: $0.00125 a minute for a 2 vCPU, 8 GB runner; premium runners fall back to standard ones when capacity is full, with no extra wait
- Evidence
- documented2 sources; a first-party page was read and the sentence quoted
- Freshness
- stale on 2026-11-22checked 2026-10-22 (live); stale on 2026-11-22
| Free tier | no free tier: billed by the minute on provisioned resources, with GitHub Actions runners from $0.00125 a minute for 2 vCPU and 8 GB and burstable VMs from $10.47 a month unit none; metered on none |
|---|
| Price | none stated |
|---|
| Limits | - request-rate (binding) billed per minute on provisioned resources: $0.00125 a minute for a 2 vCPU, 8 GB runner source
- request-rate (binding) premium runners fall back to standard ones when capacity is full, with no extra wait source
- per-object-cap runners include dedicated CPU, memory, local block storage and a public IPv4 source
not stated |
|---|
| Identity | email (placeholder) not published |
|---|
| Egress | not stated |
|---|
| Per-object cap | not stated |
|---|
| Retention | not stated |
|---|
| Interface | unknown |
|---|
| Reliability | no reliability event recorded |
|---|
| Evidence note | documented the pricing page was read on 2026-10-22 and publishes the per-minute and monthly rates with a direct comparison against GitHub. There is no free tier, so the verdict moves to paid-only |
|---|
| Parsed numbers | - price USD 9.36 10 hours a day / month
- price USD 22.46 / month
- has-free-tier 0
- request-rate 8 GB
|
|---|
Evidence 2
| date | source | what it proved |
|---|
| 2026-10-02 | www.ubicloud.com/docs/about/pricing | not published |
| 2026-10-22 | www.ubicloud.com/docs/about/pricing | 'Billing is based on the resources provisioned, pro-rated for the time they are provisioned. We calculate resource consumption at per minute granularity and bill monthly.' with the GitHub Actions table '2 vCPU 8GB $0.00125/min on Ubicloud vs $0.00600/min on GitHub' and 'Burstable VMs start at $10.47/month', quoted |
More fields 12
| keep rate | 1.0 |
|---|
| billing model | flat-pool |
|---|
| shape | {"vcpu": 2,"ram": 8,"disk": 40,"gpu_class": null,"gpu_count": null,"note": "the standard-2 runner: 2 vCPU, 8 GB and 40 GB of block storage"} |
|---|
| session cap | {"wall_clock_min": null,"idle_reap_s": null,"restart_required": false,"note": "a runner exists for the job and is billed by the minute; burstable VMs start at $10.47 a month"} |
|---|
| price note | a VPS bills by the month with an hourly rate capped at the monthly figure, so the two columns answer two questions: destroying the box between runs versus keeping it up. |
|---|
| free tier kind | none |
|---|
| m10h usd | 9.36 |
|---|
| m24h usd | 22.46 |
|---|
| price basis | 10 h/day column = 300 h at the hourly rate, which is what a server destroyed between runs costs; 24/7 column = the monthly cap, because a VPS kept up all month stops at the cap. |
|---|
| burst x | 1.0 |
|---|
| ps | {"gib": 40,"price": "included with the runner","durability": "local block storage","on_stop": false,"on_destroy": false,"retention": "the job's lifetime"} |
|---|
| net | {"out": true,"in": true,"ports": "a public IPv4 address is included with the runner","static_ip": true,"ipv6": null,"allowance": null} |
|---|
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