1732 posts tagged with "Self-Hosting"
Running your own PaaS and infrastructure on machines you own
Render Repriced Twice in One Week: Why the Migration Question Is the Full Bill, Not the $7 Starting Price
Render logged price-point changes on August 22 and August 28, 2026. A line-by-line cost sheet for an always-on web service plus Postgres at 5, 25, and 100 GB of traffic against a flat Hetzner CX22 — and why per-service multiplication, bandwidth overage, and workspace fees move the bill more than the headline price.
Your Sandbox Is Not a Home: Where Vibe-Coded Apps Actually Live After Day One
Every 2026 guide to shipping vibe-coded apps ends at 'deploy behind a sandbox' — without saying where the app lives long-term. The missing fifth stage: a permanent git-backed home with a redeploy loop, the sandbox-vs-home checklist, and the cost crossover between execution meters and flat hardware.
Render Traded $19 Seats for a $0.15/GB Meter: A 20-Person Team's Bill at 1TB, 2TB, and 5TB
Render's August 1 rollout swapped $19 per-seat pricing for a $25 flat Pro plan with unlimited members — and cut included bandwidth from 500GB to 25GB at $0.15/GB over. A worked before/after bill for a 20-person team at 1TB, 2TB, and 5TB, the small-team cases that pay more, and what the same traffic costs on owned hardware.
The Heroku Exit Playbook: Procfile to Buildpack, Every Add-on Decision, and the Real Before/After Bill
A step-by-step playbook for actually leaving Heroku's sustaining-engineering mode: Procfile to manifest, add-ons sorted into keep/replace/lose, secrets without a leak window, a rehearsed database cutover, and a real before/after bill.
Kubernetes Metrics API Is Stable in v1.37: What a Self-Hosted PaaS Must Expose Before Agents Can Safely Autoscale Apps
Kubernetes 1.37 made the Metrics API stable, but stability doesn't make it safe for an AI agent to autoscale on. Here's the isolation, staleness, and admission contract a self-hosted PaaS needs first.
SmolVM vs. Firecracker: Which MicroVM Should Actually Isolate Your AI Agent's Code?
SmolVM's sub-200ms boot challenges Firecracker's two-year default. A measured comparison of boot time, memory density, and what actually isolates untrusted agent code from the host kernel across SmolVM, Firecracker, OpenSandbox, and Docker Sandboxes.
Coolify's 11 Critical CVEs and 52,890 Exposed Dashboards: What a Single Root Daemon's Blast Radius Actually Looks Like
Coolify disclosed 11 critical CVEs in January 2026 — five rated CVSS 10.0 — with 52,890 dashboards exposed online. Eight months later, here is what changed, what didn't, and why blast radius per CVE is the number that should drive self-hosted PaaS architecture choices.
KEDA's Queue-Depth Autoscaling vs. Render and Railway's Black-Box Scaling
A practical comparison of KEDA's queue-aware Kubernetes autoscaling with Render and Railway's documented CPU, memory, and replica controls, including a worked worker-backlog example.
Kubero vs Porter vs Coolify: What Happens When Your Self-Hosted Heroku Needs a Second Server?
Kubero, Porter, and Coolify all bring Heroku-like deployment to infrastructure you control. This comparison shows where app deployment ends and machine provisioning, replacement, traffic routing, and fleet reconciliation begin.