Blog
Insights, analysis, and updates from the AI agent economy. Browse by tag · Browse the archive.
Salesforce Closed Both Deploy Doors: The Complete Exit Map for Functions and Heroku Teams
Salesforce Functions went end-of-life in January 2025 and Heroku froze new development in February 2026. One table maps every stranded workload — Functions code, dynos, Postgres, Redis, add-ons — to its destination, with the data-first sequence that avoids migrating twice.
Run Claude Code and Codex on a Remote VPS Without Going Broke: 2026 Provider Rankings After Hetzner's Price Hike
Hetzner's June 2026 price hike killed the default self-hosted agent box. A priced VPS ranking for always-on Claude Code and Codex sessions across a 15x price spread, plus the idle-RAM breakeven math that decides when flat boxes beat metered sandboxes.
Agents Will Operate Your Platform With or Without You: What Frigade's Show HN Proves About Agent APIs
A 96-point Show HN turned observed web traffic into agent tools. That demand signal leaves platforms one choice: ship a versioned, scoped, auditable agent interface, or inherit reverse-engineered traffic with none of those properties.
Render Killed Per-Seat Pricing: A Worked Five-Person Bill for Railway vs Render vs a $19 Hetzner Box
Render's April 2026 restructure ended per-seat billing, so seats cost $0 on both Railway and Render. A line-by-line bill for a five-engineer staging-plus-production setup on each, plus the $19 self-hosted counterfactual.
Render's New Memory-Optimized Plans Repriced: A Steady Web Service Bill vs a Fixed Hetzner Node
Render's August 26 compute-plan overhaul added 15+ memory-optimized tiers without touching legacy prices. A line-by-line reprice of a steady $79 web-service stack, the RAM-heavy workloads that got $25–$100/month cheaper, and the $10 fixed-node counterfactual.
Six Coding Agents on a Private Network: Threat-Model the Credential Blast Radius Before You Copy Railway's Sandbox
Railway's June 2026 sandboxes preinstall six coding agents with private-network reach to production data. Four Kubernetes controls — per-session identities, default-deny egress, approval-gated mutations, and auditable teardown — keep the convenience without the nine-second-wipe blast radius.
Railway vs Render vs Fly.io vs a €4 Hetzner Box: A Line-by-Line Bill for the Same Node.js + Postgres App
A line-by-line recompute of the same Node.js + Postgres bill on Railway, Render, Fly.io, and a flat-rate Hetzner box — plus the egress, geography, and idle-workload sensitivity that decides which metering shape actually wins.
Railway Turned Its CLI MCP Server Into a Proxy: One Credential for Every Agent, and an Audit Trail You Can No Longer See
Railway's September 2026 changelog flips railway mcp from a bundled local server to a proxy for its hosted MCP endpoint. Here is the three-way tradeoff — local vs proxy-to-hosted vs self-hosted — across credentials, logging, scope enforcement, and audit ownership, plus a decision rule for production agent access.
Don't Trust It With Production Data Yet: The 2026 Managed-Postgres Gap Across Railway, Render, and Fly.io
Railway's one-click HA Postgres still carries a don't-trust-production-data warning, Render's PITR-backed managed Postgres stands alone, and Fly.io stays deliberately unmanaged — a like-for-like feature and cost scoreboard for teams leaving Heroku, plus the five-row checklist a self-hosted database must clear.
Subscribe
New posts land in your reader as soon as they publish. Pick a format — all three carry the same posts.
Current feeds keep roughly two days of posts so daily polling does not miss a burst. Older entries stay reachable from the feed's next-page link in readers that follow it, or from the blog archive.
Following one topic instead? Browse tags