Stork Agent

Agent communication fabric.

StorkAgent connects humans, phones, hosted deploys, and AI agents through a relay and gateway architecture built for private agent workflows.

Read the docs mapUse Hatch hosted
storkagent.system
user phone
  -> stork relay
    -> gateway
      -> agent runtime

hatch
  -> provisions gateway
  -> issues setup QR
  -> hands control to user

System map

Four surfaces. One protocol story.

StorkAgent.com should explain how the pieces fit, where trust boundaries sit, and which path to use when you want hosted convenience versus operational control.

Relay

Routes encrypted agent and mobile traffic without becoming the product brain.

Accounts, rooms, pairing, delivery, and entitlement boundaries.

Gateway

Runs beside the agent and bridges local runtime tools to the relay.

Provider adapters, media boundaries, runtime sessions, and setup QR issuance.

Mobile

The user's control plane for setup, identity, notifications, and chat.

Pairing, restore flows, room access, and agent presence.

Hatch

The hosted deployment path for people who do not want to operate the stack.

Provisioning, setup flow, managed instances, and subscription surface.

Docs map

Documentation should follow the work.

Start

Install, pair, deploy, and verify a local or hosted StorkAgent setup.

Architecture

Relay, gateway, mobile, Hatch, identity, pairing, and trust boundaries.

Operate

Deployment status, diagnostics, destroy flow, logs, and failure recovery.

Build

Provider interfaces, protocol contracts, media handling, and app integration points.

Design principles

Technical trust belongs on this site.

  • User-owned identity, not platform-owned lock-in.
  • Agents receive scoped access, not master recovery material.
  • The relay moves encrypted traffic; it should not need message content.
  • Hosted convenience through Hatch without hiding the self-hosted path.

Hosted path

Hatch is the product door.

Keep StorkAgent technical. Send non-operators to Hatch when they want signup, deployment, setup QR, and instance management instead of docs and CLI workflows.

Use Hatch when the goal is a running agent.

Hatch packages the hosted setup flow around StorkAgent without replacing the underlying architecture story.

Open Hatch