> For the complete documentation index, see [llms.txt](https://docs.nuvolos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nuvolos.com/concepts/nuvolos-basic-concepts/resting-spaces.md).

# Resting Spaces

During a Space's lifecycle, you will often have periods when you don't need to access the data, but you still want to keep it available on Nuvolos for future use. The **resting** feature reduces storage costs by moving data you do not currently need to a more affordable storage class. When you are ready to work with it again, a single click brings it back to the high-performance Nuvolos Filesystem.

A Space can be in one of five states:

* **Live** - the normal state. Files are stored on the Nuvolos Filesystem and ready to use.
* **Pre-resting** - the Space meets the criteria to be rested within 24 hours. Files are still accessible. Starting any Application returns the Space to Live.
* **Entering Rest** - a brief transitional state (a few minutes) while data is moved from pre-resting to rested. No actions are allowed during this time.
* **Resting** - data has been moved to cost-effective resting storage. You can still download or distribute files through a snapshot, but you cannot run Applications.
* **Waking** - data is moving back from resting storage to the Nuvolos Filesystem. This can take from a few minutes to several hours, depending on data volume and type.

Resting is configured at the organisation level by organisation managers, in coordination with Nuvolos support.


---

# 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.nuvolos.com/concepts/nuvolos-basic-concepts/resting-spaces.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.