How do I deploy incident-response on Railway?

You can deploy incident-response on Railway by clicking the "Deploy Now" button on this page. Railway will automatically set up all the necessary services and configurations for you.

What are the system requirements?

Railway handles all the infrastructure requirements. You only need a web browser to deploy and manage your application.

Is this template free to use?

Yes, this template is free to use within your existing Railway account.

Can I customize this template?

Yes, you can fully customize this template. After deployment, you will have full control of what you've deployed in your Railway project.

How do I get support for this template?

You can get support through our community forum: incident-response-b44975a9, or join our Discord community for more assistance.

Deploy and Host incident-response on Railway

Incident-response is an AI-powered incident response and log analysis service for Railway. It monitors your Railway services, detects issues from logs, analyzes them with LLMs, and posts actionable Slack alerts with recommended remediations. For more detailed setup guide, visit this guide for a section walkthrough.

About Hosting incident-response

This template deploys a Phoenix/Elixir service with an attached Postgres database on Railway. It streams Railway logs, processes incidents with OpenAI (optionally Anthropic), and integrates with Slack for alerts and remediation updates. Required env vars are limited to secrets (OpenAI, Slack, Railway API token, secret key base); Railway injects runtime metadata and database URL. Optional monitoring lists and tuning flags can be left unset—the code supplies sane defaults.

Common Use Cases

Real-time incident detection from Railway logs with AI summaries.
Slack alerting and remediation updates for service outages.
Monitoring multiple Railway projects/environments from one agent.

Dependencies for incident-response Hosting

Railway Postgres addon (DATABASE_URL is auto-injected).
Secrets: SECRET_KEY_BASE, RAILWAY_API_TOKEN, OPENAI_API_KEY, SLACK_BOT_TOKEN, SLACK_SIGNING_SECRET, SLACK_CHANNEL_ID.

Deployment Dependencies

Railway Postgres addon attached to the service.
Railway API token with project/environment read permissions.
Slack app with chat:write, channels:read, users:read scopes; bot token, signing secret, and target channel ID.

Implementation Details (Optional)

Phoenix/Elixir app; release command runs RailwayApp.Release.migrate then starts the server.
Defaults: PHX_SERVER=true, MIX_ENV=prod; PHX_HOST falls back to RAILWAY_PUBLIC_DOMAIN.
Optional monitoring config: RAILWAY_MONITORED_PROJECTS, RAILWAY_MONITORED_ENVIRONMENTS, RAILWAY_MONITORED_SERVICES.
Optional tuning vars (RAILWAY_POLLING_INTERVAL, retries/backoff, rate limits, batch settings, endpoints) have safe code defaults.

Why Deploy incident-response 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 incident-response 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.