How to setup the Crisp Status local service
Learn how to run Crisp Status Local for private services that cannot be monitored from the public Internet.
Crisp Status Local is a daemon installed on your own infrastructure. It checks local mode nodes, such as private HTTP, TCP, or ICMP hosts, then reports their health back to Crisp Status Page.
When to use Crisp Status Local
Use Crisp Status Local when Crisp Status needs to monitor services that are not publicly reachable. This can include internal databases, private APIs, LAN services, or infrastructure that only your own network can access.
token. Running multiple instances with the same token can create conflicting reports and make monitored nodes appear unstable.Set up the service
To install Crisp Status Local, follow the instructions from the Crisp Status Local GitHub repository.
The project is open source, so your team can review the code, adapt it if needed, and compile it internally before running it on your infrastructure.
Get your reporter token
When configuring Crisp Status Local, you need your private reporter token. This token lets the daemon retrieve local nodes to check and report their health to Crisp Status.
Open Crisp, then go to Settings → Status Page → Configure your Status Reporter.
To copy your token:
- Open Settings → Status Page
- Open Configure your Status Reporter
- Copy the secret reporter token
- Paste it into your Crisp Status Local configuration
Frequently Asked Questions
Still have questions which were not covered in this article? Here is a collection of the most frequently asked questions on this topic.
Can I monitor several local nodes with one Crisp Status Local service?
Yes, one Crisp Status Local service can monitor all configured local nodes for the same setup. You do not need to run one daemon per node.
Keeping a single service also avoids duplicate reports and inconsistent status changes.
Should I use Crisp Status Local for public services?
No, public services are usually better monitored with poll mode. Use Crisp Status Local for private or LAN-only services that Crisp cannot reach directly from the public Internet.
Updated on: 03/05/2026
Thank you!