Skip to content
AltumpticPublic

About

Calm, agentless SSH security monitor for small Linux fleets. Nothing installed on servers. Beta.

Topics

Resources

Code of conduct

Contributing

Security policy

Stars

30 stars

Watchers

0 watching

Forks

Latest commit

 

History

81 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

LemonSees by Altumptic

LemonSees

A calm, agentless SOC console for Linux fleets — by Altumptic

See attacks, file changes and suspicious logins on your Linux servers — over plain SSH, with nothing installed on them.
Self-hosted web app, Windows installer/portable .exe, Linux AppImage/.deb, or macOS .dmg.

BETA · PSB-B · SIGNED (Sigstore) · ATTESTED · SBOM · NO-TELEMETRY · LOCAL-FIRST · FAIL-CLOSED · TOR-CAPABLE · AUDIT:NONE · DISCLOSURE:OK

Download · Try the demo · Install · Verify a release · Security notes


LemonSees overview dashboard

What it is

LemonSees is a self-hosted monitor for a small Linux fleet, roughly 3–30 servers. It reads what it needs over SSH — failed and successful logins, hashes of critical files, running services, basic metrics — and shows it on one calm dashboard with incidents and alerts. Nothing is installed on the servers. Everything runs on your machine or your own server; no data is sent to Altumptic.

Status: beta. The log analysis core is tested on synthetic logs and a fake SSH host, not yet on a real fleet — we are looking for testers (see Help us test). There is no independent security audit yet (AUDIT:NONE), and the Windows and macOS builds are not code-signed by a certificate authority.

Who it is for

  • Self-hosters and homelab owners with a handful of Linux servers.
  • Small teams and freelance sysadmins who want to see attacks and file changes without running a SIEM.
  • Anyone who finds Wazuh too heavy for a few servers and does not want agents on them.

Who it is not for

  • Large SOCs with thousands of endpoints, real-time file monitoring, or active response.
  • Compliance certification: LemonSees helps collect evidence; it does not certify anything.

Features (beta)

  • SOC analytics — alert volume by severity, MTTA / MTTR, response-SLA gauge, handling funnel, Sankey incident flow, day×hour heatmap, half-year activity calendar, most affected hosts, analyst workload.
  • MITRE ATT&CK — incidents are mapped to tactics and techniques (keyword heuristic; Wazuh alerts keep Wazuh's IDs).
  • SSH hygiene (beta) — one page for the whole fleet: effective sshd settings, every key that can log in with its SHA-256 fingerprint, when it was last used, duplicates, weak and unknown keys, and the change to make (shown, never applied). Read-only. Details and limits.
  • Import from ~/.ssh/config — add your servers in one step: pick the hosts, and LemonSees takes the address, user, port and key from the file you already have. Read-only; key contents are never opened.
  • File integrity (FIM) — SHA-256 + mode/owner of /etc/shadow, sudoers, sshd_config, authorized_keys, cron, systemd units…; checked on every sweep (default 5 min); drift opens an incident.
  • Detection rules — your own regex + threshold + time window over journald or any log file, with MITRE technique, severity and host scope; templates and a live test on host.
  • Threat intel — brute-force sources on a world map (geo-IP is opt-in), targeted usernames, IP investigation.
  • EDR / NDR — processes, persistence, posture with a hardening radar, configuration vulnerabilities with remediation, live traffic and sockets.
  • SOAR & GRC — incident register with timeline, auto-incidents, playbooks; CIS / NIST / ISO 27001 / GDPR control subset with human attestations, reports and an audit log.
  • Privacy routing — SSH and every outbound call via Tor / SOCKS5 / HTTP proxy or a bastion, globally or per host, with a kill switch, DNS through the proxy and a “Which IP do servers see?” check.
  • Encryption — secrets encrypted at rest with AES-256-GCM, key in the OS keychain; encrypted backups; HTTPS for web mode.
  • Integrations (optional) — out: Datadog, Slack, Microsoft Teams, Telegram, HMAC-signed webhooks, Splunk HEC, Elastic/OpenSearch, Syslog CEF, PagerDuty. In: Wazuh agents and alerts.
  • Optional agent — one read-only sh script, no root, pull (over SSH) or push (HTTPS + per-agent token).
  • Comfortable — clickable breadcrumbs, global host switcher, alerts inbox, Ctrl+K palette, g-shortcuts, customisable overview, Ivory & Graphite themes, 80–150 % UI scale, EN · UK · RU · PL · ZH.
Incident flow
SOC analytics — Sankey flow, SLA gauge, funnel
MITRE ATT&CK
MITRE ATT&CK matrix
Security and network
Security & network — Tor/proxy, kill switch, pinned keys
Threat map
Threat intel — attack sources
Integrations
Integrations — Datadog, Slack, Wazuh, SIEMs
Wazuh
Wazuh agents and alerts
Compliance
Compliance evidence
Graphite theme
Graphite theme

LemonSees and Wazuh — an honest comparison

LemonSees is not a drop-in replacement for Wazuh. It optimises for nothing installed on targets, privacy and a calm UI for small Linux fleets, and it can sit next to an existing Wazuh.

LemonSees Wazuh
On the monitored servers nothing by default (SSH); optional sh agent Wazuh agent on every endpoint
Endpoints Linux with a POSIX shell Linux, Windows, macOS, more
FIM periodic SHA-256 sweep (default every 5 min) real-time (inotify / whodata)
Detection content built-in checks + your regex rules large decoder/rule set maintained by Wazuh
Active response no (detect & report) yes
Scale designed for small fleets (3–30 servers); not load-tested at larger scale thousands of agents with indexer cluster
Analyst privacy Tor / proxy / bastion, kill switch, DNS via proxy not a focus
Deployment single process: web, portable .exe, AppImage, Docker manager + indexer + dashboard
Use together imports Wazuh agents and alerts (level 12+ → incidents) —

⚡ Try it in 30 seconds

Open LemonSees and click Try the demo (or Settings → Demo mode): six realistic hosts, a month of incidents, attacks, FIM drift, Wazuh data and agents — all generated locally; demo IPs come from documentation ranges (RFC 5737).

📦 Install

Platform Get it Notes
Windows LemonSees-<v>-setup.exe (installer), -portable.exe or .zip The portable build needs no installer and no admin rights. Data in LemonSees-data/ next to the exe. Not Authenticode-signed — verify.
macOS LemonSees-<v>-arm64.dmg / -x64.dmg (or .zip) Unsigned and not notarized: right-click → Open, after verifying checksums/Sigstore.
Linux LemonSees-<v>-x86_64.AppImage, .deb or .tar.gz chmod +x and run. Create LemonSees-data/ next to it for fully portable mode.
Web LemonSees-<v>-web.tar.gz or git clone Node.js 22.12+: npm ci && npm run build && npm start → http://127.0.0.1:5199
Docker docker build -t lemonsees . See below.

Every release ships SHA256SUMS, a Sigstore signature, GitHub build provenance and an SBOM — see docs/security/VERIFY.md.

Web mode on a network

LemonSees refuses to listen on a public interface without an access token:

LEMONSEES_HOST=0.0.0.0 \
LEMONSEES_TOKEN="$(openssl rand -hex 24)" \
LEMONSEES_MASTER_KEY="a long passphrase for the secret vault" \
LEMONSEES_TLS=self \
npm start

Docker

docker build -t lemonsees .
docker run -d --name lemonsees -p 5199:5199 \
  -e LEMONSEES_TOKEN="$(openssl rand -hex 24)" \
  -e LEMONSEES_MASTER_KEY="a long passphrase" \
  -e LEMONSEES_TLS=self \
  -v lemonsees-data:/data lemonsees
Variable Default Purpose
LEMONSEES_HOST 127.0.0.1 Bind address. Non-loopback requires a token.
LEMONSEES_PORT 5199 HTTP(S) / WebSocket port
LEMONSEES_TOKEN — Access token for the web UI and API
LEMONSEES_ALLOWED_HOSTS — Comma-separated host names accepted in web mode (DNS-rebinding defence)
LEMONSEES_TLS — self → HTTPS with an auto-generated self-signed certificate
LEMONSEES_TLS_CERT / LEMONSEES_TLS_KEY — Your own certificate and key
LEMONSEES_MASTER_KEY — Passphrase for the secret vault (recommended on servers)
LEMONSEES_SECURE_COOKIE — 1 behind a TLS-terminating reverse proxy
SHOK_CONFIG_DIR ./config Data directory

🕶️ Keep your IP private

  1. Start Tor (or your VPN, or ssh -D 1080 bastion).
  2. System → Security & network → Tor preset (SOCKS5 127.0.0.1:9050) → Apply route.
  3. Keep Kill switch and DNS via proxy on, press Which IP do servers see? — it should show the exit IP.

Per-host routes (own proxy or bastion) are in the host form under Route & privacy. This hides your IP from servers and services; it is not a guarantee of anonymity — see the threat model.

🔌 Works with what you already run — optional

LemonSees needs no external API. When you want it: System → Integrations.

  • Wazuh — manager API (https://manager:55000) and optionally the indexer (https://indexer:9200); agents and alerts appear under Console → Wazuh, level 12+ alerts become incidents.
  • Datadog — API key + site (e.g. datadoghq.eu); incidents, downtime and FIM drift arrive as Events and Logs.
  • Slack, Teams, Telegram, webhooks, Splunk, Elastic, Syslog CEF, PagerDuty — each with a severity / event filter and a Test button.

🚀 Quick start

  1. Top bar + → Host (SSH): address, a dedicated non-root user and an SSH key.
  2. Watch Overview fill with live metrics, risk and alerts.
  3. Endpoints → File integrity: the first scan becomes the baseline.
  4. Response → Detection rules: add a template, test it on a host.

Keyboard: Ctrl+K search · Ctrl+B sidebar · ? shortcuts · g o overview · g i incidents · g m MITRE.

🔐 Security

Altumptic Product Security Baseline class PSB-B. Read before deploying:

Labels mean exactly this: SIGNED — release checksums signed with Sigstore by this repo's release workflow (binaries are not Authenticode-signed). ATTESTED — GitHub build provenance. SBOM — CycloneDX attached. NO-TELEMETRY — no analytics, nothing sent to Altumptic. LOCAL-FIRST — core features never upload your data. FAIL-CLOSED — kill switch, host-key pinning, tamper-evident encryption. TOR-CAPABLE — supported, not on by default. AUDIT:NONE — no independent audit yet.

🛠️ Development

npm ci
npm run server      # engine on :5199
npm run dev         # UI on :5198 (proxies /api and /ws)
npm test            # security tests: fail-closed, crypto, authZ, input parsing
npm run typecheck
npm run dist:win    # installer + portable .exe + zip
npm run dist:linux  # AppImage + deb + tar.gz
npm run dist:mac    # dmg + zip (x64 + arm64; run on macOS)
npm run promo       # record the promo video from the live demo (needs npm start + ffmpeg; FFMPEG=path to override)

Design system: DESIGN.md · Changes: CHANGELOG.md · Contributors: CONTRIBUTORS.md

📚 Documentation and community

I want to… Read
Understand the project and its status docs/README.md (the documentation index)
Test it on my servers docs/TESTING.md and docs/VALIDATION.md
See where it is going docs/ROADMAP.md · next feature: SSH hygiene
Contribute code or docs CONTRIBUTING.md · development guide
Ask a question or share a setup GitHub Discussions
Report a security issue SECURITY.md (private reporting only)

Community standards: Code of Conduct.

License and legal

MIT © 2026 Altumptic and LemonSees contributors.

About

Calm, agentless SSH security monitor for small Linux fleets. Nothing installed on servers. Beta.

Topics

Resources

Code of conduct

Contributing

Security policy

Stars

30 stars

Watchers

0 watching

Forks

Releases

Packages

Used by

Contributors

Languages