← Tool Garage
Ship station
Railway & Render
Hosting for things that need to keep running — a server, a worker, a database of your own.
1. Learn it
- Vercel and Netlify are best at request-in, response-out. These hosts run a process continuously.
- You need one when you have a background job, a queue, a websocket, or a long task that outlives a web request.
- They bill for what's running, not per visit — so an idle service still costs something.
- Environment variables live in the dashboard, never in your code.
Cost: Small monthly cost once something runs continuously.
2. Practice it
Simulated — nothing real happensDecide if you need an always-on server
For your idea, write down anything that must happen when nobody is on the site: nightly emails, a queue, a scheduled import. If the list is empty, say so.
3. Connect it
Real — your own account- 1Sign in at railway.app or render.com with GitHub.
- 2Deploy one small service and set its environment variables in the dashboard.
- 3Set a spending cap before you leave anything running.
MessyDev never signs you up, spends your money, or touches your accounts. You do that part.
4. Use it
Background workers, scheduled jobs, self-hosted tools like n8n, or a database you want to control.
Honest alternatives
There is no single correct stack. Any of these would be a reasonable choice instead.
- Render
- Fly.io
- A plain virtual server
- Not needing one yet