---
title: "Deploy daring-analysis"
description: "Single-tenant AgentHook with Railway MySQL and ongoing admin-secret login."
category: "Other"
url: https://railway.com/deploy/daring-analysis-3
---

# Deploy daring-analysis

Single-tenant AgentHook with Railway MySQL and ongoing admin-secret login.

**[Deploy daring-analysis on Railway](https://railway.com/template/daring-analysis-3)**

- **Creator:** abhinaviitg18's Projects
- **Category:** Other
- **Total deploys:** 2

## Template content

### MySQL

- **Image:** mysql:9.4
- **Start command:** `docker-entrypoint.sh mysqld --innodb-use-native-aio=0 --disable-log-bin --performance_schema=0 --innodb-buffer-pool-size=1G`

### agenthook

- **Source:** https://github.com/abhinaviitg18/webhook_listener
- **Public domain:** Yes

## Documentation

# Deploy and Host AgentHook

Deploy AgentHook as a private, single-tenant operator console with a managed Railway MySQL service.

## About Hosting

This template creates two services: `agenthook` and `MySQL`. Enter only `SINGLE_TENANT_OWNER_EMAIL`; Railway generates `MYSQL_ROOT_PASSWORD`, wires AgentHook to the private MySQL service, and exposes that generated value to AgentHook as `SINGLE_TENANT_ADMIN_SECRET`. On first boot AgentHook creates the `railway` database if needed and runs embedded schema migrations.

## Why Deploy

AgentHook gives a partner-owned Railway workspace a private webhook listener, API-token console, listener management, event storyboard, and durable MySQL-backed storage without requiring ScaleKit or the hosted multi-tenant landing flow.

## Common Use Cases

- Deploy a private webhook intake service for a partner or customer environment.
- Generate API tokens and listener secrets from a single owner console.
- Receive webhook events on the Railway or partner custom domain and inspect them in Storyboard.
- Keep data persistent across redeploys using the bundled Railway MySQL volume.

## Dependencies for AgentHook

AgentHook depends on a MySQL-compatible database. This template includes a MySQL service by default and wires `COMMERCE_MYSQL_DSN` internally, so installers do not need to enter database host, port, user, password, or database values.

### Deployment Dependencies

The only required installer value is `SINGLE_TENANT_OWNER_EMAIL`. After deployment, open the `agenthook` service variables, copy `SINGLE_TENANT_ADMIN_SECRET`, open the deployed service URL, and enter the secret to log in as owner. The default template maps this to the generated MySQL root password so Railway can keep the setup one-field; rotate `SINGLE_TENANT_ADMIN_SECRET` after deployment if you want a separate app-login secret. For partner installs, add a custom domain in Railway and optionally set `PUBLIC_BASE_URL=https://your-domain.example` after deployment so generated webhook examples use the partner domain. Do not enable `USE_IN_MEMORY_STORE=true` for production because that mode is demo-only and non-persistent.


## Similar templates

- [Rocky Linux](https://railway.com/deploy/rocky-linux) — Hosted Rocky Linux 9 workspace with SSH and persistent storage. 🚀
- [Foundry Virtual Tabletop](https://railway.com/deploy/X5tR6G) — A Self-Hosted & Modern Roleplaying Platform
- [Letta Code Remote](https://railway.com/deploy/letta-code-remote) — Run a Letta Code agent 24/7. No inbound ports, just deploy.

Open this page in a browser: https://railway.com/deploy/daring-analysis-3