Container problem
local down
The app itself failed.
Exit codes, OOM kills, restart loops, health changes, and the log tail captured at failure.
● down · exit 137 · likely OOM
Hosted monitoring for your entire stack
Stop checking if it's still up.
Every DockTail host and service in one view. Cloud ties container health, Docker events, and Tailscale serve state into incidents you can act on.
Same DockTail agent · one environment variable · no second binary
incidents / inc_82fa
open
critical
grafana is down
prod-01 · opened 12 seconds ago
Verdict · container failure
Container exited with code 137 — likely out of memory. Its Tailscale service is still published.
local
● down
agent → container
tailnet
● published
tailscale serve
docker
● OOM
restart #4
Container evidence
at incident open
exit
137
memory
98%
logs
40 lines
The useful distinction
Not every outage is the same outage.
A plain uptime check stops at “down.” Cloud already has the Docker and Tailscale context — so it narrows the cause before you open a terminal.
Exposure problem
local up
The app's up — but unreachable.
The container answers locally, but its Tailscale service isn't published. Fix exposure, don't restart a healthy app.
● local up · tailnet not served
Host problem
no heartbeat
The whole host disappeared.
Detection runs in Cloud, not on the box — so a host that drops off still pages you, and logs its recovery when it's back.
● host offline · heartbeat missing
Services
Every DockTail service across your fleet
Search services…
ServiceHostStatus
grafana
grafana.tailnet.ts.net
immich
immich.tailnet.ts.net
webhook⚡ public
webhook.tailnet.ts.net
postgres
postgres.tailnet.ts.net:5432
One operational view
Your fleet, without the tab collection.
Search every service and host from one workspace — then trace any alert to the incident evidence behind it.
Service catalog
FQDN, image, compose project, ports, host, status, and Funnel exposure.
Docker inventory
Every other container on the host — with opt-in failure alerts for the ones you care about.
Quiet incident lifecycle
Debounced opens, confirmed recoveries, flap suppression — no alert storms.
Alerts where you work
Slack, Telegram, ntfy, webhook, and email.
Setup
One key. Fleet-wide monitoring.
Create a workspace key, add one environment variable, and restart DockTail. Hosts register themselves by Docker engine identity.
docker-compose.yml
services:
docktail:
environment:
- DOCKTAIL_CLOUD_KEY=dtc_7f3a...c91ePrivacy
Nothing hidden.
The software next to your containers should be inspectable. The data it sends should stay yours.
Open-source agent
The whole DockTail client — Cloud reporting included — is open source.
Encrypted in transit
Everything to Cloud rides an encrypted WebSocket (WSS).
Logs stay under your control
Incident log capture is bounded and configurable for the whole workspace or individual services.
Paid plans
Plans that grow with your fleet.
Flat pricing by host count. Services are not metered — a host reports every service it publishes.
Homelab
A few machines you care about.
$5 / month
or $36 billed yearly
- ✓ Up to 3 hosts
- ✓ 30-day check history
- ✓ 1 alert channel
- ✓ Single operator
Team
Shared operations across a growing fleet.
$29 / month
or $299 billed yearly
- ✓ Up to 10 hosts
- ✓ 30-day check history
- ✓ 5 alert channels + email
- ✓ Team members and roles
Business
More capacity for larger environments.
$99 / month
or $999 billed yearly
- ✓ Up to 30 hosts
- ✓ 30-day check history
- ✓ 15 alert channels + email
- ✓ Team members and roles
One environment variable
Start monitoring your fleet.
Set DOCKTAIL_CLOUD_KEY on the DockTail agent you already run. Every host and service shows up in the dashboard — no second binary, nothing dialing in.