0.0.1 is now available
Terminal-native observability for builders.
Scout keeps an always-on pulse on your APIs, docs, and internal tools. Opinionated checks, smart alerts, zero dashboard bloat.
production · green
· · ·
SLO-aware monitoring
Budget-aware alerting with burn-rate thresholds so teams only wake up when it matters.
Desktop notifications
Get instant alerts on your desktop when services go down—native notifications that don't require opening a browser.
Versioned configs
Ship configs via git. Promote from staging to prod with the same file—no dashboards to click.
3 steps to ship
Get monitoring in minutes
Install Scout, add your services, and keep a watchful eye without context switching. Everything lives in your terminal and version control.
- 1
Install
Run
brew install juststeveking/tap/scoutto get the latest release. - 2
Configure
Add endpoints and credentials in
~/.config/scout/config.yml. - 3
Watch
Run
scout monitorto see live health updates and failures.
scout.config
services:
api:
url: https://api.example.com/health
method: GET
auth:
type: Bearer
token: $API_TOKEN
json_assertions:
- path: status
value: "ok"
operator: "=="
tls_check: true
tls_warning_days: 30
API_URL=https://api.example.com/health
API_METHOD=GET
API_TOKEN=xxxxx
Version control configs with your team; keep secrets in env vars or your vault.
Ready to ship calmly?
Wire Scout into your stack in 5 minutes.
CLI-first, team-ready, with alerting that respects your sleep.
FAQ
How do you handle secrets?
Keep secrets in env vars or your vault; configs reference them. Nothing leaves your local environment.
Will this spam my team?
Desktop notifications only for now. Smart deduping and cooldowns keep the noise down—you'll only see alerts that matter.
Can it run behind auth or on-prem?
Yes. Scout supports headers and tokens, and checks can run from your network so nothing leaves your VPC.