Caliber Node
Compute · 1 record · JSON
Caliber Node Compute
paidemail?card?Rvolume-quota
| Free tier | USD 10/year for the Micro plan: 1 shared vCPU on an Intel Xeon Gold, 1 GB DDR4, 15 GB SSD, in Dallas, Nuremberg or Singapore, with a 250-app one-click catalogue, automatic HTTPS and custom domains, per-app CIDR allow-listing, one-click app updates, transactional email with SPF and DKIM, snapshots on a daily or weekly schedule, health-check monitoring with email alerts, and a container terminal, SFTP and app logs. The app count is limited only by the resources. A separate option puts the same panel on the customer's own server. This is app hosting and not a VPS: the thread says so directly. unit GiB; metered on wall-clock; none |
|---|---|
| Price | none stated |
| Per-object cap | not applicable |
| Retention | not applicable |
| Egress | not stated: no monthly transfer figure, no port speed and no overage term appear in the thread |
| Identity | email (placeholder) not stated |
| Limits |
no bandwidth figure appears anywhere in the thread, so the only numbered ceilings are the 1 GB of RAM, 15 GB of SSD and 1 shared vCPU that the plan caps. Nothing about traffic is established, and the field is named volume-quota only because the resource quota is the limit that exists; a reader should treat the transfer allowance as unverified rather than absent. |
| Binding | volume-quota no bandwidth figure appears anywhere in the thread, so the only numbered ceilings are the 1 GB of RAM, 15 GB of SSD and 1 shared vCPU that the plan caps. Nothing about traffic is established, and the field is named volume-quota only because the resource quota is the limit that exists; a reader should treat the transfer allowance as unverified rather than absent. |
| Interface | rest, cli inferred from the tooling the provider documents; not probed |
| Tooling | a panel with a container terminal, SFTP, app logs, per-app CIDR firewall rules, scheduled snapshots and health-check alerts; no API or CLI is documented on the page read |
| Composes with | USD 10 a year is USD 0.83/month for 1 GB of RAM and 15 GB of disk on a container platform with automatic HTTPS, which is the cheapest way to put a hosted application and its certificate online without administering a machine the missing transfer figure is the whole risk, since an app that serves bytes could hit a cap nobody has published |
| Reliability | no reliability event recorded |
| Notes | Not in dossier/compute (searched: caliber, no record). Recorded from the forum thread alone with no vendor page: the thread links no provider site, the offer index links only the thread, and does not guess a domain. That is why confidence is reported and the binding note says what is unverified. would-settle: the vendor domain, the transfer allowance, and whether the Bring Your Own Server option is priced separately, since the thread describes it without a figure. |
| Evidence rung | reported |
| Checked | 2026-10-22 (live); stale on 2026-11-05 |
| Parsed numbers |
|
Evidence (2)
| date | source | what it proved |
|---|---|---|
| 2026-10-22 | lowendtalk.com/discussion/221603/caliber-node-10-year-cloud- | the offer thread, posted September 29, 2026, quoted from its table: 'Plan Micro', 'CPU 1 shared vCPU - Intel Xeon Gold', 'RAM 1 GB DDR4', 'Storage 15 GB SSD', 'App catalog 250+ one-click apps', 'App limit As many as your resources can handle', 'Location Dallas, USA - Nuremberg, Germany - Singapore'; body text: 'Managed Cloud Apps - $10/year'; 'Our managed hosting is an app hosting service, not a VPS' |
| 2026-10-22 | lowendtalk.com/ | the thread carries no vendor URL in its body, and the only provider site reachable from the offer index entry is the LowEndTalk thread itself: did not establish a vendor domain for Caliber Node and did not guess one |
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 (8)
$.egress.meteredegress-unknown$.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