# Explore Fly

---

## Overview

See how Fly connects your code, packages, releases, and deployments into a single traceable chain.

These are the core entities Fly manages. Each can be accessed from multiple interfaces: your coding agent, Fly Web, or Slack.

- **[Git Repositories](git-repositories/)** -- Your connected GitHub repositories. Fly watches them for workflows, tracks artifacts, and generates releases.
- **[Artifacts](artifacts/)** -- Every package and image your team publishes or caches. Stored in your private Fly Registry.
- **[Releases](releases/)** -- Semantic records of workflow runs. What changed, who shipped it, what was produced, where it's running.
- **[Runtime Environments](runtime-environments/)** -- Deployment targets connected to your K8s namespaces for full runtime visibility.
- **[Workflows](workflows/)** -- Your GitHub Actions workflow files and their Fly configuration status.
- **[Tokens](tokens/)** -- Credentials for connecting environments, configuring package managers, and integrating external systems.
- **[Notifications](notifications/)** -- Natural-language watches that notify you in Slack when events happen.
- **[Team Management](team-management/)** -- User roles, permissions, and access control.

---

## Next Steps

- [Getting Started →](../getting-started/) - Set up your account and ship your first release
- [From Code to Production →](../developer-workflow/) - Publish packages, automate releases, and deploy
- [Fly Web →](../getting-started/fly-web/) - Your team's web interface