Railway / Render
Excellent DX. You don't own the box, the data, or the bill once the app stays up.
No Docker necessary
Describe your app once. yarder dev runs it as native processes on your laptop. The same yaml is how yarder deploy will put that stack on a VPS you own. nginx, PM2, SSL — not your problem.
Develop in the same environment you deploy to.
$ npx yarder init
See the model
Coming to npm. For solo Node developers who left Railway for a $5 box — and then remembered nginx.
$yarder dev waiting for postgres … postgres healthy waiting for redis … redis healthy waiting for api … api healthy http://api.my-saas.test web healthy http://web.my-saas.test injected API_URL DATABASE_URL REDIS_URL GUI http://127.0.0.1:3001
The false choice
Excellent DX. You don't own the box, the data, or the bill once the app stays up.
Self-hosted PaaS — if you're willing to make Docker the product. Most Node apps don't need that.
Cheap Hetzner box. Then nginx, certbot, PM2, ports, .env drift, and five terminal tabs.
yarder sits in the gap: own the infrastructure without owning all the work, and without containerizing an app that already runs as processes.
Application-shaped
name: my-saas services: web: command: npm run dev dir: ./web port: 3000 api: command: npm run start dir: ./api port: 4000 health: /health worker: command: npm run worker dir: ./worker postgres: type: postgres redis: type: redis
Web, API, worker are start commands and directories. Postgres and Redis are managed capabilities — you ask for them, you don't author a Compose service.
Starts in dependency order, waits until each service is healthy, injects discovery URLs, routes .test hostnames through nginx, and opens a GUI with logs.
Same file, same mental model, on a VPS you already have. Process supervision, reverse proxy, TLS. You think about shipping an app, not configuring a server.
The GUI
Health, hostnames, restarts, masked env, live logs. Local today. Staging and production from the same verbs next.
app
web.my-saas.test
app
api.my-saas.test
app
no port
managed
DATABASE_URL
managed
REDIS_URL
Why not Coolify
| yarder | Coolify | Foreman / PM2 | |
|---|---|---|---|
| No Docker required | yes | — | yes |
| GUI | yes | yes | — |
| Local + production, same model | coming | — | — |
| You own the server | yes | yes | yes |
| Application-shaped config | yes | — | partial |
Railway and Render still win if you want zero servers. yarder is for when you want the box.
Right now
Local yarder.yaml + yarder dev: native processes, nginx hostnames, health, env, and a GUI with logs.
yarder deploy to a VPS you already have. Same file, process supervision, reverse proxy, TLS.
Git deploy, monitoring, and paid tiers if the ops work is worth a subscription. Not priced until it exists.
You still pay Hetzner ~$5 when you self-host. yarder is the layer that makes that box feel like a platform.
FAQ
yarder is a developer tool for solo Node developers who want to self-host without becoming a DevOps engineer. You describe processes in a yarder.yaml. yarder dev runs them as native processes on your laptop with a GUI. Deploying that same stack to a VPS you own is next.
No. App services are start commands and directories. Postgres and Redis are managed capabilities you ask for — you do not author a Compose file. Docker is not the product surface.
Same job — self-host on a server you own — different model. Coolify is Docker and Compose shaped. yarder is application shaped: processes, directories, and a yaml that is not Compose. Railway and Render still win if you want zero servers.
Not yet. The current slice is local: yarder.yaml, yarder dev, hostname routing, health checks, and a GUI with logs. yarder deploy to a VPS you already have is the next slice.
Yes while it is early. There are no paid plans yet. You still pay your VPS provider if you self-host.