1732 posts tagged with "Self-Hosting"
Running your own PaaS and infrastructure on machines you own
Flatcar vs Talos vs bootc: Picking the Immutable Node OS for a CAPH-Provisioned Hetzner Fleet
Flatcar, Talos, and bootc compared as the immutable node OS for a Cluster API fleet on Hetzner: image pipelines, update and reboot semantics, CAPH integration maturity, and which one a cost-sized team should standardize on first.
Fly.io Sprites Speak MCP: What $0.07/CPU-Hour With Zero Idle Charge Really Costs Against Owned Hetzner Hardware
A line-by-line recompute of 200 agent sandboxes on Fly Sprites' idle-free meter versus E2B, Daytona, Modal, and owned Hetzner hardware — with the duty-cycle crossover points where each option wins.
Fly Postgres Is a Thin Provisioning Layer: The Exit Math When 'Managed' Stops at Replication and Backups
Fly Postgres provisions machines and replication but leaves pooling, monitoring, and failover to you. A worked three-way bill — classic Fly Postgres vs Managed Postgres vs CloudNativePG on owned nodes — for teams pricing an exit.
Fly.io vs Railway vs a $5 Droplet: What the No-Container Counter-Narrative Gets Right — and Where It Breaks at the Second Service
A $286 PaaS bill sparked the honest question: why not skip the platform and run a binary on a $6 droplet? Real 2026 numbers show the droplet wins for one app — until the second service arrives.
100 MCP Servers in Production: What a Fortune 500 Deployment Teaches Self-Hosted Agent Ops
A Fortune 500 bank went from failing AI coding assistants to 100 governed MCP servers in three months. Five practices from that deployment — registry gates, gateway auth, tool consolidation, token budgets, gateway observability — that self-hosted teams should adopt on day one.
Gateway API v1.6 Makes TCPRoute and UDPRoute Standard: Own Your PaaS's L4 Traffic Without Ingress Annotations
Gateway API v1.6 graduates TCPRoute and UDPRoute to the Standard channel as stable v1 resources. Here is the one-Gateway design for tenant Postgres, game, DNS, and agent-protocol traffic — copy-paste YAML, a port-allocation policy that keeps tenants off each other's listeners, and the controller support matrix to check first.
gVisor vs Kata vs Firecracker: Picking Sandbox Isolation for an Agent Layer on Shared Nodes
An agent sandbox on a node shared with paying tenants must survive hostile model-generated code. This concrete comparison of gVisor, Kata Containers, and Firecracker covers cold starts, memory per sandbox, and blast-radius containment — plus a decision rule for self-hosted fleets.
Heroku's Quiet End of Life: A 90-Day Exit Playbook for Teams Still Paying by the Dyno
Salesforce moved Heroku to sustaining engineering in February 2026: no new features, no new Enterprise contracts. A 90-day exit playbook with the Salesforce sunset precedent, a 12-row pre-migration audit, week-by-week phases for a Postgres plus web plus worker stack, and the honest first-year cost of moving versus waiting.
Ingress-NGINX Is Retired. Your PaaS Inherited Its Quirks — Audit Them Before They Become Outages
Ingress-NGINX retired in March 2026, leaving five silent routing behaviors behind. This behavior-by-behavior audit maps each quirk to what breaks on a naive Gateway API migration — and what a self-hosted PaaS routing layer must now own explicitly.