> ## 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.

# Edge Infrastructure Services Overview

> An introduction to Edge Infrastructure Services: the service layer for managing nodes, applications, networks, and Kubernetes operations at scale.

## Introduction

Edge Infrastructure Services is the ZEDEDA service layer for managing and orchestrating distributed edge computing infrastructure. It provides EVE-OS (Edge Virtualization Engine) based node management, workload orchestration, network configuration, and ZEDEDA Edge Kubernetes Service operations, all from a single console.

Edge Infrastructure Services was previously referred to as ZEDEDA Cloud or ZedCloud.

## Prerequisites

* A ZEDEDA user account with an assigned role. See [Permissions and Visibility](https://zededa.mintlify.site/new-ui/start/permissions-and-visibility.md).
* A supported web browser.

## How It Works

Edge Infrastructure Services acts as the central management service for all nodes running EVE-OS in your enterprise. It manages the full lifecycle of nodes and the applications running on them.

The service is organized around three core concepts:

**Enterprise and projects:** An enterprise is your complete ZEDEDA environment. Within an enterprise, projects are logical groupings of nodes, applications, and policies, organized by geography, department, or business function. Each node belongs to exactly one project.

**Nodes:** A physical or virtual compute device running EVE-OS. Before onboarding, a device is referred to as an edge device. After onboarding, it becomes a node managed by Edge Infrastructure Services. The service enforces security policies, collects metrics, and maintains the node's configuration state.

**Applications:** Containerized workloads, virtual machines, and Kubernetes-managed applications deployed to nodes. Edge Infrastructure Services handles the full application lifecycle (deploy, update, monitor, and remove) without requiring on-site IT staff.

## Service Areas

The Infrastructure tab in the ZEDEDA console is organized into the following sections:

> [card] Start here
>
> Overviews, EVE-OS concepts, API and CLI reference.

> [card] Core infrastructure
>
> Nodes, clusters, projects, networks, datastores, and volumes.

> [card] Build and library
>
> App images, runtime bundles, and edge application types.

> [card] Applications and delivery
>
> Deploy and manage workloads, virtual networks, GitOps, and release management.

> [card] Operations
>
> Remote access, monitoring, logs, alerts, administration, Kubernetes, and integrations.

> [card] Partnerships
>
> Partner hardware and software resources.

## Key Capabilities

* **Zero-touch deployments:** Use tagging and policy-based assignment to automatically match nodes with their corresponding applications and configurations at scale.
* **Remote lifecycle management:** Deploy, update, and remove applications across your entire fleet from a central console, without physical access to devices.
* **Kubernetes at the edge:** Create and manage ZEDEDA Edge Kubernetes Service clusters from the same console, using either EVE-k nodes or imported third-party Kubernetes clusters.
* **Security by design:** Hardware root of trust via the Trusted Platform Module (TPM), measured boot, remote attestation, full disk encryption, and role-based access control are built into the platform.
* **API-first:** Every capability available in the console is also accessible through the ZEDEDA API, ZCLI, and the Terraform Provider for ZEDEDA Cloud.
* **Configuration drift prevention:** Centralized policies and the Configuration Lock feature ensure nodes stay in their intended state, even in intermittently connected environments.

## User Agents

Every capability in Edge Infrastructure Services is available through three user agents in addition to the console GUI:

| User agent | Description |
| - | - |
| Console GUI | The web-based ZEDEDA console. |
| ZCLI | A Docker-based command-line interface. Requires Docker Desktop. See [Get Started With ZCLI](https://zededa.mintlify.site/zcli-reference/get-started.md). |
| Terraform Provider | The Terraform provider for infrastructure-as-code workflows. See [Integrations and Automation](https://zededa.mintlify.site/new-ui/infrastructure-services/integrations-and-automation.md). |

All functionality is also available through direct API access. See [ZEDEDA API Overview](https://zededa.mintlify.site/new-ui/infrastructure-services/zededa-api-overview.md).

## Next Steps

> [card] [Quick Start](https://zededa.mintlify.site/new-ui/infrastructure-services/infrastructure-quick-start.md)
>
> Onboard your first node and deploy an application.

> [card] [ZEDEDA API Overview](https://zededa.mintlify.site/new-ui/infrastructure-services/zededa-api-overview.md)
>
> Explore API services, versioning, and how to access endpoint documentation.

> [card] [ZCLI Reference](https://zededa.mintlify.site/zcli-reference/get-started.md)
>
> Manage edge infrastructure from the command line using Docker-based ZCLI.

> [card] [EVE-OS Overview](https://zededa.mintlify.site/new-ui/infrastructure-services/eve-os/eve-os.md)
>
> Learn about EVE-OS architecture, variants, and image types.