Dockerfile,
Railway, EC2, ECS, Vercel, or another ASGI-capable host.
Runtime environment
1
Deploy the app
Deploy this repository using your hosting provider’s normal app workflow.
2
Configure your model provider
Add
LLM_PROVIDER as an environment variable (for example anthropic,
openai, openrouter, or gemini).3
Add the matching provider API key
Use the API key that matches your provider:
ANTHROPIC_API_KEYforLLM_PROVIDER=anthropicOPENAI_API_KEYforLLM_PROVIDER=openaiOPENROUTER_API_KEYforLLM_PROVIDER=openrouterDEEPSEEK_API_KEYforLLM_PROVIDER=deepseekGEMINI_API_KEYforLLM_PROVIDER=gemini
4
Add integration env vars and deploy
Add any storage and integration environment variables required by your runtime, then deploy and verify health.
.env.example.
Run local gateway
Use the built-in gateway command when you want a local HTTP server for investigations.
The web app binds
0.0.0.0 on the port from the PORT environment variable
(default 8000).
Quick local checks:
/investigate (like /alerts) accepts only loopback callers. Set
OPENSRE_ALERT_LISTENER_TOKEN to allow remote callers with a bearer token:
Railway deployment
Railway is still supported as a hosted runtime option. Before deploying on Railway, make sure your service has:DATABASE_URIpointing to your Railway Postgres instanceREDIS_URIpointing to your Railway Redis instance