> 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/getting-started/what-is-umber.md).

# What is Umber

Umber is a virtual asset management platform built around one idea: **Asset-as-a-Service**. Instead of treating images, video, documents, and other digital assets as files that live in a folder or bucket, Umber treats each asset as a versioned service with its own stable identity and delivery URL.

This matters because the boundary between "digital" and "virtual" products keeps shrinking — gaming, e-commerce, virtual events, content platforms, and ordinary mobile apps all now depend on delivering the right asset, in the right version, to the right environment, instantly. Umber is built to be the layer that handles that for you, from the moment an asset is created to the moment it's retired.

## The problem with files

Managing assets as files creates a few recurring headaches:

* **Duplication.** The same asset gets copied into dev, staging, and prod environments, multiplying storage cost with every release.
* **Naming churn.** A new version of an asset either needs a new filename (so your code has to change) or overwrites the old one (so there's no history or rollback).
* **Manual coordination.** Updating an asset in production usually means a person — often someone in DevOps — manually renaming files and updating references across environments.

## The Umber approach

Umber addresses this with three core ideas, covered in depth under [Why Umber](/umber/why-umber/asset-as-a-service.md):

* **Asset-as-a-Service** — every asset is addressable by a stable URL that doesn't change when a new version is deployed.
* **Zero Redundancy** — a version isn't copied per environment; it's referenced.
* **Just-in-Time Experience** — deploying a new version to an environment is a few clicks (or one CLI command), with no file renaming and no code changes.

To see the core building blocks — Workspaces and Members, Environments, Virtual Assets, Virtual Collections, and Asset Types — head to [Concepts](/umber/concepts/workspaces-and-members.md). To get hands-on immediately, jump to the [Quickstart](/umber/getting-started/quickstart.md).


---

# 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/getting-started/what-is-umber.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.