> For the complete documentation index, see [llms.txt](https://docs.venn.build/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.venn.build/venn-network/getting-started/node-operators.md).

# Node Operators

{% hint style="warning" %}
Venn is currently operating in a permissioned mode. If you are interested in joining Venn as a node operator, please contact us to express your interest and learn more about the requirements and process.
{% endhint %}

## **What is a Node Operator within Venn?**

Node operators run the core Venn infrastructure to validate transactions and ensure the network's overall functionality. The Venn node architecture is designed to run on your existing nodes or be deployed as a dedicated node, making it highly modular, cost-efficient, and easy to maintain. In the Venn ecosystem, there are two types of operators:

1. **Infrastructure Node Operators**: These operators focus on the technical infrastructure, ensuring the network runs smoothly and efficiently. Infrastructure operators can run the default threat model provided by Venn or choose any other threat model from any security team based on past performance and personal preferences. [Start Installation ](/venn-network/getting-started/node-operators/installation.md)
2. **Security Node Operators**: These operators specialize in security validation, developing custom transaction analyses for potential threats and malicious activities. Security teams can integrate their unique threat models into the Venn node client using an SDK, allowing you to enforce specific security policies tailored to their expertise and approach. [Start Building Custom Threat Models](/venn-network/getting-started/security-teams.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.venn.build/venn-network/getting-started/node-operators.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.