Core appliance
The app, MariaDB, cron scheduler, and standard Python worker form the local monitoring path.
localOwn your hardware
Keep the monitoring close to the operation.
The Sentinel appliance runs the app, database, scheduler, and worker on infrastructure you control. The result is a monitoring history that belongs with the team responsible for acting on it.
LIVE CHECK BOARD01 / 06
Portal appWATCHING
MariaDB databaseWATCHING
SchedulerWATCHING
Worker queueWATCHING
Optional JS workerWATCHING
operator controlledhistory / incidents / alerts
The signal behind the check
Self-hosting changes the responsibility as well as the location: you operate the host, backups, updates, target access, notification credentials, and any proxy or external provider configuration. Outbound target and provider traffic can still leave the box.
Built to be specific
A topology you can reason about.
Optional JS lane
Pro can use a separate Playwright worker for pages that need rendering. Chromium consumes materially more resources.
ProProtect the volume
Use durable SSD-backed storage, test backups, keep updates deliberate, and choose retention with the run payload size in mind.
operatorScale from evidence
Reduce cadence or check count first. Use queue latency and service measurements before adding capacity or changing the deployment shape.
measuredMeasured profiles
Measured profiles are useful only when their limits are visible.
ProfileDeclared workloadEvidenceStatus
Starter2 domains · 200 URLs · 610 declared configs · daily2026-07-10 · x86_64 compose + loopbackcompose baseline
Standard5 domains · 1,000 URLs · 3,050 declared configs · hourly2026-07-10 · x86_64 compose + loopbackcompose baseline
JS worker2 domains · 40 URLs · 120 declared configs · 8 bounded JS jobs2026-07-10 · workload declarationcompose measure pending
These are dated deterministic fixture baselines, not generic hardware recommendations. Full queue, MariaDB, dashboard, storage-growth, and Playwright measurements must be recorded in docs/benchmarks before publishing CPU, RAM, SSD, architecture, or throughput numbers. Pro is uncapped by licence, not by compute or storage.
The network contract
Local control does not mean isolated traffic.
The appliance needs outbound DNS and HTTP(S) access to monitored targets and any configured alert, licence, or provider endpoints. Inbound access and TLS remain operator responsibilities. A supplied proxy can provide the request context a target expects.