CT-OpsCT-Ops
Home
Getting Started
Architecture
Features
Deployment
GitHub
GitHub
Home
Getting Started
Architecture
Features
Deployment
GitHub
GitHub
  • Introduction
  • Getting Started

    • Installation
    • Configuration
    • Offline Agent Install Bundle
  • Architecture

    • Architecture Overview
    • Agent Architecture
    • Ingest Service
    • Deployment Profiles
  • Features

    • Hosts & Inventory
    • Host Groups
    • Networks
    • Monitoring
    • Certificate Management
    • SSL Certificate Checker
    • Alerts
    • Notifications
    • Reports
    • Terminal
    • Service Accounts & Identity
    • Directory User Lookup
    • Tasks & Runbooks
    • Scheduled Tasks
    • Tags
    • Notes
  • Deployment

    • Docker Compose Deployment
    • Air-Gap Deployment
    • Load Testing
  • Development

    • End-to-end testing
  • Licensing
  • Security

Introduction

CT-Ops is an open-source infrastructure monitoring and tooling platform built for corporate engineering teams and individual operators who need full control over their observability stack.

What is CT-Ops?

CT-Ops gives you a single place to manage and monitor your server infrastructure — without sending data to a third-party cloud.

Core capabilities:

  • Agent-based server monitoring — A lightweight Go agent runs on each host, streaming metrics and running checks over gRPC with mTLS
  • Certificate lifecycle management — Track TLS certificates across your infrastructure and get expiry alerts before they cause outages
  • Service account and identity tracking — Inventory domain accounts, SSH keys, and users across your fleet via LDAP/Active Directory sync
  • Infrastructure tooling — A persistent terminal panel, custom script runner, service management, task runner, and runbooks
  • Alerting and notification routing — Rule-based alerts with channels for Slack, SMTP, Webhooks, Telegram, and in-app notifications

Who is CT-Ops for?

  • Engineering and platform teams who run their own servers and want a self-hosted alternative to cloud observability products
  • Security-conscious operators who require air-gapped deployments with zero external dependencies
  • Ops teams who need a single pane of glass for server inventory, certificate expiry, service accounts, and alert management

Key Design Principles

No External Dependencies

Every feature works in a fully air-gapped environment. No cloud APIs, no CDNs, no phone-home. Agent binary updates are served from your own CT-Ops server.

Open Agent

The agent is Apache 2.0 licensed and always will be. Security teams must be able to audit what runs on their hosts.

Offline-Capable Licensing

Enterprise licence validation uses a signed JWT verified against a bundled public key. No external service required.


Quick Links

InstallationGet CT-Ops running in under 5 minutes
Offline Agent Install BundleDownload a portable zip to install agents on air-gapped hosts
Architecture OverviewUnderstand how the components fit together
Agent ArchitectureRegistration flow, identity model, self-update
Ingest ServicegRPC gateway, JWT issuance, queue
Deployment Profilessingle / standard / HA configurations
Air-Gap DeploymentRun CT-Ops with zero external dependencies
Edit this page on GitHub
Last Updated: 4/18/26, 10:33 PM
Contributors: Simon Carr, Claude Sonnet 4.6, Claude, Claude Opus 4.7