Skip to content

Manage devices as code

Manage every device configuration in version-controlled files, push changes through pull requests, and roll back any configuration from your repo using Iru's Enterprise API and GitHub integration.

02-Pipe Data-2

What is Config as Code (CaC)?

"Config as code" (CaC) means managing system configurations in version-controlled files instead of a UI. Every change is a commit with full history, a pull request for review, and a record of who changed what and when.

Deploy endpoint configurations with Config as Code

01-Automation-May-15-2026-07-37-32-1750-PM

Change control by default

Every configuration change is a commit. Review it in a pull request, merge it, and the audit trail is already in your repo before anything reaches your fleet.

synctoiru

Your repo, your source of truth

Manifest files declare the desired state of your fleet. Iru syncs to match, so your repo is always the authority on what's deployed.

02-Research-1

Iru handles the hard part

The architecture for device scoping with Assignment Maps stays in Iru. Your team manages configuration in Git; Iru handles getting it to the right devices.

Manage you fleet from the tools you already have

Connect to the API

A RESTful API for managing scripts, apps, profiles, device assignment, and Blueprints. Fully configure and report on the state of your fleet programatically.

  • Create and update custom apps, profiles, and scripts as Library Items
  • Scope Library Items to devices via conditional nodes in Assignment Maps
  • Authenticate with scoped API tokens
02-Identity-1

Define in manifests

Each deployable item lives in its own manifest file. Declare what it is, where it goes, and who gets it. The sync job reads from these files and updates only what changed.

  • One manifest per Library Item you want to deploy
  • Declare key details like name, active state, Blueprint, and conditional node
  • Diff-friendly format works with code review and PR workflows
Container-4

Ship through GitHub

A GitHub Actions workflow validates and prepares changes for Iru, then pushes them on merge. The sync job compares hashes and updates only what changed.

  • Catch errors in CI before changes reach your fleet, roll back when needed
  • Sync only what changed, so deploys stay fast and predictable
  • Use GitHub Actions, or run it yourself with Iru's open-source CLI
Troubleshoot Faster-May-15-2026-07-40-15-1023-PM

Stay up to date

Iru's weekly collection of articles, videos, and research to keep IT & Security teams ahead of the curve.