> For the complete documentation index, see [llms.txt](https://docs.bitsafe.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bitsafe.finance/product-suite/decentralization-manager/architecture-overview.md).

# Architecture Overview

The Decentralization Manager runs as an HTTP server with an embedded React frontend. Multiple instances coordinate with one another over the Noise Protocol Framework to perform multi-party operations on Canton network deployments.

## Core concepts

Coordinator: the instance that initiates workflows and orchestrates multi-party operations.

Peers: instances that respond to coordinator commands, sign proposals, and execute local operations.

Automatic key management: Noise keypairs are generated automatically on first run.

## Communication protocol

Instances communicate over the Noise Protocol Framework, which provides encrypted coordinator-to-peer messaging. The coordinator listens on a Noise port (default 9000) while serving the management UI over HTTP (default 8080). Peers are configured with each other's connection details, and the coordinator orchestrates key generation, topology proposals, multi-party signing, and submission to Canton.

## Technical constraints

Each node requires access to Canton participant nodes via the Admin API and Ledger API. Configuration is supplied through DECPM\_\* environment variables or CLI arguments. Peer and party state is persisted in a local SQLite database, and the interactive API reference (Swagger UI) is only mounted in development and test builds, not in the shipped release image.