Jobs · 06
Where the app stays up
Use this when the code runs and you need a URL. Frontend hosts and app platforms a solo builder can ship on in an afternoon.
Initial editorial estimate. Not a measured benchmark. Edit scores in data/tools.json.
01
Best for Deploying a Next.js app with preview URLs
Push a frontend or Next.js app and get a URL.
- + The shortest path from a Next.js repo to a URL
- + Preview deployments are part of the product
- − Long-running jobs and heavy servers are the wrong shape
- − Commercial usage beyond the hobby tier: check site
02
Best for Edge functions and a sharp free tier
Run code on Cloudflare's edge, plus Pages for sites.
- + The free tier is one of the more generous in hosting
- + Edge latency is the point
- − The Workers runtime is not a full Node server
- − Paid plan details and limits: check site
03
Best for A long-running service without becoming a platform engineer
Deploy a service from a repo without writing a platform file first.
- + Less YAML than a hyperscaler
- + Services and databases live in one project
- − Not the default for a pure Next.js frontend
- − Pricing: check site
04
Best for Git-push hosting that is not Vercel
Git-based hosting for web apps, with functions and forms.
- + Git-based deploys are easy to explain
- + A free tier exists for small sites
- − Next.js support is real but Vercel is the path of least resistance there
- − Plan limits: check site
05
Best for Web services and cron without AWS
Web services, static sites, cron, and databases on one platform.
- + One product covers services, jobs, and data
- + Easier to reason about than a hyperscaler console
- − Cold starts and spin-down on free instances have been part of the trade
- − Current plan limits: check site