Deploy and Host AgentHook

AgentHook is a single-tenant operator console for receiving webhooks, filtering noise, storing a storyboard, and forwarding useful events to downstream tools.

About Hosting AgentHook

This Railway template deploys the AgentHook service from the connected GitHub repository using the included Dockerfile. It is intended for one partner or customer tenant per Railway project.

Why Deploy AgentHook

Use AgentHook when teams need a private control layer in front of noisy webhooks, partner integrations, and internal automations. In single-tenant mode, setup-token login replaces ScaleKit and public registration stays disabled by default.

Common Use Cases

• Filter low-value heartbeat or status events before they reach expensive automation systems.
• Store webhook history in Storyboard for audit, replay, and reclassification.
• Route high-signal events to OpenClaw, Slack, CRMs, Telegram, or custom HTTP endpoints.
• Give a partner a private console on their own Railway deployment and custom domain.

Dependencies for AgentHook

You must provide durable MySQL/TiDB storage and partner-specific public URL settings. PUBLIC_BASE_URL should be the partner custom domain, not the temporary Railway-generated domain.

Deployment Dependencies

• PUBLIC_BASE_URL: partner custom domain, for example https://hooks.example.com
• COMMERCE_MYSQL_DSN: durable MySQL/TiDB connection string
• APP_SESSION_SECRET: random high-entropy session secret
• SINGLE_TENANT_OWNER_EMAIL: owner email for the first operator account
• SINGLE_TENANT_OWNER_ALIAS: stable alias used in listener identities
• SINGLE_TENANT_SETUP_TOKEN_SHA256: SHA-256 hash of the setup token

Defaults include APP_DEPLOYMENT_MODE=single_tenant, APP_PLAN=enterprise, ALLOW_PUBLIC_REGISTRATION=false, and ScaleKit variables are intentionally omitted.