NodeForEdge documentation

How the pieces of the lab fit together, and where to read about each one.

NodeForEdge is a personal infrastructure lab. A single VPS sits in the middle, a few inexpensive Android phones work as edge nodes around it, and a set of services turns that hardware into something useful: a phone line an AI can use, an agent that handles job applications, tool servers for AI clients, and a gateway to free language models.

This site explains how each part is built and why it was built that way. For what is running right now, open the status page.

The lab at a glance

   Android edge nodes                       VPS ("nodeforge")
 ┌────────────────────┐              ┌─────────────────────────────────┐
 │ A14  GSM gateway   │── tunnel ───▶│                                 │──▶ PhoneGate
 │ A51  dev node      │── tailnet ──▶│  Caddy  ·  Docker  ·  systemd   │──▶ JobHunter
 │ A06  MCP node      │── tailnet ──▶│  PostgreSQL  ·  Tailscale       │──▶ MCP services
 └────────────────────┘              │                                 │──▶ llmRouter API
                                     └─────────────────────────────────┘
        Browsers, AI clients and email reach the lab only through Caddy.

Where to start

Section	What you will find
PhoneGate	A rooted phone as a GSM gateway: calls, SMS, speech, and the security model around it.
JobHunter	The autonomous job-search agent: pipeline, safety rules and the phone agent.
Android Edge Nodes	The phones: what each one does and how they connect back to the VPS.
MCP Services	Tool servers that let AI clients operate the lab.
Infrastructure	The VPS, the web edge, the private network, and how monitoring works.
llmRouter	An OpenAI-compatible gateway that spreads requests across free model providers.
Crysis Coop	A small relay and update server for a game mod.

Conventions

Nothing secret appears here. Tokens, keys, internal addresses and ports are deliberately left out. Each section says where a secret lives and which boundary it protects, not what it is.
Safe by default. Anything that touches the outside world, such as sending email, answering a phone call or crawling a site, is off until an operator turns it on.
One way in. Public traffic enters through Caddy. Management traffic uses the private tailnet.