EQVPS

Self-host multiple services on one VPS and one IP

Run your app, database, n8n, a dashboard and more behind a single dedicated IP with a reverse proxy. One box, one monthly crypto payment, no KYC. From $20/mo.

There's a point in every self-hosting habit where you stop wanting a server per thing. You've got an app, its database, maybe n8n for automations, a status dashboard, a small API — and running each on its own tiny VPS means five IPs, five bills, five machines to patch. It's tidier, and cheaper, to put them on one box behind one IP.

The trick that makes this work is a reverse proxy. Caddy, nginx or Traefik sits on the public ports 80/443 and routes by hostname: app.you.com goes to your app, n8n.you.com goes to n8n, db-admin.you.com to your admin panel. Every service listens only on localhost; the proxy is the single public door, and it hands each subdomain its own HTTPS certificate automatically.

The plan for this

Medium-IP ($20/mo) is the natural fit: 6 vCPU, 6 GB RAM, 45 GB NVMe, a dedicated IPv4 with every port open. That's room for a handful of small services plus their databases without them fighting for resources.

Two honest boundaries:

Setup shape

# Ubuntu 24.04, Medium-IP — Docker + Compose, Caddy as the front door
curl -fsSL https://get.docker.com | sh
# docker-compose.yml: your services on localhost, Caddy routing by subdomain
# Caddy auto-issues HTTPS for each hostname you point at the IP
docker compose up -d

Point your subdomains' A records at the one IP, list them in the Caddyfile, and each service comes up on its own clean HTTPS URL. Add reverse DNS from the dashboard if any of them send mail.

Why here

One dedicated IP you fully control, everything behind it, paid as a single flat crypto bill with no KYC. It's the homelab-on-a-VPS pattern: your stack, your machine, one predictable monthly number. When one box stops being enough, you split the heaviest service onto its own — but most people run comfortably on one for a long time. Medium-IP is where that starts.

Ready to deploy? Pay with crypto, no KYC — live in about a minute.

Deploy now →

FAQ

How do I run several services on one IP?

A reverse proxy — Caddy, nginx or Traefik — sits on ports 80/443 and routes each subdomain to the right service by hostname. app.you.com → your app, n8n.you.com → n8n, and so on. All the services listen on localhost; only the proxy is public. One IP, many services, clean HTTPS on each.

Which plan for a stack of services?

Medium-IP ($20/mo) — 6 vCPU, 6 GB RAM, 45 GB NVMe, dedicated IPv4 with all ports open. Comfortable for a handful of small services plus their databases. If it's just one app plus a DB, Small-IP ($16) is enough; if the services are memory-hungry (big databases, in-memory work), that's where the Pro line starts.

Docker Compose or bare metal?

Compose is the easy path for a multi-service box — each service in its own container, one file describing the whole stack, the reverse proxy as another container. It keeps things tidy and easy to move. Bare-metal works too if you prefer; full root, your call.

Why one box instead of separate small ones?

Cost and simplicity. One dedicated IP, one monthly bill, one machine to keep updated — versus juggling several tiny servers, each with its own IP and its own maintenance. Co-locating also means services talk over localhost with near-zero latency.

Comments

No comments yet. Be the first.

Leave a comment

Comments are moderated before they appear.