---
title: "Deploy Sazabi Log Forwarder"
description: "Send deploy and HTTP logs to Sazabi with zero code changes."
category: "Observability"
url: https://railway.com/deploy/sazabi-log-forwarder
---

# Deploy Sazabi Log Forwarder

Send deploy and HTTP logs to Sazabi with zero code changes.

**[Deploy Sazabi Log Forwarder on Railway](https://railway.com/template/sazabi-log-forwarder)**

Machine-readable deploy manifest (JSON, validated by TemplateCI): https://railway.com/deploy/sazabi-log-forwarder/manifest.json

- **Creator:** Sazabi
- **Category:** Observability

## Template content

### sazabi-forwarder

- **Image:** ghcr.io/sazabi/railway-forwarder:v0.1.0

## Documentation

# Deploy and Host Sazabi Log Forwarder on Railway

Sazabi Log Forwarder sends the deploy logs and HTTP logs of every service in your Railway environment to Sazabi, with no code changes. It runs as one extra service, reads logs from Railway's API, and forwards them to Sazabi over OpenTelemetry (OTLP/HTTP).

## About Hosting Sazabi Log Forwarder

Railway has no log drain, so the forwarder runs inside your project. It subscribes to deploy logs for the whole environment, including services you add later, and to HTTP logs for every service with a public domain. Each log carries service, environment, project, and deployment attributes. HTTP 5xx responses become errors and 4xx become warnings. The forwarder has no public networking and no volume. You need two values: the intake URL of a Sazabi Railway log source, and a Railway account token. An account token can read every project in your Railway account; the forwarder only reads its own environment.

## Common Use Cases

- Search and alert on the deploy logs of every Railway service in one place
- Track HTTP errors and slow requests across services with public domains
- Give Sazabi's AI the production logs it needs to investigate incidents

## Dependencies for Sazabi Log Forwarder Hosting

- A Sazabi account with a Railway log source (for the intake URL)
- A Railway account token

### Deployment Dependencies

- Setup guide: https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/railway
- Source: https://github.com/sazabi/railway-forwarder

### Implementation Details

The forwarder sends logs only. For traces, add the OpenTelemetry SDK to your app.

## Why Deploy Sazabi Log Forwarder 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 Sazabi Log Forwarder 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

- [Rootprint](https://railway.com/deploy/rootprint-1) — Open-source logs and traces with full-text search on object-storage.
- [VPS Fleet Watch Hub with Beszel](https://railway.com/deploy/vps-fleet-watch-hub-with-beszel) — A persistent Beszel hub for external VPS agents and fleet alerts.
- [Pyroscope profiling](https://railway.com/deploy/pyroscope-profiling) — Protected continuous profiling with durable Pyroscope storage.

Open this page in a browser: https://railway.com/deploy/sazabi-log-forwarder