Getting Started•5 min read•Start Here

What is CIEL?

Understand CIEL in simple terms: a single-tenant, self-hosted web control plane that gives you a universal remote control for all your Linux, Windows, and network servers without the enterprise bloat.

Managing multiple servers typically involves choosing between two extremes:

  1. Ad-hoc Terminal Loops: Running bash for IP in $SERVERS; do ssh root@$IP ... loops across multiple terminal tabs. A single dropped connection mid-loop can leave package managers locked and the cluster in an inconsistent, partially updated state.
  2. Heavyweight Enterprise Platforms: Tools like Ansible AWX or Tower require dedicated Kubernetes clusters, database operators, and gigabytes of memory overhead simply to run basic playbooks.

CIEL provides a lightweight middle ground: a self-hosted control plane running as a single binary that consumes approximately 150MB - 200MB of RAM idle, providing real-time visual execution and fleet management for Linux, Windows, and network infrastructure.

CIEL Workspace Dashboard Overview with Managed Hosts and Automation Shortcuts

1. How Does CIEL Work?

CIEL acts as a centralized command center for your entire infrastructure:

  • Register your servers once: Enter host IP addresses and assign SSH keys or credentials. No software needs to be installed on target machines.
  • Select your task: Choose a pre-built recipe or author an Ansible playbook (system updates, NGINX setup, security patches).
  • Hit Run: CIEL connects to all targeted servers in parallel, executes tasks, and streams color-coded, line-by-line output to your browser over WebSockets.
Interactive Architecture Diagram(Mermaid)
Rendering diagram...

2. 100% Agentless Architecture

CIEL requires zero background daemons or proprietary agents on target servers.

Target servers do not need another mystery binary running as root, consuming CPU cycles, or introducing security risks. Communication relies entirely on standard protocols already baked into modern operating systems:

  • Linux & BSD (Ubuntu, Debian, RHEL, Rocky, Alpine): Standard OpenSSH over Port 22.
  • Windows Server: Native WinRM over HTTPS (Port 5986) with PowerShell remoting.
  • Network Devices: MikroTik RouterOS and Cisco switches via SSH.

If you can SSH into a machine from your laptop, CIEL can orchestrate it. If you ever decide to stop using CIEL, there are zero leftover agent processes to clean up.


3. Real-World Scenario: The 2:00 AM CVE Fire Drill

To understand why CIEL matters, look at what happens during an actual infrastructure emergency.

The Situation: It is Tuesday night. A critical vulnerability drops - for example, CVE-2024-8926 (the high-severity PHP-CGI parameter injection flaw that bypassed CVE-2024-4577) or CVE-2024-6387 (the unauthenticated OpenSSH regreSSHion race condition allowing remote root execution). Scanners and automated exploit scripts are already hitting your public IP ranges.

You have 45 production servers across Hetzner, AWS, and private Proxmox nodes that need an immediate patch or a configuration mitigation.

Without CIEL:

  • Open multiple SSH sessions or run an unbuffered bash loop.
  • One server hangs on an apt lock; another has a stale DNS entry; a third drops SSH mid-download.
  • Operators must manually inspect ssh -V or php -v on every single IP address to confirm patch status, risking forgotten nodes.

With CIEL:

  1. Open the relevant security patch playbook in CIEL.
  2. Select the target inventory group (e.g. webservers or all-nodes).
  3. Click Execute Now.
  4. CIEL dispatches isolated parallel runner workers across all target hosts simultaneously.
  5. In your browser, the live WebSocket terminal streams output line-by-line. The Host Summary Matrix provides a clear status grid showing [OK] and [CHANGED] results.
  6. The intra-line diff inspector displays the exact configuration lines updated in /etc/ssh/sshd_config or /etc/php/8.2/fpm/php.ini.

4. Why CIEL vs The Alternatives?

DimensionManual SSH ScriptsAnsible AWX / TowerCIEL Controller
Resource Footprint0MB (Local laptop)8GB - 16GB RAM (Kubernetes required)~150MB - 200MB RAM (Single standalone binary)
Setup Time0 minutesComplex Helm charts and operator configsAbout 60 seconds (ciel start)
Execution FeedbackRaw unformatted terminal textPolling interface with delayed logsReal-time WebSocket ANSI streaming with live diffs
Credential SecurityPlaintext keys in ~/.ssh/Heavy enterprise credential pluginsAES-256-GCM encrypted vault with memory injection
Concurrency & MutexNone (Prone to race conditions)Complex queue configurationsBuilt-in cron overlap protection and job queues
Disaster RecoveryNone (Accidental deletion is permanent)Full database snapshot restore neededBuilt-in Recycle Bin with 1-click restore

5. External References

For upstream specifications, protocol details, and security advisories: