1732 posts tagged with "Self-Hosting"
Running your own PaaS and infrastructure on machines you own
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.
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.
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.
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.
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.
CVE-2026-42533: The 15-Year-Old Core-NGINX Heap Overflow Your Gateway API Migration Didn't Escape
F5's July 2026 disclosure of CVE-2026-42533 — a CVSS 9.2 heap overflow in core NGINX's map directive — reaches Gateway Fabric, the F5 Ingress Controller, and every product embedding the NGINX engine. Here is the patch matrix, the config that makes you exploitable, and the upgrade order.
Dokploy Killed Its Global Build Queue After Two Years: What Per-Server Build Slots Reveal About Scheduling Outgrowing One Box
Dokploy ran every build on every server through one global queue for two years — then v0.29.11 gave each server its own. The wait-time math behind the fix, where per-box caps still strand capacity, and what a fleet build pool owes default-1.
E2B Is Now Native in OpenAI's Agents SDK: The Bar a Self-Hosted Agent Sandbox Has to Clear
OpenAI's Agents SDK declares E2B sandboxes natively since April 2026. This post turns that integration into a six-part checklist — cold start, isolation, templates, lifecycle, MCP sandboxing, egress policy — and scores four self-hosted paths against it.
From Metered API to RuntimeClass: Building E2B-Style Sandboxes on Your Own K8s Fleet
The sandbox cost math already settled: past ~400 sandbox-hours a month, owned hardware wins. This is the build guide for what comes next — three paths to E2B-style sandboxes on your own fleet, with Kata Containers on Cluster API as the one that skips the second orchestrator.