---
title: "Deploy Latitude"
description: "Open-source observability for AI agents: traces, evals, API and MCP server"
category: "AI/ML"
url: https://railway.com/deploy/latitude-2
---

# Deploy Latitude

Open-source observability for AI agents: traces, evals, API and MCP server

**[Deploy Latitude on Railway](https://railway.com/template/latitude-2)**

Machine-readable deploy manifest (JSON, validated by TemplateCI): https://railway.com/deploy/latitude-2/manifest.json

- **Creator:** Agaz Self-Host
- **Category:** AI/ML

## Template content

### Web https://raw.githubusercontent.com/latitude-dev/latitude-llm/v0.3.126/apps/web/public/latitude-icon.png

- **Source:** https://github.com/aalfath/latitude-railway-template
- **Health check:** /api/health
- **Public domain:** Yes

### Ingest https://raw.githubusercontent.com/latitude-dev/latitude-llm/v0.3.126/apps/web/public/latitude-icon.png

- **Source:** https://github.com/aalfath/latitude-railway-template
- **Health check:** /health
- **Public domain:** Yes

### Redis https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons/png/redis.png

- **Source:** https://github.com/aalfath/latitude-railway-template

### Migrations https://raw.githubusercontent.com/latitude-dev/latitude-llm/v0.3.126/apps/web/public/latitude-icon.png

- **Source:** https://github.com/aalfath/latitude-railway-template
- **Health check:** /health

### Workflows https://raw.githubusercontent.com/latitude-dev/latitude-llm/v0.3.126/apps/web/public/latitude-icon.png

- **Source:** https://github.com/aalfath/latitude-railway-template
- **Health check:** /health

### Temporal https://raw.githubusercontent.com/temporalio/ui/f30ce6f0211bd3985d0b37b7d1c3fdf27f5c9e92/src/lib/vendor/logo.svg

- **Source:** https://github.com/aalfath/latitude-railway-template
- **Health check:** /api/v1/namespaces/default

### API https://raw.githubusercontent.com/latitude-dev/latitude-llm/v0.3.126/apps/web/public/latitude-icon.png

- **Source:** https://github.com/aalfath/latitude-railway-template
- **Health check:** /health
- **Public domain:** Yes

### Postgres https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons/png/postgres.png

- **Source:** https://github.com/aalfath/latitude-railway-template

### Workers https://raw.githubusercontent.com/latitude-dev/latitude-llm/v0.3.126/apps/web/public/latitude-icon.png

- **Source:** https://github.com/aalfath/latitude-railway-template
- **Health check:** /health

### ClickHouse https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons/png/clickhouse.png

- **Source:** https://github.com/aalfath/latitude-railway-template
- **Health check:** /ping

### SeaweedFS https://raw.githubusercontent.com/seaweedfs/seaweedfs/4.54/note/seaweedfs.png

- **Source:** https://github.com/aalfath/latitude-railway-template

## Documentation

# Deploy and Host Latitude on Railway

Latitude is an open-source (MIT) observability platform for AI agents. It ingests OpenTelemetry traces from your agents and LLM apps, groups them into sessions, flags where agents fail, runs evaluations against real traces, and exposes everything through a web UI, a REST API and an MCP server that coding agents can query.

## About Hosting Latitude

This template deploys Latitude 0.3.126 with upstream's full single-host stack: web UI, API, OTLP ingest, background workers, Temporal workflow workers and a migrations service, backed by Postgres with pgvector, ClickHouse, Redis, Temporal and a SeaweedFS S3 store. Every service builds from a public GitHub repo that pins the official images by version and digest, so Railway notifies you when a new version is merged. Data lives on volumes. Passwords and keys are generated for each deployment, and there's nothing to fill in. Sign-in links are printed to the Workers logs until you add SMTP. It needs a Hobby plan or higher.

## Common Use Cases

* Trace production AI agents: spans, tool calls, cost, latency and sessions from any OpenTelemetry-compatible framework
* Find and group recurring agent failures, then verify fixes against real traces
* Build datasets from traces and run evaluations, or let coding agents query traces through the MCP server

## Dependencies for Latitude Hosting

* Postgres 16 with pgvector, ClickHouse, Redis, Temporal and SeaweedFS, all included
* Optional: an SMTP or Mailgun account for email, and AI provider keys for evaluations and semantic search

### Deployment Dependencies

* [Latitude on GitHub](https://github.com/latitude-dev/latitude-llm) and its [v0.3.126 release](https://github.com/latitude-dev/latitude-llm/releases/tag/v0.3.126)
* [Single-host self-hosting guide](https://docs.latitude.so/deployment/single-host) and [configuration reference](https://docs.latitude.so/deployment/configuration)
* [Template source: aalfath/latitude-railway-template](https://github.com/aalfath/latitude-railway-template)

### Implementation Details

**First login (no email provider needed):**

1. Wait until every service is green. The first boot takes a few minutes while the Migrations service prepares Postgres and ClickHouse, and the app services wait for it.
2. Open the **Web** domain and enter your email address.
3. Open the **Workers** service, then its latest deployment's logs, and find the block that starts with `===== EMAIL`. Open the `Link:` it shows to finish signing in. Only members of your Railway project can read these logs.
4. Create your organization and project, then an API key. Send traces to the **Ingest** domain. The API and the MCP server (`/v1/mcp`) are on the **API** domain.

**Email:** to send real email, set these on the **Workers** service and redeploy it: `LAT_SMTP_HOST`, `LAT_SMTP_PORT`, `LAT_SMTP_USER`, `LAT_SMTP_PASS` and `LAT_SMTP_FROM`, or `LAT_MAILGUN_API_KEY`, `LAT_MAILGUN_DOMAIN` and `LAT_MAILGUN_FROM`. The log printer then switches off by itself.

**Who can sign up:** anyone who can reach the Web domain can register. To limit sign-up to your company, set `LAT_ALLOWED_EMAIL_DOMAIN=YOUR-COMPANY.com` on the **Web** service. The API's unauthenticated account bootstrap route (`POST /v1/account/bootstrap`) is blocked unless you set `LAT_ALLOW_ACCOUNT_BOOTSTRAP=true` on the **API** service.

**AI features** such as evaluations and semantic search need provider keys (for example `LAT_OPENAI_API_KEY` or `LAT_VOYAGE_API_KEY`) and `LAT_AI_*` model settings on Web, API, Workers and Workflows. See the configuration reference. Choose the embedding model once, because it can't be changed later.

**Custom domain:** if you move Web, API or Ingest to your own domain, update `LAT_WEB_URL`, `LAT_API_URL` or `LAT_INGEST_URL` on all five app services.

**Updates:** when a new Latitude release is merged into the template repo, Railway shows an update notice. Its changelog lists breaking changes first. When you apply the update, the Migrations service migrates the databases before the app services restart. Back up the Postgres and ClickHouse volumes before large upgrades.

## Why Deploy Latitude 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 Latitude 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.



## Similar templates

- [Chat Chat](https://railway.com/deploy/-WWW5r) — Chat Chat, your own unified chat and search to AI platform.
- [Weaviate](https://railway.com/deploy/weaviate-1) — Vector database with hybrid search and an API key-protected API
- [Möbius Personal AI OS](https://railway.com/deploy/mobius-v01-personal-ai-os) — Self-hosted AI agent that builds and runs apps for you, with memory.

Open this page in a browser: https://railway.com/deploy/latitude-2
