Getting Started•5 min read•Basics

Core Concepts & Simple Terms

Understand the core building blocks of CIEL using everyday analogies without getting lost in complicated DevOps jargon.

To feel right at home with CIEL, let's explore its core building blocks using straightforward analogies:


1. Host (Target Computer / Server)

A Host is any computer, virtual machine (VPS), or network appliance you manage.

  • Examples: Production Web Server (203.0.113.10), Internal Database (10.0.0.5), or a Remote MikroTik Router.
  • Every host is registered with its IP address, port, remote SSH username, and assigned SSH key or credentials.

2. Inventory (Server Group) & Target Scope

An Inventory is a logical group that organizes multiple hosts together based on environment, service role, or infrastructure tier.

  • Multiple Hosts in One Inventory: Instead of targeting servers individually, an inventory bundles multiple machines into a single collective group:
    • Production Fleet: Groups prod-web-01, prod-web-02, and prod-api-01.
    • Database Cluster: Groups db-primary and db-replica-01.
    • Staging Sandbox: Groups non-production test and staging machines.
  • Target Scope at Execution: When running a playbook, configuring a Saved Run, or creating an inbound webhook, CIEL asks for your Target Scope:
    • By Inventory: Target an entire pre-configured group (with optional granular filtering to include or exclude specific nodes).
    • Direct Hosts: Target one or more individual servers ad-hoc without needing to create an inventory.

3. Playbook / Tasks (Step-by-Step Recipe)

A Playbook is an ordered recipe of actions you want CIEL to execute across your servers.

  • Structure of an automation run:
    1. Step 1: Update system package repositories.
    2. Step 2: Install the NGINX web server package.
    3. Step 3: Configure SSL certificates.
    4. Step 4: Ensure services are enabled and running.
  • You can create, edit, and validate recipes directly in your browser using the built-in Monaco Editor.

4. Variable Sets (Reusable Settings Box)

Variable Sets are reusable packages of configuration values attached across servers, inventories, or playbooks.

  • Examples: Domain name (example.com), application port (3000), or release version (v2.4.0).
  • Updating a value in a Variable Set propagates the change to all attached runs automatically.

5. SSH Keys & Secret Variables

CIEL protects sensitive credentials with authenticated encryption:

  • SSH Keys: Centrally managed key pairs assigned to servers via dropdown.
  • Secret Variables: Mark sensitive variables as secret to encrypt them at rest with AES-256-GCM.
  • When tasks execute, secrets are kept strictly in volatile memory and automatically masked (******) in live terminal output streams.

6. Unified Storage & Git-Friendly Workspaces

CIEL organizes project data in a clean directory structure per workspace:

  • Playbooks: YAML recipes authored in the web editor.
  • Roles: Modular task packages and reusable Ansible roles.
  • Templates: Dynamic Jinja2 template files (.j2).
  • Files: Static assets (nginx.conf, systemd service files, shell scripts) copied to target servers.

7. Control Interfaces: Browser, CLI, Webhooks & MCP

You can interact with CIEL through multiple specialized interfaces:

  • Web Dashboard: Visual control plane with real-time WebSocket diff streaming and run history.
  • CLI (ciel): Standalone binary for system diagnostics, user management, and daemon lifecycle.
  • Inbound Webhooks: Secure CI/CD triggers for automated deployments from GitHub Actions or GitLab.
  • Model Context Protocol (MCP): Native stdio server connecting AI coding agents (Claude Code, Cursor, Hermes) with zero-trust safety tiers and local Ansible linting.

Summary Workflow

text
[ 1. Register Hosts & Group into Inventories ]
                         |
[ 2. Select Playbook & Target Scope (By Inventory / Direct Hosts) ]
                         |
[ 3. Click RUN! CIEL executes tasks in parallel across targeted nodes ]

8. External References

For foundational concepts and upstream standards: