SentinelReady

You're in. Let's get you running.

Four steps: get your access, pull the image, drop in your config, point one alert source at it. Most of this takes under 10 minutes once access lands.

Not a customer yet? Run Community free instead — same engine, no card.

1Get your access

Early customers get set up personally rather than a bare self-serve download — expect an email from support@sentinelready.io within one business day of purchase with your container registry access and confirming your license key (also in your receipt email). If it's been longer than that, just reply to your receipt or email us — nothing else to do on your end until you hear from us.

2Pull and run

Once you have registry access:

docker login ghcr.io -u YOUR_GITHUB_USERNAME
# paste the access token from your setup email when prompted

git clone https://github.com/browningjc97/sentinelready-docker
cd sentinelready-docker
cp sentinelready.yaml.example sentinelready.yaml

First startup takes 3-5 minutes — SentinelReady pulls Ollama and downloads the llama3.1 model automatically.

3Add your license key

In sentinelready.yaml, under license:, paste the key from your receipt email:

license:
  ls_license_key: "your-key-from-the-receipt-email"

Then start it up:

docker compose up -d

SentinelReady checks in automatically from here — no manual re-issuing as your subscription renews.

4Point one alert source at it

Prometheus/Alertmanager example — add a receiver to your Alertmanager config:

receivers:
  - name: sentinelready
    webhook_configs:
      - url: 'http://your-sentinelready-host:8000/webhook/grafana'
        send_resolved: true
        http_config:
          headers:
            x-sentinel-secret: 'your-webhook-secret'

Your webhook secret is either what you set in sentinelready.yaml under customer.webhook_secret, or check the container logs on first run — SentinelReady generates and prints a real one automatically if you didn't set your own. Fire a test alert and watch it arrive.

Using Grafana, CloudWatch, Datadog, Slack, or a UniFi controller instead? Same idea, different endpoint path (/webhook/cloudwatch, /webhook/datadog, etc.) — or point anything else at /webhook/auto and SentinelReady figures out the field mapping itself the first time it sees that payload shape.