1732 posts tagged with "Self-Hosting"
Running your own PaaS and infrastructure on machines you own
Render Cut Docker Builds From 87s to 32s: Where the Seconds Went and How to Match It on Hardware You Own
Render cut median Docker builds from 87 seconds to 32 with upload tuning, faster scheduling, and registry-backed caching. A lever-by-lever teardown of where those seconds lived, and the owned-hardware recipe — warm BuildKit builders, registry cache, cache mounts — that matches it.
Render's 75% Faster Builds, Decoded: What Native Environments Really Measure and the Bar for Self-Hosted Pipelines
Render's native environments claim 75% faster builds than Dockerfiles through intelligent layer caching. Decoding the warm-rebuild arithmetic behind the number, the three Dockerfile mistakes that hand it over, and the benchmark checklist a self-hosted BuildKit pipeline must clear to match it.
France's Railway Runs Kubernetes on Cluster API: What a National Railway's Declarative Rebuild Teaches a Two-Person Fleet Team
SNCF cut cluster provisioning from a month to 30 minutes and now updates every cluster monthly with Cluster API on its own hardware. Three lessons transfer directly to a two-person team on Hetzner — and four pieces of enterprise ceremony to skip.
Five Subsystems, Sixteen Days: Vercel's July 2026 Incident Cluster, Counted
Between July 8 and July 23, 2026, five separate Vercel subsystems failed — builds, SSO login, GitHub deploys, the dashboard, and telemetry export. Counting the whole cluster shows the real background failure rate of shared platforms, and why a six-minute Log Drains gap marked unrecoverable can't happen when your logs never cross a third-party pipe.
Your Build Takes 4 Minutes and Nobody Knows Why: What Cloud Native Buildpacks' RFC 0131 Would Itemize
Deploy-from-git builds report success or failure and nothing else — no per-buildpack timing, no cache-hit signal, no failure attribution. RFC 0131 would fix that with opt-in OpenTelemetry traces per phase and buildpack, and a self-hosted PaaS can turn them into tenant-facing build receipts plus fleet-wide dashboards.
Coolify's Zero-Downtime Asterisk: Why Every Docker Compose Deploy Still Goes Down
Coolify deploys single-container apps with zero downtime but takes Docker Compose stacks offline on every deploy — a 10-to-30-second 502 window. The mechanical reason runners can't do what orchestrators get for free, where Dokploy's Swarm bet fits, and the four questions that cut through any self-hosted PaaS feature matrix.
Your 8B Model Isn't Dumb. Its Harness Is: Forge's 53%-to-99% Guardrail Lesson for Platform Ops
Forge's May 2026 result took an 8B model from 53% to 99.3% on agentic tasks with guardrails alone — beating unguardrailed Claude Sonnet outright. What the retry-nudge math, the 75-point serving-backend swing, and a worked token-vs-hardware breakeven mean for running platform-ops agents on a self-hosted GPU.
Headscale at 40,000+ Stars: Mesh Your Multi-Region Fleet Without Anyone Else's Control Plane
Headscale passed 43,000 GitHub stars as the open-source, self-hosted Tailscale control server. A concrete build for meshing a multi-region fleet — embedded DERP, pre-auth keys, per-site subnet routers, ACLs in git — plus the single-instance HA catch and the cost math against Tailscale's 2026 per-user pricing.
Your GPUs Are 60% Idle and Kubernetes Says Everything Is Fine
A July 2026 CNCF case study found Kubeflow GPUs ~60% idle with every pod green — a scheduler-vs-network conflict fixed with topology constraints (40% to 85% utilization). The three families of GPU waste, a DCGM-based instrumentation ladder, and the rule for earning your next GPU node.