684 posts tagged with "Self-Hosting"
Running your own PaaS and infrastructure on machines you own
One Repo, Five Services: Path-Filtered Deploys on Render, Railway, and Vercel — and When to Do It Yourself With the Dependency Graph
A docs typo shouldn't rebuild five services. How Render build filters, Railway watch paths, and Vercel's two skip mechanisms decide what a push rebuilds, where every static path filter breaks (shared libraries, lockfiles), and what a self-hosted Render-compatible PaaS should implement instead.
Static Outbound IPs Are a Paid Add-On on PaaS and a Free Property of Your Own Server
Railway shipped static outbound IPs and IPv6 on July 3, 2026 — Pro-only, three shared IPs per service with HA migration by July 13. What that costs, why allowlists turn egress into a production dependency, and why hardware you own solves it with one exclusive IP and no feature toggle.
Render Just Made PgBouncer Free. Here's the Connection-Pooling Homework You Inherit When You Self-Host Postgres
Render's July 2026 changelog bundles PgBouncer free with paid Postgres. Here is every decision that toggle makes for you — pooler choice, transaction vs session mode, prepared-statement fixes — plus a complete pgbouncer.ini for reproducing it on your own hardware.
Self-Hosting Firecracker Sandboxes for AI Agents: The Real Math Behind the 60–80% Cost Drop
E2B, Modal, and Daytona meter AI-agent sandboxes at $0.17–0.24 per hour; one $115 Hetzner box running Firecracker delivers them for cents. A worked cost model shows where the 60–80% savings actually start — and why the popular 500-sandbox-hour threshold assumes your ops time is free.
Runbooks Your Agents Maintain: Inside WUPHF's Markdown-Plus-Git Wiki Model
WUPHF keeps agent-maintained runbooks and postmortems as Markdown in Git. Why a repo agents can PR beats a SaaS wiki API for auditability, reverting bad knowledge, and owning your platform's operational memory.
Bitwarden's July 2026 Update Broke Every Vaultwarden Overnight: The Real Cost of Reimplementing a Protocol You Don't Own
Bitwarden's 2026.7.0 client silently repurposed a wire-format field Vaultwarden had emitted for eight years, breaking every self-hosted deployment overnight. A concrete cost accounting of running a compatible reimplementation of a protocol you don't control — and why bex's Render-compatible API carries the same risk.
Cloudflare Containers Bill 5-10x More Than an Always-On VPS: What the 10ms Meter Actually Costs a Long-Running Service
A line-by-line recompute of what an always-on service costs on Cloudflare Containers' 10ms meter versus a flat-rate VPS: $35-58 vs $7-15 for a small web+worker, a ~9-hour-a-day duty-cycle crossover, and why memory billed on provisioned size makes the gap structural.
Cloudflare OS Is Apache-2.0 — But the Only Supported Substrate Is Cloudflare's Network
Cloudflare OS launched Apache-2.0 with zero-access agents and Gatekeeper Workers — but the only supported production path deploys into a Cloudflare account. A component-by-component portability ledger, the Hacker News stress test, and a four-question audit separating open code from an open substrate.
Coolify v4 Shipped an MCP Server. Dokploy Didn't. The Self-Hosted PaaS Race Just Split in Two
Coolify's v4.x releases made a native MCP server its headline differentiator while Dokploy stayed deliberately minimal. A side-by-side comparison of both platforms — idle RAM, install, MCP surface — and why agent-operability's real cost is API discipline, not footprint.