Deploy Latitude
Open-source observability for AI agents: traces, evals, API and MCP server
Just deployed
Just deployed
Just deployed
/data
Migrations
Just deployed
Workflows
Just deployed
Just deployed
Just deployed
Just deployed
/var/lib/postgresql/data
Just deployed
ClickHouse
Just deployed
/var/lib/clickhouse
SeaweedFS
Just deployed
/data
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 and its v0.3.126 release
- Single-host self-hosting guide and configuration reference
- Template source: aalfath/latitude-railway-template
Implementation Details
First login (no email provider needed):
- 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.
- Open the Web domain and enter your email address.
- Open the Workers service, then its latest deployment's logs, and find the block that starts with
===== EMAIL. Open theLink:it shows to finish signing in. Only members of your Railway project can read these logs. - 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.
Template Content
Migrations
aalfath/latitude-railway-templateWorkflows
aalfath/latitude-railway-templateClickHouse
aalfath/latitude-railway-templateSeaweedFS
aalfath/latitude-railway-template

