Fleet gives you SQL-based visibility into every endpoint — query any device in real time, manage configurations in Git, and build compliance evidence without touching each machine individually. I help teams get from zero to a production-ready, versioned Fleet deployment.

What this looks like

• GitOps repo creation — osquery config, query packs, and schedule in Git, with branching strategy and CI validation so changes are reviewed before they reach endpoints
• Query library and policies — queries for software inventory, process auditing, network connections, and compliance evidence (CIS, SOC 2, ISO 27001); with pass/fail endpoint policies built on the same baseline
• Fleet OSS setup — self-hosted Fleet deployment on your infrastructure, with enrolment, teams, and role-based access configured from day one
• Migrations and coexistence — move from ad-hoc osquery deployments or SIEM-only visibility to a managed Fleet setup, or run Fleet alongside your existing tools to close visibility gaps without disruption
• Reporting queries — SQL queries and saved views covering fleet health, patch posture, running processes, installed software deltas, and threat indicators

Platform support

macOS, Linux (Debian/Ubuntu, RHEL/Fedora, NixOS), Windows, and Android via Fleet’s unified agent. Mixed fleets are the common case, not the exception.

Who it’s for

Security and IT teams that need endpoint visibility across a mixed fleet. Compliance teams that need queryable evidence at scale. Engineers who want fleet configuration in code, not buried in a web UI.

What I don’t do

I don’t run Fleet as a managed service. I build the setup, the repository, and the documentation — then hand it to your team in a state they can own and extend.