


























Built for operators · Local-first · No data leaves your machine
Reticle puts your servers on a real-world map alongside submarine cables, IXPs, and cloud regions — then gives you live SSH terminals to reach them. Define everything in YAML. Overlay your own site surveys. Built for the people who keep things running.
macOS today, Windows and Linux coming soon. Come shape the roadmap on Discord.
15MB binary
Rust backend
0 telemetry
See the whole internet. Act on any server. All from a map built for operator workflows.
🗺️
Submarine cables, landing points, cloud regions, IXPs, backbone routes, fiber, data centers, and satellite orbits — all on an interactive globe your team can actually read.
📋
Define servers, actions, crons, and custom layers in a single config.yaml. Git-trackable, auditable, reviewable in PRs. Infrastructure as code your whole team can follow.
🔄
Schedule SSH commands every 30s, 5m, or 1h. Server markers turn red when checks fail. Know before your users do — and before your team gets paged.
💻
Fullscreen xterm.js with PTY-backed SSH. Full ANSI color support. Zoom the font with Cmd/Ctrl +/-. Escape to close. The terminal your operators already know.
🎯
Overlay your GeoJSON files — site surveys, planned routes, coverage polygons. Auto-detects points, lines, and fills. The context your operator team has been missing.
🌐
No data leaves your machine. No telemetry, no accounts, no cloud dependency. The entire app is a 15MB binary. SSH key auth assumed. Operators trust what they can audit.
1
servers:
- name: web-01
host: 10.0.0.1
user: deploy
lat: 41.88
lng: -87.63
crons:
- name: check nginx
interval: 60s
script: systemctl is-active nginx
layers:
- name: Chicago Network
file: chicago.geojson
color: "#ff6600"
2
Servers appear on the map with live health status. Green = all crons pass. Red = something's wrong. Yellow = checking. Overlay your own network plans. Every operator sees the same picture.
3
Click any server to see details, run one-off actions, or open a live SSH terminal. The map stays visible while you work. No context switching — just you and the machine.
deploy@web-01
deploy@web-01:~$ systemctl is-active nginx
active
deploy@web-01:~$ df -h /
Filesystem Size Used Avail Use% Mounted on
/dev/vda1 50G 23G 25G 48% /
deploy@web-01:~$ uptime
14:23:07 up 47 days, 3:12, 1 user, load average: 0.42, 0.38, 0.35
deploy@web-01:~$ █
The full app is free for personal use — no limits, no feature gates. Pay when your team needs shared visibility.
Personal
Free
For homelabs, side projects, and solo operators
Download
Coming soon
Team
$12/seat/mo
$120/seat/yr · 14-day free trial
Shared visibility for operator teams
Coming soon
Enterprise
Custom
For organizations with compliance needs
Coming soon
No. Reticle is completely local-first. SSH connections go directly from your machine to your servers. Config is stored locally. No telemetry, no accounts, no phone home. Operators trust what they can audit.
Reticle assumes SSH key-based authentication. Your existing ~/.ssh/config and keys work out of the box. No passwords are stored or transmitted.
Yes. All map layers — built-in infrastructure layers and your own custom GeoJSON overlays — are included in the free Personal tier. No feature gates on the map.
You define a bash command and an interval (e.g. 60s, 5m, 1h) in your YAML config. Reticle runs it over SSH on schedule. If the command exits non-zero, the server turns red on the map.
macOS (Apple Silicon & Intel), Windows, and Linux. The app is built with Tauri (Rust) so it's a native binary — no Electron, no Chromium overhead.
Yes. You can add servers, actions, and crons from the UI. The YAML file is always the source of truth — edits in the UI write to YAML, and external edits are picked up automatically.
Personal is free for individual operators — one person, one config, no account needed. Team adds shared maps, config sync, role-based access (viewer vs operator), alerting integrations, and audit logging for when your whole team needs to see and act on the same infrastructure.
Download, add your servers to config.yaml, and see them on the map. That's it.
此内容由惯性聚合(RSS阅读器)自动聚合整理,仅供阅读参考。 原文来自 — 版权归原作者所有。