---
question: "Where does a module keep the files its apps and templates use?"
kind: overview
---

# Assets

An asset is a file a module ships that is not code: a logo, an agent's avatar, an image an app shows, or a template that a Nexus section starts from. Agents and apps point at assets; the engine never imports them.

<!-- matrix -->

## Key concepts

- **Files an app shows.** Images, scripts and styles go in the app's own folder, `apps/<name>/`. The module serves them with the app, under `/app-html/remote/<module_id>/<name>/`, to the users of a workspace that turns the app on. The page points at them with relative URLs (`img/logo.png`).
- **App icon.** An app's manifest sets `icon_emoji`, which Nexus shows in the apps list.
- **Template trees.** Seeds for Nexus Slides, Documents and Sheets: a folder of `<id>.html` files plus an optional `catalog.json`. ABI's own are served as `abi/<id>`. A deploy adds more under a namespace of its own with `slides_template_sources`, `documents_template_sources` or `sheets_template_sources` in `nexus_config`.
- **The public mount.** The API serves `assets/public/` at `/modules/<module path>/assets/public/<file>` for the marketplace modules it loads, with no API key: `naas_abi_marketplace.domains.intelligence` serves `/modules/naas_abi_marketplace/domains/intelligence/assets/public/osint-researcher.png`. Your modules' files are not served there.
- **No agent avatar.** A module publishes an agent with an `AgentDescriptor`: a name, a description and its capabilities. There is no avatar field yet. For a workspace logo in the `config.yaml` seed, use a full `https://` URL.
- **Not artifacts.** An asset is a file a module ships. [Artifacts](/capabilities/build/artifacts/overview), things you author inside a module, are coming soon.

The place of assets among a module's parts is on [Overview](/architecture/overview#what-a-module-contains).
