Meta pixel



Fleet is an open-core company that sells subscriptions that offer more features and support for Fleet and osquery, the leading open-source systems management platform and security agent. Today, Fleet enrolls millions of laptops and servers, and it is especially popular with enterprise IT and security teams.

Fleet is dedicated to a comprehensive strategy against whatever this is:

  • 🔌 making security and IT interoperable and easy to automate with open standards and data.
  • 🚪 creating an inviting (outsider-friendly) way to manage computers, CVEs, and infrastructure.
  • 🪟 building clarity and trust through open-source software.

This is the guiding purpose behind Fleet's product strategy, operating principles, and brand.


All remote

Fleet Device Management Inc. is an all-remote company with 40+ team members spread across four continents and nine time zones. The broader team of contributors worldwide submits patches, bug reports, troubleshooting tips, improvements, and real-world insights to Fleet's open-source code base, documentation, website, and company handbook.

Open source

Fleet is open by design. The majority of the code, documentation, and content we create at Fleet is public and source-available. The Fleet handbook is the central guide for how we run the company, and even it is open to the world. We strive to be open and transparent in the way we run the business, as much as confidentiality agreements (and time) allow. We perform better with an audience, and our audience performs better with us.

Why this way?

At Fleet, we write things down. Even when we might be wrong. This helps us move quickly, provides clarity, and enables asynchronous work. The "Why this way?" page in the handbook discusses some of our most important decisions about the best way to work and the reasoning for them. For example: "Why open source?", "Why do we use a wireframe-first approach?", "Why direct responsibility?, and "Why handbook-first strategy?" You can read more about these principles and suggest improvements in "📖Company/Why this way?"

An icon indicating that this section has important information

You can read more about what it's like to work at Fleet in "📖Company/Communications".

Open positions

Is it any good?

Here are a few reasons to work at Fleet:

  • Work from anywhere with good internet. (We're 100% remote, No office. No commute.) Everyone works remote, but you don't feel remote. There is no 'headquarters'. You are free to travel and move. Organize your workday to fit your lifestyle. Take breaks. Go to the dentist.
  • Fleet can offer you a competitive salary, significant equity, and an independent, outsider-friendly culture. Work with helpful, kind, and motivated people who know what they're doing.
  • At Fleet, we value focus, iteration, and meaningful results – not 60 hour work weeks. We are non-judgmental and laser-focused on growing the company.
  • Work closely with experienced, well-funded founders and a great team, including the people who created osquery and Sails. We care about openness and transparency.
  • Work computers can be private and safe. Help make endpoint monitoring less intrusive and more transparent.
  • Protect the production servers and employee laptops of Earth's largest companies. Work on a product used by lots of people who care about what you do.
  • Fleet is growing quickly, with significant revenue from Fortune 1000 customers. You will have lots of opportunities to make decisions, learn, and try new things.


Fleet's values are a set of five ideals adopted by everyone on the team. They describe the shared mindset we are working together to create, inside and outside the company: 🔴 Empathy, 🟠 Ownership, 🟢 Results, 🔵 Objectivity, and 🟣 Openness.

Values play an important role in hiring, performance management, and compensation decisions. When a new team member joins the company, they adopt our values, from day one.

This way, everybody knows what to expect from the people they work with.

🔴 Empathy

Empathy leads to smarter decisions. Take an interest in what people are going through, so you can help make it better.

  • Assume positive intent. Think and say positive things, and assume others are doing the same. Keep it light.
  • Be a helper. Take care of customers first. But give hospitality and service with a smile to everyone you can.
  • Read what you write. Shorten it. Repeat.
  • Get curious. Wonder about things. Notice. Ask people genuine questions, and listen closely.

🟠 Ownership

It takes a fully-activated mind to achieve ambitious goals, and remote work requires self-discipline. Think like an owner of the company.

  • Be reliable. Reply quickly to email, Slack, and GitHub. Prepare for meetings. Arrive on time. Use handbooked processes and decisions.
  • Finish what you start. Follow through on commitments. Take responsibility for mistakes. There's no time for finger-pointing. Just fix it.
  • No one is coming. Take care of things that need doing, or loop in the right people fast. It's up to you.
  • Think long term. Contribute to the big picture, beyond your department's goals. Reduce maintenance. Beware the thicket.

🟢 Results

We work to get results. How we work determines what we get. Aim to deliver results daily.

🔵 Objectivity

To reach our goals, we need to see reality clearly.

  • Find the bottleneck. When something isn't working, look for the worst part. Fix that first.
  • Change your mind. Be willing to reconsider in the face of new evidence. Escape the sunk cost fallacy.
  • Be rigorous. A lucky streak can do more harm than good. Understand why it works first. Change one variable at a time.
  • Think for yourself. Remember how often conventional wisdom isn't.

🟣 Openness

Take the time to make yourself and your work visible. This also takes courage.


2014: Origins of osquery

In 2014, our cofounder Zach Wasserman, together with Mike Arpaia and the rest of their team at Facebook, created an open source project called osquery.

2016: Origins of Fleet v1.0

A few years later, Zach, Mike Arpaia, and Jason Meller founded Kolide and created Fleet: an open source platform that made it easier and more productive to use osquery in an enterprise setting.

2019: The growing community

When Kolide's attention shifted away from Fleet, and towards their separate, user-focused SaaS offering, the Fleet community took over maintenance of the open-source project. After his time at Kolide, Zach continued as lead maintainer of Fleet. He spent 2019 consulting and working with the growing open source community to support and extend the capabilities of the Fleet platform.

2020: Fleet was incorporated

Zach partnered with our CEO, Mike McNeil, to found a new, independent company: Fleet Device Management Inc. In November 2020, we announced the transition and kicked off the logistics of moving the GitHub repository.

2022: Millions of hosts

Fleet raised its Series A funding round. The world now has at least 1.65 million computers and virtual hosts enrolled in Fleet, including enterprises, governments, startups, families, and hobbyist racks all over the world.

2023: Your last MDM migration

Fleet added support for scripting and management capabilities on macOS, Windows, and Linux devices, allowing IT departments to manage devices more consistently using modern tooling and best practices. This allowed many customers to simplify their management practices. In several cases, Fleet was also able to save customers several hundreds of thousands of dollars (USD) by cutting tool overlap across platforms such as Jamf, Airwatch, Intune, MobileIron, Nexthink, Tanium, Uptycs, and Rapid7.

An icon indicating that this section has important information

Org chart

To provide clarity about decision-making, responsibility, and resources, everyone at Fleet has a manager, and every manager has direct reports. Fleet's organizational chart is accessible company-wide as a sub-tab in "🧑‍🚀 Fleeties" (private google doc). On the other sub-tabs, you can also check out a world map of where everyone is located, hiring stats, and fun facts about each team member.

  • 🔦 Business Operations: The Business Operations department is directly responsible for people operations, finance + invoicing, tax, compliance, and legal + deal desk.
  • 🌦️ Customer Success: The customer success department is directly responsible for ensuring that customers and community members of Fleet achieve their desired outcomes with Fleet products and services.
  • 🐋 Sales: The Sales department is directly responsible for attaining the revenue goals of Fleet and helping customers deliver on their objectives.
  • 🫧 Demand: The Demand department is directly responsible for growing awareness of Fleet and nurturing the community through participation in events, conversations, and other programs.
  • 🚀 Engineering: The Engineering department at Fleet is directly responsible for writing and maintaining the code for Fleet's core product, as well as Fleet's Information technology (IT) infrastucture.
  • 🦢 Product Design: The Product Design department is directly responsible for defining and prioritizing the changes made to the core product, Fleet API, and reference documentation.
  • 🌐 Digital Experience: The Digital Experience department is directly responsible for the framework, content design, and technology behind Fleet's remote work culture and overall brand experience, including, the handbook, issue templates, UI style guides, consistent brandfronts, internal tooling, Zapier flows, Docusign templates, key spreadsheets, and project management processes.


While most improvements at Fleet are driven by informal conversations with customers and open-source contributors, the company also has a few dozen advisors and investors, including
Sid Sijbrandij (GitLab), Dylan Field (Figma), Mike Arpaia (osquery), Alexandr Wang (Scale AI), Sanjay Poonen (VMware, Cohesity), and other smart people who are eager to help. If you have a question for one of them, Fleet's CEO is happy to introduce you. (Just ask.)

An arrow pointing upBack to top