---
title: "Deploy tindra"
description: "Deploy and Host Tindra on Railway"
category: "Observability"
url: https://railway.com/deploy/tindra
---

# Deploy tindra

Deploy and Host Tindra on Railway

**[Deploy tindra on Railway](https://railway.com/template/tindra)**

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

- **Creator:** Tom
- **Category:** Observability

## Template content

### tindra-setup

- **Source:** https://github.com/monotykamary/railway-template-tindra

### postgres

- **Image:** postgres:18-alpine

### tindra

- **Image:** ghcr.io/blendbyte/tindra:0.6.4
- **Health check:** /healthz
- **Public domain:** Yes

## Documentation

# Deploy and Host Tindra on Railway

## About Hosting Tindra

Tindra is a self-hosted error tracking, performance monitoring, profiling, uptime monitoring, and cron monitoring platform with full Sentry SDK compatibility. This template deploys the stable release `0.6.4` as a single Go binary backed by PostgreSQL 18, with persistent volumes for the database and uploaded source maps.

## Common Use Cases

- Capture exceptions from any Sentry SDK by pointing the DSN at your private Tindra instance
- Monitor API latency with transaction traces, span waterfalls, and p50/p75/p95/p99 percentiles
- Profile slow transactions with flame graphs from Sentry SDK profiling
- Probe HTTP/HTTPS endpoints for uptime with status-code and body assertions, and get down/recovery alerts
- Monitor scheduled jobs with cron check-ins and missed/error alerts
- Alert teams through email, Slack, Discord, Microsoft Teams, or webhooks

## Dependencies for Tindra Hosting

### Deployment Dependencies

The template creates three Railway resources: the public `tindra` service, a PostgreSQL `18-alpine` service, and a one-shot `tindra-setup` service that creates the first administrator. Tindra owns a persistent volume at `/data` for source maps; Postgres owns a persistent data volume. There is no Redis, no queue, and no separate worker — all background jobs run inside the Tindra process.

### Implementation Details

The `tindra` service owns the public HTTPS domain and listens on port 8080. `DATABASE_URL` references Postgres over Railway private networking with a generated password. Tindra runs database migrations automatically at startup, so the schema is always current on deploy.

The first administrator is created by `tindra-setup`, which runs the official Tindra CLI once and stops. Fill in `SETUP_ADMIN_EMAIL` and `SETUP_ADMIN_PASSWORD` (minimum 12 characters) when deploying — the template prompts for them. The service exits successfully after creating the administrator (or if the administrator already exists on a later redeploy), and can be deleted after your first login. First login requires MFA setup by default (`REQUIRE_MFA=true`).

Generated variables: `POSTGRES_PASSWORD` for the database, `PUBLIC_URL` wired to `https://` plus the Railway public domain (used to build project DSNs), and `COOKIE_SECURE=true` for HTTPS-only cookies. `PUBLIC_URL` must match the domain users actually visit or DSNs generated in the dashboard will point at the wrong host.

Do not change cross-service references independently — `DATABASE_URL` is wired to the Postgres private hostname and the generated `POSTGRES_PASSWORD`.

### Why Deploy Tindra on Railway?

Railway provides the public HTTPS endpoint your Sentry SDKs and cron check-ins need, private networking for the database, durable volumes for source maps, and one-click redeploys — all for a two-service stack that starts in seconds and needs no orchestrator.

## Limitations

- Email alerts require an external provider credential; without one, webhook, Slack, Discord, and Teams alerts still work.
- SSO requires provider credentials and a correctly set `OAUTH_REDIRECT_BASE`.
- Source maps persist on the `tindra` volume; deleting that volume loses stack-trace resolution for previously uploaded maps.
- The version-update check contacts `tindra.sh` every 6 hours unless `DISABLE_VERSION_CHECK=true`.
- Tindra is Elastic License 2.0 software: self-hosting is free, but offering it to third parties as a managed service is prohibited.


## Similar templates

- [Pyroscope profiling](https://railway.com/deploy/pyroscope-profiling) — Protected continuous profiling with durable Pyroscope storage.
- [SigOnly](https://railway.com/deploy/sigonly) — Deploy SigNoz with a working demo app & config in one click
- [Unwrapped Spotify Music Stats](https://railway.com/deploy/wide-bold) — Unwrapped Spotify Music Stats, Estatísticas de músicas disponíveis

Open this page in a browser: https://railway.com/deploy/tindra