Hoody — Computers That Are URLs

kit / daemon / hero

Process Management

Run Anything as a Service. Control It Over HTTPS.

Node, Python, Go, Rust, or any binary becomes a persistent, auto-restarting service. Start, stop, and watch it — all through HTTP, with no SSH and no unit files.

View Documentation

daemon-1.hoody.com

# Add a program

POST /api/v1/daemon/programs/add

["name":"server","command":"node server.js","boot":true]

# Response

["success":true,"id":2,"status":"RUNNING","pid":12345]

kit / daemon / services-grid

All Kit Services

The Daemon Service Manages Them All

Every Hoody Kit service — Terminal, Display, Files, SQLite, and 10 more — runs as a supervisord program you can start, stop, or restart via HTTP. (Illustrative: simulates supervisord status.)

RUNNING

Terminal

Shell sessions via HTTP + WebSocket

RUNNING

Display

Full desktops in your browser

RUNNING

Files

Filesystem as a REST API

RUNNING

Exec

Scripts become HTTP endpoints

RUNNING

SQLite

Databases queryable via HTTP

RUNNING

Browser

Chrome/Puppeteer automation

RUNNING

Agent

AI orchestration with 100+ tools

RUNNING

Code

VS Code instances in browser

RUNNING

cURL

REST calls as shareable GET URLs

RUNNING

Notifications

Push notifications via HTTP

BACKOFF

Daemon

Background process management

RUNNING

Cron

Scheduled task management

RUNNING

Pipe

Streaming data between containers

RUNNING

Watch

File and directory change monitoring

RUNNING

Workspaces

Multi-window desktop layouts

kit / daemon / lifecycle

Lifecycle

Every State, Every Transition

From creation to removal, each lifecycle step is a single HTTPS call — no SSH, no CLI, no host access required.

Launch a process via supervisorctl. Program must be enabled first.

daemon — start

# Enable then start

POST /api/v1/daemon/programs/{id}/enable

POST /api/v1/daemon/programs/{id}/start

{"wait":true,"timeout":30}

# Response

{"success":true,"status":"RUNNING","pid":12345}

kit / daemon / compare

vs Process Managers

Built for HTTP. Not for the Terminal.

systemd needs host access and unit files. PM2 is Node-only. Hoody Daemon is supervisord-backed and works with any binary over HTTPS.

Feature	Hoody Daemon	systemd	PM2
Works with any language / binary
HTTP API — no host access needed
Ephemeral Quick-Start programs
Auto-restart on crash
Boot priority ordering
Webhook on state change
Per-process user isolation
Log tailing via API

kit / daemon / endpoints

API Reference

18 Endpoints. One Consistent Interface.

Program management, process control, status monitoring, and ephemeral quick-start — all under the same base URL.

Program Management

6 endpoints

POST /api/v1/daemon/programs/add

GET

/programsList all programs

GET

/programs/{id}Get program details

POST

/programs/addRegister a new program

POST

/programs/edit/{id}Update program config

POST

/programs/remove/{id}Remove a program

POST

/programs/resetReset all programs

Quick Start

5 endpoints

POST /api/v1/daemon/quick-start

GET

/quick-startList quick-start programs

POST

/quick-startCreate ephemeral program

GET

/quick-start/{id}/statusGet quick-start status

GET

/quick-start/{id}/logsTail quick-start logs

POST

/quick-start/{id}/stopStop quick-start program

Process Control

4 endpoints

POST /api/v1/daemon/programs/{id}/start

POST

/programs/{id}/enableEnable program

POST

/programs/{id}/disableDisable program

POST

/programs/{id}/startStart process

POST

/programs/{id}/stopStop process

Status & Monitoring

3 endpoints

GET /api/v1/daemon/status

GET

/statusStatus of all programs

GET

/status/{id}Status of one program

GET

/programs/{id}/logsTail process logs

kit / daemon / cta

Your Crash-Loop Retries, Auditable Over HTTP.

Add a program, point it at any binary, set a boot priority. supervisord does the supervising — you just POST.

Read the Docs