Strike

strike.bz · Compute · 1 record · JSON

Strike Compute

paidemail?card?Dvolume-quota

strike.bz · cloud VM · compute/strike · JSON · compare

Free tier	Budget line 'Pico' at EUR 25.00/year: 1 vCPU, 512 MB RAM, 10 GB NVMe SSD, 1 TB bandwidth, sold in Poland and the USA (the tracker names Gdansk and New Jersey). The Budget 'Nano' is EUR 3.00/month with 1 GB and 15 GB, and the Pro line's 'Pico' is EUR 30.00/year with the same 512 MB and 10 GB. The tracker's EUR 2.08/month row is this EUR 25.00 annual plan divided by twelve. unit GiB; metered on wall-clock; none
Price	none stated
Per-object cap	not applicable
Retention	not applicable
Egress	1 TB a month is the stated allowance on this plan; the card states no overage price and no throttle, so the post-allowance behaviour is unverified free_allowance: 1 TB per month
Identity	email (placeholder) not stated
Limits	volume-quota 1 TB a month is stated on the plan card as 'Bandwidth 1TB'; the card states no port speed for this plan (the tracker claims 1 Gbps) and no overage rule source 1 TB a month is stated on the plan card as 'Bandwidth 1TB'; the card states no port speed for this plan (the tracker claims 1 Gbps) and no overage rule
Binding	volume-quota 1 TB a month is stated on the plan card as 'Bandwidth 1TB'; the card states no port speed for this plan (the tracker claims 1 Gbps) and no overage rule
Interface	rest inferred from the tooling the provider documents; not probed
Tooling	order links point at clientarea.strike.bz/index.php?rp=/store/... product pages; no API, panel or image documentation appears on the page read
Composes with	EUR 25.00 a year for 512 MB in Poland or New Jersey is a standing host for a webhook receiver, a certificate checker or an uptime monitor, where 1 TB is ample and the annual prepay is the only real cost; it is not a host for anything that moves bytes
Reliability	no reliability event recorded
Notes	The vendor card states the annual price and the tracker states the monthly equivalent, so the two agree on the plan. The vendor's own no-KYC claim is recorded in the evidence rather than in identity_cost, because the signup page itself was not fetched and the field therefore stays at the email floor. Not in dossier/compute (searched: strike.bz, no record). would-settle: whether EUR 25.00/year renews at the same rate, and whether the 1 TB is enforced or shaped; the card states neither. Rendering and provenance: currency symbols are written out (EUR, GBP, RUB, VND), diacritics in place names are folded to ASCII, and a price the page splits across two lines is joined as value/period; the tracker page stated 'Database update: 7 hours ago' when it was read on 2026-10-22.
Evidence rung	documented
Checked	2026-10-22 (live); stale on 2026-11-21
Parsed numbers	`$.limits[0].value` limit:volume-quota 1.0 TB / month

Evidence (4)

date	source	what it proved
2026-10-22	vpspricetracker.com/provider/Strike/vps	cheapest row: 'Strike - EUR 2.08 / month', 'yearly Service', '1 Intel Cores (shared)', '512 MB RAM', '10 GB NVMe', '1,000 GB/month bandwidth', '1 Gbps port speed', 'New Jersey U.S.A.' and a second identical row for 'Gdansk Poland'
2026-10-22	strike.bz	Budget 'Pico' card, quoted: 'Annual VPS for basic tasks', 'CPU 1 vCPU', 'RAM 512MB', 'Disk 10GB NVMe SSD', 'Bandwidth 1TB', 'Price EUR 25.00/yr', under the location columns 'Poland' and 'USA'
2026-10-22	strike.bz	Budget 'Nano' at 'EUR 3.00/mo' with '1GB' and '15GB NVMe SSD'; Pro 'Pico' at 'EUR 30.00/yr' with the same 512MB and 10GB; Pro 'Nano' at 'EUR 4.00/mo' with 1GB and 15GB
2026-10-22	strike.bz	identity, quoted from the FAQ list and the closing block: 'No KYC required - order without revealing your identity. Anonymous payment methods accepted. We collect minimal data by design.'

More fields (1)

{
 "wave2": {
  "class": null,
  "free_tier_kind": "none",
  "shape": {
   "vcpu": 1,
   "ram_gib": 0.5,
   "disk_gib": 10,
   "gpu_class": null,
   "gpu_count": null
  }
 }
}

Unknown or withheld values (7)

$.identity_cost.detail not-stated
$.identity_cost.kind identity-defaulted
$.per_object_cap.notes process
$.per_object_cap.stated not-applicable
$.reliability_note none-observed
$.retention.notes process
$.retention.stated not-applicable