fshy

Home / Compute

SnapDeploy

snapdeploy.dev/pricingContainer and VM sandboxcompute/snapdeployJSONcomparereport an errorprovider JSON

Free allowance
One Small container per app, up to 4 apps, no credit card: 512 MB RAM, 0.25 vCPU, 10 deploys a day (at most 5 in any 12 hours), 100 running hours a month across the account, sleeps after 15 minutes without visitors.
Verdict
caveatusable, with a named limit or an unprobed read path
Cost
free tier
Identity
emailno card, no phone
Binding limit
retention-clamped100 running hours a month across the whole account, not per container, so four containers average about 25 hours each and the box sleeps after 15 idle minutes and takes about a minute to wake, which breaks any request that must answer cold.
Evidence
documented5 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 tierOne Small container per app, up to 4 apps, no credit card: 512 MB RAM, 0.25 vCPU, 10 deploys a day (at most 5 in any 12 hours), 100 running hours a month across the account, sleeps after 15 minutes without visitors. Quoted from the pricing page.
unit hours; metered on wall-clock; perpetual-free
Pricenone stated
Limits
  • retention-clamped (binding) 100 running hours a month across the whole account, not per container, so four containers average about 25 hours each and the box sleeps after 15 idle minutes and takes about a minute to wake, which breaks any request that must answer cold. source
Identityemail no card and no payment method: the pricing page lists the free tier with 'no credit card', so no hold exists. The evidence does not say which identifier the account is created with, so whether an email alone suffices is not stated; debit and prepaid acceptance are not stated
Egressnot stated
Retention100 running hours a month across the whole account, not per container, so four containers average about 25 hours each and the box sleeps after 15 idle minutes and takes about a minute to wake, which breaks any request that must answer cold.
Interfaceunknown web dashboard, GitHub push-to-deploy, an MCP connector (npx @snapdeploy/mcp), and an HTTP API reference at https://snapdeploy.dev/api for the /api/mobile/** endpoints, authenticated with a scoped personal access token or a legacy API key sent as X-API-Key; the docs/api path answers HTTP 404
Toolingnot stated
Composes with100 hours is enough for a daily batch job that runs a few minutes, and the 2 GB Docker image limit lets a real scientific Python image ship; it does not compose into anything always-on.
Reliabilityno reliability event recorded
NotesFound via awesome-hosting Containers section, which lists the free tier as 100 h/month and the paid floor as USD 12 a month. The docs/free-tier page was not read separately; the pricing page already states the cap.
Parsed numbers
  • has-free-tier 1
  • retention-clamped 25 hours
Evidence 5
datesourcewhat it proved
2026-10-22snapdeploy.dev/pricingfree tier: one Small container per app, up to 4 apps, 512 MB RAM and 0.25 vCPU, 10 deploys a day, 100 running hours a month across the account, sleeps after 15 minutes, no credit card, quoted
2026-10-22snapdeploy.dev/pricingreference to the free-tier page at https://snapdeploy.dev/docs/free-tier as the authority for free-tier rules
2026-11-03snapdeploy.dev/docs/mcpan MCP connector exists for deploying and managing containers
2026-11-03snapdeploy.deva web dashboard exists
2026-11-04snapdeploy.dev/apian API reference page exists for the /api/mobile/** endpoints, authenticated by a scoped token or legacy API key
More fields 1
facets{"class": "perpetual-free-allowance","free_tier_kind": "perpetual-free","shape": {"vcpu": 0.25,"ram_gib": 0.5,"gpu_class": null,"gpu_count": 0}}
Unknown values 6
  • egress metered: egress metering was not published
  • egress terms: a source was read and is silent on this field
  • 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
  • tooling: a source was read and is silent on this field