# Docker Swarm deployments

URL: https://openship.io/features/docker-swarm

Use your existing Swarm manager as an OpenShip deployment destination.

Deploy new applications and Compose services through a connected Docker Swarm manager. Keep environment settings, build history, logs, replica changes and rollbacks in the same OpenShip workflow.

Connect an existing manager, review its identity and select the registered Swarm as a project destination. Stateless services can use replicas across eligible Linux nodes. Named-volume services stay pinned to the manager to preserve their node-local data.

Connecting a manager preserves its existing stacks. This path does not support existing-stack adoption, node administration or distributed Swarm storage. Replacement can interrupt a service; review the deployment guide before moving production traffic.

## Native Swarm services

Deploy supported application and Compose workloads through the manager.

## Replica controls

Set stateless service instance counts and inspect observed task state.

## Shared operations

Use the existing deployment, environment, log and rollback workflows.

Cluster management is available from self-hosted and desktop controllers on registered Linux servers.

[Read the guide](https://openship.io/docs/guides/mcp-clusters-and-scaling#existing-docker-swarm)
