Deploy OpenLIT

OpenTelemetry LLM observability: OpenLIT, ClickHouse, NATS, secure gateway

Deploy OpenLIT

Just deployed

/var/lib/clickhouse

/data

/app/client/data

Deploy and Host OpenLIT on Railway

OpenLIT is an open-source, OpenTelemetry-native observability platform for generative AI. It collects traces, metrics and costs from LLM calls, AI agents, vector databases and GPUs, and adds a prompt hub, a secrets vault, evaluations, realtime rules and an LLM playground. Apps send data with the OpenLIT SDKs or any OpenTelemetry exporter.

About Hosting OpenLIT

This template runs OpenLIT 2.1.1 as four Railway services built from one public GitHub repo, each pinned by version and digest. Gateway (Caddy) is the only public URL: it serves the UI and takes OTLP/HTTP data on /v1/traces, /v1/metrics and /v1/logs. OpenLIT runs the web UI, the OTLP receiver and the realtime engine, with users and settings in SQLite on a volume. ClickHouse stores telemetry on its own volume. NATS (JetStream, on a volume) carries realtime signals. All passwords are generated per deploy, self sign-up is closed, and OTLP ingest needs an OpenLIT API key.

Common Use Cases

  • Trace LLM and agent calls (OpenAI, Anthropic, LangChain, LlamaIndex, CrewAI and more) with tokens, latency and cost per request
  • Manage prompts and API secrets centrally, and run evaluations and guardrails on model output
  • Watch GPU and vector-database usage next to your application traces, with realtime alert rules

Dependencies for OpenLIT Hosting

  • ClickHouse (included, on a Railway volume)
  • NATS with JetStream (included, on a Railway volume)

Deployment Dependencies

Implementation Details

After the deploy finishes, open the Gateway's URL and sign in as user@openlit.io with the password in the OpenLIT service's OPENLIT_ADMIN_PASSWORD variable. Create an API key in Settings → API Keys, then point your app at the Gateway:

export OTEL_EXPORTER_OTLP_ENDPOINT="https://YOUR-GATEWAY-DOMAIN"
export OTEL_EXPORTER_OTLP_HEADERS="Authorization=Bearer YOUR-OPENLIT-API-KEY"

Services in the same Railway project can send to http://openlit.railway.internal:4318 (HTTP) or port 4317 (gRPC) with the same key. Optional settings: ALLOW_SIGNUP=true on Gateway opens self sign-up (for adding teammates), and GOOGLE_CLIENT_ID/GOOGLE_CLIENT_SECRET or GITHUB_CLIENT_ID/GITHUB_CLIENT_SECRET on OpenLIT enable OAuth sign-in. Updates: when the repo's pinned versions are bumped, Railway shows an update notice on your project; read the repo's CHANGELOG.md, then apply it. Volumes are kept, and OpenLIT runs its own migrations on start.

Why Deploy OpenLIT 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 OpenLIT 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.


Template Content

More templates in this category

View Template
Rootprint
Open-source logs and traces with full-text search on object-storage.

Rootprint
1
View Template
Pyroscope profiling
Protected continuous profiling with durable Pyroscope storage.

Anton Orel
1
View Template
SigOnly
Deploy SigNoz with a working demo app & config in one click

zoeyjones
21