No terminal
Account, AI access, deployment, and pairing all happen in a browser flow.
Hatch web service
Your own AI Agentic computing Without the technical need
Agentic computing is artificial intelligence where agents act as autonomous digital workers that plan, use tools, and complete multi-step tasks by themselves to achieve a specific goal without constant human instruction.
Hatch is the simple way to get a private Stork agent running. Create an account, choose how it should access AI, click deploy, scan the QR code, and chat from your phone.
hatch.storkagent.com
Name
Email
ChatGPT profile
OpenAI key
Anthropic key
Setup QR ready
Hosted agent setup
Hatch turns StorkAgent into a service.
No server chores
Hatch creates the machine, installs the stack, starts services, and tracks deployment state.
Phone-ready
When the agent is live, Hatch shows the setup QR. Scan it with Stork and start chatting.
The path
Three moments. One working agent.
Sign up
Create the account and choose how the agent should access AI.
Deploy
Hatch provisions the agent machine and installs the StorkAgent stack.
Pair
Scan the setup QR from Stork mobile and talk to your agent from your phone.
Trust boundary
The setup QR is for pairing. It is not your recovery phrase.
Short-lived setup codes
Gateway-owned pairing state
Technical proof on storkagent.com
Choose your path
Hosted if you want the result. Docs if you want the machinery.
Hatch hosted
Managed deployment
Use Hatch when you want the private agent running without operating the stack yourself.
Start with HatchStorkAgent docs
Self-host and build
Use storkagent.com for architecture, CLI workflows, protocol details, and self-hosting.
Read the docsFor technical users
The CLI stays for builders and operators.
Hatch web is for people who want the result. Hatch CLI and Stork CLI are for builders who want control, diagnostics, scripting, and direct instance management.
- Web service: signup, mock subscription, deploy, scan, manage
- Hatch CLI: operator setup, deploy diagnostics, doctor checks
- Stork CLI: technical workflows and direct control
- Same stack underneath, different surface for each audience
Before you deploy
Short answers.
Do I need to know servers?
No. Hatch exists so setup feels like a hosted service, not a cloud project.
Is Hatch the same as StorkAgent?
No. StorkAgent is the broader communication stack. Hatch is the hosted deployment path.
Can I self-host instead?
Yes. The CLI and docs path stays for builders, operators, and self-hosters.
Where do the docs live?
storkagent.com is the docs and ecosystem site. Hatch links there for the technical path.
StorkAgent ecosystem
Hatch is the front door. StorkAgent is the system behind it.
Keep Hatch focused on hosted setup. Let storkagent.com carry architecture, self-hosting, protocol details, and builder workflows.