How do I host an API and database in one place?

You can host an API and a database “in one place” by putting them on the same server/VM/container platform, or by using a managed service that gives you both in the same cloud account/project.

Common ways to do it

1) One VPS or server

Run both:

• your API app (Node, Python, Go, etc.)
• your database (PostgreSQL, MySQL, MongoDB)

on the same machine.

Typical setup

• Nginx or Caddy as reverse proxy
• API app behind it
• Database bound to localhost/private network only

Pros

• Simple
• Cheap
• Easy to understand

Cons

• Single point of failure
• Resource contention: API and DB share CPU/RAM/disk
• Harder to scale

---

2) Docker Compose on one machine

Use Docker containers for both services on the same host.

Example idea:

• api container
• db container
• optional nginx container

This is a very common “one place” setup for small projects.

Pros

• Easy to deploy/reproduce
• Clean separation
• Easy backups if volumes are configured right

Cons

• Still one physical host
• Need to manage persistent storage carefully

---

3) Single cloud app + managed database in same provider

Host your API on:

• Render, Fly.io, Railway, Heroku-like platforms, AWS ECS, Azure App Service, etc.

And use the provider’s managed database in the same region/account.

Pros

• Easier operations
• Backups, updates, monitoring often included
• Better reliability than self-hosting DB

Cons

• Usually costs more
• Less control than self-hosting

---

Recommended architecture for most small apps

If you want “one place” but still reasonably safe:

• API: Docker container or process manager on a VPS
• Database: PostgreSQL in a Docker container or managed DB
• Reverse proxy: Nginx/Caddy
• TLS: Let’s Encrypt
• Firewall: expose only ports 80/443 publicly
• DB port: keep private, not public

---

Basic example with Docker Compose

You can run both on one server like this:

version: "3.9"

services:
  api:
    build: ./api
    ports:
      - "3000:3000"
    environment:
      DATABASE_URL: postgres://appuser:apppass@db:5432/appdb
    depends_on:
      - db

  db:
    image: postgres:16
    environment:
      POSTGRES_USER: appuser
      POSTGRES_PASSWORD: apppass
      POSTGRES_DB: appdb
    volumes:
      - db_data:/var/lib/postgresql/data

volumes:
  db_data:

Notes:

• The API connects to the DB using the service name db
• The database data persists in a volume
• You should secure the password and not hardcode it in production

---

Important security tips

• Don’t expose your database directly to the internet unless absolutely necessary
• Use environment variables or secrets for DB credentials
• Use backups
• Use HTTPS
• Keep the OS and DB updated
• Limit DB permissions to only what the API needs

---

If you mean “same server, same domain”

That’s also common:

• example.com → frontend
• api.example.com → API
• database stays internal only

The DB does not need its own public domain.

---

Best choice depends on your goal

• Learning / side project: VPS + Docker Compose
• Small production app: VPS + managed DB or Docker Compose with strong backups
• Serious production: separate API and managed DB, same cloud region

If you want, I can show you:

1. a Docker Compose setup
2. a setup on a VPS with Nginx
3. a cloud deployment option for your specific stack (Node, Python, etc.)