Apply.Build

apply.build · Compute · 1 record · JSON

Apply.Build Compute

caveatemailno cardDper-object-cap

apply.build/ · platform host · compute/apply-build · JSON · compare

Free tier	Quoted: 'Free tier: 0.5 vCPU and 512 MiB' and 'No credit card. It stays active when you add paid packages, and after you cancel them.' Paid capacity is sold in packages: 'One package is 1 vCPU, 1 GiB of memory and 10 GB of storage' at 'EUR 5 a month each', split across apps and databases, with per-app sizes from '0.25 vCPU and 256 MiB up to 2 vCPU and 2 GiB' and 'Ephemeral disk per app, 2.5 to 20 GB'. unit GiB; metered on wall-clock; free-forever
Price	none stated
Per-object cap	not applicable
Retention	not applicable
Egress	not stated
Identity	email no card: the pricing page states 'No credit card. It stays active when you add paid packages, and after you cancel them.' No hold exists on the free tier because no payment method is taken. The signup form itself is not quoted in the record, so the email requirement is inferred rather than read, and debit and prepaid acceptance are not stated; a card appears only when a paid package is bought.
Limits	per-object-cap the free tier is one account-wide ceiling of 0.5 vCPU and 512 MiB, so a second app divides the same half-core and nothing scales past it without a package. source the free tier is one account-wide ceiling of 0.5 vCPU and 512 MiB, so a second app divides the same half-core and nothing scales past it without a package.
Binding	per-object-cap the free tier is one account-wide ceiling of 0.5 vCPU and 512 MiB, so a second app divides the same half-core and nothing scales past it without a package.
Interface	unknown inferred from the tooling the provider documents; not probed
Tooling	not stated
Composes with	the cheapest paid step is EUR 1.25 a month for 0.25 vCPU and 256 MiB, so a second always-on small process costs less than a coffee while the free 0.5 vCPU covers the first.
Reliability	no reliability event recorded
Notes	Aggregator claim checked: free-for.dev describes '0.5 vCPUs / 512 MiB RAM, European servers, automatic firewall' and the vendor agrees on the shape, so the gap is small. What the aggregator omits: the free allowance survives cancellation of paid packages, and the paid floor is EUR 1.25 for a quarter of a package. No sleep timer is published for the free tier, which would make it one of the few free PaaS tiers that does not scale to zero; that is documented absence, not a measurement, and probing an idle app is what would settle it.
Evidence rung	documented
Checked	2026-10-22 (live); stale on 2026-11-21
Parsed numbers	`$.limits[0].value` limit:per-object-cap 512.0 MiB

Evidence (3)

date	source	what it proved
2026-10-22	apply.build/	'Free tier: 0.5 vCPU and 512 MiB' and 'No credit card. It stays active when you add paid packages, and after you cancel them.', quoted
2026-10-22	apply.build/	'You buy resource packages at EUR 5 a month each. One package is 1 vCPU, 1 GiB of memory and 10 GB of storage', with a worked bill line 'Tiny - 0.25 vCPU, 256 MiB - EUR 1.25', quoted
2026-10-22	apply.build/	'Each app gets its own micro-VM' and the per-app range '0.25 vCPU and 256 MiB up to 2 vCPU and 2 GiB per app', quoted

More fields (1)

{
 "wave2": {
  "class": "floor-price",
  "free_tier_kind": "free-forever",
  "shape": {
   "vcpu": 0.5,
   "ram_gib": 0.5,
   "gpu_class": null,
   "gpu_count": null
  }
 }
}

Unknown or withheld values (9)

$.egress.metered egress-unknown
$.egress.terms not-stated
$.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