← redevops.ioReDevOps QA →
Public, signed image · source-available

A SOC dashboard. Over a real CrowdSec core.

Edge Sentinel reads CrowdSec's alerts and ban decisions, turns each into a replayable case with its evidence, and runs a response only after a named operator has approved it. It does not replace CrowdSec's own detection — it is the triage, evidence and approval layer on top of it.

Status: public, signed image, two install paths. The source is apps/edge-sentinel in github.com/redevops-io/agentic-os. The published image is ghcr.io/redevops-io/edge-sentinel:0.6.3 (linux/amd64 + linux/arm64), signed keyless with cosign and carrying a GitHub build-provenance attestation and a BuildKit SBOM — see Verify the image. It is source-available, not open source: AGPL-3.0-or-later as modified by the Commons Clause, the same family licence as the rest of rAIls. Install it on its own, or as one of three products in the combined install.
Try the live demo → Full install guide → View the repository path →

What it does

Alert feed and KPIs

Reads active decisions and alerts straight from the CrowdSec Local API. A source that cannot be read is reported as unavailable, never as zero.

Cases and evidence

Every alert becomes a case: immutable, content-addressed evidence and a proposed response for critical and high severities. The case id re-derives from the stored evidence.

Approval and execution

An operator approves or rejects, by name. Execution runs only an approved action, once, and is a recorded dry run until SENTINEL_BLOCK_ENABLED=1 — then it reads the ban back from CrowdSec before calling it contained.

Ban guard

Loopback, private and reserved ranges, the LAPI host and the operator's own address are never banned unless explicitly allowed. Durations are capped.

What this does not claim

Try it

The public demo at sentinel.redevops.io runs on sample security events — seeded SSH bruteforce, port scans, a path-traversal probe, a WordPress login bruteforce and a credential-stuffing range, each with its own severity and expiry. Triage and the approval-gated response action are shown; the real block/unblock endpoint is not reachable from that page.

Get it

There are two ways to run Edge Sentinel today.

1. On its own (standalone)

One host, Docker Compose or Kubernetes/k3s, no other ReDevOps product:

git clone https://github.com/redevops-io/agentic-os.git
cd agentic-os/deploy/standalone/edge-sentinel
./bootstrap.sh

Brings up CrowdSec and Edge Sentinel, generates every secret, and ends with the dashboard at http://127.0.0.1:8203/. Full reference, Kubernetes manifests, backup/upgrade and the configuration table: docs/standalone/edge-sentinel.md.

2. As part of the combined install

Edge Sentinel is one of three products in a single documented install — Projects and Sidekick (the operator console and chat), redevops-qa and Edge Sentinel — wired through a shared product registry and a shared approval secret, on one Docker host. A ban approved in the Projects UI is recorded in Sentinel under a named actor, not an anonymous service call. A real recorded install and walkthrough, both install paths (a single-pull signed bundle or a from-source checkout), and the digests to verify are on the combined install page.

git clone https://github.com/redevops-io/agentic-os.git
cd agentic-os/deploy/combined
./bundle-bootstrap.sh # or ./bootstrap.sh for the file-secrets, from-source path

What you get, and the stated limitations (QA's browser lanes are linux/amd64 only; the approval round trip from QA to Sentinel is exercised on Linux installs): deploy/combined/README.md. A release gate (combined-install-e2e.yml) runs the file-secrets path on every change; a failure there withdraws the claim, not the test.

Verify the image

cosign verify ghcr.io/redevops-io/edge-sentinel@sha256:0650bba74539e9500d537236cf843eca407e45be99fe5b7ae2530096e0abbd72 \
  --certificate-identity 'https://github.com/redevops-io/agentic-os/.github/workflows/oci-edge-sentinel.yml@refs/heads/main' \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com
ReleaseTagsIndex digestSource commit
0.6.30.6.3sha256:0650bba7…abbd72d7b79530d496 (tag edge-sentinel-v0.6.3, on main)
0.6.20.6.2sha256:90fd0ab8…e1b8fdd81761a4f (tag edge-sentinel-v0.6.2, on main)

Tags are built from the main line of the repository, not the v0.6.x release line; there is no latest. The full digest table (per-architecture manifests included) is in the install guide.

View the repository → Combined install + demo → ReDevOps QA →

// Edge Sentinel · public signed image · evidence as of release 0.6.3 (14 November 2026, UTC) · CrowdSec is a trademark of CrowdSec SAS, named here to describe what the adapter reads from; this is an independent project, not endorsed by them.