How to choose
Classify the backend before picking a platform:
- Traditional web service: Express, FastAPI, Django, Rails or Go services are easiest on Render or Railway-style PaaS platforms.
- Lightweight API or webhook: Cloudflare Workers is a strong fit if the code can run in an edge/serverless runtime.
- Backend-as-a-service: Firebase is better when you want auth, database, hosting, storage and functions without managing a server process.
- Containerized app: Fly.io gives more control for Dockerized services, private networking and global placement, but it expects more operational comfort.
The key decision is sleep versus runtime flexibility. Platforms that run a normal server process often save money by sleeping idle free instances. Platforms that avoid sleep usually do so by limiting the runtime model, request duration, CPU time, bundle size or available APIs.
Practical recommendation
For a beginner backend API, start with Render if you can tolerate cold starts. It is direct, Git-based and supports common backend languages without forcing a serverless rewrite.
For a webhook receiver, simple JSON API, auth callback, small proxy or edge-friendly backend, start with Cloudflare Workers or Pages Functions. You avoid the classic sleeping-server problem, but you must design around Workers limits.
For mobile apps, realtime prototypes and apps where authentication matters more than custom server code, start with Firebase. It is not “hosting a backend server” in the old sense, but it can remove the need for one.
Use Railway or Fly.io when you value the developer experience or container model enough to accept that current free access is trial-shaped or usage-based.
Free-tier catches to watch
Free backend hosting usually fails on one of these edges:
- idle sleep and cold starts
- monthly instance hours or credits
- CPU time per request
- memory and bundle-size limits
- database storage and backups
- background worker support
- WebSocket behavior
- outbound traffic or external API calls
- trial expiration
- missing production uptime guarantees
If your backend serves a public product, stores user data or handles paid customers, choose the paid path before launch. Free backend hosting is excellent for learning, prototypes, demos and low-traffic side projects, but the first real users often expose the hidden limit quickly.