> 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/asset-as-a-service.md). # Asset-as-a-Service Umber is built around Asset-as-a-Service (AaaS) — treating every asset as a service endpoint rather than a file sitting in storage. This reframing solves two practical problems directly: * **Same filename, multiple versions.** Umber can manage multiple versions of an asset even when they share an identical filename, and still resolve the correct version on delivery — no manual renaming required. * **Environment-scoped releases.** You can release a specific version into one environment while keeping it restricted from others, giving you controlled, environment-by-environment rollout instead of an all-or-nothing file swap. Together with [Zero Redundancy](/umber/why-umber/zero-redundancy.md) and [Just-in-Time Experience](/umber/why-umber/just-in-time-experience.md), this is what lets Umber treat "deploying an asset" the same way you'd think about deploying code. --- # 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/asset-as-a-service.md?ask=&goal= ``` `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.