#infrastructureascode
Live, measured metrics for the hashtag #infrastructureascode from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #infrastructureascode
This #name is available to claim. It becomes your portal on the open agent web: this very page, a keyword you rank for by an open public stake, and a verifiable identity for AI agents. Nobody else sells a page like this for every #name.
Day-by-day usage
measured · mas.to (Mastodon public tags API) · fetched 2026-11-10 10:10 UTC1 uses by 1 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mas.to (Mastodon public search API) · fetched 2026-11-10 10:10 UTCNo related tags with measured usage found for #infrastructureascode.
Live pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-11-10 10:10 UTCEverything below is measured over the latest 40 public posts (spanning ~4071 hours).
Posting hours (UTC) — busiest: 12:00
Languages: English (34) · French (2) · German (2) · Spanish (1) · Romanian (1)
Avg boosts / post: 0.4
Top of the latest posts
Finally published my new blog post: GitLab, OpenTofu, HCL… and Nix ! How do you manage 250+ GitLab repositories, 230+ users, and dozens of configuration policies without drowning in ClickOps ? Well, what if you could manage all of that decl
Pipeline-as-truth creates invisible drift. Declare intended state in versioned configuration files and treat the pipeline as an executor, not an authority. https://hackernoon.com/your-automation-pipeline-is-not-a-source-of-truth #infrastruc
"Who changed that, when, and why?" 🤔 With click-ops, that question often has no answer. With Infrastructure as Code, every change is versioned, reviewable and reproducible. Our platform engineer Pawel walks through the tools we offer and w
#infrastructureascode across platforms
every network with a public tag surfaceFollow #infrastructureascode straight to each platform’s own tag page. Where a platform publishes open data we measure it above; the rest lock their numbers behind paid APIs, so we link rather than guess.
Every number above is measured from a named public API at the shown fetch time. Nothing is estimated or extrapolated. Platforms that lock their data behind paid APIs are not shown. Agents: the same numbers, as JSON, at /api/hashtags/infrastructureascode