No record of intent.
Audit logs show who changed a setting and when, not why, not what the old value was, and not whether it was tested. Six months later nobody can reconstruct the decision.
INFRASTRUCTURE AS CODE
ClickOps manages devices by hand. Fleet manages them as code.
Define your fleet in version-controlled YAML. Review every change in a pull request. Let Fleet enforce the desired state across macOS, Windows, Linux, iOS, iPadOS and Android. Fleet is MIT-licensed open source and runs on your own infrastructure.
organizations
devices managed
average support response time
countries
Where ClickOps runs out of road
Configuration drift.
One engineer tweaks a setting. Another makes a conflicting change. What counts as standard stops being knowable, and the only way to find out is to go and look.
Knowledge leaves with people.
Configuration knowledge lives in the heads of a few admins. When someone leaves, the context goes with them, and the next person inherits settings without reasons.
Teams stay reactive.
Repetitive GUI work consumes the time that should go to higher-priority projects. The queue never shortens because the work never becomes repeatable.
From clicks to commits
| Fleet GitOps | ClickOps | |
|---|---|---|
| Primary interface | Git repository and YAML | GUI or web console |
| Source of truth | Version-controlled files | Spreadsheets or a vendor database |
| Change control | Pull requests with peer review | Verbal approval or action logs |
| Drift management | Continuous self-healing | Manual or periodic reporting |
| Rollback | Revert a Git commit | Manual redo, or restore from backup |
| Audit trail | Immutable commit history | Fragmented, or click history |
| Onboarding a new engineer | Read the repository | Shadow a senior admin |
| Coverage | One workflow, every operating system | One console per platform |
| Tooling required | fleetctl and any Git provider | The vendor's console only. |
Fleet's GitOps controls profiles, policies, software, queries, labels and settings. Available in Fleet Free and Fleet Premium.
Adopt it without rebuilding anything
Fleet's GitOps is a first-party workflow, not a community integration. You do not need Terraform, a vendor-specific cloud subscription or a rewrite. Export what you have, put it in the repository you already use, and let Fleet enforce it from there.
- 1.
Export your current configuration to YAML. Fleet ships fleetctl, a command line tool that reads YAML and applies it to your Fleet server.
- 2.
Open a pull request. Every change is peer-reviewed before it reaches a device, and nothing unreviewed ships.
- 3.
Connect fleetctl to your CI runner. From then on Fleet compares device state against Git and restores the approved configuration automatically.
Recover from a bad change by reverting one commit.
Teams already managing devices as code
Fastly
“The shift to GitOps has modernized our operations, giving us the agility and change control we needed…”
Dan Jackson
Senior Manager, Systems Engineering, Fastly
Fastly gains visibility into all endpoints and critical infrastructure around the world.
One platform, every endpoint
Terraform not required
Fleet ships fleetctl, a CLI that reads YAML and applies it to your Fleet server.
Full console coverage
Profiles, policies, software, queries, labels and settings. Your whole admin console, not a subset.
Any Git provider
GitHub, GitLab, Bitbucket or anything Git-compatible. No vendor cloud subscription.
Every operating system
One repository and one workflow for macOS, Windows, Linux, iOS, iPadOS and Android.
Host it your way
Your infrastructure or Fleet's cloud, with the same features either way.
Open source, MIT licensed
All of Fleet's source code is public. Read it, audit it, adapt it.
Pricing you can read without a phone call
Fleet Free
$0
Basic features · per host / month
- Core device management
- Self-hosted
- GitOps, SSO and REST API
- Community Slack
Fleet Premium
$7.00
Manage every endpoint · per host / month
- Managed cloud or self-hosted
- MDM migration and zero-touch setup
- Disk encryption, RBAC and audit logging
- Email, phone and video support
Custom
Let's talk
Large deployments · volume pricing
- Everything in Premium
- Volume pricing
- Migration support
FAQ
Is Fleet actually open source?
Yes. Fleet is MIT-licensed and all of Fleet's source code is public, along with the company handbook. You can read exactly how devices are managed and adapt it to your needs.
Do we need Terraform?
No. Fleet ships fleetctl, a command line tool that reads your YAML and applies it to your Fleet server. Connect it to your CI runner and you have a complete GitOps pipeline, with no third-party provider required.
Does GitOps cover everything, or just some settings?
Fleet's GitOps controls profiles, policies, software, queries, labels and settings. It covers the entire admin console rather than a subset.
Do we need to write code?
No. Configuration is YAML, which is structured and readable rather than programming. You describe the desired state and Fleet applies the changes needed. Fleet Free is available at no cost if you want to try it before talking to anyone.
Put your fleet in version control.
Walk through your environment with Fleet, or join a free workshop and build a GitOps pipeline for device management alongside other engineers.