Make your infrastructure legible.
Draw the systems you work with. Connect them to health checks. Keep the context you need to investigate a problem and choose what to do next.
Reticle starts with a map you author, saved as one YAML file. You choose the nodes, relationships, and boundaries; configured checks add current observations. You can use the diagram without configuring any checks or commands.
Start with one useful map#
Create your first diagram: open a sample or a new workspace, draw a service and its dependencies, and add your first HTTP check.
- Install Desktop — choose a package and prepare the tools your checks need.
- Understand Desktop and Team — choose where your map and checks run.
- Find a fix — start with the symptom you see.
Draw and organize#
- Workspaces and files — autosave, YAML, samples, and backups.
- Draw your map — nodes, connections, notes, and embedded pages.
- Groups and Tree view — containment, reparenting, and group health.
- Export and share — PDF, portable YAML, and shared browser access.
- Keyboard shortcuts — navigate and edit efficiently.
Connect to live systems#
- Checks and named actions — collect evidence and run a reviewed response.
- Desktop terminals — SSH and Kubernetes sessions on macOS and Linux.
- JSON API and MCP — read topology and observations from other tools.
- Optional chat — ask questions about the graph with OpenAI or local Ollama.
Share with your team#
- Team Daemon — one always-on topology, browser access, and viewer/editor roles.
- Production deployment — install, configure, upgrade, and operate a Linux service.
- Daemon architecture — collection, revisions, and the WebSocket protocol.
Look something up#
- Topology YAML reference
- Supported platforms
- v1.3.0 release notes, licensing, and v1.2 migration guide
Reticle complements your monitoring tools. It does not discover infrastructure, retain metrics or logs, or remediate failures automatically. See capabilities and limitations for the current boundaries.