🚀 Introducing Gantry: A local-first launch control room for AI-native workflows

[amcdev1]

Hi everyone! 👋

I built Gantry to solve a specific problem in my own workflow: launch coordination in the age of AI coding assistants.

While AI agents (like Cursor, Claude, or Gemini) are excellent at writing code and maintaining files, they struggle to track launch readiness without structured schemas. At the same time, I wanted a clear, plain-language dashboard that answers one question: "Are we ready to launch?" without having to dig through scattered markdown checklists, issue trackers, and Git logs.

Gantry is a local-first desktop app (Tauri + Rust) that bridges this gap by offering two views over a single repository-based source of truth:

1. For AI Agents: A structured .gantry/ vault of markdown, YAML frontmatter, and JSON schemas, verified by a stable CLI.
2. For Us: A plain-language Go / At Risk / No-Go desktop dashboard with a live timeline of git-attributed activity.

---

Core Features

• Verification over Vibes: All readiness indicators are mapped directly to files, checklists, or telemetry.
• Git-Attributed Auditing: Toggling a checklist item in the UI automatically signs it directly in the markdown using your local git config signature (e.g., <!-- @owner YYYY-MM-DD by:@author -->), giving you an offline audit trail for free.
• CI-Ready Gating: Run gantry validate --ci in your CI/CD pipelines to block or allow deployments based on launch readiness.
• 100% Local-First: No external servers, no databases, and no cloud accounts. Everything lives in Git.

---

Installation & Quick Start

You can install and run the Gantry CLI directly:

# Install the CLI on your PATH
cargo install --git https://github.com/trygantry/gantry gantry-cli

# Initialize a .gantry vault in your repository
gantry init

Once initialized, download the Tauri desktop app to open your repository's control room.

---

🗺️ Future Vision & Multi-Repo Scaling

While Gantry is designed to be completely open-source and local-first for individual repositories, I am actively designing the next phase—specifically, how to scale Gantry to aggregate and coordinate launch readiness across multiple repositories, microservices, and larger engineering teams.

If you are a fast-growing team running into multi-repo release coordination bottlenecks, I would love to connect and have you as an early design partner.

---

💬 Feedback & Collaboration

I am dogfooding Gantry daily and would love your feedback:

• How do you track launch readiness today?
• What AI assistants are in your development workflow?

Please share your thoughts below or star the Gantry Repository!