# DIDComm Mediator

> A DIDComm Mediator is a messaging server that securely processes and forwards DIDComm messages between parties.

A DIDComm Mediator is a messaging server that manages access control, provides temporary message storage, and forwards messages to other mediators without accessing their content.

Recipients can fetch, decrypt, and verify messages sent to their DID using DIDComm libraries such as [DIDComm for Dart](/products/affinidi-elements/affinidi-messaging/integration-guides/didcomm-dart.md), [Meeting Place SDK for Dart](/products/affinidi-elements/affinidi-messaging/integration-guides/meeting-place.md), or [Mediator SDK for Rust](/products/affinidi-elements/affinidi-messaging/integration-guides/didcomm-rust.md).

## Supported Access Control Lists (ACLs)

The DIDComm Mediator server offers granular Access Control Lists (ACLs). These allow administrators to control which DIDs can send and receive messages within the network.

  [List of supported Access Control Lists for mediator and users](/products/affinidi-elements/affinidi-messaging/didcomm-mediator/supported-acls.md)

Important Note

You can only update DID-level Access Control Lists (ACLs) on self-hosted DIDComm Mediators.

## Mediator operating modes

As an administrator, you can adjust your mediator’s access control lists (ACLs) to operate in different modes, depending on how you want the mediator to manage access and handle messages transmitted across the network.

  [Different mediator configurations operating modes](/products/affinidi-elements/affinidi-messaging/didcomm-mediator/mediator-operating-modes.md)

Important Note

You can only configure the DIDComm Mediator into different modes when running a self-hosted instance.

## Deployment options

Choose a deployment option based on your infrastructure and operational requirements. Use Affinidi Portal for a fully managed instance with no infrastructure to maintain. Use AWS Marketplace to deploy into your own AWS account using a CloudFormation template. Use the open-source version for local development or to run on custom infrastructure.

      [

Affinidi Portal (Affinidi-hosted) →

Affinidi provides a fully managed, hosted DIDComm Mediator, a secure message relay service for decentralised messaging built on the DIDComm v2.1 protocol.

      ](/products/affinidi-elements/affinidi-messaging/didcomm-mediator/deployment-options/mediator-affinidi-portal.md)

      [

AWS Marketplace (self-hosted) →

DIDComm Mediator, published on AWS Marketplace, allows you to host the mediator in your AWS account using the CloudFormation template.

      ](/products/affinidi-elements/affinidi-messaging/didcomm-mediator/deployment-options/mediator-aws-marketplace.md)

      [

Open source (self-hosted) →

Affinidi provides an open-source DIDComm Mediator implementation based on the DIDComm v2.1 protocol.

      ](/products/affinidi-elements/affinidi-messaging/didcomm-mediator/deployment-options/mediator-open-sourced.md)

## What’s next

  [Explore Meeting Place, an implementation of Affinidi Messaging](/products/affinidi-elements/affinidi-messaging/meeting-place.md)

  [Explore different mediator deployment options](/products/affinidi-elements/affinidi-messaging/didcomm-mediator/deployment-options.md)

  [Test the mediator connection](/products/affinidi-elements/affinidi-messaging/didcomm-mediator/test-mediator-connection.md)

## Pages in this section
- [Deployment options](/products/affinidi-elements/affinidi-messaging/didcomm-mediator/deployment-options.md): Deployment options for the DIDComm Mediator.
- [Mediator operating modes](/products/affinidi-elements/affinidi-messaging/didcomm-mediator/mediator-operating-modes.md): DIDComm Mediator operating modes and their configuration.
- [Supported Access Control Lists (ACLs)](/products/affinidi-elements/affinidi-messaging/didcomm-mediator/supported-acls.md): List of supported access control lists (ACLs) of DIDComm Mediator.
- [Test mediator connection](/products/affinidi-elements/affinidi-messaging/didcomm-mediator/test-mediator-connection.md): Test your mediator server after deployment.