Render vs Merge
Side-by-side trajectory, velocity, and editorial themes.
Render keeps polishing core PaaS while edging into durable execution and agent-driven workflows.
The Render changelog reads as steady platform maturation: dedicated outbound IPs for enterprise networking, dashboard-API parity (changing a service's backing repo/image from the UI), 27% faster Python builds, and runtime-default updates for Node and Go. Pricing has been reshaped for scaling teams, and a new workspace-plan structure rolled out in April. The deeper move is Render Workflows entering public beta — durable, agent-friendly background processes.
Render is positioning as the deployment substrate for AI-era backends. The CLI's services-create command explicitly names agents as users; Workflows beta is framed around agent logic and pipelines; build performance and runtime defaults keep the developer-experience surface competitive against Vercel, Fly, and the hyperscaler PaaS layers. Enterprise dials — dedicated IPs, audit-log additions, pricing tiers — are filling in to support scaled, security-conscious customers.
Expect Render Workflows to graduate to GA with broader SDK and observability coverage, and continued agent-as-user framing in CLI/API surfaces. Pricing-page reshuffles suggest more granular usage-based add-ons (egress, IPs, build minutes) rather than a tier rewrite.
Merge is building an AI-infrastructure stack alongside its unified-API core, with Gateway emerging as a safety/governance layer.
Merge Unified continues a weekly cadence of API maintenance and connector expansion, with Oracle Fusion Cloud ERP launching for Accounting in beta. Merge Agent Handler — the MCP/agent-tools product — is shipping new connectors almost weekly and added Scoped Access Keys for least-privilege agent runtimes. Merge Gateway, the LLM gateway, just shipped Prompt Injection Protection, DLP, RBAC, audit trails, model pinning, and provider-free routing in back-to-back weeks.
Merge is no longer just a unified-API company. Two adjacent products — Agent Handler and Gateway — are getting the heaviest investment, while Unified gets steady connector and reliability work. The Gateway moves into safety and governance target enterprise AI deployments where native provider safety isn't enough. Agent Handler's connector pace suggests Merge wants to be the default tool-pack provider for agent builders.
Expect more Gateway governance features (custom DLP rules, broader vendor support, finer role-based controls) and continued weekly connector drops in Agent Handler — most likely targeting enterprise-SaaS gaps. The Unified roadmap may start incorporating agent-shaped endpoints, blurring lines between Unified and Agent Handler.
See more alternatives to Render →
See more alternatives to Merge →