fshy

fshy / Compute

ClickHouse Cloud

clickhouse.com · Compute · 1 record · JSON

ClickHouse Cloud Compute

trialemailno cardDvolume-quota

clickhouse.com/pricing · managed database · compute/clickhouse-cloud · JSON · compare

Free tierPricing page, quoted: 'Start free with $300 in credits for 30 days' and, in the FAQ, 'ClickHouse Cloud starts with $300 in credits over 30 days, no credit card required. ClickHouse open source is free forever.' The page adds: 'The trial ends after 30 days or once the credits are consumed, whichever comes first; the account then converts to pay-as-you-go.' Trial credits expire at the end of the 30-day trial period, even after a payment method has been added.
unit mixed; metered on wall-clock; trial-credit
Pricenone stated
Per-object capnot applicable
Retentionnot applicable
Egressthe 30-day clock ends the free window before the USD 300 does for an idle service, because compute scales to zero when the service is idle; a service left running continuously for the 30 days is about 732 compute-unit-hours and the USD 300 has to cover those plus storage, backups and egress.
Identityemail the pricing FAQ states no credit card is required; the signup console is JavaScript-only and was not exercised, so the gate is the vendor's sentence and not a completed signup
Limits
  • volume-quota the 30-day clock ends the free window before the USD 300 does for an idle service, because compute scales to zero when the service is idle; a service left running continuously for the 30 days is about 732 compute-unit-hours and the USD 300 has to cover those plus storage, backups and egress. source
the 30-day clock ends the free window before the USD 300 does for an idle service, because compute scales to zero when the service is idle; a service left running continuously for the 30 days is about 732 compute-unit-hours and the USD 300 has to cover those plus storage, backups and egress.
Bindingvolume-quota the 30-day clock ends the free window before the USD 300 does for an idle service, because compute scales to zero when the service is idle; a service left running continuously for the 30 days is about 732 compute-unit-hours and the USD 300 has to cover those plus storage, backups and egress.
Interfaceunknown inferred from the tooling the provider documents; not probed
Toolingnot stated
Composes withUSD 300 of ClickHouse time is the cheapest route to scanning a multi-hundred-gigabyte corpus once; the same query then re-runs on the free open-source binary on rented compute, because the SQL is identical.
Reliabilityno reliability event recorded
NotesCompute scales to zero when idle, which stretches the credit if the service is not left running. Single-replica services are limited to 8 to 12 GiB of memory. Compute is billed per compute-unit-hour at a region-specific rate where 1 compute unit is 8 GiB RAM and 2 vCPU, and the page lists a separate rate per instance family, so no single per-hour figure is quoted here. No probe was run.
Evidence rungdocumented
Checked2026-10-24 (live); stale on 2026-11-23
Evidence (4)
datesourcewhat it proved
2026-10-22clickhouse.com/pricing'Start free with $300 in credits for 30 days' and 'The trial ends after 30 days or once the credits are consumed, whichever comes first; the account then converts to pay-as-you-go', quoted
2026-10-22clickhouse.com/pricingFAQ: 'ClickHouse Cloud starts with $300 in credits over 30 days, no credit card required. ClickHouse open source is free forever.', quoted
2026-10-22clickhouse.com/pricingBasic plan includes 'Up to 1 TB storage', '8-12 GiB total memory', '1 availability zone', backups every 24h retained for 1 day
2026-10-23clickhouse.com/docs/cloud/manage/billing'Trial credits expire at the end of the 30-day trial period, even after a payment method has been added.', quoted; the pricing page states 'Start free with $300 in credits for 30 days'
More fields (1)
{
 "wave2": {
  "class": "analytics-trial-credit",
  "free_tier_kind": "trial-credit",
  "shape": {
   "vcpu": 2,
   "ram_gib": 8,
   "disk_gib": null
  }
 }
}
Unknown or withheld values (7)
  • $.interface interface-unknown
  • $.per_object_cap.notes process
  • $.per_object_cap.stated not-applicable
  • $.reliability_note none-observed
  • $.retention.notes process
  • $.retention.stated not-applicable
  • $.tooling not-stated