1732 posts tagged with "Self-Hosting"
Running your own PaaS and infrastructure on machines you own
The Self-Hosted Governance Gap: Why Your Compliance Team Says No to Coolify, Dokku, CapRover, and Dokploy
Coolify, Dokku, CapRover, and Dokploy win engineering evaluations and lose security reviews: no enterprise SSO, no audit trail. A capability-by-capability look at what compliance-bound teams need and what a self-hosted PaaS must build to win them.
From One Box to a Fleet: A Second-Machine Migration Playbook for Coolify, Dokploy, and CapRover Teams Moving to Cluster API
Outgrown your single-box PaaS? A phase-by-phase playbook for moving live workloads from Coolify, Dokploy, or CapRover onto a Cluster-API-managed Hetzner fleet — with a stay-or-go checklist, data-migration options, and a weighted DNS cutover that keeps the old box as rollback.
Spotify Portal for Backstage Is GA: The Build-vs-Buy Math for Your Golden Path Just Changed
Spotify Portal for Backstage is GA: onboarding wizards, bundled premium plugins, and an AI assistant in one box. What the DIY cost numbers say, who already switched, and a build-buy-skip verdict for self-hosted platform teams.
The Month-13 Bill: What $500 in Fly.io and Render Startup Credits Really Buys
Fly.io's $500 credit buys 6-12 months and Render's buys a meaningful Pro window — then the full meter starts. A line-by-line pricing of the post-credit bill against flat-rate dedicated hardware, and how to spend credits with an exit planned.
Green Status Page, Broken Deploy: What Two July 2026 Vercel Incidents Teach About Scoped Failures in Multi-Tenant PaaS
Vercel's July 2026 status history holds two scoped failures — four hours of Hobby-only invocation errors and a six-minute telemetry gap disclosed the next day — with two more recurrences that quarter. What they share structurally, and four incident-communication guarantees a multi-tenant deploy platform should build instead.
What AI Agents Actually Deploy: Vercel's Ship 2026 Numbers and the PaaS Defaults They Break
Vercel's Ship 2026 numbers show agent-triggered deployments passing 50% while AI Gateway tokens grew 10x to 20 trillion a month. What the shift toward inference-calling apps means for PaaS egress, secrets, and metering defaults — and a scorecard for self-hosted platforms.
Zerops's $2M Bet: Your Coding Agent Is the PaaS Customer Now
Zerops raised $2M to build a PaaS control plane for AI coding agents. How its ZCP work loop — live state, deploy evidence, behavior proof — compares to Render and Railway, plus a five-item MCP checklist for self-hosted platforms.
Agents Deploy, Agents Never Hold the Keys: What Arcade.dev's OAuth-Handling MCP Runtime Means for Deploy-from-Chat
Deploy-from-chat dies the moment the agent asks for your API key. Arcade.dev's MCP runtime — Engine-vaulted OAuth, URL elicitation co-built with Anthropic, per-call scoped credentials — shows how agents deploy without holding tokens, with the deny, revoke, and re-scope paths spelled out.
Your Side Project Doesn't Need Kubernetes: What an Ask HN Deploy Thread Gets Right About the $5-vs-$40 Decision
A four-container side project priced five ways: a $5 Hetzner-class box, a $6 droplet, Railway's $5 meter, Render at $21-plus, and managed Kubernetes at $39 minimal or $79 production-grade. The cost table lands first, then the decision rule keyed on experience, service count, and traffic shape.