zopdev writing tagged platformengineering. Engineering and FinOps notes, post-mortems, and benchmarks.
Getting a teammate to install a specific app used to start with a conversation, not a click: open ZopDay, find Starter Templates, search the catalog, find the right chart, then start the flow. Every…
An MCP server sits between a platform and every AI client that talks to it: Claude, Cursor, Codex, and anything else built against the Model Context Protocol spec. When that spec moves forward, the…
The chart version a service is running is usually a guess. A team imports a Helm release or installs something from a catalog, and the chart version stays whatever it was on day one until someone…
ZopNight's newest release notes open with a new feature: you can now migrate a database from one GCP Cloud SQL instance to another without leaving ZopDay, the Kubernetes platform ZopNight ships…
Alert-only incident response transfers the cost of every failure from the system to the engineer, and that transfer compounds at scale.
HashiCorp's August 2023 switch from the Mozilla Public License to the Business Source License forced every infrastructure team running Terraform to make a governance decision they had not budgeted…
Most AIOps implementations treat the "Act" phase as the finish line, and that architectural choice turns automated remediation into a liability rather than a guarantee.
Visibility without workflow integration is a cost center, not a cost cure. Most engineering organizations have invested in dashboards, tagging policies, and cost explorer tools. The spend keeps…
HashiCorp's August 2023 relicensing of Terraform from MPL-2.0 to the Business Source License 1.1 was not a routine legal update. It was a governance event that forced every infrastructure team to…
When an on-call engineer is your primary failure mitigation strategy, you have not built reliability. You have built a human circuit breaker that trips at 2 a.m.
Alert-only monitoring does not reduce operational cost. It defers labor and compounds it.
A single bad deployment cost $180,000 not because the deployment was uniquely catastrophic, but because nothing in the system was configured to stop it from spreading (ZopDev, "Blast Radius by…
Every Internal Developer Platform carries two price tags: the one on the sales deck, and the one buried in your engineers' calendars.
Every internal developer platform carries a hidden 4-week tax: engineer time spent on platform setup before a single service ships (ZopDev, "The IDP Tax"). That number is not a rounding error. It is…
Platform engineering teams are paying $180,000 per year in duplicate tooling costs without a line item that names it (ZopDev, "The IDP Tax"). That cost has a name: the IDP tax. It accumulates because…
Most IDPs ship as friction-reducers and land as a new category of sprint tax. The promise is a self-service portal that abstracts infrastructure complexity. The reality, in production, is a platform…
Most engineering organizations budget precisely for building an Internal Developer Platform and budget nothing for operating one. The build cost is visible: headcount, tooling licenses, sprint…
Every Internal Developer Platform we have seen hits the same wall: feature shipping slows down at the three-month mark, not because the platform was built wrong, but because the forces that made…
Ticket-based infrastructure workflows inject a minimum three-day delay into every deployment cycle because each request moves through a queue where a centralized team must interpret, validate, and…
Most IDPs fail because they solve the wrong problem: they build self-service portals instead of standardizing the work developers already do. We measured this in production. Teams spend six months…
Building an Internal Developer Platform for 12 teams costs $400,000 (Platform Engineering for 12 Teams: The $400k IDP Bill), and understanding where that money goes determines whether you build or…
One post a week. Sundays. No "10 ways to think about cloud" listicles, just the engineering and FinOps notes we'd want to read.
See. Find. Fix. Automatic.
Connect your first cloud account in under 5 minutes. See your first remediation in under 7. No credit card required.