Deploy and Host Zyk on Railway

Zyk is Claude-native workflow automation. Describe what you want in conversation, Claude generates real TypeScript and deploys it as a durable workflow — with retries, scheduling, and human-in-the-loop built in. No node editors, no connectors to configure.

About Hosting Zyk

Zyk runs as three Railway services: the Zyk MCP Server, Hatchet Engine (durable workflow execution), and PostgreSQL. The MCP Server exposes a public HTTPS URL you paste into Claude — that's the only configuration needed on your end. Workflows are stored on a persistent volume and workers restart automatically on
crash or redeploy. Env vars for third-party APIs (Slack, GitHub, Anthropic) are added directly in the Railway dashboard and picked up automatically by
generated workflows.

Common Use Cases

Automate Slack notifications triggered by GitHub issues, with AI-assessed severity and human approval before posting
Build human-in-the-loop approval workflows that pause mid-execution, wait for a decision, and resume automatically
Schedule recurring reports, API monitors, or data pipelines that survive failures with automatic retries

Dependencies for Zyk Hosting

PostgreSQL (provisioned automatically by the template)
Hatchet Engine (provisioned automatically by the template)

Deployment Dependencies

Implementation Details

Workflows are plain TypeScript files stored on a persistent volume at /app/workflows. Each workflow runs as a child process that connects to Hatchet via
gRPC on port 7077. Trigger workflows via Claude, on a cron schedule, or via webhook.

Why Deploy Zyk on Railway?

Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.

By deploying Zyk on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI
agents, and more on Railway.