Appulsemonitor
Private Checkers

Monitor services inside your network

Your most critical services run behind firewalls. Now you can monitor them with the same reliability as public endpoints — no inbound firewall rules required.

🔒

No Firewall Changes

Private checkers make outbound connections only. Your firewall rules stay locked down.

🐳

One Docker Container

Deploy with a single docker run command. No complex setup, no agents to configure.

👥

Team Isolated

Your private regions are visible only to your team. Complete tenant isolation.

What you can monitor internally

HTTP endpoints and TCP ports accessible from within your network

Kubernetes Services

Internal cluster endpoints, pods, health endpoints

Databases (TCP)

PostgreSQL, MySQL, Redis, MongoDB port availability

Message Queues

RabbitMQ, Kafka, SQS queue management endpoints

Internal APIs

Microservices, admin panels, tooling

CI/CD Systems

Jenkins, GitLab runners, Argo

Monitoring Tools

Grafana, Prometheus, ELK stack

On-Prem Services

Legacy systems, data center apps

Dev Environments

Staging servers, test environments

Deploy in 2 minutes

Get your API key from the dashboard, run one command

1

Create a private region

Go to Settings → Private Regions and create a new region. Give it a name like "Production VPC" or "Staging Cluster".

2

Deploy the checker

docker run -d \
  --name rhealth-checker \
  --restart unless-stopped \
  -e CHECKER_API_KEY="your-api-key" \
  -e REGION_ID="your-region-id" \
  rhealth/checker:latest
3

Create monitors using your private region

When creating a monitor, select your private region instead of public regions. The checker will monitor internal IPs and hostnames accessible from its network.

Included on every plan

Private checkers are available on Free, Pro, and Business

Free
1
private region
Pro
3
private regions
Business
unlimited regions

Ready to monitor your internal services?

Deploy a private checker in minutes. Free tier includes 1 private region.