Skip to content
AtGlance
Sign up free
Self-hosted · For SREs by SREs

Operations at a glance,
inside your boundary.

A CLI-focused operations platform with a calm, auditable CLI and a self-hosted Management Console. No telemetry. No vendor lock-in.

  • Ubuntu / systemd
  • REST API gateway
  • RBAC + PAT tokens
  • DB circuit breaker
Sign up free Read the quickstart
One platform · Two surfaces

A CLI for the host. A Console for the org.

The CLI runs on every Linux/systemd host and handles discovery, registration and configuration safety. The Console runs inside your boundary and gives operations teams dashboards, RBAC and resilience.

/usr/local/bin/atglance

AtGlance CLI

A focused agent for systemd hosts: service discovery, health, configuration backup and import, registration, deregistration and reactivation.

Explore the CLI
Self-hosted

Management Console

Self-hosted console with REST API gateway, database and cache. Dashboards, RBAC, configuration history, queue resilience and a database circuit breaker.

Explore the Console
Why AtGlance

Calm operations. Strict boundaries.

Self-hosted by design

Deploy the entire Console inside your VPC, on-prem or hybrid. No data leaves your perimeter.

Native systemd discovery

The CLI reads journalctl and ss/netstat on Ubuntu hosts to discover services and their ports. No extra daemons.

Configuration safety

Every config change writes a versioned backup. Import and validate before applying. Rollback is a single flag.

RBAC + PAT tokens

Three roles (superadmin, admin, user) and short-lived Personal Access Tokens for the CLI. Every action is auditable.

DB circuit breaker

When the database is unhealthy, writes are buffered as queued jobs and replayed idempotently when it recovers.

One REST API

A single REST surface for registration, configuration files and token validation, fronted by a rate-limited gateway.

Resilience story

Database outage? Your writes don't disappear.

What happens behind the curtain when the database goes down.

  1. STEP 01
    DB outage detected
    The circuit breaker trips. Reads fall back to cache where safe.
  2. STEP 02
    Writes are queued
    Mutations are encoded as jobs and buffered in the cache. Clients get fast acks.
  3. STEP 03
    DB recovers
    Health checks pass; the circuit closes. Workers pick up where they left off.
  4. STEP 04
    Jobs replay
    Queue workers apply buffered writes idempotently. State converges. Audit logs restored.
Architecture

A boring, predictable stack.

A REST gateway fronts the Console, backed by a database and a cache. The CLI talks to the gateway over HTTPS. That's it.

AtGlance end-to-end architecture
End-to-end · CLI → Gateway → Console → Database / Cache
Read the architecture deep-dive

One curl. systemd-friendly. Idempotent.

The installer sets up the CLI package. The CLI writes its config to ~/.config/atglance and registers your host with the Console.

Get started free CLI reference
install bash 
$ curl -fsSL https://app.atglance.live/cli/atglance-installer.sh | sudo bash
→ Detected: Ubuntu 22.04 · systemd 249
→ Installed atglance → /usr/local/bin/atglance
$ atglance --configure
✓ Wrote ~/.config/atglance/config.json
$ atglance --system-register
✓ Registered system_id=sys_8e1a in org=acme