Shared patterns across Gantry Tools.
Project sites remain the authority for project-specific commands and features. These docs cover the conventions that make the suite coherent: how self-hosted apps are reached, run as services, exposed behind TLS, launched from a desktop, connected to one another and eventually operated across fleets or clusters.
Use the guide that matches the friction you are trying to remove.
Running one local app? You may not need any of this—the default ports and my.* launchers are designed to work with almost no setup. The docs become useful when you want persistence, remote access, several instances or cross-project workflows.
my.* launchers
Zero-config localhost behaviour, named instances, browser-local configuration and the planned my.gantry.cv app drawer.
Read guide → ServicesService lifecycle API
The complete install/start/stop/restart/status/logs/uninstall model, using Cortex’s real implementation as the reference.
Read guide → DesktopDesktop & dock launchers
Linux .desktop entries, app/PWA mode, Wayland grouping, macOS and Windows launchers, and when to target my.*.
Read guide → HostingServe & deploy
Loopback-first services, systemd user mode, DNS/TLS, Caddy, nginx, VPN/private hosting, firewalls and multi-instance deployment.
Read guide → SuiteProjects working together
Concrete build, development and operations flows, plus the boundaries that keep integrations useful instead of creating suite lock-in.
Read guide → OperationsFleet, cluster & distributed direction
Machine identity, configuration bundles, secrets, drift, Cortex remediation, Watchpost HA and regional Webfleet workers.
Read guide →