# Full Nodes Infrastructure

## Overview

RPC and REST requests are an application’s gateway to the Terra Classic cluster. The requests are serviced by blockchain Full Nodes, which are typically dedicated to the task rather than participating in consensus. Nevertheless, from an application user’s perspective, poor RPC/REST performance is no different from poor cluster performance.&#x20;

Developers are encouraged to use a local cluster during development, especially in the early stages and for testing. Local clusters are more flexible than the public offerings, granting the freedom to run unoptimized early iterations. Once the application reaches a stable state, deploying on a public cluster becomes more appropriate.

## Free Services: Public Full Nodes <a href="#free-services" id="free-services"></a>

Several providers offer free RPC and REST access to the public Terra Classic cluster. These services are good for real-world testing, early demos, and small, private beta programs. Free services typically do not autoscale, are rate-limited, offer no SLA, and are not afraid to ban abusers. When an application is ready to be opened to the public, it is time to invest in private access.

Some free Full Node providers:

**Public Node by All Nodes:** [**https://terra-classic.publicnode.com**](https://terra-classic.publicnode.com/)

* RPC Endpoints:
  * RPC: <https://terra-classic-rpc.publicnode.com:443>
  * WS RPC: wss\://terra-classic-rpc.publicnode.com:443/websocket
  * GRPC: terra-classic-grpc.publicnode.com:443
  * GRPC-WEB: <https://terra-classic-grpc-web.publicnode.com>
* REST Endpoints:
  * FCD: <https://terra-classic-fcd.publicnode.com>
  * LCD: <https://terra-classic-lcd.publicnode.com>

**Autostake:** [**https://autostake.com/networks/terraclassic/#validator**](https://autostake.com/networks/terraclassic/#validator)

* RPC Endpoints:
  * RPC: <https://terraclassic-mainnet-rpc.autostake.com:443>
  * GRPC: terraclassic-mainnet-grpc.autostake.com:443
* REST Endpoints:
  * LCD: <https://terraclassic-mainnet-lcd.autostake.com:443>

## Paid Services: Private Full Nodes <a href="#free-services" id="free-services"></a>

Due to the variability in requirements between applications, generalized public Full Node infrastructure rarely fits the bill. To ensure users get a good experience, public facing applications need to secure their own private access. This will allow you to autoscale based on user demand, relax rate limits according to your application, and have peace of mind that other applications’ users won’t crowd yours out. Several organisations offer high-availability, on-demand Full Node services; see below:

**All Nodes:** [**https://www.allnodes.com**](https://www.allnodes.com/)

**Autostake:** [**https://autostake.com/**](https://autostake.com/)

**Hexxagon:** [**https://www.hexxagon.io**](https://www.hexxagon.io/)

**NOW Nodes:** [**https://nownodes.io**](https://nownodes.io/nodes)

If none of the providers above are a good fit, you can also check out the Terra Classic Foundation's Server Program. This program provides discounted RPC and REST access to select Terra Classic participants. This program was designed to subsidise costs for struggling Terra Classic developers so access to Full Nodes is not guaranteed.

**Terra Classic Foundation Server Program:** [**https://terraclassic.foundation/server-program**](https://terraclassic.foundation/server-program)


---

# Agent Instructions: 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:

```
GET https://docs.terraclassic.network/resources/full-nodes-infrastructure.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
