Blog
Insights, analysis, and updates from the AI agent economy. Browse by tag · Browse the archive.
Dokploy Has an MCP Server Too — and It's Bigger Than Coolify's: An AI-Agent Operator's Comparison on a $5 Hetzner Box
Dokploy's official MCP server gives AI agents full deploy and lifecycle control while Coolify's built-in MCP is read-only — here is what each agent interface can actually do, and what each control plane costs in idle RAM on a $5 Hetzner box.
Chat Deploys My App: What the Coolify–AnythingLLM MCP Bridge Proves, and the 5 Gaps a Render-Compatible MCP Server Closes
A community MCP server lets an LLM inspect, restart, and debug apps on a self-hosted Coolify box through AnythingLLM chat — but behind one shared API token sit a docker-socket tap and a root shell over SSH. Here is what the bridge proves, how Render's official MCP server scopes agent power instead, and the five gaps a Render-compatible MCP server still has to close.
A Czech Self-Hosting Hub Gave Claude Shell Access to Its Coolify Fleet: A 130-Line MCP Bridge Teardown
A Czech self-hosting hub wired Claude to its Coolify fleet through a 133-line MCP bridge — and handed the agent raw SSH instead of scoped deploy tokens. A code-level teardown of all seven tools, plus the five authorization rules a platform-owned MCP server needs.
CNCF's 'Agentic Enterprise' Essay, Scored: What First-Class Agent Consumers Actually Require
CNCF's July 2026 agentic-enterprise essay lists what treating AI agents as first-class platform consumers requires. A row-by-row score against a self-hosted PaaS: five requirements ship, the shared context model is half-built, and the enterprise catalog baggage can be skipped.
The Agent Is the Primary Tenant Now: Auditing CNCF's Platform Engineering 2.0
CNCF says internal platforms must be rebuilt for AI agents. A pillar-by-pillar audit of Platform Engineering 2.0 separates the genuinely new constraints — agent identity, MCP tool surfaces, machine-readable state — from old good practice, with a four-item checklist for self-hosted teams.
Cluster API v1.12: Update the Node, Don't Replace It — What In-Place Updates and Chained Upgrades Buy a Hetzner Fleet on Talos
Cluster API v1.12 trades full machine rollouts for in-place updates and multi-version chained upgrades — a change that saves real time and money on bare-metal Hetzner fleets running Talos. Here is what converges in place, what still replaces, and the operator rule for telling them apart.
Your Agent Can Call 7,000 SaaS APIs. Can It Deploy to a Machine You Own?
Arcade.dev gives agents 7,500+ SaaS tools behind brokered OAuth; Capix MCP gives them 37 tools that deploy models, provision GPUs, and emit signed receipts. Only one of those surfaces operates infrastructure you own — here is the checklist your PaaS MCP server still has to complete.
The Four Capabilities an AI Coding Agent's Deploy Sandbox Actually Needs in 2026
Sub-second provisioning, hardware-isolated execution, agent-readable validation, and canary rollback: the four capabilities a deploy sandbox needs before an AI coding agent can ship unsupervised — scored against what a self-hosted Kubernetes fleet already provides.
60 Million AI Code Reviews Later: The CI Gate Your Self-Hosted PaaS Should Steal
GitHub processed 60M+ AI code reviews in 2026 while AI-written code shipped roughly 1.7x more defects per pull request. Here is the multi-agent review pattern behind the numbers, and how to wire it into a self-hosted PaaS pipeline as a proper CI gate.
Subscribe
New posts land in your reader as soon as they publish. Pick a format — all three carry the same posts.
Current feeds keep roughly two days of posts so daily polling does not miss a burst. Older entries stay reachable from the feed's next-page link in readers that follow it, or from the blog archive.
Following one topic instead? Browse tags