fshy

Home / Compute

Apply.Build

apply.build/Platform hostcompute/apply-buildJSONcomparereport an errorprovider JSON

Free allowance
'Free tier: 0.5 vCPU and 512 MiB' and 'No credit card.
Verdict
caveatusable, with a named limit or an unprobed read path
Cost
free tier
Identity
emailno card, no phone
Binding limit
per-object-capthe 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.
Evidence
documented9 sources; a first-party page was read and the sentence quoted
Freshness
stale on 2026-12-05checked 2026-11-04 (live); stale on 2026-12-05
Free tier'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
Pricenone stated
Limits
  • per-object-cap (binding) 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
Identityemail 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.
EgressPer-app egress cap by size: Tiny 2.5 MB/s, Small 5 MB/s, Medium 10 MB/s, Large 20 MB/s; ingress uncapped; fair-use terms apply to all traffic. No per-GB egress allowance and no overage price is published: 'There's no usage billing, and traffic spikes don't show up on your invoice.'
Interfaceunknown inferred from the tooling the provider documents; not probed
Toolingnot stated
Composes withthe 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.
Reliabilityno reliability event recorded
NotesAggregator 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.
Parsed numbers
  • has-free-tier 1
  • per-object-cap 512 MiB
Evidence 9
datesourcewhat it proved
2026-10-22apply.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-22apply.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-22apply.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
2026-11-04apply.build/pricingthe pricing page states fair-use terms for all traffic and no fixed cap on incoming traffic
2026-11-04apply.build/pricingper-size egress rate cap listed under the app size on the pricing page
2026-11-04apply.build/pricingper-size egress rate cap listed under the app size on the pricing page
2026-11-04apply.build/pricingper-size egress rate cap listed under the app size on the pricing page
2026-11-04apply.build/pricingper-size egress rate cap listed under the app size on the pricing page
2026-11-04apply.build/no usage billing, so no per-GB overage price is published
More fields 1
facets{"class": "floor-price","free_tier_kind": "free-forever","shape": {"vcpu": 0.5,"ram_gib": 0.5,"gpu_class": null,"gpu_count": null}}
Unknown values 5
  • interface: the access interface was not established
  • per object cap stated: the field does not apply to this kind of offer
  • reliability note: nothing of this kind was observed
  • retention stated: the field does not apply to this kind of offer
  • tooling: a source was read and is silent on this field