Skip to content

Quick Start

Get a production-ready AI infrastructure stack deployed to Railway in under 5 minutes.

Prerequisites

  • A Railway account
  • API keys for your preferred LLM providers (OpenAI, Anthropic, etc.)

Choose Your Template

Option 1: LiteLLM + Langfuse Starter

Best for: Getting started quickly, development, small teams.

Includes:

  • LiteLLM proxy (unified LLM API)
  • Langfuse (observability & tracing)
  • PostgreSQL database

Deploy:

Deploy on Railway

Option 2: LiteLLM + Langfuse Production

Best for: Production workloads, enterprise teams.

Includes everything in Starter, plus:

  • Automated daily backups
  • Health monitoring & alerts
  • Redis with AOF persistence
  • Operations runbook

View Production Template →

Post-Deployment Setup

1. Configure Environment Variables

After deployment, configure these required variables in Railway:

# Required: Your LLM API keys
OPENAI_API_KEY=sk-...
ANTHROPIC_API_KEY=sk-ant-...

# Optional: Additional providers
AZURE_API_KEY=...
GOOGLE_API_KEY=...

2. Access Your Services

Once deployed, you'll have URLs for:

Service Purpose URL Pattern
LiteLLM LLM API Gateway https://litellm-xxx.railway.app
Langfuse Observability UI https://langfuse-xxx.railway.app

3. Test Your Setup

Test the LiteLLM proxy:

curl https://your-litellm-url.railway.app/health

Make your first request:

curl https://your-litellm-url.railway.app/v1/chat/completions \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_LITELLM_KEY" \
  -d '{
    "model": "gpt-4",
    "messages": [{"role": "user", "content": "Hello!"}]
  }'

4. View Traces in Langfuse

  1. Open your Langfuse URL
  2. Log in with the default credentials (check Railway variables)
  3. Navigate to Traces to see your requests

Next Steps

Troubleshooting

Common Issues

Service not starting:

  • Check Railway logs for errors
  • Verify all required environment variables are set

API requests failing:

  • Verify your LLM API keys are valid
  • Check the LiteLLM /health endpoint

Can't access Langfuse:

  • Ensure the Langfuse service has finished deploying
  • Check that PostgreSQL is healthy

Getting Help