website-and-documentation/content/en/docs/components/deployments/edgeconnect/_index.md

title	linkTitle	weight	description
EdgeConnect	EdgeConnect	20	Secure connectivity solution for edge devices and environments

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

• Jira Ticket: TICKET-6734
• Assignee: Waldemar
• Status: Draft
• Last Updated: 2025-12-16
• TODO:
  • Add detailed component description
  • Review and finalize content {{% /alert %}}

Overview

EdgeConnect is a custom cloud provided by the project as a whole. It has several goals, including retaining sovereign control over cloud compute resources, and supporting sustainability-aware infrastructure choices.

While EdgeConnect is managed outwith our Edge Developer Platform, we have produced a number of tools to facilitate its use and broaden its applicability. These include an SDK, command-line client, and bespoke provider for Terraform.

Key Features

• Managed by broader project, not specifically EDP
• Focus on sovereignty and sustainability
• EDP supplies tools such as CLI and Terraform provider
• Primary EDP products such as Forgejo are hosted on OTC rather than EdgeConnect

SYSTEM IS NOT ACTUALLY DEPLOYED HERE JUST RUNNERS, CODER, individual components

Purpose in EDP

Working with EdgeConnect allows us to ensure our work supports that of our colleagues, ultimately leading to a platform that is as broadly and deeply usable as possible. By working in a sovereign system we are encouraging European development, while sustainability features are offered by very few other clouds. It also gives us possibilities to work closely with other teams, ensuring both teams' work is better than would be possible otherwise.

Access

• Gardener console access
  • Choose Log in with mg3 then platform before entering credentials set up by the Platform Team.
• Edge cluster
• Orca cluster

Notes

Documentation for Edge Connect is provided using other systems, including Confluence.