{"id":6275,"date":"2026-11-16T18:20:00","date_gmt":"2026-11-16T18:20:00","guid":{"rendered":"https:\/\/www.cmsgalaxy.com\/blog\/?p=6275"},"modified":"2026-11-19T14:20:00","modified_gmt":"2026-11-19T14:20:00","slug":"infraops-state-of-play-web-hosting","status":"publish","type":"post","link":"https:\/\/www.cmsgalaxy.com\/blog\/infraops-state-of-play-web-hosting\/","title":{"rendered":"InfraOps in 2026: A State-of-Play Review for Web and CMS Teams"},"content":{"rendered":"<p>Web teams used to treat hosting as somebody else&#8217;s department. A content platform went live, an agency handed over credentials, and the servers underneath were assumed to be fine. That arrangement is fading. Staging sites, preview environments, edge rules and databases are now commonly described in configuration files, which makes the surrounding practice, often called InfraOps, relevant to anyone who ships websites. This review looks at where the field stands in the final quarter of 2026. It leans on the Ops Atlas entry and keeps an eye on what matters for CMS and web-development shops.<\/p>\n<h2>A label without an owner<\/h2>\n<p>The first thing to know about the state of InfraOps is that nobody governs the word. <a href=\"https:\/\/www.xopsschool.com\/infraops\/\">The Atlas entry<\/a> records that it is used informally for infrastructure operations, appears in job titles and team names, was adopted by an analyst firm as an umbrella for infrastructure automation, and collided in 2025 with a commercial product that shares the name. The Atlas therefore uses it as an editorial label for the lifecycle of infrastructure defined in code. For agencies writing proposals, the practical consequence is to describe what you actually do rather than lean on the term.<\/p>\n<h2>The tooling landscape in brief<\/h2>\n<p>Two developments shaped recent years. First, the dominant engine moved to a source-available licence from version 1.6, announced in 2023, and a community fork under a permissive licence followed, entering the CNCF sandbox in 2025. The Atlas lists current releases from October 2026, v1.16.6 for the former and v1.13.1 for the latter, and treats them as largely interchangeable for everyday work. Second, other options matured: general-purpose-language tools, cloud-native template services, and Kubernetes-style controllers, one of which reached CNCF graduation in 2025. The upshot for a web agency is simple. Pick based on team skills and client constraints, and keep modules clean enough that a switch stays possible.<\/p>\n<h2>Where practice is improving<\/h2>\n<ul>\n<li><strong>Secrets handling.<\/strong> Ephemeral resources arrived in the main engine at 1.10 and write-only arguments at 1.11, so credentials need not be saved in state. The fork added state encryption in 1.7.<\/li>\n<li><strong>Refactoring without breakage.<\/strong> Declarative blocks for moving, importing and removing resources replaced fragile command-line surgery, leaving a review trail.<\/li>\n<li><strong>Testing.<\/strong> A native test command appeared at 1.6, with mocking following in 1.7, so even small agencies can check modules before release.<\/li>\n<li><strong>Image pipelines.<\/strong> Building machine images on a schedule, and replacing hosts rather than patching them in place, is now treated as ordinary hygiene for production.<\/li>\n<\/ul>\n<h2>Where it still goes wrong<\/h2>\n<p>Progress in tools has not removed older habits. The Atlas catalogues the repeat offenders: skipping review of change previews, one oversized state for every client, applying from laptops, and using ignore settings as a mute button. It also stresses a gap that tooling cannot close alone. A clean preview says nothing about resources created outside the code, so coverage measurement remains a human discipline. A site that was cloned by hand during a launch rush is the classic example, quietly sitting outside every review.<\/p>\n<h2>What the web-development crowd should note<\/h2>\n<p>Three themes stand out for CMS and front-end teams. First, environment parity: the Atlas treats the match between staging and production as a core concern, because a plugin update that behaves on one and fails on the other is usually a configuration difference. Second, the blast radius of a mistake, for which it points to a well-known 2017 storage outage where a single command with one wrong input removed more capacity than intended; the provider later introduced slower removal and minimum-capacity safeguards. Third, decommissioning. Retired campaign sites and forgotten test servers keep costing money and attack surface unless someone removes them deliberately, and code-derived inventory is how you notice them.<\/p>\n<h2>Scale lessons from large estates<\/h2>\n<p>Small agencies can still learn from the big names the Atlas profiles. One messaging company ended up with around 1,400 state files by giving each region of each account its own, and it needed roughly a quarter to move between major engine versions in 2019. Module testing was encouraged there but not enforced, which is a candid reminder that tooling does not guarantee behaviour. A Brazilian financial technology firm compiled its definitions into cloud templates, ran past 3,000 stacks, and retired old resources only after new ones had carried rising load alongside them. For a web portfolio with dozens of client sites, the transferable idea is the same: split by ownership and risk, and delete only after the replacement has proven itself.<\/p>\n<h2>Standards and governance<\/h2>\n<p>No InfraOps standard exists, but the Atlas points to adjacent ones. the NIST 800-53 catalogue (Rev. 5) has a configuration-management group dealing with baselines, change records, deviations and inventories, while a major cloud framework includes guidance on preventing in-place changes to production under an immutable approach. Agencies serving regulated clients can map their pipelines onto these families to show evidence. For a related viewpoint on running reliable operations at scale, our overview of <a href=\"https:\/\/www.cmsgalaxy.com\/blog\/essential-strategies-for-mastering-cloud-automation-and-resilient-infrastructure-operations\/\">resilient infrastructure through cloud automation<\/a> reads well alongside it, as does the roadmap article on <a href=\"https:\/\/www.cmsgalaxy.com\/blog\/building-a-practical-roadmap-for-devops-sre-and-platform-engineering\/\">sequencing DevOps, SRE and platform work<\/a>.<\/p>\n<h2>Outlook<\/h2>\n<p>Looking ahead, I would bet on three changes. Coverage and drift metrics will move from optional dashboards to contractual reporting for larger clients. Secret-free state will become the default expectation in reviews. And teams will keep arguing about whether continuous reconciliation belongs to this discipline, a question the Atlas answers by placing it with a neighbouring practice. For web shops, the takeaway is modest and practical: write the infrastructure down, review it like code, and measure how much of it the code really covers.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Where infrastructure-as-code practice stands in late 2026 and what it means for agencies and teams that build and host websites.<\/p>\n","protected":false},"author":14,"featured_media":6276,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1455],"tags":[],"class_list":["post-6275","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-web-development"],"_links":{"self":[{"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/posts\/6275","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/users\/14"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/comments?post=6275"}],"version-history":[{"count":1,"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/posts\/6275\/revisions"}],"predecessor-version":[{"id":6392,"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/posts\/6275\/revisions\/6392"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/media\/6276"}],"wp:attachment":[{"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/media?parent=6275"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/categories?post=6275"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/tags?post=6275"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}