Operations like these should be real commands you can run from your terminal:
- "Deploy the login fix to staging"
- "What's the functional difference between production and staging?"
- "Notify me when any security fix hits production"
- "Promote Jen's last changes to staging"
- "Share the new beta API SDK with the partners at Acme"
That's what Fly does.
Every time a CI run pushes artifacts to the Fly Registry, it creates a release - including the binaries produced, an AI-generated summary, captured architectural decisions, merged PRs and commits. All of it is searchable. So when you ask your agent "when did we release a fix for the connection timeout" it runs a semantic search across all of that and finds the right evidence. No version numbers, no digging through run IDs, no Git hashes.
Fly also understands your runtime environments and works with whatever deployment framework your coding agent already knows - Argo CD, Flux, etc. It tracks what gets deployed through them automatically, so "what's the latest change in production right now" gets a real answer.
A few other things worth knowing:
- Integrates out of the box with your GitHub repositories
- Works with Claude Code, Cursor, Codex, etc. via MCP
- Agentless integration with your runtime environments
- Slack notifications in natural language - Fly watches releases and notifies with context when something matches
- Runs Artifactory as a scalable package registry under the hood
- Supports Docker, Helm, npm, PyPI, Maven, Gradle, Go, and .NET, with more package types coming
- Once installed, your package managers just work: npm publish, pip install, docker push - all route through your private Fly registry automatically. No .npmrc editing, no token wrangling
Take it for a spin and upgrade the way you manage your release binaries - and finally get real visibility into WHAT is actually running where. Happy to get into how it works, what else it handles, and where we're taking it next.
No comments yet.
