Kuroit
Compute · 1 record · JSON
Kuroit Compute
paidemail?card?Rvolume-quota
| Free tier | GBP 3.00/month: 1 Intel core (shared), 1,024 MB RAM, 15 GB NVMe, 1,024 GB/month bandwidth, 1 Gbps port, IPv4 and IPv6, Toronto Canada. The tracker lists a cheaper GBP 2.25/month plan (2 cores, 2,048 MB RAM, 25 GB NVMe, 10 Gbps, Toronto) but that card carries no order link, so GBP 3.00 is the cheapest offer the page presents as orderable. The vendor homepage states VPS servers start at 3 GBP a month, with the pound sign written GBP for ASCII. unit GiB; metered on wall-clock; none |
|---|---|
| Price | none stated |
| Per-object cap | not applicable |
| Retention | not applicable |
| Egress | 1,024 GB a month included per the tracker card (free_allowance is in GB a month); overage price and policy are not stated on either page read free_allowance: 1024 |
| Identity | email (placeholder) not stated |
| Limits |
1,024 GB a month is the whole egress budget on the GBP 3.00 plan, which rules out serving the 500 GB to 1 TB a day the corpus needs; the 15 GB NVMe disk is the second wall |
| Binding | volume-quota 1,024 GB a month is the whole egress budget on the GBP 3.00 plan, which rules out serving the 500 GB to 1 TB a day the corpus needs; the 15 GB NVMe disk is the second wall |
| Interface | rest, cli inferred from the tooling the provider documents; not probed |
| Tooling | my.kuroit.com runs the client area and per-location WHMCS store pages; kuroit.com documents a CLI and API access; the Toronto store page answered 403 (bot challenge) to the broker, so no plan table was read from the store itself |
| Composes with | GBP 3.00 for 1 GB RAM and 15 GB NVMe is a scheduler or a crawler front end, not a store: 1 TB a month is the entire egress budget, so the archive and the served pages have to live on a host with either a large monthly allowance or no metering |
| Reliability | no reliability event recorded |
| Notes | Absent from dossier/compute (no file for the slug; no record with this provider name). The vendor lists 12 locations including Toronto and Auckland, while the tracker's map names seven countries. The GBP 2.25 card is published but not orderable, which is why the record is the GBP 3.00 plan; the tracker's own starting-price line (2.25 GBP a month) therefore overstates what can be bought. Would settle: the plan table behind my.kuroit.com, which is behind a 403 challenge, and whether the GBP 3.00 plan is a fair-share core or a pinned one. |
| Evidence rung | reported |
| Checked | 2026-10-22 (live); stale on 2026-11-05 |
| Parsed numbers |
|
Evidence (3)
| date | source | what it proved |
|---|---|---|
| 2026-10-22 | vpspricetracker.com/provider/Kuroit/vps | Kuroit card, with the pound sign written GBP for ASCII: the price line prints 3.00 with the pound sign and '/ month'; the rest quotes verbatim as '1 Intel Cores (shared)', '1,024 MB RAM', '15 GB NVMe', '1,024 GB/month bandwidth', '1 Gbps port speed', 'IPv4 + IPv6', 'Toronto Canada'. The raw HTML carries a live order link /offer/1804245/Kuroit/CA_AVA_1_15GB_Disk_1vCore_1GB_RAM |
| 2026-10-22 | vpspricetracker.com/provider/Kuroit/vps | the cheaper card, priced 2.25 in the same currency and quoted verbatim as '2 Intel Cores (shared)', '2,048 MB RAM', '25 GB NVMe', '10 Gbps port speed', 'Toronto Canada', has its Go control rendered as a span with class 'button_card button_bar_short button_bar_right button_disabled', so no order link is published for it |
| 2026-10-22 | www.kuroit.com/ | product grid quoted, with the pound sign written GBP for ASCII: 'VPS Servers ... Starting at GBP 3/Month' and 'Storage Servers ... Starting at GBP 3/Month'; the page also documents a CLI ('kuro deploy --region ind-jal') and names 12 locations including Toronto and Auckland |
More fields (1)
{
"wave2": {
"class": null,
"free_tier_kind": "none",
"shape": {
"vcpu": 1,
"ram_gib": 1,
"disk_gib": 15,
"gpu_class": null,
"gpu_count": null
}
}
}Unknown or withheld values (7)
$.identity_cost.detailnot-stated$.identity_cost.kindidentity-defaulted$.per_object_cap.notesprocess$.per_object_cap.statednot-applicable$.reliability_notenone-observed$.retention.notesprocess$.retention.statednot-applicable