⚖️ AnubisWatch

The Judgment Never Sleeps

Zero-dependency, single-binary uptime and synthetic monitoring platform

---

🎯 What is AnubisWatch?

AnubisWatch is a zero-dependency, single-binary uptime monitoring platform built in pure Go. Inspired by the Egyptian god of the afterlife who weighed the hearts of the dead, AnubisWatch "weighs" your services' health with precision and authority.

Key Features

• 🔥 Zero Dependencies — Only requires Go stdlib + minimal external packages
• 📦 Single Binary — Everything in one anubis executable
• 🌍 10 Protocols — HTTP/HTTPS, TCP, UDP, DNS, ICMP, SMTP, IMAP, gRPC, WebSocket, TLS
• ⚡ Distributed — Built-in Raft consensus for multi-node clusters
• 🌐 Multi-Region — Geographic region support with cross-region replication
• 🔬 Synthetic Monitoring — Multi-step HTTP journeys with assertions & variable extraction
• 🎨 Beautiful Dashboard — React 19 + Tailwind 4.1 embedded in binary
• 🤖 MCP-Native — Built-in Model Context Protocol server for AI integration
• 🔔 Rich Alerts — Slack, Discord, Telegram, Email, PagerDuty, OpsGenie, SMS, Ntfy, WebHook
• 🏷️ Multi-Tenancy — Workspace isolation with quotas and RBAC
• 📋 Status Pages — Public status pages with custom domains and ACME
• 🗄️ Backup/Restore — Full data export/import with compression
• 📊 Profiling — Built-in performance profiling (CPU, heap, goroutines)

---

🏛️ Architecture

Terminology

AnubisWatch uses Egyptian mythology theming throughout:

Term	Meaning
Soul	A monitored target (HTTP endpoint, TCP port, etc.)
Judgment	A single check execution result
Verdict	An alert decision based on judgment patterns
Jackal	A probe node that performs health checks
Pharaoh	The Raft leader in a cluster
Necropolis	The distributed cluster
Feather	The embedded B+Tree storage engine (CobaltDB)
Ma'at	The alert engine (goddess of truth)
Duat	The WebSocket real-time layer
Journey	Multi-step synthetic monitoring

Project Structure

AnubisWatch/
├── cmd/anubis/          # CLI entry point
├── internal/
│   ├── api/             # REST, WebSocket, gRPC, MCP APIs
│   ├── alert/           # Alert engine (Ma'at) with 9 dispatchers
│   ├── auth/            # Authentication (local, OIDC, LDAP)
│   ├── backup/          # Backup/restore functionality
│   ├── cluster/         # Cluster coordination (Necropolis)
│   ├── core/            # Domain types (Soul, Judgment, Verdict)
│   ├── journey/         # Synthetic monitoring (Journeys)
│   ├── probe/           # Protocol checkers (8 protocols)
│   ├── profiling/       # Performance profiling (pprof)
│   ├── raft/            # Raft consensus (Pharaoh)
│   ├── region/          # Multi-region support
│   ├── release/         # Release tooling
│   ├── storage/         # CobaltDB B+Tree storage (Feather)
│   ├── statuspage/      # Public status pages
│   └── version/         # Version management
├── scripts/             # Build and release scripts
└── web/                 # React 19 + Tailwind 4.1 dashboard

---

📊 Comparison

Feature	AnubisWatch	Uptime Kuma	UptimeRobot	Checkly
Self-Hosted	✅ Yes	✅ Yes	❌ SaaS only	❌ SaaS only
Single Binary	✅ Go (zero deps)	❌ Node.js + npm	❌ N/A	❌ N/A
Protocol Support	✅ 8 protocols	⚠️ 5 protocols	❌ 1-2 protocols	⚠️ 2 protocols
Distributed Probes	✅ Raft consensus	❌ Single node	❌ Cloud only	⚠️ SaaS multi-location
Synthetic Monitoring	✅ Multi-step journeys	❌ No	❌ No	✅ Yes (SaaS)
Embedded Dashboard	✅ React 19 (compiled)	⚠️ Vue.js (separate)	❌ Web UI	✅ Web UI
Embedded Storage	✅ CobaltDB (encrypted)	⚠️ SQLite (plaintext)	❌ Cloud DB	❌ Cloud DB
Multi-Tenant	✅ Workspace isolation	❌ Single tenant	❌ Single tenant	❌ Teams add-on
MCP Integration	✅ Native	❌ No	❌ No	❌ No
Cluster Mode	✅ Built-in Raft	❌ No clustering	❌ Cloud only	❌ Cloud only
Cost	✅ 100% Free (Apache 2.0)	✅ Free (GPL)	⚠️ Freemium	❌ $29+/mo

---

🚀 Quick Start

Installation

# Linux/macOS (using install script)
curl -fsSL https://anubis.watch/install.sh | sh

# Or download from releases
wget https://github.com/AnubisWatch/anubiswatch/releases/latest/download/anubis-linux-amd64
chmod +x anubis-linux-amd64
mv anubis-linux-amd64 /usr/local/bin/anubis

# macOS with Homebrew (coming soon)
brew install anubiswatch/tap/anubis

Docker

# Pull from GHCR (GitHub Container Registry)
docker pull ghcr.io/anubiswatch/anubiswatch:latest

# Single node
docker run -d \
  --name anubis \
  -p 8443:8443 \
  -v anubis-data:/var/lib/anubis \
  ghcr.io/anubiswatch/anubiswatch:latest

# With custom config
docker run -d \
  --name anubis \
  -p 8443:8443 \
  -v $(pwd)/anubis.yaml:/etc/anubis/anubis.yaml \
  -v anubis-data:/var/lib/anubis \
  ghcr.io/anubiswatch/anubiswatch:latest

Initialize & Run

# Create default configuration
anubis init

# Edit configuration
vim anubis.yaml

# Start server
anubis serve

# Access dashboard
open https://localhost:8443

---

🎮 CLI Usage

# Show version
anubis version
anubis version --json    # JSON output

# Initialize configuration
anubis init

# Quick-add a monitor
anubis watch https://api.example.com --name "API"

# View current status
anubis judge

# Backup & Restore
anubis backup --output ./backup.tar.gz
anubis restore --input ./backup.tar.gz

# Server management
anubis serve --single                    # Single node mode
anubis serve --config ./anubis.yaml      # Custom config
anubis status                            # Show server status
anubis logs --follow                     # View logs
anubis config validate                   # Validate config
anubis config show                       # Show current config
anubis export --format json              # Export data

# Cluster management
anubis necropolis              # Show cluster status
anubis summon 10.0.0.2:7946    # Add node
anubis banish jackal-02        # Remove node

---

🏗️ Architecture

┌─────────────────────────────────────────────────────────────┐
│                    AnubisWatch Binary                        │
│                                                             │
│  ┌──────────┐  ┌──────────┐  ┌──────────┐  ┌────────────┐  │
│  │  Probe   │  │   Raft   │  │   API    │  │  Dashboard  │  │
│  │  Engine  │  │ Consensus│  │  Server  │  │  (React 19) │  │
│  │          │  │          │  │          │  │  embedded   │  │
│  │ 8 proto- │  │  Leader  │  │ REST +   │  │  Tailwind   │  │
│  │ col chk  │  │  Election│  │ gRPC +   │  │  4.1 +      │  │
│  │          │  │  Log Rep │  │ WebSocket│  │  shadcn/ui  │  │
│  │          │  │  State   │  │ MCP Svr  │  │  Lucide     │  │
│  └────┬─────┘  └────┬─────┘  └────┬─────┘  └──────┬─────┘  │
│       │              │              │               │        │
│  ┌────┴──────────────┴──────────────┴───────────────┴─────┐  │
│  │                    CobaltDB Engine                      │  │
│  │         Embedded Storage (B+Tree, WAL, MVCC)           │  │
│  │     Time-Series Optimized · AES-256-GCM Encryption     │  │
│  └────────────────────────────────────────────────────────┘  │
│                                                             │
│  ┌────────────────────────────────────────────────────────┐  │
│  │                Alert Dispatcher                        │  │
│  │  Webhook · Slack · Discord · Telegram · Email(SMTP)   │  │
│  │  PagerDuty · OpsGenie · SMS(Twilio) · Ntfy.sh        │  │
│  └────────────────────────────────────────────────────────┘  │
└─────────────────────────────────────────────────────────────┘

---

🌍 Distributed Cluster (Necropolis)

Every node in an AnubisWatch cluster is both a probe and a controller. Powered by Raft consensus:

• Pharaoh (Leader): Schedules checks, dispatches alerts
• Jackal (Follower): Executes checks, replicates state
• Auto-discovery via mDNS or gossip protocol

# Node 1 (becomes leader)
anubis serve --node-name jackal-01 --region eu-west --cluster

# Node 2 (joins cluster)
anubis serve --node-name jackal-02 --region us-east --cluster \
  --join jackal-01:7946

# Node 3 (joins cluster)
anubis serve --node-name jackal-03 --region apac --cluster \
  --join jackal-01:7946

---

📡 Monitoring Protocols

Protocol	Description	Example
HTTP/HTTPS	Full HTTP checks with assertions	Status codes, body, JSON path, schema
TCP	Port checks with banner grab	Connect + banner match
UDP	Packet send/receive	Hex payload support
DNS	Resolution and propagation	Multi-resolver checks
ICMP	Ping with packet loss	Latency stats, jitter
SMTP/IMAP	Email server checks	STARTTLS, AUTH
gRPC	Health checks	Custom metadata
WebSocket	Realtime connection	Subprotocols, ping/pong
TLS	Certificate monitoring	Expiry, cipher audit

---

🔧 Configuration Example

server:
  host: "0.0.0.0"
  port: 8443
  tls:
    enabled: true
    auto_cert: true
    acme_email: "admin@example.com"

souls:
  - name: "Production API"
    type: http
    target: "https://api.example.com/health"
    weight: 30s  # Check every 30s
    http:
      method: GET
      valid_status: [200]
      json_path:
        "$.status": "ok"
      feather: 500ms  # Max latency

  - name: "Database"
    type: tcp
    target: "db.example.com:5432"
    weight: 15s

checks:
  - name: "ops-slack"
    type: slack
    slack:
      webhook_url: "${SLACK_WEBHOOK}"

verdicts:
  rules:
    - name: "Service Down"
      condition:
        type: consecutive_failures
        threshold: 3
      severity: critical
      channels: ["ops-slack"]

---

🎨 Dashboard

The Hall of Ma'at dashboard is built with React 19 and embedded directly into the binary:

• Real-time WebSocket updates
• 90-day uptime heatmaps
• Response time sparklines
• Regional node map
• Dark/Light themes (Tomb Interior / Desert Sun)

---

🤖 MCP Integration

AnubisWatch includes a built-in MCP server for AI agent integration:

# List monitored targets
anubis_list_souls

# Get current status
anubis_get_soul_status api.example.com

# Trigger check
anubis_trigger_judgment api.example.com

---

📊 Test Coverage

Package	Coverage	Status
internal/core	98.9%	✅
internal/cluster	90.0%	✅
internal/alert	89.3%	✅
internal/statuspage	88.7%	✅
internal/dashboard	87.5%	✅
internal/journey	86.7%	✅
internal/api	86.2%	✅
internal/auth	86.2%	✅
internal/raft	86.1%	✅
internal/probe	86.1%	✅
internal/storage	84.4%	✅
internal/acme	81.8%	✅
internal/backup	80.5%	✅
internal/region	78.2%	✅
internal/version	95.0%	✅
internal/release	85.0%	✅
cmd/anubis	77.3%	✅
Average	86.0%	✅

---

📦 Development

Prerequisites

• Go 1.26+
• Node.js 22+ (for dashboard)
• Make (optional)

Quick Start

# Clone repository
git clone https://github.com/AnubisWatch/anubiswatch.git
cd anubiswatch

# Install Go dependencies
go mod download

# Install and build dashboard
cd web && npm ci && npm run build && cd ..

# Build binary
make build
# or
go build -o bin/anubis ./cmd/anubis

# Run tests
make test
# or
go test -race -coverprofile=coverage.out ./...

# Run locally
make dev
# or
./bin/anubis serve

---

🗺️ Roadmap

• Phase 1: Foundation (Go module, core types, config)
• Phase 2: Probe Engine (8 protocols)
• Phase 3: Raft Consensus (distributed cluster)
• Phase 4: Alert System (9 channels, escalation)
• Phase 5: API Layer (REST, WebSocket, gRPC, MCP)
• Phase 6: Dashboard (React 19, Hall of Ma'at)
• Phase 7: Advanced Features (multi-tenant, status page)
• Phase 8: Multi-Region & Backup (region support, backup/restore)
• Phase 9: Release Preparation (versioning, CI/CD, packaging)
• Phase 10: Enterprise Features (SSO, audit logs, compliance)

---

📄 License

AnubisWatch is licensed under the Apache License 2.0. See LICENSE for details.

Copyright 2026 Ersin Koç — ECOSTACK TECHNOLOGY OÜ

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

---

🙏 Acknowledgments

• Anubis: Egyptian god of the afterlife, who inspired this project
• Ma'at: Goddess of truth and justice, whose feather weighs against our metrics
• The Go Team: For the amazing standard library

---

anubis.watch · anubiswatch.com

The Judgment Never Sleeps ⚖️