# Coswarm > Coswarm turns your Linux servers into a Docker Swarm platform: deploys, domains with automatic HTTPS, databases and logs in one panel, free to self-host. Cosmo, its assistant, reads the cluster and proposes changes you approve. Website: https://coswarm.dev · Contact: contact@coswarm.dev · Built by Kints ## Install `curl -fsSL https://coswarm.dev/install.sh | bash` Run as root on a Linux server with Docker and a public IPv4 address. The script sets up Swarm, an encrypted overlay network named "cloud", the panel, the proxy and its database, and asks for a domain, a panel subdomain, how Let's Encrypt should check it, and the admin's email. Sign in over HTTPS and change the first password. ## Deployments: Ship an image. Swarm rolls it out. https://coswarm.dev/features/deployments Deploy from any registry, a Compose file or the marketplace. Replicas move to the new version one at a time, and every change is kept with who made it. - **No downtime by default.** Updates start the new replica before stopping the old one, one at a time, and pause if one fails. Set the failure action to rollback and Swarm goes back on its own. - **Compose, as Swarm runs it.** Paste a docker-compose file and get its services, volumes and networks. Keys Swarm cannot apply are listed as warnings instead of being dropped quietly. - **Every knob of a service.** Resources, ports, volumes, networks, secrets, placement, healthcheck, restart and update policy, DNS, sysctls and capabilities, from a form instead of a flag. - **A history you can read.** Each change becomes a version with its kind and author: a deploy, an env change, a scale. Cosmo compares any two, field by field. ### Where images come from - Public or private registries: Docker Hub, GitHub, GitLab, Quay, AWS ECR, Google and Azure registries, or your own. - A pasted Compose file, as one stack. - A marketplace template, with its volumes and secrets set up. ### Running an app - Replicated with a count, or global on every node. - Start, stop and restart; a terminal into any replica; a file browser inside its container. - Live CPU and memory, rollout state, and the incidents it has had. ### Many at once - Point several services at a new image or tag and roll them out together, with private registry credentials used. - Swarm Sync adopts services that already run on the server, without restarting them. ### With Cosmo Cosmo can deploy an image, scale, set environment variables, change resources, ports, networks and volumes, roll back to the previous spec, or install a whole Compose file as one change. Each one waits for your approval. ## Domains & edge: Domains with HTTPS, guarded at the edge. https://coswarm.dev/features/networking Coswarm’s own proxy routes every host to its service, gets certificates from Let’s Encrypt and filters traffic with Coraza and the OWASP Core Rule Set. - **HTTPS without thinking about it.** Certificates come from Let’s Encrypt by HTTP-01 or TLS-ALPN-01 and renew on their own. Upload your own instead when you have one; expiry dates are always in sight. - **A firewall per domain.** Coraza with the OWASP Core Rule Set. Choose from 14 rule groups per domain: SQL injection, XSS, remote code execution, scanners and more. - **Decide who gets in.** IP allowlists and blocklists, by address or CIDR, and basic auth. Requests from outside an allowlist are dropped without an answer. - **gRPC, TLS upstreams, Cloudflare.** Serve gRPC over h2c, talk HTTPS to the upstream, and read real client addresses when Cloudflare sits in front. ### Traffic you can see - Proxy logs you can search by host, address or path, filtered by status class. - A 24-hour traffic chart on the dashboard, with each deploy marked where it happened. - What the firewall dropped, counted. ### Routing - Each host goes to a service and its port; Swarm spreads requests over the replicas. - Subdomains under your panel’s domain, an HTTPS redirect per domain. - The proxy runs as its own service on ports 80 and 443. ### With Cosmo Cosmo can add, change and remove domains, summarise traffic for any window up to a week, and probe DNS, TCP or HTTP from inside an app’s container to find where a request stops. ## Databases: Your databases, in the browser. https://coswarm.dev/features/databases Connect to PostgreSQL, MySQL and Redis running beside your apps in one click, then query them, edit them and keep an eye on their keys. - **One click to what is running.** Databases already in the swarm show up ready to open. The password is read on the server and never passes through your browser. - **A query editor that keeps up.** Tabs, history, saved queries, EXPLAIN, and results paged on the server, exported as CSV or JSON. - **Edit with a seatbelt.** Edit rows in place. Statements that delete data ask first, and read-only connections are enforced by the server, not the button. - **Redis, too.** Browse keys by type, see and set TTLs, edit values, or use the console. ### Engines - PostgreSQL - MySQL, with MariaDB and Percona images recognised - Redis - TLS modes for connections outside the swarm ### With Cosmo Cosmo can find the databases running in the swarm, read their logs and resource use, and restart one that is stuck. It does not run SQL: that stays with you, on purpose. ## Observability: Know what broke before anyone asks. https://coswarm.dev/features/observability Live logs, incidents, traffic and findings the server spots on its own, with an Explain button wherever something went wrong. - **Findings, found for you.** The server notices a service down or short of replicas, failing tasks, the change made just before, certificates about to expire and a disk filling up. No model needed. - **Logs that follow along.** Live, with search, levels, highlights and a time range up to 30 days, per container or all together, exported as text, JSON or CSV. - **Incidents, with a timeline.** When an app goes down an incident opens, and closes when it recovers. Each app keeps its incidents and the history of its changes. - **Told where you already are.** Slack, Discord and Mattermost webhooks for deploys, starts and stops, an app going down, and approval requests. ### Explain, where it happened - A rollout that did not finish, a container killed for memory or a failed healthcheck, an error line, an incident: each has an Explain that opens Cosmo with the context filled in. ### Watches - Ask Cosmo to keep an eye on something: on a schedule from every 15 minutes to weekly, or when an app goes down. - Watches only read, and can post to your notification channels. ### And the rest - An audit log of who did what, filterable and grouped by day. - Container stats, inspect and logs. - The dashboard: services, CPU, memory, requests, error rate and firewall drops at a glance. ### With Cosmo Every finding on the dashboard opens its own conversation: Cosmo reads the tasks, the logs and the last change, says why, and puts the fix on the same card for you to approve. ## Marketplace: 65 self-hosted apps, one click each. https://coswarm.dev/features/marketplace Databases, analytics, developer tools, chat, media and more, as templates that set up the service, its volumes and its secrets on your own servers. - **22 categories.** From PostgreSQL and ClickHouse to Grafana, n8n, Gitea and Nextcloud, sorted so you find the one you came for. - **Secrets made for you.** Passwords a template needs are generated for you and marked as generated, so nobody ships admin123. - **Official images.** Templates point at the projects’ own images where they publish them. - **Or ask for anything.** Cosmo can search Docker Hub, read an image’s own documentation and set it up as one change. ### Databases & data - PostgreSQL, MariaDB, MongoDB, Redis, ClickHouse, ScyllaDB, YugabyteDB, InfluxDB, TigerBeetle - pgAdmin, Adminer, CloudBeaver, Hasura, NocoDB - SeaweedFS for S3 ### Observe & operate - Grafana, Prometheus, Netdata, cAdvisor, Jaeger, Telegraf, Uptime Kuma - Plausible, Matomo, Meilisearch - RabbitMQ, NATS, HashiCorp Vault ### Build & collaborate - GitLab CE, Gitea, Drone, Verdaccio, code-server - n8n, Wiki.js, DokuWiki, Redmine, OpenProject - Rocket.Chat, Element, Jitsi, Excalidraw, draw.io ### At home - Nextcloud, ownCloud, Jellyfin, Plex, Home Assistant - Bitwarden, Authelia, AdGuard Home, WireGuard ### With Cosmo Cosmo looks at what is already running before it reaches for Docker Hub, reads the image’s documentation for the settings it needs, and installs it as one plan with one approval. ## Automation: Deploys that run themselves. https://coswarm.dev/features/ci-cd A deploy token per app for your CI, a GitHub Action that uses it, updates rolled out in bulk, and Cosmo checking for newer images on any registry. - **A token that does one thing.** Each app can have a deploy token that redeploys it with a new image, and nothing else. Rotate or revoke it from the app. - **A GitHub Action, copied in a click.** The app page writes the workflow step for you with kintsdev/coswarm-deploy. Push a tag, and the new image rolls out. - **Bulk updates.** Move many services to a new image or tag and roll them out together. - **Swarm Sync.** Services created outside Coswarm are found every two minutes and can be adopted, and records that drifted from Swarm reconciled. ### Keeping up to date - Cosmo checks what your apps run against Docker Hub and any OCI registry: GitHub, Quay, Harbor and others. - A deploy, a redeploy, a start or a stop can post to Slack, Discord or Mattermost. ### Coswarm itself - The panel tells you when a new version is out, with its changelog, and updates its own services in one click. ### With Cosmo Ask Cosmo which apps run an old image, what a newer tag changes, or to keep a watch that tells you when something needs attention. ## Everything else in the panel ### Workloads - **Apps**: Swarm services with every setting, logs, a terminal, files and history. - **Compose**: Paste a compose file, get a stack; unsupported keys are listed. - **Bulk updates**: Many services to a new image or tag, rolled out together. - **Containers**: Standalone containers: create, logs, stats, inspect, exec, networks. - **Swarm Sync**: Adopt services made outside Coswarm; reconcile drifted records. - **Projects**: Group services by project, projects by workspace. ### Platform - **Domains**: Every host with its certificate, firewall and access rules. - **Images**: Who uses each image, cleaning up the rest, and Docker Hub search. - **Volumes**: What uses each volume, what sits idle. - **Secrets**: Swarm secrets, set once, never shown again, mounted from the panel. - **Networks**: Overlay networks, what is attached, and the ones Docker made. - **Registries**: Credentials for Docker Hub, GitHub, ECR, GitLab, Quay and more, with a login test. - **Database tool**: PostgreSQL, MySQL and Redis in the browser. - **Proxy logs**: Every request through the edge, searchable. - **Health checks**: HTTP probes with thresholds and latency, Coswarm’s own services included. ### On the server - **Console**: A root shell on the host, in the browser; every session logged. - **File manager**: The host’s files: browse, upload, edit, download. ### Administration - **Users & roles**: Custom roles with create, read, update and delete on each area. - **Approvals**: Four-eyes review for the areas you choose. - **Activity**: The audit log: who did what, from where, by day. - **Notifications**: Slack, Discord and Mattermost webhooks for the events you pick. - **Settings**: Panel domain, mail, integrations, Cosmo, node join tokens and one-click updates. - **Command menu**: Find any page, app or project from the keyboard. ## Cosmo, the assistant https://coswarm.dev/cosmo Cosmo lives in the panel. It reads apps, logs and history to explain what went wrong, and proposes changes that run only after a person approves that exact plan. It is off until an administrator turns it on. ### Where it shows up - **On the dashboard.** Each finding the server spots opens its own conversation. Cosmo’s answer becomes the “why”, its proposal the “fix”, approved on the spot. - **Where something went wrong.** A rollout that stalled, a container killed for memory, an error line, an incident: each has an Explain that opens Cosmo with the context filled in. - **Wherever you are.** A side panel on every page with ⌘J, its own page for long work, and “Ask Cosmo” in the command menu when a search finds nothing. - **While you are away.** Watches check on something every 15 minutes to weekly, or when an app goes down, and tell you in the panel or in Slack, Discord or Mattermost. ### Read tools (no approval) - Apps: list_apps, get_app, get_app_tasks, get_app_logs, get_app_stats, sample_app_stats, list_incidents, app_timeline, diff_app_versions - Cluster: get_swarm_overview, list_containers, get_container, get_container_logs, get_disk_usage - Images: list_local_images, search_images, list_image_tags, read_image_docs, check_image_updates - Platform: list_projects, list_volumes, list_networks, list_registries, list_secrets, list_domains, get_traffic, list_backups, list_backup_files, list_app_configs, list_approvals, open_in_panel ### Change tools (each approved) - Low risk: restart_app, probe_from_app, take_backup - Medium risk: scale_app, update_app_resources, update_app_ports, attach_app_network, attach_app_volume, set_app_env, rollback_app, create_app, install_compose, add_app_domain, update_app_domain, remove_app_domain, prune_images, delete_backup_file - High risk: deploy_image, delete_app, delete_volume ### Never, on purpose - No shell - No SQL - No writing files - No users or roles - No arbitrary HTTP ### Safety - **Secrets stay on the server.** Private keys, tokens, cloud and API keys, JWTs and password variables are masked before anything reaches the model. A value you paste becomes a placeholder the server fills in when the change runs. - **What it reads is data, not orders.** Logs and tool output are marked as untrusted, so a line in a log that says “ignore your instructions” stays a line in a log. - **Your permissions, twice.** Cosmo can do only what your role can. Permissions are checked when the plan is made and again just before it runs. It can never approve anything itself. - **A yes that expires.** An approval is a single-use token for you alone, bound to a hash of the plan, valid for ten minutes, five for high risk. If the app changed in between, nothing runs. - **Four eyes stay human.** In areas held for a second person, Cosmo does not make the change. It takes you to the page in the panel where the request goes through review. - **Limits you set.** Messages per minute per user, daily token budgets per user and in total, a read-only mode, and how long conversations and the change record are kept: 30 and 180 days by default. ### Models - OpenAI: Responses API, nothing stored - Anthropic: Extended and adaptive thinking - OpenRouter: Any model it carries - Ollama: On your hardware, no key - OpenAI-compatible: vLLM, LM Studio, LiteLLM… ### In the conversation - Edit a message or write a reply again, and move between versions - Slash commands and @ mentions of apps - Files and pictures attached to a message - Charts and live app cards in the answer - A plan it keeps for work in several steps - Subtasks in conversations of their own - Memory per user, and the administrator’s instructions - Replies run on the server and survive a reload - Pin, export as Markdown, share to read - Model and effort chosen per conversation ## Compared | | Coswarm | Kubernetes | Docker Swarm alone | |---|---|---|---| | Getting started | One line, a few questions | A cluster, an ingress, cert-manager, a dashboard… | docker swarm init, then the CLI | | What you learn | Apps, domains, projects | Pods, deployments, services, ingress, CRDs | Stacks and the Docker CLI | | Web panel | Built in | Add-ons | None | | HTTPS | Automatic, Let’s Encrypt | cert-manager | Up to you | | Web application firewall | Per domain, OWASP CRS | Add-on | Up to you | | Databases in the browser | PostgreSQL, MySQL, Redis | Separate tools | Separate tools | | Approvals and audit | Four-eyes areas, activity log | GitOps, admission policies | None | | AI assistant | Cosmo, every change approved | — | — | | Autoscaling | Not yet: replicas by hand | Horizontal and vertical | No | | Built for | A few servers to a mid-size fleet | Large fleets and many teams | Small setups run by hand | ## FAQ **What is Coswarm?** A self-hosted platform on Docker Swarm. It gives your own servers what a hosted platform gives you: deploys with rollouts, domains with automatic HTTPS and a firewall, a database tool, logs and a marketplace of apps, in one web panel. Cosmo, its assistant, can explain what went wrong and propose fixes you approve. **What do I need to run it?** A Linux server with Docker installed, root access, a public IPv4 address and a domain you can point at it. The install script sets up Swarm and everything else. More servers join as Swarm nodes with the token the panel shows you. **Is it really free?** Yes. Self-hosting Coswarm costs nothing, with every feature and no limits on apps, nodes or users. If your organisation wants help with setup, architecture or support, write to us. **Do I have to use Cosmo?** No. Cosmo is off until an administrator turns it on and sets up a model provider, and the panel works fully without it. You can also let it read only, so it explains but never changes anything. **Which models does Cosmo work with?** OpenAI, Anthropic and OpenRouter with your own key, Ollama on your own hardware, or any OpenAI-compatible server such as vLLM, LM Studio or LiteLLM. A model has to pass a check that it can call tools before it is used. Keys are stored encrypted and never sent back to the browser. **What does Cosmo send to the model provider?** Your messages and what Cosmo reads to answer them. Passwords, tokens and keys are masked before anything leaves the server, and values you paste become placeholders the server fills in, so the model never sees them. With Ollama, nothing leaves your network. **Can Cosmo break something?** Every change it proposes waits for your approval of that exact plan, and is checked against your role’s permissions twice. It deliberately has no shell, no SQL, no file writes and no user management. Deletes need the name typed out, and areas under four-eyes approval stay with people. **Do I need to know Kubernetes, or even Swarm?** No. Coswarm uses Swarm underneath and shows it as apps, domains and projects. If you know Swarm, every service setting is there when you want it. **I already run services on Swarm. Can Coswarm take them over?** Yes. Swarm Sync finds services created outside Coswarm and adopts them as a record, without restarting anything. **Can I deploy by pushing to git?** Coswarm deploys images, not source code. Build in your CI and deploy with the app’s deploy token: the panel writes a GitHub Actions step for you. **How do I update Coswarm?** The panel tells you when a new version is out and shows its changelog. One click updates its services. Releases are named by date, like v2026.10.24. ## Changelog **v2026.10.24.3** (Oct 24, 2026): Clearer nodes, a friendlier narrow sidebar - The dashboard shows real CPU and memory use for the panel’s node, and each node’s limit total in words, saying when it is more than the RAM. - With the sidebar narrow, each item shows its name and icon beside it on hover or focus. **v2026.10.24.2** (Oct 24, 2026): An operations dashboard - The server spots what needs looking at on its own: a service down or short of replicas, failing tasks, the change made just before, certificates and disks running out. - Open a finding and Cosmo says why, with its fix on the same card, approved from the dashboard. - Traffic over 1 hour, 24 hours or 7 days, with app changes marked where they happened. **v2026.10.24.1** (Oct 24, 2026): Meet Cosmo - Cosmo, an assistant in the panel: it reads apps, logs and history, explains what went wrong, and proposes changes that run only once approved. - Bring your own model: OpenAI, Anthropic, OpenRouter, Ollama or any OpenAI-compatible server. - Explain buttons wherever something goes wrong, watches that check on things for you, and a side panel on every page with ⌘J. - Four-eyes approvals for roles, users, apps, domains, secrets and settings, with a page for each request. - Each change to an app is kept as a version with who made it, and Cosmo compares any two field by field. - A database tool for the swarm, a Secrets page, a command menu, a rebuilt marketplace, and Coswarm’s new mark. **v2026.10.23.1** (Oct 23, 2026): A new panel - A new look across the panel: the app overview, logs and terminal, the file manager and the container page rebuilt. - App creation matches app editing, with WAF, networks and TTY. - The browser session moved into an HttpOnly cookie; permissions and deploy tokens tightened. - Requests from outside a domain’s IP allowlist are dropped without an answer. **v2026.08.26.2** (Aug 26, 2026): Security hardening - The host console requires authentication and the system update permission. - Each installation signs sessions with its own key; a password change ends open sessions. - Two-factor sign-in is bound to the password step, and sign-in is rate limited. **v2026.08.25** (Aug 21–25, 2026): Swarm Sync - Swarm Sync adopts services that already run on the server, and reconciles records that drifted. - Mail delivery rewritten, a clean-up for stopped Swarm containers, and the Turkish translation finished. **v2026.08.15.1** (Aug 15, 2026): Every service setting - The remaining Docker service settings, and real Compose syntax. **v2026.07.14.1** (Jul 11–14, 2026): Inside your containers - A terminal into any running replica, and a browser for the files inside its container. - Container and network management, and request timing at the proxy. **v2026.07.02.1** (Jul 2, 2026): Edit rows in place - Inline row editing in the database tool, and the real client address passed on to your apps.