1732 posts tagged with "Self-Hosting"
Running your own PaaS and infrastructure on machines you own
ClawBleed: How One Clicked Link Turned 40,000 Self-Hosted Agent Gateways Into Remote Shells
CVE-2026-25253 let one malicious link steal an OpenClaw gateway token and take over the host. The kill chain, the 40,000 exposed instances, and the gateway-auth checklist for anything an agent can deploy through.
100x Faster Than Containers: What Cloudflare's Dynamic Workers Get Right About Sandboxing Agent Code
Cloudflare's Dynamic Workers run AI-generated snippets in V8 isolates with millisecond startup — but the 100x headline only holds for sub-second tool calls. Here are the real numbers against containers and microVMs, the isolation tradeoff Spectre exposed, and the two-tier sandbox rule for self-hosted platforms.
One Cluster for Training and Inference: How a Bank Cut AI Token Costs 60% on Kubernetes
China Merchants Bank won the CNCF End User Case Study Contest for running AI training and inference on a single Kubernetes stack of nearly 10,000 accelerator cards — lifting utilization from 35% to over 60% and cutting inference cost per million tokens by more than 60%. The component-by-component breakdown, the fairness rules behind it, and what smaller self-hosted fleets can copy.
Colmena vs Cluster API: Nix Fleet Management Without Kubernetes — What It Gets Right and Where It Stops
Colmena manages a NixOS fleet with no control plane, no agent, and no state database — but it cannot provision machines, schedule containers, or heal dead processes. A grounded comparison with Cluster API, an honest NixOps 4 status check, and a decision checklist.
Coolify's MCP Server Just Made Deploy-From-Chat Table Stakes: What 'Ask Claude to Ship It' Really Covers (and What It Doesn't)
Coolify's native read-only MCP endpoint plus 42-tool community servers let agents deploy to self-hosted infrastructure from chat. A labeled walkthrough of the Postgres-to-FastAPI loop, and the five governance controls a fast follower needs.
Coolify Fixed 11 Critical CVEs in v4.0.0 — How to Audit Any Self-Hosted PaaS Before Trusting It With Secrets
Coolify's v4.0.0 release rolled up fixes for 11 critical CVEs, several scoring CVSS 10.0. A breakdown of what the flaws allowed, the patterns they share, and a six-point checklist for auditing any self-hosted platform before it holds your secrets.
Cursor Made Sandboxes Interchangeable: What Eight Backends Behind One Agent Pool Means for Self-Hosted Platforms
Cursor's Self-Hosted Machines launch routes cloud-agent sessions through one worker pool across eight sandbox backends — Lambda, Cloudflare, Coder, Daytona, E2B, Modal, Namespace, and Vercel. The pool and the idle-machine lifecycle are the real product, and here is the four-item checklist for making your own fleet backend number nine.
E2B's $150/Month Sandbox Meter vs a $70 Hetzner Box: What Agent Sandbox-Hours Really Cost
E2B bills agent sandboxes per second on top of a $150/month Pro plan; a Hetzner box you own runs the same Firecracker isolation for a flat $70. A worked recompute across three team sizes shows where the meter wins, where the flat box wins by 10x, and why E2B's CPU-only ceiling settles the GPU question before pricing does.
eBPF Ate the Sidecar: What Hubble, Pixie, and Coroot Actually Replace on a Self-Hosted Fleet
67% of Kubernetes teams at scale already run eBPF observability. The sidecar-per-pod telemetry model costs ~250MB RAM per pod and milliseconds per request — a per-node kernel agent replaces it at a fraction of the cost. What Hubble, Pixie, and Coroot each replace, and which one a team that patches its own stack should run.