1732 posts tagged with "Self-Hosting"
Running your own PaaS and infrastructure on machines you own
Your Migrated App Still Asks Which PaaS It's On
Migrated apps keep sniffing for DYNO, RAILWAY_*, and FLY_APP_NAME long after they leave those platforms. The concrete inject list and do-not-fake list a Render-compatible self-hosted API must honor so tenants' health checks and telemetry keep telling the truth.
Netlify Killed Per-Seat Pricing and Doubled Bandwidth Meters: What Your App Actually Pays Now
Netlify traded $20-per-seat billing for unlimited seats and doubled usage meters. A credit-by-credit recompute of what traffic-heavy apps pay under the new rates — and the few-hundred-gigabyte crossover where owned hardware wins.
Node Lifecycle Conditions Land as Alpha in v1.37: The Machine-Readable Node Health Vocabulary Your Agent Operator Has Been Waiting For
Kubernetes v1.37 reserves five well-known Node conditions for drains, maintenance, and graceful shutdown. No core controller reads them yet — but for agent operators, a stable machine-readable vocabulary is the prerequisite, and self-hosted fleets can start publishing today.
Northflank BYOC vs Owning Hetzner Boxes: What Bring-Your-Own-Cloud Actually Saves
The same API-plus-Postgres stack priced five ways: Render, Railway, Northflank managed, Northflank BYOC on AWS, and a Hetzner box under Cluster API — plus the sensitivity analysis that decides which one is actually cheapest for your workload.
Ownkube's Named AI Agents Run Your Ops — but the AWS Bill Is Still Yours
Ownkube pairs a Heroku-style deploy UX with named AI agents for cost, incident, scaling, and security — but its Production shape still runs on EKS. A worked 8-vCPU comparison puts the AWS route at $460–510 a month against €60–90 on owned hardware.
Proxly Puts ngrok on Your Own Domain — but Your Laptop Is Still the Server
Proxly is a self-hosted ngrok alternative that exposes localhost on subdomains of your own domain through a VPS relay and wildcard DNS. How its WebSocket relay works, what it costs against ngrok's paid tiers, and why a tunnel still isn't a deployment.
Railway's Guardrails, Rebuilt in Kubernetes: Two Admission Policies That Keep Internal Services Off the Public Internet
Railway's April 2026 Guardrails stop non-admins from exposing internal services via public domains or TCP proxies. Here is how to enforce the same two policies on a self-hosted Kubernetes platform with ValidatingAdmissionPolicy and Kyverno.
Railway's $10/GB Overage Math: The Exact Headroom Point Where One Hetzner Box Wins
Railway's rate card works out to about $10 per GB of RAM and $20 per vCPU each month. A line-by-line recompute puts a modest API-plus-worker-plus-database app near $147 a month — and pins the exact footprint where one Hetzner box becomes the cheaper default.
Railway's One-Click Redis HA, Priced: What Sentinel-Plus-HAProxy Costs Against Self-Hosted Valkey
Railway's one-click Redis HA converts a standalone service into a Sentinel-plus-HAProxy cluster at roughly $55-80/month metered for a small 3-node setup, against about $18 on owned Hetzner nodes running Valkey. A line-by-line accounting of the failover bundle, its conversion gotchas, and the ops work the meter buys you out of.