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

# Zero Redundancy

An asset typically gets copied many times on its way from idea to production: a designer saves versions locally, the file gets committed to a version-control system once it reaches engineering, QA keeps its own copy to avoid stepping on the dev team's changes, and production holds the final live copy. Every one of those copies costs storage, and the cost compounds with every release — by our estimate, most teams pay 30–40% more in cloud storage costs than necessary, just to keep redundant copies of assets around.

Umber avoids this by not copying a version even when it's deployed across multiple environments. An environment doesn't get its own copy of a file — it gets a pointer to the version it should serve. That makes Umber meaningfully more storage-efficient than typical cloud storage or file-based digital asset management systems, especially as the number of environments and releases grows.


---

# 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://umber.gitbook.io/umber/why-umber/zero-redundancy.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.