Deploy and Host SigLens Log Analytics on Railway

Query logs and traces with durable storage and private ingestion.

Draft status: Configuration and upstream documentation reviewed. Container startup, Railway application workflows, restart behavior, backup restoration and costs remain unverified.

About Hosting

Query logs and traces with durable storage and private ingestion.

Service	Role	Persistent path
`app`	Private application or dependency	`/siglens/data`
`siglens`	Public owner gateway	`None`

Why Deploy

Run this application in your own Railway project, with explicit configuration and storage under your control.

Common Use Cases

Query logs and traces with durable storage and private ingestion.

Dependencies for SigLens Log Analytics

Deployment Dependencies

The application images are pinned by registry digest. Database services, when included, stay on the private network. One replica is supported for each volume-backed service.

First use

Open the siglens service's HTTPS domain. Sign in to the owner gateway with username admin and its generated ACCESS_PASSWORD. Complete the application's own setup afterward.

API calls must also send X-Template-Key with that owner password. The gateway forwards native Bearer tokens, strips Basic Authorization, and limits requests to 32 MiB. Browser sessions receive a secure owner cookie. Native clients, webhooks and public sharing require specific compatibility checks before use. Gateway /healthz only checks the proxy, not application readiness.

Sign into the protected query UI. Configure application log shippers in this project to use the app private domain on port 8081; the OTLP trace endpoint is /otlp/v1/traces.

Scope and limitations

Only the query UI is routed publicly; ingestion on port 8081 stays private.
Seven-day retention is configured. Size memory and disk for ingestion volume; this is a single-node service.
The template does not include a metrics collector or automatically collect other Railway services.

Acceptance checks before use

Ingest a known structured log through the private listener and find it in the UI.
Restart and verify the log and saved state survive.
Confirm generated credentials are distinct on a second fresh deployment.
Back up every listed persistent path and database, then restore into a separate test project.
Measure Railway usage with representative data and workload before estimating operating costs.

Backups and upgrades

Back up databases, file volumes, encryption keys and configuration together. Keep a copy outside the running project. Review upstream migration notes before changing a digest; rollback can require restoring a compatible database and files, not just selecting an older image.

Sources and selection evidence

Upstream documentation: Source specifies query and ingestion listeners, dataPath, retentionHours and stable ssInstanceName.
Upstream documentation: Official image working directory is /siglens; binary /siglens/siglens.
Upstream documentation: Query/UI port 5122 and ingestion port 8081 are distinct.
Upstream project

Product and alias searches found no matching public Railway listing during this research. This is a bounded search result; private, unindexed or differently named listings may exist. It is not evidence of demand or revenue.

Upstream software retains its own license and edition restrictions. This deployment draft does not imply upstream endorsement.