1512 posts tagged with "PaaS"
Platform-as-a-Service tooling, economics, and self-hosted alternatives
Five Subsystems, Sixteen Days: Vercel's July 2026 Incident Cluster, Counted
Between July 8 and July 23, 2026, five separate Vercel subsystems failed — builds, SSO login, GitHub deploys, the dashboard, and telemetry export. Counting the whole cluster shows the real background failure rate of shared platforms, and why a six-minute Log Drains gap marked unrecoverable can't happen when your logs never cross a third-party pipe.
Your Build Takes 4 Minutes and Nobody Knows Why: What Cloud Native Buildpacks' RFC 0131 Would Itemize
Deploy-from-git builds report success or failure and nothing else — no per-buildpack timing, no cache-hit signal, no failure attribution. RFC 0131 would fix that with opt-in OpenTelemetry traces per phase and buildpack, and a self-hosted PaaS can turn them into tenant-facing build receipts plus fleet-wide dashboards.
Coolify's Zero-Downtime Asterisk: Why Every Docker Compose Deploy Still Goes Down
Coolify deploys single-container apps with zero downtime but takes Docker Compose stacks offline on every deploy — a 10-to-30-second 502 window. The mechanical reason runners can't do what orchestrators get for free, where Dokploy's Swarm bet fits, and the four questions that cut through any self-hosted PaaS feature matrix.
Your 8B Model Isn't Dumb. Its Harness Is: Forge's 53%-to-99% Guardrail Lesson for Platform Ops
Forge's May 2026 result took an 8B model from 53% to 99.3% on agentic tasks with guardrails alone — beating unguardrailed Claude Sonnet outright. What the retry-nudge math, the 75-point serving-backend swing, and a worked token-vs-hardware breakeven mean for running platform-ops agents on a self-hosted GPU.
Headscale at 40,000+ Stars: Mesh Your Multi-Region Fleet Without Anyone Else's Control Plane
Headscale passed 43,000 GitHub stars as the open-source, self-hosted Tailscale control server. A concrete build for meshing a multi-region fleet — embedded DERP, pre-auth keys, per-site subnet routers, ACLs in git — plus the single-instance HA catch and the cost math against Tailscale's 2026 per-user pricing.
Kubernetes 2.0 on HN: Why Rivet's Docker Compose Story Ends at the Second Server
A skeptic on HN asked how Docker Compose could be a more reliable, scalable alternative to Kubernetes for Rivet's actor platform. Rivet's own docs supply the answer: the Postgres-plus-NATS second-machine path, the 1,000-actor ceiling, and where K0s fits instead.
10,000 MCP Servers and No Human Wiring Them Up: What Server Cards and Stateless Operation Mean for Agents That Deploy Your Apps
MCP passed 10,000 public servers and is going stateless and self-describing, so agents will soon reach your deploy tools with no human wiring anything up. Here is the three-tier tool surface — observe freely, gate mutation, deny destruction — that survives contact with autonomous callers.
k3s Now, EKS Later? Pricing Ownkube's Graduation Ladder Against Cluster API on Day One
Ownkube lets teams start on hosted compute and graduate the same app into their own AWS account, from free single-node to metered multi-AZ. A priced run of one steady 2-vCPU team workload across every rung — plus what re-surfaces on migration day — against committing to Cluster API on flat hardware from the first deploy.
Docker Is Enough Until the Second Server: Why We Still Bet on Kubernetes
2026's PaaS-first chorus says Docker on one box handles 95% of workloads and Kubernetes is overkill. The verdict table, the Coolify/Dokploy/CapRover facts, and the five things that break at the second server — plus where the backlash is completely right.