1732 posts tagged with "Self-Hosting"
Running your own PaaS and infrastructure on machines you own
Borrow the Claim, Skip the Cloud Sprawl: What Crossplane's Modelplane Teaches a Self-Hosted PaaS About GPU APIs
Modelplane puts GPU inference fleets behind a Crossplane claim API so teams request an endpoint, not a machine. The before/after YAML, a six-row borrow-vs-skip table for a Hetzner CAPI fleet, and the €184/mo card math that decides it.
CPU Lies: What a Git-Push PaaS Should Autoscale Tenants On Instead
CPU sits at 35% while your service melts — because it was waiting, not working. A concrete pipeline for autoscaling tenants on in-flight requests and queue depth, the adapter-vs-KEDA decision, multi-tenant guardrails, and what Render and Railway get right.
Do I Really Need Kubernetes? What the PaaS-First Backlash Gets Wrong
HN threads say a PaaS is the default and Kubernetes is overkill. The honest answer separates operating a cluster by hand from owning a git-push platform built on it — plus the concrete second-machine test that decides which side you are on.
Dokploy's One-Click Templates Deploy Over HTTP: The TLS Gap in the Catalog and the One-Field Fix
Dokploy's template format has no way to request a TLS certificate, so every app installed from the one-click catalog lands on HTTP until someone hand-wires HTTPS. What that costs a team at catalog scale, how Coolify and Render handle the same moment, and the one optional field that would close the gap.
Your AI Coding Assistant Is Outpacing Your Pipeline: What DORA's Numbers Say About Platforms
Three years of DORA research agree: AI tools make developers faster and delivery less stable, and platform quality decides which effect wins. The numbers behind the amplifier finding and what they mean for teams running their own PaaS.
Heroku Is Gone: We Re-Ran Encore's Exit Map With Real Bills for Render, Railway, Fly.io, and Hetzner
Encore's Heroku exit map points refugees at Render, Railway, Fly.io, and a VPS. A line-by-line re-audit prices the same stack on each — quiet month and traffic-spike month — and finds the meter shape matters more than the headline number.
etcd 3.7 RangeStream: The End of Your 4GB Control Plane's Worst Memory Spike
etcd 3.7 streams large range reads instead of buffering them whole, flattening the LIST-driven memory spike that OOM-kills small self-hosted control planes — plus the checklist for upgrading a Cluster API-managed cluster safely.
etcd 3.7 Boots From the v3 Store: What Changes About Backups and Recovery on a Self-Hosted Fleet
etcd 3.7 boots entirely from the v3 store, with the last v2 leftovers slated for removal in 3.8 — what that means for snapshots, compaction, and corruption recovery, plus a six-step fleet-wide backup drill to run before your next Kubernetes upgrade.
No More Annotations: Gateway API v1.5 and v1.6 Make PaaS Ingress 100% Portable YAML
Gateway API v1.5 and v1.6 moved the CORS filter, TLSRoute, and TCP/UDP routes into the Standard channel, so a git-push PaaS can express a tenant's whole ingress layer as portable YAML with zero annotations. Includes the GRPCRoute timeline correction and the four-item conformance checklist to run before tenants rely on it.