Kaniko Is Dead: Google Quietly Archived It in June 2025 — What Rootless BuildKit Means for a Git-Push PaaS's Image-Build Path
Google archived Kaniko in June 2025 with no successor named. Here's why rootless BuildKit is the closest maintained replacement for daemonless, unprivileged Kubernetes image builds — and the caching, security, and kernel details a git-push PaaS has to re-verify before migrating.
KEDA's Scale-to-Zero: What It Actually Buys a Self-Hosted PaaS Billing Tenants for Idle Containers
A dormant tenant app held at a minimum of one replica costs real money — on Railway's metered pricing, about $30/month for a 1 vCPU/1GB container that serves zero requests. Here's what wiring KEDA's true scale-to-zero into a Cluster API fleet actually changes, in dollars and in cold-start seconds.
OCI VolumeSource Goes Stable in Kubernetes 1.36: Do You Still Need to Bake Large Assets Into Your App Image?
Kubernetes 1.36 made OCI VolumeSource stable, letting a Pod mount any OCI image as a read-only volume. Here's the honest before/after against a well-cached Dockerfile, a worked build-pipeline split, and what a self-hosted platform must verify before offering it to tenants.
The "PaaS-First, Kubernetes as Exception" Narrative of 2026 Misses the Platforms Built on Kubernetes You Never See
Coolify and CapRover are cited as proof self-hosting should default to a single-node PaaS with Kubernetes as the exception. But Render, Railway, and Heroku Fir all run on Kubernetes underneath a git-push UX you never see — here's what a Cluster-API-managed fleet gets you that Docker Swarm structurally can't.
Port and Cortex Anchor 2026's IDP Category: What a Git-Push PaaS Actually Needs to Borrow
SD Times named Port and Cortex 2026's internal-developer-portal category anchors. Here's what a git-push PaaS's deploy API already covers, what's genuinely missing, and how to borrow the rest without standing up a second system of record.
Dependabot Has No Path to Forgejo or Gitea, and Only a Community Patch for GitLab: Why Renovate Is the Only Bot Built for All Three
Dependabot has no official route onto GitLab, and none at all onto Gitea or Forgejo. Renovate runs natively on both, plus Bitbucket and Azure DevOps, covers roughly three times the package ecosystems, and ships a dependency dashboard and automerge Dependabot still doesn't have. What that gap actually costs a self-hosted, git-agnostic PaaS.
Rivet Actors Give an AI Agent State That Survives Between Tool Calls — What a Container-Only PaaS Is Missing
Rivet Actors is an open-source, self-hostable take on Cloudflare Durable Objects, built for AI agent memory and realtime state. Here's what its cold-start and cost numbers actually are, what self-hosting it takes, and whether a container-only PaaS like bex needs to build its own actor primitive.
Sealos and the Rise of Prompt-to-Deploy AI-Native Clouds: What 'Deploy Anything With a Prompt' Gets Right That a Git-Push PaaS Still Doesn't
Sealos pitches 'deploy anything with a prompt' as a new AI-native category, but its own architecture shows agent skills calling the same Kubernetes CRDs the dashboard already used. Here's the actual dividing line between a real AI-native platform and a chat UI bolted onto an existing API.
Broadcom Donated Velero to CNCF — Here's the Backup Checklist a Self-Hosted PaaS Should Actually Run
Broadcom handed Velero to the CNCF Sandbox, but Sandbox-tier projects still archive at a 15-20% rate within three years. Here's the honest risk read and the concrete backup checklist for running Velero against owned object storage.