> ## Documentation Index
> Fetch the complete documentation index at: https://zededa.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Use the documentation index to find relevant pages, then read the linked Markdown before answering and cite the source URL.
> Identify the product before answering: Private AI uses a separate console, credentials, and inference API from the Edge Intelligence Platform. Do not apply instructions from one product to the other.
> Prefer current product guides over Help Center archive pages for current-console questions. Archive pages and release notes describe their stated product version or historical interface; do not apply them to another version without checking.
> Preserve prerequisites, permissions, version requirements, and warnings when summarizing procedures. Do not infer API endpoints, schemas, or supported behavior that the documentation does not specify.

# Manage App Instances with the Local Profile Server

> Enable the Local Profile Server (LPS) on a node network adapter to allow local configuration changes without cloud connectivity.

# Manage App Instances with the Local Profile Server

The Local Profile Server (LPS) is a per-network-port toggle that allows a local operator to make limited configuration changes to a node adapter directly on the device, without requiring connectivity to Edge Infrastructure Services. When LPS is enabled on a port, a local operator can adjust that port's configuration using the LPS endpoint on the device. When LPS is disabled, the port follows only the cloud controller configuration, and any local override is reverted.

LPS is particularly useful for remote sites where network connectivity to the cloud controller might be intermittent. By keeping a management port accessible locally, a site technician can restore connectivity without needing access to the cloud controller.

## How It Works

The LPS toggle is a per-adapter setting on each network port. When enabled, the port's configuration source can be reported as **LPS** (meaning a local override is active) rather than **Controller**. The **Network Environment** tab on the node detail page shows the current configuration source for each port.

### Configuration source values

| Source | Meaning |
| - | - |
| **Controller** | Configuration is applied from Edge Infrastructure Services. |
| **Bootstrap** | Configuration was set during initial bootstrapping. |
| **Override** | A local override is active. |
| **LPS** | Configuration was applied via the Local Profile Server. |
| **Last Resort** | The node is using its last-resort configuration (cloud unreachable). |
| **TUI** | Configuration was set using the text user interface on the device. |

## Enable LPS on a Network Adapter

1. In the sidebar, select **Infrastructure > Fleet > Nodes**.
2. Select the node name to open the node detail page.
3. Select the **Adapters** tab.
4. In the Network Adapters section, locate the adapter you want to enable LPS on.
5. Toggle **Local Port Config (LPS)** on for that adapter.
6. Select **Save**.

The interface displays a warning when you disable LPS: disabling reverts the adapter to cloud configuration, overriding any active local setting.

## Enable LPS During Node Onboarding

LPS can also be enabled during the Zero-Touch or Manual Onboarding wizard when configuring network ports in the network configuration step. Toggle **Local Port Config (LPS)** on for any port that should allow local management.

## Check the LPS Configuration Source

1. Open the node detail page.
2. Select the **Adapters** tab.
3. Select the **Network Environment** sub-tab.
4. Review the **Source** column for each adapter to confirm the current configuration origin.

## Use Case: Graceful Shutdown with a UPS

For nodes connected to an uninterruptible power supply (UPS), LPS enables a local operator or UPS management system to initiate a graceful shutdown when power loss is detected.

When connectivity to Edge Infrastructure Services is unavailable, the local operator can use the LPS endpoint to trigger the **Prepare Power Off** action. This gracefully stops all application instances on the node before power is removed.

After power is restored, the node restarts and all previously running application instances return to their previous state automatically.

To initiate Prepare Power Off from the console (when connectivity is available):

1. Open the node detail page.
2. Select **More actions** from the header action menu.
3. Select **Prepare Power Off**.
4. In the confirmation dialog, select **Prepare Power Off** to confirm.

## Use Case: Managing Node Profiles Locally

LPS allows local management of port configuration without cloud access. This is useful in the following scenarios:

* Remote sites with unreliable WAN connectivity.
* Maintenance scenarios where a technician needs to adjust network settings on-site.
* Environments with strict network policies that block management traffic during certain windows.

When a local override is active, the Network Environment tab shows **LPS** as the configuration source for the affected adapter.

## Next Steps

> [card] [Configure Node Adapters](https://zededa.mintlify.site/new-ui/infrastructure-services/nodes/configure-node-adapters.md)
>
> Configure network and hardware adapters on nodes.

> [card] [Manage Node Lifecycle](https://zededa.mintlify.site/new-ui/infrastructure-services/nodes/manage-node-lifecycle.md)
>
> Handle node activation, deactivation, reboot, and deletion.