> For the complete documentation index, see [llms.txt](https://vaulta.gitbook.io/vaulta-guides/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vaulta.gitbook.io/vaulta-guides/networks/network-resources.md).

# Network Resources

In order to begin engaging with [Vaulta Native](/vaulta-guides/user-guides/getting-started-on-vaulta.md), it helps to have an understanding of how transactions are powered on the network. Vaulta utilizes a resource-based model, which is more efficient and cost effective than gas fees used by other networks. 

## **CPU (Processing Power)**

CPU is used when your account runs a transaction (like sending tokens or using an app). CPU is rented alongside NET using the PowerUp model.

## **NET (Network Bandwidth)**

NET is used to send data across the network when you interact with apps or other users. NET is rented alongside CPU using the PowerUp model. 

## **RAM (Storage, Decentralized State Data)**

RAM is used to store persistent blockchain data including account information and smart contract data. Unlike CPU and NET, RAM is not rented but bought and sold on a free market.

## How do I get more Resources? 

The following guides will walk you through managing resources in the Vaulta portal:

* [Managing Resources (CPU/ NET)](/vaulta-guides/user-guides/getting-started-on-vaulta/manage-resources-cpu-net.md)
* [Buy/ Sell RAM](/vaulta-guides/user-guides/getting-started-on-vaulta/buy-sell-ram.md)

## Benefits of a Resource-Based Model

Unlike Ethereum where every transaction has a gas fee, Vaulta uses a **resource-based model** — which keeps things **cheaper and more flexible**.

Our resource-based model offers:

💸No surprise fees\
🚫 No bidding wars to get your transaction confirmed\
🌱 A solution that is more efficient for developers and users

## Takeaway

Vaulta's resource model is designed to maximize efficiency, scalability, and user control. 

| Resource | Access Method                                                                                          | Used For                        | Notes                               |
| -------- | ------------------------------------------------------------------------------------------------------ | ------------------------------- | ----------------------------------- |
| CPU      | [Rented via PowerUp](/vaulta-guides/user-guides/getting-started-on-vaulta/manage-resources-cpu-net.md) | Executing transactions          | Fee-based, 24-hour rental           |
| NET      | [Rented via PowerUp](/vaulta-guides/user-guides/getting-started-on-vaulta/manage-resources-cpu-net.md) | Transmitting data               | Typically bundled with CPU          |
| RAM      | [Purchased on market](/vaulta-guides/user-guides/getting-started-on-vaulta/buy-sell-ram.md)            | Storing data, creating accounts | Price fluctuates with market demand |

## Resources


---

# 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://vaulta.gitbook.io/vaulta-guides/networks/network-resources.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.