From bf1f155a321df1f386dc0932ecd87d600bce92ab Mon Sep 17 00:00:00 2001 From: "kiloconnect[bot]" <240665456+kiloconnect[bot]@users.noreply.github.com> Date: Mon, 23 Feb 2026 22:23:25 -0600 Subject: [PATCH] Emphasize infrastructure as code over GitOps on fleet-gitops marketing page (#40224) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit ## Summary Updates the `/fleet-gitops` marketing page (`website/views/pages/fleet-gitops.ejs`) and its meta tags (`website/config/routes.js`) to lead with **infrastructure as code** rather than **GitOps** throughout headings, body copy, and meta tags — using varied, natural phrasing instead of rigidly prefixing "Fleet" every time. Also adds a new **AI-accelerated IT** section with Kilocode screenshot reference and three pitch points about AI-accelerated device management. ### Changes - Page title tag: `Fleet GitOps` → `Infrastructure as code` - Meta description updated to emphasize infra-as-code - Hero `

`: `Fleet GitOps` → `Infrastructure as code` - Bottom CTA `

`: `Fleet GitOps` → `Infrastructure as code for your devices` - Hero paragraph rewritten to lead with infra-as-code - Features list item heading: `Get to know Fleet infrastructure as code` → `Manage your infrastructure as code` - Section heading: `Get to know Fleet infrastructure as code` → `Infrastructure as code for your devices` - Body copy: `adopt Fleet infrastructure as code` → `adopt infrastructure as code for device management` - Image alt text, caption, and two-column feature body copy updated - Workshop CTA heading: `GitOps workshop` → `Infrastructure as code workshop` - Challenges section rewritten to lead with infra-as-code; GitOps still mentioned where it fits naturally - Testimonial quote updated to reference infra-as-code - **New**: AI-accelerated IT section with Kilocode screenshot and three pitch points: - Everyone can contribute, but an expert from IT stays the human in the loop - Without GitOps there is no way to do AI-accelerated device management - Iterate more quickly by reducing friction and hand-offs with natural language changes via tools like Kilocode ### What stays as GitOps - Workshop href (`/gitops-workshop`) — URL unchanged - One natural mention: "If DevOps or GitOps is already used by an organization…" - Workshop link anchor text in the challenges section body Built for [mikermcneil](https://fleetdm.slack.com/archives/D0AFASLRHNU/p1771879170001129) by [Kilo for Slack](https://kilo.ai/features/slack-integration) --------- Co-authored-by: kiloconnect[bot] <240665456+kiloconnect[bot]@users.noreply.github.com> Co-authored-by: Mike McNeil Co-authored-by: Kilo Code --- website/config/routes.js | 4 +- website/views/pages/fleet-gitops.ejs | 66 ++++++++++++++++++---------- 2 files changed, 46 insertions(+), 24 deletions(-) diff --git a/website/config/routes.js b/website/config/routes.js index 79cf738008..b9dcd97e0c 100644 --- a/website/config/routes.js +++ b/website/config/routes.js @@ -580,8 +580,8 @@ module.exports.routes = { 'GET /fleet-gitops': { action: 'view-fleet-gitops', locals: { - pageTitleForMeta: 'Fleet GitOps', - pageDescriptionForMeta: 'See every change, undo any error, repeat every success. Fleet and GitOps work together to optimize your endpoint management strategy.', + pageTitleForMeta: 'Infrastructure as code', + pageDescriptionForMeta: 'See every change, undo any error, repeat every success. Fleet\'s infrastructure as code approach lets you manage every endpoint setting in version-controlled YAML.', currentSection: 'platform', } }, diff --git a/website/views/pages/fleet-gitops.ejs b/website/views/pages/fleet-gitops.ejs index daf7f7d4db..5c65716b63 100644 --- a/website/views/pages/fleet-gitops.ejs +++ b/website/views/pages/fleet-gitops.ejs @@ -3,10 +3,10 @@
-

Fleet GitOps

+

Infrastructure as code

The future of device management is declarative

-

See every change, undo any error, repeat every success. Fleet and GitOps work together to optimize your endpoint management strategy.

+

See every change, undo any error, repeat every success. Fleet's infrastructure as code approach lets you manage every endpoint setting in version-controlled YAML — with GitOps workflows built in.

Get a demo @@ -15,7 +15,7 @@
-
Get to know Fleet GitOps
+
Manage your infrastructure as code

Implement collaboration, version control, and automation workflows built into Fleet that accelerates enforcing controls, OS updates, software deployments, and reduce downtime.

Learn more
@@ -26,7 +26,7 @@
Challenges
-

The most common first question about GitOps: “Is it hard?” Acknowledging complexity and meeting resistance with investments in tools and training can help to relieve bottlenecks during adoption.

+

The most common first question about infrastructure as code: "Is it hard?" Acknowledging complexity and meeting resistance with investments in tools and training can help to relieve bottlenecks during adoption.

Learn more
@@ -44,19 +44,19 @@
-

Get to know Fleet GitOps

+

Infrastructure as code for your devices

- An image showing the process of the Fleet Gitops workflow. A developer pushes a device management profile to GitHub, and an IT admin approves the new profile. When the updated profile is merged, the CI/CD runner sends the profile to a Fleet server. The Fleet server then sends the updated profile to a managed device and verifies the result. + An image showing the process of the Fleet infrastructure as code workflow. A developer pushes a device management profile to GitHub, and an IT admin approves the new profile. When the updated profile is merged, the CI/CD runner sends the profile to a Fleet server. The Fleet server then sends the updated profile to a managed device and verifies the result.
-

Fleet GitOps commands to modify the Fleet UI are executed by the fleetctl binary (the “engine” under the hood.) The binary lives on a CI / CD “runner” (e.g., GitHub Actions). A git push with updated YAML code kicks off automation that results in real-time changes you can see.

+

Fleet infrastructure as code commands to modify the Fleet UI are executed by the fleetctl binary (the "engine" under the hood.) The binary lives on a CI / CD "runner" (e.g., GitHub Actions). A git push with updated YAML code kicks off automation that results in real-time changes you can see.

Declarative device management

Most device management solutions have an API, but most do not provide comprehensive control over the admin console with configuration-as-code like Fleet.

-

Managing the Fleet UI console with GitOps means you have total declarative control over your devices.

+

Managing the Fleet UI console with infrastructure as code means you have total declarative control over your devices.

Unlock powerful automations that allow you to:

  • Ensure every change is peer-reviewed
    • @@ -69,7 +69,7 @@
    Observable, reversible, and repeatable workflows

    Nothing builds knowledge, trust, and fosters engineering teamwork like peer-reviewed changes made in the open.

    -

    Collaboration on Fleet GitOps workflows helps to prevent problems before they occur. Version control means it is straightforward to fix problems that do make it into production (nobody’s perfect...)

    +

    Collaboration on infrastructure as code workflows helps to prevent problems before they occur. Version control means it is straightforward to fix problems that do make it into production (nobody's perfect...)

    Another powerful technical benefit: less effort on long-term maintenance. Controlling the Fleet UI with code results in a library of stable, known-good configurations that can be copied and modified to easily add new management objects, like device profiles and software. Tame the endless sprawl of manually re-creating automations and scoping.

@@ -82,11 +82,11 @@
Rethink change managment
-

Replacing change management forms and risk assessments with asynchronous GitOps workflows and approvals can dramatically increase operational speed.

+

Replacing change management forms and risk assessments with asynchronous infrastructure as code workflows and approvals can dramatically increase operational speed.

Stay the course
-

Changes made in the console or to devices directly can cause device state to “drift” - away from compliance, security posture, and an organization’s intended user experience.

+

Changes made in the console or to devices directly can cause device state to "drift" - away from compliance, security posture, and an organization's intended user experience.

Choose automation over repetition
@@ -98,16 +98,38 @@
Make end users happy
-

Mired in engineering details, it’s easy to lose sight of an important, oft-stated goal that should be part of any device strategy aimed at operational excellence: enabling work.

+

Mired in engineering details, it's easy to lose sight of an important, oft-stated goal that should be part of any device strategy aimed at operational excellence: enabling work.

+
+
+

AI-accelerated IT

+
+
+
+
Everyone can contribute — IT stays the human in the loop
+

Infrastructure as code opens device management to the whole organization. Engineers, security, and ops can all propose changes — while an expert from IT reviews and approves every update before it ships. Collaboration without chaos.

+
GitOps is the foundation for AI-accelerated device management
+

Without GitOps there is no way to do AI-accelerated device management. With GitOps you can take advantage of the modern tools your org is already pushing, and keep IT from being left behind as a cost center.

+
Reduce friction, skip the ticket queue
+

Iterate more quickly by reducing friction and hand-offs. Instead of ticket queues, easily propose changes with natural language.* Use any LLM — even airgapped — and easily integrate tools like Kilocode that work with Slack and Microsoft Teams.

+

* Use any LLM, even airgapped, and easily integrate tools like Kilocode that work with Slack and Microsoft Teams.

+
+
+
+ Kilocode screenshot showing a natural-language device management change proposed in a chat interface, reviewed and merged via GitOps +
+
+
+
+
-

“One Fortune 500 company had a 1.5-hour Change Advisory Board (CAB) meeting, 100 attendees, and they reviewed around 50 changes per meeting. This cost them $750k not including opportunity costs.”

+

"One Fortune 500 company had a 1.5-hour Change Advisory Board (CAB) meeting, 100 attendees, and they reviewed around 50 changes per meeting. This cost them $750k not including opportunity costs."

@@ -121,18 +143,18 @@
Your culture matters, and so does ours
-

For some organizations, GitOps is a natural fit to the engineering culture even if IT teams lack experience or the practice is new.

+

For some organizations, infrastructure as code is a natural fit to the engineering culture even if IT teams lack experience or the practice is new.

If DevOps or GitOps is already used by an organization, device management engineers may be aware of the concepts and tooling. Having an internal example to follow can result in an easier path to adoption.

-

But, GitOps adoption is not always simple. Admins may resist unfamiliar workflows or solutions. They may also have concerns about losing the value of certifications or specialized training.

-

By meeting potential challenges with phased implementation and thought leadership, any team can successfully adopt Fleet GitOps. We’ve seen it, and we’ve helped our customers do it.

+

But, adoption is not always simple. Admins may resist unfamiliar workflows or solutions. They may also have concerns about losing the value of certifications or specialized training.

+

By meeting potential challenges with phased implementation and thought leadership, any team can successfully adopt infrastructure as code for device management. We've seen it, and we've helped our customers do it.

-
Making GitOps benefits real
-

At Fleet, we believe that showing organizations how to migrate to GitOps workflows represents an enormous opportunity for them to increase engineering efficiency and operational speed. This ultimately improves both end user experience and enterprise compliance. We design the product around these goals. We want to help you achieve them.

-

One way we can help is by improving the product itself, which we’re doing every day.

-

Another way we can help is through training. To learn more about GitOps, you can attend one of our free, hands-on, in-person GitOps workshops, or you can request that one be delivered in your area.

+
Making infrastructure as code benefits real
+

At Fleet, we believe that showing organizations how to migrate to infrastructure as code workflows represents an enormous opportunity for them to increase engineering efficiency and operational speed. This ultimately improves both end user experience and enterprise compliance. We design the product around these goals. We want to help you achieve them.

+

One way we can help is by improving the product itself, which we're doing every day.

+

Another way we can help is through training. To learn more about managing devices with infrastructure as code, you can attend one of our free, hands-on, in-person GitOps workshops, or you can request that one be delivered in your area.

@@ -140,7 +162,7 @@
-

“The shift to GitOps has modernized our operations, giving us the agility and change control we needed, giving leadership real-time confidence in device health and compliance.”

+

"The shift to infrastructure as code has modernized our operations, giving us the agility and change control we needed, giving leadership real-time confidence in device health and compliance."

Dan Jackson @@ -163,7 +185,7 @@
-

Fleet GitOps

+

Infrastructure as code for your devices

The future of device management is declarative