Skip to content

Servers and protocols

REACH separates public traffic handling from admin control surfaces.

Public server

The public server serves dynamic routes and protocol handlers.

  • HTTP (ASGI)
  • FTP (TCP capture)
  • WSS (WebSocket)

Start:

reach server start --role public --host 0.0.0.0 --port 8000

Admin server

The admin server exposes CRUD APIs for routes, rules, logs, and DNS zones. Start:

reach server start --role admin --host 127.0.0.1 --port 8001

Combined

Run both public and admin in one process:

reach server start --role both --port 8000

Protocol selection

The CLI can run multiple public protocol listeners via presets. See config.md for preset examples.

For protocol internals, TLS notes, and edge proxy patterns, see ../core/protocols/protocols.md.