---
title: "Deploy AiSOC"
description: "Open-source AI SOC: alert fusion, LLM triage, MITRE ATT&CK, cases"
category: "Observability"
url: https://railway.com/deploy/aisoc
---

# Deploy AiSOC

Open-source AI SOC: alert fusion, LLM triage, MITRE ATT&CK, cases

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

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

- **Creator:** Agaz Self-Host
- **Category:** Observability

## Template content

### web https://raw.githubusercontent.com/beenuar/AiSOC/main/apps/docs/static/img/favicon.png

- **Source:** https://github.com/aalfath/aisoc-railway-template
- **Health check:** /api/health
- **Public domain:** Yes

### actions https://raw.githubusercontent.com/beenuar/AiSOC/main/apps/docs/static/img/favicon.png

- **Source:** https://github.com/aalfath/aisoc-railway-template
- **Health check:** /readyz

### agents https://raw.githubusercontent.com/beenuar/AiSOC/main/apps/docs/static/img/favicon.png

- **Source:** https://github.com/aalfath/aisoc-railway-template
- **Health check:** /readyz

### realtime https://raw.githubusercontent.com/beenuar/AiSOC/main/apps/docs/static/img/favicon.png

- **Source:** https://github.com/aalfath/aisoc-railway-template
- **Health check:** /health

### Redis https://cdn.sanity.io/images/sy1jschh/production/0ce0bfdcfbdbf69662b1116671f97c2dd788b655-157x157.svg

- **Image:** redis:8.2
- **Start command:** `/bin/sh -c "rm -rf $RAILWAY_VOLUME_MOUNT_PATH/lost+found/ && exec docker-entrypoint.sh redis-server --requirepass $REDIS_PASSWORD --save 60 1 --dir $RAILWAY_VOLUME_MOUNT_PATH"`

### Postgres https://devicons.railway.app/i/postgresql.svg

- **Image:** ghcr.io/railwayapp-templates/postgres-ssl:18

### ingest https://raw.githubusercontent.com/beenuar/AiSOC/main/apps/docs/static/img/favicon.png

- **Source:** https://github.com/aalfath/aisoc-railway-template
- **Health check:** /readyz

### redpanda https://raw.githubusercontent.com/beenuar/AiSOC/main/apps/docs/static/img/favicon.png

- **Source:** https://github.com/aalfath/aisoc-railway-template
- **Health check:** /v1/status/ready

### api https://raw.githubusercontent.com/beenuar/AiSOC/main/apps/docs/static/img/favicon.png

- **Source:** https://github.com/aalfath/aisoc-railway-template
- **Health check:** /readyz

### fusion https://raw.githubusercontent.com/beenuar/AiSOC/main/apps/docs/static/img/favicon.png

- **Source:** https://github.com/aalfath/aisoc-railway-template
- **Health check:** /readyz

### connectors https://raw.githubusercontent.com/beenuar/AiSOC/main/apps/docs/static/img/favicon.png

- **Source:** https://github.com/aalfath/aisoc-railway-template
- **Health check:** /readyz

## Documentation

# Deploy and Host AiSOC on Railway

AiSOC is an open-source (MIT), self-hosted AI Security Operations Center. It ingests security telemetry, runs detection rules, fuses related alerts into incidents, triages them with AI agents whose every prompt and tool call is recorded in a replayable decision ledger, and maps findings to MITRE ATT&amp;CK. Analysts work cases in a web console.

## About Hosting AiSOC

AiSOC is a set of cooperating services: a FastAPI core API that owns the database schema, a Next.js console, an AI agents service, a realtime WebSocket gateway, an ingest gateway, alert fusion, connectors and response actions. They share PostgreSQL (with row-level security), Redis and a Kafka-compatible event bus. This template runs AiSOC v23.5.2 as nine services built from one GitHub repo plus Railway's PostgreSQL and Redis. On the first deploy the API applies all SQL migrations, sets the runtime database role's password and creates the first administrator with a generated password. Only the console is public; everything else talks over Railway's private network.

## Common Use Cases

* Run a self-hosted SOC console that collects alerts from security tools and groups them into incidents
* Triage alerts with an LLM agent (OpenAI, Anthropic or an OpenAI-compatible endpoint) while keeping an auditable record of every agent step
* Investigate incidents against MITRE ATT&amp;CK and manage cases, with a human approving any response action

## Dependencies for AiSOC Hosting

* PostgreSQL (Railway Postgres)
* Redis (Railway Redis)

### Deployment Dependencies

* AiSOC: https://github.com/beenuar/AiSOC
* AiSOC documentation: https://beenuar.github.io/AiSOC/
* Template source: https://github.com/aalfath/aisoc-railway-template
* Redpanda (Kafka-compatible event bus): https://github.com/redpanda-data/redpanda

### Implementation Details

**Signing in.** Open the `web` service's public URL. Sign in with `AISOC_ADMIN_EMAIL` (default `admin@example.com`) and the generated `AISOC_ADMIN_PASSWORD`, both shown in the `api` service's Variables tab. Change the password in the console after the first login. The administrator is created only once, so later deploys never overwrite a password you changed.

**Services.** `web` (console, public), `api` (core API and migrations), `agents`, `realtime`, `ingest`, `fusion`, `connectors`, `actions`, `redpanda` (event bus, volume `/var/lib/redpanda/data`), plus `Postgres` and `Redis`. The `agents` service keeps playbooks on a volume at `/data`. Every service has a health check and restarts on failure.

**Secrets.** The session key, JWT secret, credential-vault key, runtime database password and service-to-service tokens are generated per deployment and live on the `api` service. The other services reference them, so no secret is shared between deployments.

**AI triage (optional).** Without an LLM key AiSOC falls back to deterministic triage. To use a model, add `OPENAI_API_KEY` (or `ANTHROPIC_API_KEY`, or `OPENAI_BASE_URL` for an OpenAI-compatible endpoint) to the `agents` and `api` services. SMTP, SSO and connectors to your security tools are set up in the console or with extra variables; see the AiSOC docs.

**Not included.** Upstream's optional ClickHouse, Neo4j, Qdrant, LiteLLM gateway and bundled Ollama model are switched off to keep the template small. The core SOC workflow (ingest, fusion, alerts, cases, triage) works without them.

**Sizing.** Upstream recommends 8 GB of memory for a full install. Expect several GB across all services under load.

**Updates.** The template's services build from [aalfath/aisoc-railway-template](https://github.com/aalfath/aisoc-railway-template). When a new AiSOC version is merged there, Railway shows an update notice on your project and you choose when to apply it. Read `CHANGELOG.md` first. Migrations run automatically when the `api` service starts.

## Why Deploy AiSOC 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 AiSOC 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.
- [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

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