selfhost.directory

The index of self-hostable projects — ranked, categorized and served with live updates.
Own your data and stop giving it to big tech.

AiSOC logo

Self-host AiSOC

v22.2.0

AI Security Operations Center with auditable agent decisions

ReleaseOpen SourceMIT
Updated3 days ago
LanguagePython
Setup difficultyAdvanced
MobilePWA
Stars
6 755
RAM
8 GB
Storage
20 GB
Ports
3000 (Web console (frontend)), 8080 (Ingest API), 8000 (Core API), 8084 (Agents service), 4000 (Realtime gateway / LiteLLM)
Requires
Kafka, LiteLLM, Ollama, PostgreSQL, Qdrant, Redis, ZooKeeper
Docker
ghcr.io/beenuar/aisoc-core-api
Install with Docker Compose
Alerts queue showing alerts attributed to their connector sourceAI triage verdict in the Investigation Rail with confidence and rationaleThreat intelligence page showing CISA KEV entriesSOC operations dashboard with honest empty states

What is AiSOC?

AiSOC is an open-source AI Security Operations Center that security teams can self-host to detect, investigate, and respond to threats with full auditability. It ingests telemetry from 87+ connectors including EDR, SIEM, cloud, and identity providers, normalizes events to a common schema, and runs a detection engine with 2,535 executable rules from a 6,991-rule library. Alerts are correlated into incidents and investigated by LangGraph-based AI agents that write all prompts, tool calls, and reasoning to a replayable Investigation Ledger. The system includes a local LLM (Ollama with Llama 3.2 3B) for CPU-only triage, a CISA KEV threat intelligence feed, UEBA baselines, honeytokens, purple-team emulation, and compliance dashboards for major frameworks. It deploys via Docker Compose (CORE profile: 16 services, ~8 GB RAM), Helm charts for Kubernetes, or a one-click installer script. Authentication supports built-in credentials, SAML 2.0, OIDC, and TOTP MFA. The project is MIT licensed and funded by Cyble with no commercial gating.

Should you self-host AiSOC?

AiSOC scores 80/100 on selfhost.directory (how scoring works) and ranks #3 of 78 in Security. It has 6 755 GitHub stars, +4 373 in the last 30 days.

It shipped 44 stable releases in the past year. The latest, v22.2.0, came out on 6 November 2026. New versions land roughly every 1 days.

Setup is advanced: plan for several services and some ongoing maintenance. An official Docker image is available. It is MIT-licensed and written mostly in Python.

Its closest alternative on selfhost.directory is CyberChef (83/100, 36 346 stars). It scores higher overall, so compare the two before you pick. See AiSOC vs CyberChef side by side.

Features

  • AI-powered alert triageRuns with local Ollama model (Llama 3.2 3B) by default; hosted LLMs optional
  • Alert Correlation
  • Compliance dashboards
  • Detection engineRules must pass replay proof to be counted as executable
  • Entity graphFull profile
  • HoneytokensExtras profile
  • Investigation LedgerOCSF 1.9.0 format
  • MCP Server
  • Multi-tenancy with RBAC
  • Playbook engineThree opt-ins required; preview by default
  • Plugin SDKBeta
  • Purple team emulationExtras profile
  • Retro-huntsOpt-in, full profile
  • Threat IntelligenceCISA KEV works out of the box with no API key
  • UEBARequires full profile

AiSOC README

AiSOC

AiSOC

An open-source, self-hostable AI Security Operations Center. It ingests your security telemetry, detects and correlates threats, investigates them with AI agents whose reasoning is fully auditable, and proposes responses a human approves.

License: MIT Version CI CodeQL OpenSSF Scorecard Technical Guide

Technical Guide (PDF) · Docs · Architecture · What actually works · Discussions


What AiSOC does

Telemetry arrives from your security tools. AiSOC normalizes it, runs the 2966 executable rules of its 7407-rule library, groups what fires into incidents, investigates each one with an AI agent whose every prompt and tool call is recorded, and proposes an action. New threat intelligence re-sweeps the history you already collected, and a human approves before anything reaches a vendor.

How to install AiSOC

Install AiSOC with Docker Compose

Environment variables
AISOC_VERSION, AISOC_PULL_POLICY, ENVIRONMENT, SECRET_KEY, AISOC_CONSOLE_URL, AISOC_CONSOLE_BIND_ADDR, AISOC_BIND_ADDR, AISOC_DEMO_MODE, AISOC_REALTIME_JWT_SECRET, JWT_SECRET, METRICS_TOKEN, AISOC_CREDENTIAL_KEY, POSTGRES_PASSWORD, AISOC_APP_DB_PASSWORD, REDIS_PASSWORD, CLICKHOUSE_PASSWORD, KAFKA_BOOTSTRAP_SERVERS, OPENSEARCH_URL, QDRANT_URL, OPENAI_API_KEY, OPENAI_MODEL, LITELLM_MASTER_KEY, LLM_GATEWAY_URL, AISOC_LITELLM_REQUEST_TIMEOUT, SSO_ENABLED, SSO_PROVIDER, OIDC_ISSUER, OIDC_CLIENT_ID, OIDC_CLIENT_SECRET, OIDC_REDIRECT_URI, OIDC_SCOPES, SSO_GROUPS_CLAIM, SSO_LOGIN_LABEL, SSO_LOCAL_ADMIN_ONLY, and many more

git clone https://github.com/beenuar/AiSOC && cd AiSOC make up

CORE profile (16 services, ~8 GB RAM); full profile adds ClickHouse, Neo4j, OpenSearch, enrichment

How to configure AiSOC

  • AISOC_VERSIONlatest─── Image Pinning ──────────────────────────────────────────────────────────── Tag pulled by every `image: ghcr.io/beenuar/aisoc-*:${AISOC_VERSION:-latest}` in docker-compose.yml. Docker pulls this tag on first boot and skips the local build (~90 s vs ~15 min). Pin to a release tag (e.g. v12.0.0) for reproducible deploys; leave as `latest` to track the newest release.
  • ENVIRONMENTproduction─── Core Configuration ─────────────────────────────────────────────────────── `development` enables the dev auth bypass in services/api/app/api/v1/dev_auth.py. Set `production` for anything network-reachable; docker-compose.yml reads this value, so changing it here is enough. Production is the default because the value of this variable used to decide whether an uncredentialed request was served a
  • LOG_LEVELinfo
  • SECRET_KEYHS256 signing key for console sessions, shared by the API and the connectors service. Left empty here and generated by `scripts/ensure_env.py` — see the note on AISOC_CREDENTIAL_KEY below for why a placeholder is not used.
  • AISOC_REALTIME_JWT_SECRETShared HS256 secret used ONLY for short-lived realtime WS/SSE tickets (Issue #239). The API mints tickets at `POST /api/v1/realtime/ticket` and the Node realtime service (`services/realtime`) verifies them on every WebSocket upgrade and SSE request — both sides MUST read the same value. This is intentionally separate from SECRET_KEY so the realtime edge can be rotated independently and a leaked ti

AiSOC releases & version history

@ Every self-hosted release, weekly

One Monday email with the week's stable releases across the directory.

More in Security

Rate this project

Click to rate — no account needed.

0 comments

Posting as guest
Loading comments…