Skip to content
StatusTick
Join the beta

See every service, outside and in.

Checks from outside show what your customers see. A private agent checks what only your network can reach: internal APIs, databases, intranets and VPN-only tools. Both feed the same alerts, incidents and status pages.

Free while in beta. Launching Q1 2027.

How it connects Example
Inside your network, the agent checks private services and connects out to StatusTick on port 443. Nothing connects in.Your networkorders-dbadmin.corp.examplesessions-cacheAgent:443 outnothing inStatusTickyour alertsInside your network, the agent checks private services and connects out to StatusTick on port 443. Nothing connects in.Your networkorders-dbadmin.corp.examplesessions-cacheAgent:443 outnothing inStatusTickyour alerts

The agent checks what only your network can reach and sends the results out on port 443. By default you open no ports, and nothing connects in.

office OnlineExample
  • orders-dbPostgreSQL · 10.0.4.12:54323 msUp
  • admin.corp.examplehttps://admin.corp.example/health842 msDegraded
  • sessions-cacheRedis · 10.0.4.20:63791 msUp
Example private location with three internal monitors.
Install with Docker
docker run -d --name statustick-agent \
  --restart unless-stopped --shm-size 512m \
  --cap-drop ALL --cap-add SETUID --cap-add SETGID \
  -e STATUSTICK_TOKEN="sta_live_…" \
  ghcr.io/statustick/agent:1

What leaves your network, and what stays.

The agent connects out to agent.statustick.com on port 443 with its own token. By default you open no ports.

Sent to StatusTick

  • Check results: status, timings, status codes and short errors.
  • For a database check, only the one value you compare.
  • For a browser check, its screenshot and trace.

Kept on your machine

  • Database passwords, in STATUSTICK_SECRET_* variables bound to their hosts.
  • Your allow list (STATUSTICK_ALLOW): with it set, only the targets on it are checked, and nobody at StatusTick can change it.
  • Cloud metadata addresses, refused unless you allow them.

The same checks, inside.

  • Websites and APIs

    Internal HTTP(S) services, admin tools and health endpoints, through your proxy and your own CA if you use them.

  • Databases

    PostgreSQL, MySQL, Redis and MongoDB: it logs in and runs one read-only command.

  • TCP, ping and DNS

    Hosts, ports and records on private addresses.

  • Playwright checks

    Real browser flows on intranet apps. Each run is its own process and user, stopped after 2 minutes.

Built to run on its own.

  • Keeps checking offline

    If StatusTick can’t be reached, the agent keeps checking for up to an hour and uploads the results later.

  • Agents that take over

    Run several agents in one private location; they share its checks and take over when one stops.

  • Heartbeat relay

    Jobs on servers without internet access ping the agent instead.

  • Rotate or revoke a token

    The old token keeps working for 60 minutes after a rotate. Revoke stops a leaked one at once.

Questions.

What does the agent need from my network?
Outbound HTTPS to agent.statustick.com on port 443. No inbound port, VPN or IP allowlisting.
Can StatusTick make my agent reach anything?
Not with an allow list. Set STATUSTICK_ALLOW and the agent checks only the targets on it; the list lives on your machine.
Where can the agent run?
As a Docker container, a static Linux binary or a Helm chart: a VM, a Kubernetes cluster or a server in your office.

Private agents docs

See it on your own product.

Point it at your product tonight. In the morning you’ll see what happened while you slept, and which of it needed you.

Closed beta now. Free while in beta. Launching Q1 2027.