Deployment |
||
Managed cloud | ||
Self-hosted | ||
Multi-tenancy | ||
Deployment tools |
Configuration |
||
Private update registry | ||
Control agent versions | ||
Command line tool (CLI) | ||
GitOps | ||
Two-factor authentication* | ||
Role-based access control | ||
Audit logging | ||
Scope transparency |
Integrations |
||
REST API | ||
Webhooks | ||
Grant API-only access | ||
Single sign on | ||
Automatic user creation (JIT, SCIM) | ||
Third-party automation | ||
Third-party orchestration | ||
Munki compatibility + visibility |
Support |
||
Open-source issue tracker (GitHub) | ||
Community Slack channel | ||
Unlimited email support (confidential) | ||
Phone and video call support |
* Coming soon
* Coming soon
Deployment |
||
Managed cloud | ||
Self-hosted | ||
Multi-tenancy | ||
Deployment tools |
Configuration |
||
Control agent versions | ||
Command line tool (CLI) | ||
GitOps | ||
Two-factor authentication* | ||
Role-based access control | ||
Scope transparency |
Integrations |
||
REST API | ||
Webhooks | ||
Grant API-only access | ||
Single sign on | ||
Automatic user creation (JIT, SCIM) | ||
Third-party automation | ||
Third-party orchestration | ||
Munki compatibility + visibility |
Support |
||
Open-source issue tracker (GitHub) | ||
Community Slack channel | ||
Unlimited email support (confidential) | ||
Phone and video call support |
* Coming soon
* Coming soon
Deployment |
||
Managed cloud | ||
Self-hosted |
Configuration |
||
Private update registry | ||
Audit logging | ||
Scope transparency |
Integrations |
||
Grant API-only access |
Support |
||
Open-source issue tracker (GitHub) | ||
Community Slack channel | ||
Unlimited email support (confidential) | ||
Phone and video call support |
* Coming soon
* Coming soon
Parts of the UI are unfamiliar to us. Is this too far out of my team's comfort zone?
You already know how to manage the operating system. In Fleet, you can focus on managing Apple, Windows and Linux; not Intune, Omnissa, and your anxiety.
Fleet is perfect, it's just missing this one feature...
We're moving pretty fast, and we have every incentive to listen. At Fleet, everyone can contribute. We also regularly deliver customer promises, and all the code is 100% source-available.
What actually is Fleet? Was it purpose built for this kind of thing?
Fleet started as an osquery management server. After 10 years of production osquery use at scale in huge organizations, Fleet added "write" and "execute" device management capabilities, with all the necessary integrations to be comparable with other device management platforms like Omnissa (fka WS1, fka Airwatch), Jamf, Intune, and more. Today, Fleet is actively used as the next-gen MDM in homelabs all over the world, and at larger fleets at Epic Games, Cisco, Stripe, Fastly, Lear, and more.
Couldn’t find an answer? Talk to us.
{{selectedFeature.description}}
Learn more