> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.chrisp.chat/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# 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.

||| Run only one Crisp Status Local service with the same reporter `` `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](https://github.com/crisp-im/crisp-status-local).

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](https://app.crisp.chat), 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

|| The token is an alphanumeric string separated by dashes. Keep it private, because it authorizes your local monitoring service.

---

# 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.