Back to The Gateway

Install guide

Install The Gateway safely.

Use this guide to install the gateway service, confirm recovery access, define DNS and route ownership, validate fallback behavior, and keep a rollback path before traffic depends on the box.

1. Pick deployment mode

Choose primary gateway, embedded gateway, portable gateway, or appliance-style install. Name the host, interfaces, upstream router, and devices in scope.

2. Confirm recovery

Keep console, SSH, or local admin access available before changing DNS, routes, firewall rules, or remote access.

3. Run installer

Install the service with curl -fsSL https://thegateway.pro/install.sh | bash, then open the local setup flow.

4. Configure policy

Map device groups, DNS policy, route profiles, fallback mode, backup target, and the final operator who approves apply.

5. Validate behavior

Check local admin access, resolver behavior, route state, fallback behavior, leak checks, privacy posture, and binary checksum verification.

6. Record evidence

Save redacted install notes, route/DNS checks, fallback checks, recovery confirmation, and known limitations for the deployment.

Install command

Run this on the target gateway host.

Do not run the installer on a machine where losing network access would also remove your only recovery path.

curl -fsSL https://thegateway.pro/install.sh | bash

After install, validate local UI access, DNS behavior, route state, fallback behavior, and recovery access.

Install evidence

Use these operator views during configuration and validation.

Redacted Gateway devices inventory screen
Configure Device scope.

Shows the client groups that should be configured before route and DNS policy apply.

Redacted Gateway routing policies screen
Preview Route intent.

Shows the route profile and fallback behavior that should be reviewed before apply.

Redacted Gateway dashboard showing route, DNS, tunnel, device, and backup status cards
Validate Post-install state.

Shows the dashboard evidence that should accompany install notes and remaining risks.

Next action

Validate before moving real traffic.

Confirm route ownership, DNS ownership, fallback behavior, recovery access, and privacy posture before making The Gateway the path that devices rely on.