Deploy Seq | (Just Updated) Structured Log Server with API Key & Login Preset, Data Survives Redeploys
Seq structured log server: ingest, search and query logs over HTTP
Just deployed
/data
Deploy and Host Seq on Railway
Built for an LLM agent to deploy and use. There is no setup page to open: the admin login and one API key are created from generated variables on first boot, and the contract below lists every address, variable name and one script that ships a structured log event, reads it back and filters it.
Seq is a structured log server from Datalust. Applications send log events to it over HTTP (the CLEF format, or through the Serilog, NLog, Microsoft.Extensions.Logging, Pino, Winston and OpenTelemetry integrations), and Seq indexes the properties of every event so they can be searched with a query language, charted and alerted on.
About Hosting Seq
This template runs one service: the official Datalust Seq 2026.1 image in a small wrapper, pinned by digest, with a volume on /data. The volume holds the event store, the users and the API keys, so logs and settings survive redeploys. The wrapper accepts the Seq licence agreement for you (deploying this template is that acceptance), listens on Railway's injected PORT on IPv4 and IPv6, and seeds the admin user and an API key named railway-agent (Ingest, Read and Write permissions) from the two generated variables before the server is reachable by anything else. A redeploy keeps the existing user and key.
Seq is free for a single user. If you add more users, you need a licence from Datalust.
Agent contract
- Public URL:
SEQ_PUBLIC_URL(https://plus the service'sRAILWAY_PUBLIC_DOMAIN). The web UI is at/, the HTTP API under/api. - Private URL:
SEQ_PRIVATE_URL(http://seq.railway.internal:8080). - Credentials:
SEQ_API_KEY(ingest and query),SEQ_ADMIN_PASSWORD(useradmin, web UI). - Auth: API clients send the header
X-Seq-ApiKey: $SEQ_API_KEY. The web UI uses the login form with useradmin. - Health:
GET /apireturns 200 without credentials. - API:
POST /ingest/clefto write events,GET /api/eventswith thefilter,countandrenderquery parameters to read them.
# run from any service in the project that has curl, with these variables set:
# SEQ_PRIVATE_URL SEQ_API_KEY
U="$SEQ_PRIVATE_URL"; K="X-Seq-ApiKey: $SEQ_API_KEY"
curl -s -o /dev/null -w "health: %{http_code}\n" "$U/api"
curl -s -o /dev/null -w "no key: %{http_code}\n" "$U/api/events?count=1"
curl -s -o /dev/null -w "ingest without key: %{http_code}\n" -X POST "$U/ingest/clef" -H 'Content-Type: application/vnd.serilog.clef' --data '{"@mt":"anonymous"}'
curl -s -o /dev/null -w "ingest: %{http_code}\n" -X POST "$U/ingest/clef" -H "$K" -H 'Content-Type: application/vnd.serilog.clef' \
--data '{"@t":"2026-01-01T00:00:00Z","@mt":"Agent {Name} shipped {Count} events","Name":"demo","Count":3}'
sleep 3
curl -s -G -H "$K" "$U/api/events" --data-urlencode "count=5" --data-urlencode "render=true" --data-urlencode "filter=Count = 3" | grep -o '"RenderedMessage":"[^"]*"'
A fresh deploy prints health: 200, no key: 401, ingest without key: 401, ingest: 201 and the line "RenderedMessage":"Agent demo shipped 3 events".
To use it from your own service, send events to SEQ_PRIVATE_URL with the X-Seq-ApiKey header: in Serilog set .WriteTo.Seq(serverUrl, apiKey: key), in Node use pino-seq or winston-seq, or point an OpenTelemetry exporter at $SEQ_PRIVATE_URL/ingest/otlp.
Why Deploy Seq 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 Seq 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.
- Agent-ready - a generated login, a generated API key, a contract block and one working script; nothing to type into the deploy form.
- Locked from boot - writing and reading events both need the key, and the key exists before the first request is served.
- State survives redeploys - events, users and keys live on a volume, and the image is pinned by digest.
- Private-network ingest - services in the same project send logs over
seq.railway.internalwithout leaving Railway.
Common Use Cases
- Central application logs - one place to search structured logs from every service in a Railway project.
- Agent debugging - a coding agent ships events from the app it is building and queries them back by property to find a failing request.
- Trace and OpenTelemetry sink - receive OTLP logs and traces from instrumented services and inspect them in the Seq UI.
Dependencies for Seq Hosting
- One Railway volume on
/data, created by the template.
Deployment Dependencies
Implementation Details
| Variable | Purpose |
|---|---|
SEQ_ADMIN_PASSWORD | Password of the admin user for the web UI. Generated per deploy. |
SEQ_API_KEY | API key with Ingest, Read and Write permissions. Generated per deploy. |
SEQ_PUBLIC_URL | HTTPS address of the web UI and API. |
SEQ_PRIVATE_URL | Address of Seq on the private network. |
The image entrypoint starts Seq on the loopback first, logs in as admin, creates the API key if it is missing, stops Seq and then starts it again on the public listen address.
Template Content

