Skip to content

armgit / AiSOC

Public Imported from GitHub
0

Open-source AI Security Operations Center: alert fusion, LLM-agent triage, MITRE ATT&CK investigation, and a replayable decision ledger for every agent step. Self-hostable, runs with no API keys, MIT licensed. Ships an MCP server for Claude, Cursor and Continue.

feat(deploy): WS-A3 — one-click Render button + 60s README section + render.yaml at repo root

Beenu Arorad11f4cf45c8d
diff --git a/.gitleaksignore b/.gitleaksignore
index 4ea404d34..a9e544e5a 100644
--- a/.gitleaksignore
+++ b/.gitleaksignore
@@ -14,8 +14,8 @@ detections/fixtures/positive/jwt-none-alg.json:jwt:2
# Render IaC env-var keys (`AISOC_DISABLE_NEO4J`, `AISOC_DISABLE_QDRANT`).
# The generic-api-key rule fires on the long key name; the value is "true",
# not a secret.
-infra/render/render.yaml:generic-api-key:70
-infra/render/render.yaml:generic-api-key:124
+render.yaml:generic-api-key:70
+render.yaml:generic-api-key:124
# Detection rule literal: `count_5min_per_ip_gt: 30` matches the heuristic.
# This is a rule definition, not a credential.
diff --git a/AI_STACK_PLAN_PROGRESS.md b/AI_STACK_PLAN_PROGRESS.md
index f2aa9d543..5e04cb2d2 100644
--- a/AI_STACK_PLAN_PROGRESS.md
+++ b/AI_STACK_PLAN_PROGRESS.md
@@ -185,7 +185,7 @@ timing.
Six triaged false positives, each with a comment:
- `detections/fixtures/positive/jwt-none-alg.json:jwt:2` — positive test fixture.
-- `infra/render/render.yaml:generic-api-key:70` and `:124` — env var **names**
+- `render.yaml:generic-api-key:70` and `:124` — env var **names**
(`AISOC_DISABLE_NEO4J=true`).
- `scripts/detection_specs_part3_application.py:generic-api-key:61` —
detection rule literal `count_5min_per_ip_gt: 30`.
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 44aae02b7..f3aabd64b 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -669,7 +669,7 @@ demo profile. Details below.
- **Fly.io** (`infra/fly/`) — first-class config for `api`, `agents`,
`realtime`, `web`. Deploys via `infra/fly/fly-demo-deploy.sh`,
~$14/mo for the whole stack.
-- **Render** (`infra/render/render.yaml`) — managed, sleep-on-idle
+- **Render** (`render.yaml`) — managed, sleep-on-idle
config suitable for hobbyists and design partners.
- **Railway** (`infra/railway/railway.toml`) — pay-as-you-go PaaS.
- **Coolify** (`infra/coolify/README.md`) — self-hosted on your own VPS,
diff --git a/README.md b/README.md
index 7d8bb295a..192ab3022 100644
--- a/README.md
+++ b/README.md
@@ -11,7 +11,7 @@ An open-source, self-hostable AI SOC. The agent's prompts, tool calls, and ratio
[![PRs welcome](https://img.shields.io/badge/PRs-welcome-8b5cf6?style=flat-square)](CONTRIBUTING.md)
[![Version](https://img.shields.io/badge/version-6.1.0-f59e0b?style=flat-square)](CHANGELOG.md)
-[Live demo](https://tryaisoc.com) · [How AiSOC compares](#how-aisoc-compares) · [Public eval harness](apps/docs/docs/benchmark.md) · [Deployment options](#deployment-options) · [Architecture](#architecture) · [Docs](apps/docs/)
+[Live demo](https://tryaisoc.com) · [How AiSOC compares](#how-aisoc-compares) · [Public eval harness](apps/docs/docs/benchmark.md) · [Deploy in 60 seconds](#deploy-in-60-seconds) · [Deployment options](#deployment-options) · [Architecture](#architecture) · [Docs](apps/docs/)
<sub>The demo at <a href="https://tryaisoc.com">tryaisoc.com</a> is a self-hosted instance fronted by a Cloudflare Tunnel — when it's reachable, the stack is running locally on a maintainer's box. It can therefore go offline at any time. To run your own (in 3.5 min, with seeded data), see <a href="#one-shot-demo">One-shot demo</a>; to expose your own instance on your own domain via Cloudflare Tunnel, see <a href="#public-demo-on-your-own-domain">Public demo on your own domain</a>.</sub>
@@ -53,6 +53,38 @@ Closed-source AI SOC vendors ship working products. AiSOC's contribution is maki
---
+## Deploy in 60 seconds
+
+Three frictionless paths to a running, seeded AiSOC instance with `INC-RT-001` (the LockBit 3.0 ransomware showcase) already mid-investigation when you land on it. Each path runs `alembic upgrade head` and `python -m app.scripts.seed_demo` as part of its lifecycle, so the seeded data is present without a manual step.
+
+### 1. Render — one click, hosted
+
+[![Deploy to Render](https://render.com/images/deploy-to-render-button.svg)](https://render.com/deploy?repo=https://github.com/beenuar/AiSOC)
+
+Render reads [`render.yaml`](render.yaml) at the repo root, provisions Postgres + Redis, and brings up the demo profile (api, agents, web, realtime). The `preDeployCommand` migrates and seeds, so the canonical `INC-RT-001` is present on first boot. Sleep-on-idle on the hobby tier; flip to standard instances for production. Demo runs deterministic-mode by default — no OpenAI/Anthropic key needed. See [`infra/render/README.md`](infra/render/README.md) for cost, scaling, and BYO-LLM details.
+
+### 2. Docker Compose — one command, local
+
+```bash
+git clone https://github.com/beenuar/AiSOC.git && cd AiSOC && pnpm aisoc:demo
+```
+
+Pulls prebuilt `ghcr.io/beenuar/*` images, brings up the slim demo profile (Postgres, Redis, Kafka, api, agents, realtime, web), runs the seeder as a one-shot container, and opens your browser at `/cases/INC-RT-001?tab=ledger` with `[email protected]` already auto-logged-in. Idempotent: re-running is a no-op against a seeded volume. Target on a clean Mac with a warm Docker daemon: clone-to-investigation in **~3.5 min warm / ~5 min cold**. Stop with `pnpm aisoc:demo:down`. See [One-shot demo](#one-shot-demo) for the timing breakdown and what you'll see on screen.
+
+### 3. Fly.io — one script, hosted, persistent
+
+```bash
+git clone https://github.com/beenuar/AiSOC.git && cd AiSOC
+./infra/fly/fly-demo-deploy.sh --provision # first run: also creates Postgres + Upstash
+./infra/fly/fly-demo-deploy.sh # subsequent runs: deploys updates
+```
+
+Idempotent shell wrapper around `flyctl` that deploys four apps (api, agents, web, realtime) plus managed Postgres + Upstash Redis, wires the `*.internal` 6PN DNS between them, runs migrations + seeding as a `release_command`, and issues TLS certs for your domain. ~$14/mo at idle. **Time-to-first-investigation budget: <60s from the click**, since the seeder pre-warms a running investigation so the deeplink lands inside the TTFI budget regardless of cold-start. See [`infra/fly/README.md`](infra/fly/README.md) for DNS prerequisites and per-app sizing.
+
+> **Production-grade install?** Skip the demo paths above and use [`infra/helm/`](infra/helm/) (Kubernetes) or [`infra/terraform/`](infra/terraform/) (AWS). Both bring up the full storage tier — ClickHouse, Kafka, OpenSearch, Neo4j, Qdrant — gated behind compose profiles in the demo paths above.
+
+---
+
## Deployment options
Each target ships a tested config in [`infra/`](infra/):
@@ -60,7 +92,7 @@ Each target ships a tested config in [`infra/`](infra/):
| Platform | Status | Config | Notes |
|---|---|---|---|
| Fly.io | first-class | [`infra/fly/`](infra/fly/) | 4 apps, ~$14/mo. See [infra/fly/README.md](infra/fly/README.md). |
-| Render | supported | [`infra/render/render.yaml`](infra/render/render.yaml) | Sleep-on-idle, hobbyist tier. |
+| Render | supported | [`render.yaml`](render.yaml) + [`infra/render/`](infra/render/) | Sleep-on-idle, hobbyist tier. One-click via blueprint button. |
| Railway | supported | [`infra/railway/railway.toml`](infra/railway/railway.toml) | PaaS, pay-as-you-go. |
| Coolify | supported | [`docker-compose.yml`](docker-compose.yml) | Self-hosted on your own VPS. See [infra/coolify/README.md](infra/coolify/README.md). |
| Kubernetes / Helm | first-class | [`infra/helm/`](infra/helm/) | `helm install aisoc ./infra/helm/aisoc` |
@@ -414,7 +446,7 @@ When you're done: `pnpm aisoc:demo:down` (stops containers and deletes the demo
#### Hosted, public-internet equivalent
-The same stack ships a Cloudflare Tunnel template (see [Public demo on your own domain](#public-demo-on-your-own-domain)) and tested deployment configs for [Render](infra/render/render.yaml) and [Fly.io](infra/fly/) — both wire `alembic upgrade head && python -m app.scripts.seed_demo` into the deploy lifecycle so the same `INC-RT-001` showcase is present after `render blueprint launch` or `fly deploy`.
+The same stack ships a Cloudflare Tunnel template (see [Public demo on your own domain](#public-demo-on-your-own-domain)) and tested deployment configs for [Render](render.yaml) and [Fly.io](infra/fly/) — both wire `alembic upgrade head && python -m app.scripts.seed_demo` into the deploy lifecycle so the same `INC-RT-001` showcase is present after `render blueprint launch` or `fly deploy`.
The full development quick start with all services (UEBA, Honeytokens, Purple Team, ClickHouse, OpenSearch, Neo4j, Qdrant) is below.
diff --git a/infra/render/README.md b/infra/render/README.md
index 335c455f5..6efcd8d7a 100644
--- a/infra/render/README.md
+++ b/infra/render/README.md
@@ -56,8 +56,8 @@ If you need the full storage tier in production, use:
1. Click the **Deploy to Render** button above.
2. Render asks for permission to read your fork of `beenuar/AiSOC`. Grant it.
-3. Render parses [`render.yaml`](render.yaml), shows the service plan, and
- asks you to confirm.
+3. Render parses [`render.yaml`](../../render.yaml) at the repo root, shows
+ the service plan, and asks you to confirm.
4. Click **Apply**. Render provisions Postgres + Redis first (~2 min),
then deploys the four web services in dependency order (~6-8 min for
the first build because Docker layers aren't cached yet).
@@ -71,8 +71,8 @@ If you've forked the repo and changed things:
```bash
# From the repo root, after pushing your fork to GitHub:
gh repo view --web
-# Then in Render: New + → Blueprint → Connect repo → select fork →
-# point at infra/render/render.yaml → Apply.
+# Then in Render: New + → Blueprint → Connect repo → select fork.
+# Render auto-detects render.yaml at the repo root → Apply.
```
## Post-deploy: pre-warm the demo
@@ -137,8 +137,13 @@ can take 20-30s on cold Postgres. Subsequent investigations land in
```
infra/render/
-├── README.md — this file
-└── render.yaml — Render Blueprint manifest (the source of truth)
+└── README.md — this file (Render-specific walkthrough + cost notes)
+
+<repo root>/
+└── render.yaml — Render Blueprint manifest (the source of truth).
+ Lives at the root because Render's "Deploy to Render"
+ button only auto-detects blueprints at the root of
+ the repo, not in subdirectories.
```
For the full deployment philosophy and platform comparison, see the
diff --git a/infra/render/render.yaml b/render.yaml
similarity index 100%
rename from infra/render/render.yaml
rename to render.yaml