Operations for standalone infrastructure

Kubernetes-grade operations.
Without the cluster.

Operate Docker workloads across any cloud, VPS or on-prem infrastructure — without Kubernetes, proprietary runtimes or infrastructure lock-in.

The missing operations layer

There is a lot between Docker Compose and Kubernetes.

Inside CCS Operations

Your entire operation, in one live view.

Explore a lightweight preview of the real CCS control plane. The data below is simulated.

Interactive preview
Simulated data

Keep the infrastructure simple. Upgrade the operations.

Understand the difference

CCS — Operate everything.

Four subsystems cover the whole lifecycle of a Docker server: prepare, ship, run and protect. They all run through the same CCS client and are operated from the same dashboard.

01

Implant

Prepare the host.

Optimizes the host and provides the server's security controls: hardening, compliance and connectivity.

  • Host optimization and tuning
  • Hardening and compliance checks
  • Security controls and SSH key management
  • Connectivity and edge protection (Traefik)
02

Runner

Ship your code.

CI/CD for standalone Docker. It detects your project, generates an explicit manifest and ships every version with health checks and rollback.

  • Wizard that detects runtime, port and health check
  • .deploy.yml manifest versioned with your code
  • Blue-green and canary without a cluster
  • Rollback to the previous version
03

DeployAlly

Run ready-made software.

A catalog of ready-made software. It runs third-party apps such as n8n, WordPress or Redis from templates and keeps every instance aligned with its manifest.

  • Deploy from catalog templates
  • Drift detection and correction
  • Upgrade to the latest template version
  • Container status per instance
04

BackupAlly

Protect what runs.

Protection built into operations. It runs workload backups, tracks their history and restores when you need it.

  • Full backups and quick directory backups
  • Run history and storage status
  • Restore to the target you choose
  • Backup coverage visible in the dashboard

DeployAlly Template Explorer

Install apps in a few clicks.

DeployAlly reads optimized, configurable templates and brings the application up ready on your server. Image, version, ports, volumes and health check are already defined: pick one, adjust what you need and publish.

  • Optimized templatesImage, ports, volumes and health check defined and tested for each application.
  • ConfigurableAdjust domain, environment variables and version before publishing.
  • Operations includedReady-made actions per app, like exporting n8n workflows, plus restart and stop.
  • Always alignedDrift detection and upgrades to the latest template version.

Cloud agnostic by design

Independent hosts, anywhere.
One operation.

AWS, Hetzner, DigitalOcean, OVHcloud or the server in your office. Each host runs the CCS client and connects from the inside out over mTLS: no open ports, no host depending on another, and all of them in the same operation.

AWS🇧🇷 São Paulo
production-01
CPU21%
RAM43%
7 containers
Hetzner🇩🇪 Germany
client-04
CPU18%
RAM39%
12 containers
DigitalOcean🇺🇸 New York
edge-02
CPU27%
RAM51%
5 containers
OVHcloud🇨🇦 Québec
backup-01
CPU12%
RAM33%
3 containers
On-prem Your office
office-01
CPU31%
RAM62%
4 containers
Socket · persistent mTLSHandshake · public endpoint
CCSControl plane
hosts
5
containers
31
average CPU
22%
healthy
5/5

Runner · CI/CD

From git push to production.

Push your code to GitHub (GitLab, Bitbucket, your own Git and local files are coming soon). On the server, Runner fetches the repository, reads .deploy.yml and runs the instructions, building or adjusting the image and putting the new container in production. The old one only leaves once the new one is healthy.

  • Any projectNode, PHP, Python, Go, Rust or any Dockerfile. No SDK, no framework.
  • Zero downtimeThe old container is only removed after the new one passes the health check.
  • Canary and blue-greenTraffic moves gradually to the new version, without a cluster.
  • Automatic rollbackIf the health check fails, the current version stays live and the candidate is discarded.
Project
Code source
  • GitHub
  • GitLabsoon
  • Bitbucketsoon
  • Own Gitsoon
  • Local filessoon
PushCode pushed to GitHub
FetchRunner pulls the repository
.deploy.ymlReads the project instructions
BuildBuilds or adjusts the image
ReleaseHealth check, canary and rollback
runner · github
$ git push origin main
→ github.com/acme/storefront  9e3779b  feat: one-click checkout
runner fetch  9e3779b
runner read   .deploy.yml · strategy: canary
runner build  npm ci && npm run build
runner start  storefront:v42 (candidate)
✓ health /health 200
runner route  traefik v42 weight 10
runner route  traefik v42 weight 50
runner route  traefik v42 weight 100
runner stop   storefront:v41
✓ v42 in production
storefront.acme.com
TraefikHost(`storefront.acme.com`)
Productionstorefront:v41removed0%
Candidatestorefront:v42healthcheck /health · 200 · approved100%
traefik · dynamic/storefront.ymlservices:
  storefront:
    weighted:
      services:
        - { name: v42, weight: 100 }

Plans

Start with visibility.
Add operations as you grow.

Every plan runs on the same control plane. Connect your hosts and see everything at no cost; when operations ask for more, turn on app installs, CI/CD with canary and rollback, and backup with recovery. No migrating infrastructure, no swapping tools, no rebuilding what is already running.

  1. 01
    See MonitorHost and container state, live metrics and alerts across every server. Free to start.
  2. 02
    Ship DeployInstall applications in a few clicks with DeployAlly and operate containers with health checks and rollback.
  3. 03
    Run OperateRunner with CI/CD, blue-green and canary: from git push to production with no downtime.
  4. 04
    Recover ProtectBackupAlly with scheduled backups, restore and disaster-recovery readiness for what matters.