---
title: "Platform Overview"
linkTitle: "Platform Overview"
weight: 10
description: >
  High-level overview of the Edge Developer Platform (EDP), its purpose, and product structure.
---

{{% alert title="Draft" color="warning" %}}
**Editorial Status**: This page is currently being developed.

* **Jira Ticket**: TBD
* **Assignee**: Team
* **Status**: Draft - Initial structure created
* **Last Updated**: 2025-11-16
* **TODO**:
  * [ ] Add detailed product structure from excalidraw
  * [ ] Include platform maturity matrix
  * [ ] Add links to component pages as they are created
{{% /alert %}}

## Purpose

The Edge Developer Platform (EDP) is a comprehensive DevOps platform designed to enable developers to build, deploy, and operate cloud-native applications at the edge. It provides an integrated suite of tools and services covering the entire software development lifecycle.

## Target Audience

* **Developers**: Build and deploy applications using standardized workflows
* **Platform Engineers**: Operate and maintain the platform infrastructure
* **DevOps Teams**: Implement CI/CD pipelines and automation
* **Auditors**: Verify platform capabilities and compliance

## Product Structure

EDP consists of multiple integrated components organized in layers:

### Core Platform Services

The foundation layer provides essential platform capabilities including source code management, CI/CD, and container orchestration.

### Developer Experience

Tools and services that developers interact with directly to build, test, and deploy applications.

### Infrastructure & Operations

Infrastructure automation, observability, and operational tooling for platform management.

## Platform Maturity

Components in EDP have different maturity levels:

* **Production**: Fully integrated and supported for production use
* **Beta**: Available for testing with potential changes
* **Experimental**: Early stage, subject to significant changes

## Getting Started

For quick start guides and onboarding information, see the [Getting Started](../getting-started/) section.

For detailed component information, explore the [Components](../components/) section.