DNSControl
DNSControl v5 is feature-frozen with a ship date, and rc9 is pure provider cleanup
Comparison · Infra & APIs
AWS vs Merge
A side-by-side editorial comparison of AWS and Merge — release velocity, themes, recent moves, and the top alternatives to consider.
AWS vs Merge: at a glance
| Feature | AWS | Merge |
|---|---|---|
| Sector | Infra & APIs, DevOps | Infra & APIs |
| Velocity score | 6.3 | 6.3 |
| Sparks · 30d | 0 | 1 |
| Top themes | ai-agents, serverless, workspaces, observability | unified api, agent handler, mcp connectors, ai gateway |
| Last editorial update | 3mo ago | 11h ago |
| Website | Visit → | — |
What is AWS?
AWS hands AI agents a key to the legacy desktop while modernizing the serverless toolbelt.
AWS is shipping its usual broad May cadence — most of the entries are incremental capability extensions (SAM gains BuildKit and WebSockets, ElastiCache adds 13 CloudWatch diagnostics, MQ enables in-place RabbitMQ 4 upgrades, EKS gets a managed Instance Store CSI driver). The standout is WorkSpaces opening a preview that lets AI agents drive desktop applications inside managed WorkSpaces environments, framed explicitly as the 'last-mile' for AI agents reaching mainframes, ERP, and proprietary tools without modern APIs.
What is Merge?
Merge is turning its weekly integration digest into an agent control plane — the news is always at the bottom.
Merge publishes one dated digest a week, and the structure is consistent: unified Accounting, ATS, CRM, File Storage and HRIS reliability work up top, then Agent Handler and Gateway at the end, where the directional changes live. The feed now also carries per-product breakout entries (Gateway, Unified, Agent Handler) that restate the same week's items in more detail rather than adding new ones. The Agent Handler catalog carries hundreds of generic MCP connectors alongside Merge's own, on shared authentication and policy, and Gateway has been accumulating model coverage, routing controls and guardrails over the same period.
AWS vs Merge: editorial side-by-side
AWS
6.3INFRA · APISDEVOPS
AWS hands AI agents a key to the legacy desktop while modernizing the serverless toolbelt.
◆ Current state
AWS is shipping its usual broad May cadence — most of the entries are incremental capability extensions (SAM gains BuildKit and WebSockets, ElastiCache adds 13 CloudWatch diagnostics, MQ enables in-place RabbitMQ 4 upgrades, EKS gets a managed Instance Store CSI driver). The standout is WorkSpaces opening a preview that lets AI agents drive desktop applications inside managed WorkSpaces environments, framed explicitly as the 'last-mile' for AI agents reaching mainframes, ERP, and proprietary tools without modern APIs.
◆ Where it's heading
Two arcs are visible. First, AWS is positioning itself as the connective layer for enterprise AI agents — WorkSpaces for desktop apps, Amazon Quick + MCP for observability, integrations across legacy estates. Second, the serverless tooling story (SAM, Lambda container images, API Gateway) is finally catching up to how production teams already build, with BuildKit and WebSockets closing real gaps.
◆ Prediction
Expect WorkSpaces' agent-operable preview to add managed evaluation and audit primitives next, since enterprises won't put agents on top of ERP without traceable execution. On the serverless side, look for SAM to extend toward more first-class support for HTTP API constructs and tighter Lambda + container image authoring loops.
Merge
6.3INFRA · APIS
Merge is turning its weekly integration digest into an agent control plane — the news is always at the bottom.
◆ Current state
Merge publishes one dated digest a week, and the structure is consistent: unified Accounting, ATS, CRM, File Storage and HRIS reliability work up top, then Agent Handler and Gateway at the end, where the directional changes live. The feed now also carries per-product breakout entries (Gateway, Unified, Agent Handler) that restate the same week's items in more detail rather than adding new ones. The Agent Handler catalog carries hundreds of generic MCP connectors alongside Merge's own, on shared authentication and policy, and Gateway has been accumulating model coverage, routing controls and guardrails over the same period.
◆ Where it's heading
The through-line is that Merge is repositioning from data plumbing to the layer agents pass through. Each week adds either reach (more connectors, more tools per connector, more models) or control (guardrails, per-project policy, access configuration). This window is reach-and-efficiency: the GitHub connector expanded to 145 tools, Outlook payloads were cut substantially, and Gateway guardrails became configurable per project rather than per account.
◆ Prediction
Expect the per-project granularity applied to guardrails to spread to the rest of Gateway's controls, and the connector catalog to keep absorbing hosted third-party MCP servers the way Axiom was added.
Alternatives to AWS and Merge
Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either AWS or Merge.
Casdoor
Casdoor is spending its release cadence moving auth checks from the client to the server
ESPHome
ESPHome ships on a calendar, and the August beta train is now five builds deep
Strimzi
Strimzi's 1.2.0 candidate closes with a logging fix and nothing else
Prowler
Prowler's assistant decides what to do with findings; the patches keep the scanner honest
NetBox
NetBox adds a cooling data model — the first new infrastructure domain since power
Recent activity from AWS and Merge
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 12d agoMergeGitHub connector hits 145 tools; Gateway adds per-project guardrails
- 19d agoMergeHundreds of generic MCP connectors land in Agent Handler ⚡
- 26d agoMergeLink setup flow becomes configurable per integration
- 1mo agoMergeEmbedded Routing Stack gives Gateway per-customer model controls
- 1mo agoMergeGateway breakout page for the week already covered by Week 2
- 1mo agoMergeUnified breakout page for the week already covered by Week 3
- 3mo agoAWSAWS Elemental MediaTailor now provides automatic secure server-to-server integration with Google's ad platforms
- 3mo agoAWSAWS SAM CLI adds BuildKit support for AWS Lambda functions packaged as container images
- 3mo agoAWSAWS SAM now supports WebSocket APIs for Amazon API Gateway
- 3mo agoAWSAmazon ElastiCache adds thirteen new Amazon CloudWatch metrics for network capacity planning and engine diagnostics
- 3mo agoAWSAmazon WorkSpaces now lets AI agents operate desktop applications (Preview) ⚡
- 3mo agoAWSAWS IoT Core for Device Location adds Confidence Level Configuration and Measurement Type support
Frequently asked questions
What is the difference between AWS and Merge?
They serve adjacent needs but don't currently overlap on shipped themes. AWS and Merge are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is AWS better than Merge?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. AWS and Merge are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
What are the best alternatives to AWS?
Top AWS alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "AWS alternatives" section above for the current picks, or visit /alternatives/aws for the full list with editorial commentary on each.
What are the best alternatives to Merge?
Top Merge alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Merge alternatives" section above for the current picks, or visit /alternatives/merge-dev for the full list with editorial commentary on each.