---
title: Asset Hub
slug: edgemanager/lem-user-guide/manage-assets/asset-hub
docTags: 
createdAt: 2026-09-21T12:07:07.088Z
---

Asset Hub is a centralized catalog that lets Litmus host, version, and distribute Industrial Internet of Things (IIoT) assets, such as AI/ML models, configuration templates, and application packages. Litmus Edge Manager (LEM) connects to this catalog to browse, import, and deploy these assets to edge devices, instead of requiring manual coordination between platform engineering and operations teams.

## Why this matters

Deploying a new model or driver to edge environments requires significant coordination between platform engineering and operations teams. You cannot currently discover, browse, or deploy Litmus-provided Digital Twins models, such as OPC UA companion specifications or maintenance schemas, from within LEM. Litmus also has no visibility into which models are actually adopted across devices.

Asset Hub addresses this by giving you a catalog you can browse and deploy from directly, without custom modeling or manual file import, and by giving Litmus visibility into model adoption in real time.

Two groups of users benefit most:

- **Plant or site operators** with the administrator role, who need to deploy standard asset models across edge devices without custom engineering.
- **Solutions architects and systems integrators** who want Litmus-certified models as a starting point for customer deployments.

## Core components

- **Litmus Central Portal:** The cloud service that hosts the Asset Hub catalog. Each catalog asset lists its name, version, vendor, tags, and the range of Litmus Edge versions it supports, for example Litmus Edge 4.0.10 and later. A single catalog asset can bundle more than one Digital Twins model.
- **Client ID/Client Secret:** An administrator connects LEM to Litmus Central Portal from the LEM Admin Console, under **Integration** > **Litmus Central Portal**, using a **Client ID** and **Client Secret** issued for your account in Litmus Central Portal. Each LEM instance needs its own client, and an account can have up to 10 active clients at a time.
- **Litmus Edge Manager:** LEM shows the asset catalog inside the app, with an **Import from Asset Hub** action on pages such as Digital Twins models. LEM downloads and checks each asset, then deploys it to edge devices.
- **Edge device:** The edge device receives the model from LEM, checks it, installs it, and reports the result back to LEM.

## How the components work together

When Litmus publishes a new or updated asset, Litmus Central Portal makes it available in the catalog.

LEM connects securely to Litmus Central Portal and then loads the live catalog. You can then browse or search the catalog, import an asset into LEM, and deploy it to one edge device or a device group. The edge device checks the asset before installing it and reports the result back to LEM, which passes the import and deployment details back to Litmus Central Portal.

Deployment works for a single device, multiple devices, or a device group, and LEM shows the status for each device as the deployment runs.

![Asset hub architecture](https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/cklu5LXWBMRL8NrYMexzd_assethubarch-2.png)

Litmus Central Portal holds the complete catalog. Edge devices can't share assets directly with each other. You can view, deploy, and clone an imported model inside LEM, but can't edit it. This keeps a clear link back to the original asset and its version history. If you clone a model, the clone becomes independent and no longer has that link to Litmus Central Portal.

## Operational model

LEM keeps a connection to Litmus Central Portal while it is running. If the connection is lost:

- The Asset Hub catalog is hidden, so operators cannot browse or import new assets.
- Assets already deployed to edge devices continue running, unaffected by the lost connection.
- Assets already imported into LEM stay visible and usable.
- The catalog reappears automatically once the connection is restored.

The following diagram shows the process flow from Asset Hub to the asset hierarchy.

![Asset Hub to asset hierarchy process flow](https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/_oQWU1YjfYN8jMrLD0H5I_assethub-assethierarchy.png)

Deployment works for a single device, multiple devices, or a device group, with the status for each device shown as the deployment happens.

## Roles and permissions

Asset Hub uses roles to control which users can deploy which assets.

- **Admin:** Full access. Can browse the catalog, import models, and deploy them to edge devices.
- **Viewer:** Read-only. Can view imported models, but can't import or deploy them.

## Next steps

- Connect Litmus Central Portal
- Asset hierarchy