> For the complete documentation index, see [llms.txt](https://docs.cleric.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cleric.ai/integrations/private-resources.md).

# Connecting Private Resources

Connect Cleric to resources in private networks

Cleric provides a lightweight Connector that you deploy inside your private network (on a VM or inside Kubernetes). The Connector functions as a simple network proxy, allowing Cleric to query your private endpoints, such as your Kubernetes API servers.

## How It Works

You configure what Cleric can access by providing configuration to the Connector. Cleric cannot reach any part of your network beyond the endpoints you configure.

The Connector creates a secure connection from your private environment to ours. No public IPs, VPN appliances, or special firewall rules required. The connection is end-to-end encrypted, ensuring that your data stays protected.

## Use Cases

Common scenarios for the Connector include:

* **Private Kubernetes clusters**: Access clusters without public API server endpoints
* **Internal monitoring systems**: Connect to Prometheus, Grafana, or other tools behind a firewall
* **On-premises infrastructure**: Query resources in data centers not exposed to the internet

## Getting Started

Connector deployment is guided by the Cleric team. Reach out via your dedicated Slack Connect channel to set up private resource access for your environment.