Back to all features
App Management

Connect Apps

Connect any two apps on the same server by defining a private Docker network — Server Compass auto-configures networking, injects service URLs as environment variables (e.g. REDIS_URL), and monitors network health to detect ghost or misconfigured networks.

Connect Apps screenshot in Server Compass

Connect Apps: Step by Step

Connect Apps is designed to be intuitive. Here's how you use it in Server Compass.

1

Open Connect Apps

From any app's detail page, click Connect Apps. Server Compass lists every other app on the same server.

2

Pick caller and target

Choose 'I call the other app' or 'Other app calls me', or click Auto-detect to infer roles from container images (Redis, Postgres, MySQL, MariaDB, MongoDB, Valkey, KeyDB, TimescaleDB).

3

Accept the suggested env value

For known data services, the modal prefills a working URL like redis://shared-redis:6379. Edit the env key or value if your app expects a different name.

4

Optionally remove the producer public port

Tick 'Remove producer public port' to drop the producer's published ports while linked apps keep talking internally. Original ports are snapshotted for safe unlinking.

5

Connect

Server Compass writes the network into both compose files, runs docker network create on the server, redeploys producer then consumer, and persists the link in the app_connections table.

Raw Commands

Before Connect Apps Existed

This is what you'd have to do manually without Connect Apps. We don't recommend it.

1

SSH into your server

You need a shell on the host to wire up Docker networking.

terminal
ssh root@your-server-ip
2

Create a shared private network

Two apps on the same host can't talk privately by default. You have to create a user-defined network.

terminal
docker network create shared

# Verify it exists
docker network ls | grep shared

Forget this step and your apps fall back to localhost or public IPs — neither works the way you want.

3

Edit the producer's docker-compose.yml

Add the network at the top level and attach the service. Optionally remove published ports so it's no longer reachable from the internet.

terminal
# /opt/apps/redis/docker-compose.yml
services:
  redis:
    image: redis:7
    # ports:
    #   - "6379:6379"   # delete this if you want it private
    networks:
      - shared
networks:
  shared:
    external: true

Indentation matters. One bad space and compose silently ignores the network block.

4

Edit the consumer's docker-compose.yml

Same network change, plus add the env var your app reads. The hostname is the producer's service name.

terminal
# /opt/apps/api/docker-compose.yml
services:
  api:
    image: my-api:latest
    environment:
      REDIS_URL: "redis://redis:6379"
    networks:
      - shared
networks:
  shared:
    external: true

Get the hostname wrong (e.g. `localhost`, the public IP, the container ID) and the connection silently fails on the next deploy.

5

Redeploy both stacks in the right order

Producer first, then consumer. If you redeploy in the wrong order, the consumer's env var points at a hostname that doesn't exist yet.

terminal
cd /opt/apps/redis && docker compose up -d
cd /opt/apps/api   && docker compose up -d

# Did the network actually attach? Check.
docker network inspect shared | grep -A2 Containers

No rollback. If the consumer fails to start, you have to manually undo the env var, the network block, and the port removal.

6

Document what you connected — somewhere — anywhere

There is no source of truth. In six months you will not remember which apps share which network or which env var came from where.

terminal
# Hope you wrote it down. Otherwise grep through every compose file:
grep -l "shared:" /opt/apps/*/docker-compose.yml
grep -r "REDIS_URL" /opt/apps/*/

Multiply this by every Redis, Postgres, and Mongo you self-host across your projects.

The Easy Way

Or... Just Use Server Compass

Connect Apps isn't just faster—it's safer. No typos, no forgotten flags, no accidental disasters.

  • Point and click
  • Instant validation
  • Safe defaults
  • Works with any provider
Download Server Compass$49 • Lifetime license
Capabilities

Connect Apps: Full Feature List

Everything you need for app management in one integrated tool, replacing complex CLI commands and manual configuration.

Get Started
Auto-detect connection direction from Docker image names (Redis, Postgres, MySQL, MariaDB, MongoDB, Valkey, KeyDB, TimescaleDB)
Suggested env values: REDIS_URL, DATABASE_URL, MONGODB_URI prefilled with real internal hostnames
Remove producer public ports while keeping linked apps reachable internally
Manage links from either the app's Connected Apps tab or the server-level App Connections panel
Atomic redeploy: producer first, then consumer; rolls compose files back on failure
Per-link record of network name, env var, and original ports for safe unlinking

Connect Apps: Why It's Essential

Server management shouldn't require a DevOps team. Connect Apps makes professional-grade app management accessible to everyone.

Complete Visibility

Connect Apps gives you a bird's-eye view of all your applications. No more guessing container states.

Instant Actions

Connect Apps puts start, stop, restart, and rollback at your fingertips with one-click controls.

Safe Operations

Connect Apps includes safety guards and confirmations to prevent accidental destructive actions.

Historical Context

Connect Apps keeps a full audit trail so you always know what changed and when.

Questions About Connect Apps

Common questions about Connect Apps in Server Compass

How do I access Connect Apps in Server Compass?

Connect Apps is available in the App Management section of Server Compass. Simply connect to your server, navigate to App Management, and you'll find Connect Apps ready to use. No additional setup or plugins required.

Does Connect Apps require any server-side installation?

No. Server Compass operates as a desktop application that connects to your server via SSH. Connect Apps works through this connection without installing any agents or packages on your server (except the optional monitoring agent for resource tracking).

Is Connect Apps included in all Server Compass plans?

Yes. Every Server Compass feature, including Connect Apps, is included with the one-time $49 payment. There are no tier restrictions, add-ons, or per-server fees. You get all 102+ features for all your servers.

Can I use Connect Apps with any VPS provider?

Connect Apps works with any VPS or dedicated server that supports SSH access and Docker. This includes DigitalOcean, Hetzner, Vultr, Linode, AWS EC2, Google Cloud, Azure, and any other provider. It also works with local servers and homelab setups.

What makes Connect Apps different from command-line alternatives?

Connect Apps provides a visual, intuitive interface that replaces complex CLI commands and configuration files. You get real-time feedback, safety confirmations, and a consistent experience across all your servers without memorizing syntax or writing scripts.

Try Connect Apps Today

Download Server Compass and get access to Connect Apps along with 101 other features. One-time $49 payment. No subscriptions. No per-server fees.