agile.flights Review (2026): Pricing, Features & Honest Verdict
TLDR
agile.flights replaces Scrum jargon with aviation metaphors: Flights instead of sprints, Landings instead of releases, Crates instead of user stories. Fresh take on project management. Best for: startups tired of agile ceremony. Price: Free to start, paid plans undisclosed. Rating: 6.6/10
What is agile.flights?
We found agile.flights while browsing Product Hunt for fresh approaches to project management. Created by a developer named Olivia in Sweden, the tool launched on March 5, 2026 with 109 upvotes. It replaces traditional agile terminology with aviation metaphors that non-technical stakeholders can immediately understand.
The methodology, inspired by Simon Hoiberg’s “Flight Manual” essay, reimagines how teams track work. Sprints become Flights (time-boxed but without fixed lengths, using ETAs instead). Releases become Landings. User stories become Crates. Team leads become Captains. The whole-company legibility angle is genuinely compelling. Your CEO probably does not know what a sprint retrospective is, but they understand that Flight 7 is “In Flight” and expected to land next Tuesday.
Key Features
Airport Board
A visual status board showing all Flights with four states: Takeoff, In Flight, Landed, and Emergency. Real-time progress tracking without status meetings. Each Flight shows its Captain, Crew, ETA, and progress against items. The board communicates project status in a way that non-technical people instantly grasp.
Captain/Crew Role System
Every Flight has a single Captain (accountable owner), Crew members (contributors), and Ground Mechanics (handling maintenance between Flights). Clear accountability without the overhead of Scrum ceremonies. The single-owner model prevents the “shared responsibility means no responsibility” problem.
Ground Work Separation
Dedicated space for maintenance, tech debt, and operational tasks between Flights. This prevents maintenance work from getting buried in backlogs or competing with feature development for sprint slots. Ground Mechanics handle this work independently while Flights focus on delivery.
Dev Tool Integrations
Connects to GitHub, Jira, and Linear with webhook support. Auto-landing configuration triggers Flight completion based on external signals. Real-time item counts and progress from external sources. This lets teams keep their existing dev tools while adding the Flights visibility layer on top.
Pricing
- Free plan available (“Start for free”)
- Paid plans exist but prices are not publicly disclosed
- Enterprise features include PDF branding, Google SSO with domain enforcement, organization management
- Contact support@agile.flights for custom/enterprise pricing
The undisclosed pricing is a concern. Without knowing what the paid plans cost, it is hard to evaluate the full value proposition. The free plan lets you start, but feature limitations are unclear.
Pros and Cons
The aviation metaphor works surprisingly well. Non-technical stakeholders immediately understand project status without learning agile vocabulary. The Airport Board is a smart abstraction over complex project data. Ground Work separation genuinely solves the “tech debt gets ignored” problem. And the integrations with existing dev tools (GitHub, Jira, Linear) mean teams do not have to switch their entire workflow.
The concerns are practical. This appears to be a solo developer project, which raises questions about long-term maintenance and support. Pricing is undisclosed. The user base is small and unproven. The methodology itself is niche and untested outside a few teams. And established tools like Linear, Jira, and ClickUp have massive ecosystems that agile.flights cannot match.
| Plan | Price | Plan Features | Best For |
|---|---|---|---|
| Free | $0 | Basic features, limitations unclear | Trying the methodology |
| Paid | Undisclosed | Extended features, Google SSO, PDF branding | Growing teams |
| Enterprise | Custom | Organization management, domain enforcement | Larger companies |
Who Should Use agile.flights?
Startups where non-technical founders need to understand engineering progress. Teams frustrated with Scrum ceremonies and agile overhead. Organizations wanting a lightweight project visibility layer on top of existing dev tools. Teams that have tried agile and found the terminology more confusing than helpful.
Who Should Skip agile.flights?
Enterprise teams needing compliance, audit trails, and established vendor support. Large engineering organizations with mature agile practices. Teams that need deep resource management, budgeting, and reporting. Anyone requiring a proven, battle-tested tool with an established community.
Alternatives
Linear
Modern, fast issue tracker for software teams. Clean interface, keyboard-first design, and excellent performance. $8/user/month. The closest competitor in the “developer-friendly PM” space. Much more mature and proven.
Shortcut
Lightweight agile PM built for software teams (formerly Clubhouse). Kanban, sprints, roadmaps, and docs. From $8.50/user/month. Good balance of features and simplicity.
Plane
Open-source alternative to Jira, Linear, and ClickUp. Tasks, sprints, and docs. Free self-hosted option. Good for teams wanting full control over their PM tool.
The Verdict
agile.flights is a creative reimagining of project management that solves a real communication problem between technical and non-technical stakeholders. The aviation metaphor is more than a gimmick. But the product is very early, pricing is unclear, and it appears to be a solo developer effort. Worth trying the free plan if your team struggles with agile jargon and ceremony. Not yet ready to replace established tools for serious production use.
FAQ
Is agile.flights free?
There is a free plan available. Paid plan pricing is not publicly disclosed. Contact support@agile.flights for details.
What is the Flights methodology?
A project management approach replacing agile terms: Flights (sprints), Landings (releases), Crates (user stories), Captains (team leads), Ground Mechanics (maintenance). Inspired by Simon Hoiberg’s “Flight Manual.”
Does agile.flights replace Jira?
Not exactly. It integrates with Jira (and GitHub and Linear) as a visibility layer on top. Your dev team keeps using their existing tools while agile.flights provides the cross-company status view.
Who built agile.flights?
Created by Olivia in Sweden. Built using AI-assisted development (Claude/Anthropic). The methodology has been tested in production for over a year before the public launch.
Can I integrate with my existing dev tools?
Yes. GitHub, Jira, and Linear integrations with webhook support and real-time progress tracking from external sources.
agile.flights Pros & Cons
What We Like
- Aviation metaphor makes project status instantly legible to non-technical stakeholders
- Ground Work separation prevents tech debt from being buried in backlogs
- Integrates with GitHub, Jira, and Linear as a visibility layer
- Single Captain accountability model prevents shared-responsibility problems
What Could Be Better
- Appears to be a solo developer project with limited long-term guarantees
- Paid plan pricing is not publicly disclosed
- Very early with small, unproven user base
- Cannot match the ecosystems of established tools like Linear or Jira
agile.flights FAQ
Is agile.flights free?
There is a free plan. Paid plan pricing is not publicly disclosed.
What is the Flights methodology?
Replaces agile terms: Flights (sprints), Landings (releases), Crates (user stories), Captains (team leads). Inspired by Simon Hoiberg.
Does agile.flights replace Jira?
Not exactly. It integrates with Jira as a visibility layer on top. Dev teams keep using existing tools.
Who built agile.flights?
Created by Olivia in Sweden. Built with AI-assisted development. Methodology tested for over a year before public launch.
Can I integrate with existing dev tools?
Yes. GitHub, Jira, and Linear with webhook support and real-time progress tracking.
How much does agile.flights cost?
agile.flights pricing starts at Undisclosed. A free plan is available.
