1732 posts tagged with "Self-Hosting"
Running your own PaaS and infrastructure on machines you own
66% Run AI Inference on Kubernetes, 7% Deploy Daily: The Golden Path to an AI-Ready PaaS
CNCF survey data shows 66% of organizations run AI inference on Kubernetes while only 7% deploy models daily. Four mechanisms — versioned model artifacts, DRA accelerator requests, eval-gated promotion, and correlated inference telemetry — close the gap between running a model and shipping one.
Kubernetes v1.37 Node Lifecycle Conditions: Machine-Readable Node State for Agent-Driven Fleet Ops
Kubernetes v1.37 adds five Node Lifecycle Conditions — DrainInProgress, Drained, MaintenancePlanned, MaintenanceInProgress, and GracefulNodeShutdownInProgress — so nodes report intent, not just readiness. Here is who should publish each one on a Cluster API fleet, how to rewrite NotReady paging, and the agent policy that turns machine-readable state into safe machine operators.
One Scheduler Per Cluster Isn't a Fleet Strategy: How KubeStellar, Cluster API, and Hive Split the Multi-Cluster Job
kube-scheduler goes blind the day you add a second cluster. How Cluster API provisioning, KubeStellar placement policy, and hive agent orchestration split the multi-cluster job — and when placement belongs in your platform versus tenant BYO.
Your Fleet Patches Weekly but Reboots Never: Kured Closes the Stale-Kernel Gap
Unattended upgrades patch the disk, but the running kernel stays old until something reboots the node. Kured automates the cordon-drain-reboot cycle one node at a time — here is the runbook it replaces and the four guardrails (MHC timeouts, PDBs, drain timeouts, alert gates) that make it safe on multi-tenant CAPI fleets.
We're Leaving Kubernetes: What the Exit Posts Get Right About Small-Team Overhead, and What a PaaS Layer Answers
A fair accounting of the recurring 'we're leaving Kubernetes' posts: which small-team complaints survive scrutiny with real numbers, why most exits just rent someone else's Kubernetes-shaped API, and what a git-push PaaS layer answers.
The Managed Control-Plane Tax: Coolify $5 vs Dokploy $4.50/Server vs Deploynix $12 — and the Server Count Where the Meter Comes Back
Dokploy's $4.50 managed panel wins at one server, Coolify's $5 base wins at two through four, and Deploynix's flat $12 wins at five — a server-by-server fee accounting that names the count where each panel costs more than the Hetzner box it manages.
MCP Just Got Its Biggest Update Ever: What Stateless Servers Mean for Self-Hosting Deploy-from-Chat
The 2026-07-28 MCP spec killed sessions, sticky routing, and handshake affinity — September coverage calls it the biggest update since launch. For self-hosters, that means an infrastructure MCP server is now an ordinary HTTP service behind the same load balancer as everything else.
454 MCP Servers Catalogued and Quality-Scored Daily: Finding a Production-Grade Server in a Flood of Demos
A daily automated scan catalogues 455 MCP servers and scores them on hygiene — average 16 out of 100. What the data reveals about supply, churn, and how to vet servers before your agents call them.
MCP Went Stateless: What the 2026-07-28 Spec Means for Long-Running Deploy Tools
MCP revision 2026-07-28 drops sessions, handshakes, and server-initiated requests. A migration map for deploy-from-chat servers whose minute-long tools must rebuild on Tasks, multi-round-trip confirmations, and an explicit task store.