1512 posts tagged with "PaaS"
Platform-as-a-Service tooling, economics, and self-hosted alternatives
The Seat Is Dead: What Cost Per Accepted Change Means for Metering Agent-Driven Deploys
Coding-agent prices collapsed from seats to per-outcome cost in 2026. This post defines cost per accepted change, prices one agent deploy across three retry scenarios, and gives deploy platforms a four-rule metering model for MCP-driven deploy and rollback calls.
Daytona Raised $24M in February, Then Closed Its Source in June: A Buy-vs-Build-vs-Fork Read on Agent Sandboxes
Daytona's $24M Series A and June closed-source pivot, E2B's Apache-2.0 runtime, Modal's $355M scale bet, and Runloop's seed — a vendor scorecard plus the DRA, snapshot, and concurrency work you inherit when agent sandboxes move onto owned hardware.
Leaving Heroku With Django? Inventory First, Price Table Second
A Django-on-Heroku migration inventory — buildpack pins, release-phase migrations, collectstatic, Celery topology, and Postgres extensions — that decides whether your exit to Render, Railway, Fly.io, or owned hardware is a weekend or a quarter, before any price table can tell you.
Flipt v2 Goes Git-Native: Feature Flags That Branch With Your Code
Flipt v2 stores feature flags in Git instead of a database, turning releases into reviewed pull requests. A comparison of the 2026 self-hosted flag field plus a worked deploy-dark workflow for a git-push PaaS, with the license and Pro-gate caveats spelled out.
Fly.io's Edge Premium, Priced: A Single-Region Always-On App vs Render, Railway, and a $7 Hetzner Box
Fly.io's $2.19 headline assembles to $19 for an always-on single-region stack — priced line by line against Render (~$34), Railway (~$57), and a $7 Hetzner box, with an egress sensitivity table and the honest carve-out where the edge earns its keep.
Fly.io's Logs Went Dark for 4.5 Hours While Apps Stayed Up: What Owning Your Log Pipeline Actually Costs
Fly.io's historical logs lagged 4 hours 24 minutes on October 13 — its second log-ingestion incident in thirteen days — while apps kept serving. This teardown maps which half of the pipeline failed, prices 10 GB/month of logs across Datadog, Better Stack, Axiom, and a €4.35 self-hosted VictoriaLogs box, and shows how owning the log path turns the next backed-up queue into your own alertable metric.
Fly.io's 37-Region Edge vs the Two Regions You Actually Serve: Pricing the $3.88 Machine Against the $7 Heroku Dyno
Fly.io's $3.88 shared-cpu machine undercuts Heroku's $7 dyno per process — but the assembled two-region stack costs $30 vs $23 once Postgres enters, against ~$5–10 on flat Hetzner hardware, plus the edge ops overhead neither unit price shows.
From Azure to Hetzner: What a 2026 Switchers' Guide Gets Right About the Hyperscaler Exit Wave
A 2026 Azure-to-Hetzner switchers' guide promises 70–90% savings; this teardown verifies the egress math and unbundling map, prices the re-assumed ops labor, and distills a PaaS migrator's runbook.
Heroku Put Cloud Native Buildpacks on Legacy Cedar Apps: Why OCI-Via-Buildpacks Is Now the Safe Build Bet
Heroku's September 3, 2026 changelog brought Cloud Native Buildpacks to Cedar-generation apps — what the four build-artifact deltas change, why a sustaining-mode platform spent engineering on convergence, and the default-to-CNB build strategy for git-push platforms.