1732 posts tagged with "Self-Hosting"
Running your own PaaS and infrastructure on machines you own
Your Three Replicas Are All in FSN1: TopologySpreadConstraints, Hetzner Failure Domains, and the Placement Policy a Self-Hosted PaaS Owes Its Tenants
Two replicas across three Hetzner locations at maxSkew 1 lands 1/1/0, with one location always empty. The skew formula behind it, the minDomains trap that wedges pods in Pending, what cross-location spread really costs on Hetzner's private networks, and the soft-by-default placement policy a self-hosted PaaS should ship.
Don't Build Cron Into Your PaaS: Running Windmill's Script-to-Webhook Engine as a Tenant Workload
Every git-push PaaS eventually needs cron and background workers. A concrete build-vs-route decision: run Windmill's open-source workflow engine as a tenant workload, or build your own — with the six-dimension tradeoff table and the three conditions that flip the answer.
Azure Container Apps' Per-Second Meter vs a €4 Hetzner Box: Where Serverless Containers Win, and Where They Cost 8x
Azure Container Apps bills $0.000024 per vCPU-second with a free grant that makes spiky workloads genuinely free — but a steady app costs ~$34/mo against a ~€4 Hetzner CX23. A worked duty-cycle sweep, the breakeven at ~25% of the month, and why the Dedicated tier costs more, not less.
When the Grid Itself Is the Threat Model: What Berlin's Four-Day Blackout Teaches About Fleet Placement
A January 2026 arson attack naming AI data centers left 45,000 Berlin households dark for four days. Why concentrated compute is now an explicit target — and why a distributed self-hosted fleet is the cheapest hedge.
No Human Typed This Deploy: What Claude's Cron-Triggered Agents Demand From Your MCP Auth Story
Anthropic's June 2026 scheduled deployments let agents wake on a cron schedule, pull vault credentials, and ship with no human watching. Here is the six-rule auth checklist — scoped per-run grants, platform-written audit trails, blast-radius limits — a deploy-from-chat MCP surface needs before a timer gets deploy rights.
Coolify vs Dokploy vs CapRover: What 57K Stars and 280+ Templates Hide
Coolify (~57K stars), Dokploy (~35K), and CapRover (~15K) dominate 2026 self-hosted PaaS roundups — but stars measure onboarding smoothness, not fleet lifecycle. A head-to-head on the June 2026 numbers plus the three gaps popularity hides: multi-node scheduling, declarative machine provisioning, and agent-ready APIs.
Coolify v4.1's Railpack Bet: Should Your Self-Hosted PaaS Follow?
Coolify 4.1.0 added Railway's Railpack as a beta build option next to Nixpacks — with Nixpacks in maintenance mode and Dokploy shipping Railpack too. A three-way comparison against Paketo/CNB, Railway's real image-size numbers, and a decision tree for your platform's build layer.
Every PaaS Now Speaks MCP: What Render, Fly, and Railway's Agent Bet Means for Whoever Owns the Server
In six weeks of summer 2026, Render, Fly.io, and Railway all shipped agent surfaces — OAuth MCP servers, disposable computers, chat plugins. A side-by-side inventory of what each actually exposes, the five things agent-operated deploys require, and the case for an open MCP server on machines you own.
Fly.io's Two New 2026 Line Items, Priced Line by Line: Snapshots and Cross-Region Traffic vs a Flat Hetzner Fleet
Fly.io started metering volume snapshots in January 2026 and inter-region private traffic in February. A line-by-line bill for a typical two-region app totals ~$23 vs ~$11 on flat Hetzner hardware — and ~$45 with an Africa/India region.