🧭 Product maturity assessment

Fleet provides comprehensive device management across the entire computing lifecycle, from enrollment through configuration, monitoring, maintenance, and offboarding. As we continue to evolve and expand our capabilities, different stages and features are at varying levels of maturity. This assessment provides transparency into Fleet's current state and roadmap, helping customers, prospects, and internal teams understand where we excel today and where we're investing for the future. We use a structured maturity framework that evaluates both individual categories (specific features and capabilities) and overall stages (major lifecycle areas) to give a clear picture of Fleet's product maturity.

Maturity legend

Category maturity

• 🥚 Planned: Not yet implemented in Fleet, but on our roadmap
• 🐣 Minimal: A minimal foundation so people can see where we're going and to validate customer need
• 🐥 Viable: Used by customers to solve real problems
• 🦆 Complete: Contains a competitive feature set sufficient to displace other device management tools
• 🦢 Lovable: Provides an elevated experience that customers love

Stage lifecycle

• Early development (most categories 🥚 Planned/🐣 Minimal)
• Core capabilities available (key platforms/categories 🐥 Viable)
• Enterprise ready (majority 🐥 Viable/🦆 Complete, competitive feature set)
• Market competitive (🦆 Complete across all major use cases)
• Market leading (🦢 Lovable in key areas, 🦆 Complete elsewhere)

Computing lifecycle stages

Enroll

Stage lifecycle: Enterprise Ready

Analyst reports

• Gartner: Market Guide for Endpoint Management Tools - 2025-01-13

Configure

Stage lifecycle: Enterprise Ready

Analyst reports

• Gartner: Market Guide for Endpoint Management Tools - 2025-01-13

Monitor

Stage lifecycle: Market Competitive

Analyst reports

• Gartner: Market Guide for Endpoint Management Tools - 2025-01-13

Maintain

Stage lifecycle: Enterprise Ready

Analyst reports

• Gartner: Market Guide for Endpoint Management Tools - 2025-01-13
• Gartner: Innovation Insight: Autonomous Endpoint Management - 2025-01-15

Offboard

Stage lifecycle: Core Capabilities Available

Analyst reports

• Gartner: Market Guide for Endpoint Management Tools - 2025-01-13

Cross-cutting stages

Platform support

Stage lifecycle: Varies by platform (see individual platform rows)

Integrate

Stage lifecycle: Market Leading

Operate

Stage lifecycle: Market Competitive

Planned category maturity

The maturity framework makes it easy to visualize where Fleet is making investments and resulting category maturity improvements. As part of the planning process for each category, the set of features required and expected date to reach the next maturity is maintained.

How to fill out and maintain this page

Use this guide to keep assessments consistent and up to date. Updates are typically made quarterly and when major features ship.

Maturity levels (per category)

• 🥚 Planned: Not yet implemented, but on Fleet's roadmap
• 🐣 Minimal: Basic foundation, validating customer need
• 🐥 Viable: Used by customers in production to solve real problems
• 🦆 Complete: Competitive feature set that can replace competitors
• 🦢 Lovable: Elevated experience that customers love (e.g., NPS/surveys)

When deciding a category's maturity, ask:

1. Is it shipped? If not, it's Planned
2. Is it used in production? If yes, at least Viable
3. Does it match leading competitors? If yes, Complete
4. Do customers praise the experience? If yes, Lovable

Stage lifecycle (per stage)

Choose the best description for the stage overall based on the mix of category maturities:

• Early Development (most categories Planned/Minimal)
• Core Capabilities Available (key platforms/categories Viable)
• Enterprise Ready (majority Viable/Complete, competitive feature set)
• Market Competitive (Complete across all major use cases)
• Market Leading (Lovable in key areas, Complete elsewhere)

Replace placeholders with the current assessment. Look at the overall mix of category maturities in the stage to determine the appropriate lifecycle stage.

Platform support maturity (per platform)

Platform support maturity is determined by aggregating all platform-specific categories across all lifecycle stages (Enroll, Configure, Monitor, Maintain, Offboard). Use the following algorithm:

1. Identify all platform-specific categories: Collect all categories from Enroll, Configure, Monitor, Maintain, and Offboard that apply to the platform (e.g., "macOS", "Windows", "Apple", "iOS/iPadOS", "Android", "Linux", "ChromeOS", or specific platform mentions).

2. Count maturity distribution: Calculate the percentage of categories at each maturity level (🥚 🐣 🐥 🦆 🦢).

3. Apply maturity criteria:

   • 🥚 Planned: Platform is actively being researched with a few Planned categories identified, but no Minimal or higher categories exist yet
   • 🐣 Minimal: 50%+ of categories are Planned/Minimal, with at least one Minimal category in a critical area (enrollment or basic configuration)
   • 🐥 Viable: 50%+ of categories are at least Viable, AND enrollment is at least Viable, AND at least 2 out of 3 critical categories (enrollment, basic configuration, monitoring) are at least Viable, AND at least one category from Configure/Maintain/Monitor is at least Viable
   • 🦆 Complete: 75%+ of categories are Complete, AND enrollment is at least Viable, AND all critical categories (enrollment, basic configuration, monitoring) are at least Viable
   • 🦢 Lovable: 50%+ of categories are Complete/Lovable, AND key areas (enrollment, monitoring, or configuration) include at least one Lovable category

4. Critical categories (must be considered):

   • Enrollment (foundational - must be at least Viable for platform to be Viable+)
   • Basic configuration (profiles or equivalent)
   • Monitoring (device status or inventory)

5. Edge cases:

   • If a platform has very few categories (< 5), use qualitative judgment based on coverage of critical capabilities
   • For platform variants (e.g., Linux distributions), consider both shared capabilities and platform-specific features

Example calculation for macOS:

• Categories: DEP/ABM enrollment (🦆), Account Driven User Enrollment (🐣), Setup experience (🐥), Configuration profiles (🐥), Disk encryption (🦆), OS update management (🐥), Remote lock/wipe (🦆)
• Distribution: 43% Complete, 43% Viable, 14% Minimal
• Enrollment: DEP/ABM enrollment (🦆) ✓
• Critical categories: Enrollment (🦆) ✓, Basic configuration (🐥) ✓, Monitoring (🦆 via cross-platform) ✓ = 3/3 ✓
• At least one Configure/Maintain/Monitor category Viable+: Multiple (Disk encryption, Remote lock/wipe, etc.) ✓
• Result: 🐥 Viable (43% Complete, not 75%+ Complete, but all critical categories met)

Example calculation for Linux (Ubuntu):

• Categories: Linux enrollment (🐥), Setup experience (Linux) (🐣), Disk encryption management (Linux) (🦆), OS update management (Linux) (🥚), Remote lock/wipe (Linux) (🦆)
• Distribution: 40% Complete, 20% Viable, 20% Minimal, 20% Planned
• Enrollment: Viable (🐥) ✓
• Critical categories: Enrollment (🐥) ✓, Basic configuration (🐣) ✗, Monitoring (🦆 via cross-platform) ✓ = 2 out of 3 ✓
• At least one Configure/Maintain/Monitor category Viable+: Disk encryption (🦆) and Remote lock/wipe (🦆) ✓
• Result: 🐥 Viable (60% at least Viable, enrollment Viable, 2/3 critical categories Viable+)

What to include in each stage section

1. Stage lifecycle: Replace the placeholder with the current stage-level assessment
2. Analyst reports: Add any relevant mentions (optional)
3. Category maturity table: For each category row, set Current maturity (emoji only) and projections for future quarters (Q1–Q4)
   • Category name: Include a link to Fleet documentation if available, or plain text if not
   • Maturity columns: Use only emojis (🥚 🐣 🐥 🦆 🦢) without text labels

Example row transformation:

• Before: | DEP/ABM enrollment | | | | | |
• After: | [DEP/ABM enrollment (Apple)](https://fleetdm.com/guides/apple-mdm-setup#apple-business-manager-abm) | 🦆 | 🦆 | 🦆 | 🦆 | 🦆 |

This indicates: Current maturity is Complete (🦆), with Complete maintained across all quarters.

Tips for projections

• Be realistic; don't overpromise
• Show progress; gradually advance maturity levels
• Consider dependencies; some categories need others to mature first
• Align with Fleet's public roadmap and release plans
• Not everything must advance each quarter

Common patterns:

• Rapid maturation: 🥚 → 🐣 → 🐥 → 🦆 → 🦢
• Steady improvement: 🐥 → 🐥 → 🦆 → 🦆 → 🦢
• Maintenance mode: 🦆 → 🦆 → 🦆 → 🦢 → 🦢
• Already excellent: 🦢 → 🦢 → 🦢 → 🦢 → 🦢

Quarterly review checklist

1. Advance categories that met goals; adjust projections as needed
2. Update stage lifecycle if overall maturity improved based on category changes
3. Review and update category names to reflect current naming conventions
4. Update the "Last updated" date in your PR description

Governance

• Internal review: Product design and engineering to validate assessments
• Consistency: Ensure projections align with public roadmap and release plans
• Transparency: Avoid commitments that create legal obligations; treat projections as targets