itcmdr

itcmdr 1.0.0

Self-healing IT for small offices.

An agent on every PC checks the network, connections and services each night and repairs what it safely can. A server on site keeps the history, alerts and backups. And nothing internal leaves the office.

Download View on GitHub

itcmdr logo: a navy shield with a teal terminal prompt

Features

Nightly checks and repairs

The agent checks network settings, connectivity and services, repairs what it safely can, and logs every check. Checks with no safe repair are reported, not guessed at.

Plugins and schedules

Checks are signed plugin packages. Tampered or unsigned packages are quarantined. Schedules run on the agent, even while it's offline.

Alerts that make sense

Site alerts come in three severity levels. You can acknowledge, resolve or silence them, and they also show up as push notifications in the admin app.

Metrics and log search

Flapping checks, repeat offenders, charts, and log search with filters and paging.

Backups that stay home

Backup coverage checks, encrypted backups and on-site restore. Backups never leave the site server.

Keys, not passwords

A 24-word master key backs certified keys, and every request is signed. Passkeys and security keys can be added as a second factor on the admin server.

The privacy promise

No internal information leaves the office it's installed in.

  • The site server decides what leaves, and it denies by default.
  • Hostnames, IPs, paths, usernames and message text never leave. The admin server sees opaque IDs, alert codes, counts and timestamps.
  • Display names are only shared if the office owner opts in on that site.
  • Backups never leave the site server, and the admin server can't restore them.

How the security and privacy work →

How it works

  1. Install the site server on the office server. First-run setup shows your 24 words once and creates the first admin key.
  2. Enroll each PC with a one-time token. The agent gets its own certificate from the site, and every connection is mutually authenticated.
  3. Let it run. Checks and repairs run on schedule, results come back to the site server, and problems become alerts.
  4. Optionally connect an admin server to watch many sites from one place, with redacted data only.

Components

Agent

A Rust service on every PC and on the office server. It enrolls with mutual TLS, keeps a heartbeat, renews its certificate, runs plugins and schedules, and queues alerts while offline.

Site server

A Rust gRPC server for the office, with an encrypted database, roles and users, plugins, schedules, alerts, backups and an audit log.

Office app

A Flutter desktop app for the office: overview, metrics, logs, schedules, plugins, backups, audit, keys and settings.

CLI

itcmdr-cli handles setup, backup and restore, settings and enrollment tokens.

Admin server

Optional and off-site, for IT providers. It runs on SQLite or Postgres, uses passkeys and sends push alerts. Changes it sends need preview, two-person approval and can be frozen by the owner. It runs as a service on Linux, macOS or Windows, or as a container.

Admin app and CLI

A Flutter app and itcmdr-admin CLI for the people who look after many sites: alert inbox, servers, users and service plugins.