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

# Overview

Telller's network of distributed cloud nodes operates as Proof of Cloud (POC) consensus validators for the Teller Protocol. In other words, the nodes act as a data router for the protocol's smart contracts.

The current system architecture resembles the following diagram:

![](/files/-MOrAugU80H2VVI9LDke)

The two core components of the distributed cloud network are:

1. The Teller Subgraph
2. Teller Validator

## Subgraph

Teller's Subgraph listens for events emitted through interactions with the protocol's deployed smart contracts and then parses them to a graphQL service.

## Validator

Validator is the primary web service endpoint of the node, which handles user requests via an RPC JSON v2.0 service.

## Kubernetes

All of these components are deployed and distributed via docker images using kubernetes, which is in turn packaged as a helm chart installation.

The system architecture diagram is as follows:

![](/files/-MOrBD8qInRWKqiQlNcE)

{% hint style="info" %}
The Node manages everything inside kubernetes cluster:
{% endhint %}


---

# 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.teller.org/teller-docs/teller-nodes/overview.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.