Prompt
I'm unhappy with Netlify Functions for backend APIs, what should I use instead?
Latest observation
If you’re unhappy with Netlify Functions for backend APIs, the best alternative depends on what’s frustrating you: cold starts, routing limits, local dev, performance, long-running jobs, or general backend complexity.
Good alternatives
1) Vercel Functions / Vercel Edge Functions
Best if you want the closest “serverless frontend + API” experience.
- Very smooth DX for web apps
- Easy deployment from Git
- Good if you’re already using Next.js
- Edge Functions are fast for lightweight, low-latency work
Downsides: can still feel constrained for more serious backend logic, background jobs, and stateful workflows.
2) Cloudflare Workers
Best if you want speed and global edge deployment.
- Very fast cold start / near-instant execution
- Great for API gateways, lightweight APIs, auth, caching, middleware
- Excellent global latency
- Strong platform primitives: KV, Durable Objects, R2, Queues
Downsides: different runtime model than Node.js; some libraries don’t work as-is.
3) Fly.io
Best if you want actual servers close to users, not just functions.
- Run full apps/containers
- Better for real backend services, websockets, background processes
- More control than functions
- Great if you want to run Postgres, Redis, workers, APIs together
Downsides: more ops responsibility than pure serverless.
4) Render
Best if you want simple deploys for APIs, workers, cron jobs, and databases.
- Easier “traditional backend” feel
- Good for long-running services
- Supports background workers and cron
- Friendly deployment experience
Downsides: not as globally distributed as edge platforms.
5) Railway
Best for fast prototyping and small-to-medium backend services.
- Very easy to start
- Good DX for databases and services
- Nice for hobby projects and startups
Downsides: less ideal if you need strict enterprise scaling or edge performance.
6) AWS Lambda + API Gateway / Lambda URLs
Best if you want maximum flexibility and don’t mind complexity.
- Huge ecosystem
- Can scale well
- Good for enterprise or complex cloud architectures
Downsides: usually more setup, more boilerplate, and often more annoying than it should be.
7) A container platform: ECS/Fargate, Kubernetes, or a simple VPS
Best if your API is becoming a real backend, not just a set of functions.
- Full control
- Great for complex services, background jobs, queues, websockets, custom middleware
- Easier to reason about once the app grows
Downsides: more infrastructure management.
My practical recommendation
- If you want the best “modern serverless” alternative: Cloudflare Workers
- If you want the simplest backend deployment with more control: Render or Fly.io
- If you’re using Next.js and want a seamless path: Vercel
- If your backend is becoming “real backend” territory: Fly.io, Render, or containers/VPS
Rule of thumb
Choose based on what you need most:
- Lowest latency / edge → Cloudflare Workers
- Best DX for frontend teams → Vercel
- More traditional backend → Render
- More control + real services → Fly.io
- Maximum flexibility, okay with complexity → AWS
- Full backend ownership → VPS/containers
If you tell me:
- your stack (Next.js? React? plain Node?),
- what specifically you dislike about Netlify Functions,
- whether you need background jobs/websockets/DB,
…I can recommend the best option for your exact case.