incident.io
Nexus does the diagnosis; the rest is on-call plumbing
A side-by-side editorial comparison of Cursor and ZoneMinder — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Cursor | ZoneMinder |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 6.3 | 2.5 |
| Sparks · 30d | 1 | 0 |
| Top themes | agent-fleet-management, model-routing, mobile-agents, enterprise-governance | security-hardening, rbac, api-authorization, maintenance-branch |
| Last editorial update | 12d ago | 4h ago |
| Website | — | Visit → |
Cursor is becoming a control plane for agent fleets — routed, governed, and driven from a phone.
Cursor has stopped shipping editor features and started shipping fleet management. The last two months added cloud VMs that run agents independently of the laptop, an iOS and now iPad client that launches and merges work from anywhere, Slack as a first-class agent entry point, and Bugbot as an automated reviewer in the pull-request path. Underneath all of it, Cursor Router now decides which model handles each request, with admins setting policy per team.
1.38.4 is a security release in all but name, closing ACL gaps across the API.
The 1.38 line is in maintenance, and 1.38.4 is almost entirely authorization work: per-monitor access control enforced on event, frame, zone, tag and media endpoints, two auth bypasses fixed in token validation, and SQL injection and overflow hardening. The 1.36 branch still receives backports, with 1.36.38 carrying its own SQL injection fix. The last feature release was 1.38.0 in February, which brought role-based access control, WebRTC and Go2RTC streaming, and the split of monitor function into separate capturing, analysing, and recording settings.
Cursor has stopped shipping editor features and started shipping fleet management. The last two months added cloud VMs that run agents independently of the laptop, an iOS and now iPad client that launches and merges work from anywhere, Slack as a first-class agent entry point, and Bugbot as an automated reviewer in the pull-request path. Underneath all of it, Cursor Router now decides which model handles each request, with admins setting policy per team.
Every surface added this quarter points the same way: the agent is the unit of work, and the IDE is only one of several places you supervise it from. The admin-facing releases — team marketplaces, distributed MCP servers, org-group access, router policy and model block lists — are assembling an enterprise control plane around that fleet. Cursor is competing less on editing quality and more on whether an organization can run, route, price, and audit many agents at once.
The entries name their own next step: Bugbot's /review is explicitly marked "coming soon" to the CLI, and Cursor Router already spans desktop, web, iOS, CLI, and SDK — so expect review and routing to reach parity across every surface next. Finer-grained router policy, scoped per repo or per task rather than per team, is the natural follow-on to the admin controls just shipped.
The 1.38 line is in maintenance, and 1.38.4 is almost entirely authorization work: per-monitor access control enforced on event, frame, zone, tag and media endpoints, two auth bypasses fixed in token validation, and SQL injection and overflow hardening. The 1.36 branch still receives backports, with 1.36.38 carrying its own SQL injection fix. The last feature release was 1.38.0 in February, which brought role-based access control, WebRTC and Go2RTC streaming, and the split of monitor function into separate capturing, analysing, and recording settings.
Every release since 1.38.0 has been consolidation of what that release opened up. RBAC shipped as a headline feature in February, and the four maintenance drops since have been finding the endpoints it did not cover — the familiar pattern when a permission model is retrofitted onto an API that predates it. Cadence is slow and irregular, months apart, with a 1.39 spec bump already visible in the repo but nothing from that series shipped.
Expect more per-endpoint ACL fixes on the 1.38 line before anything from 1.39 reaches release.
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 Cursor or ZoneMinder.
Nexus does the diagnosis; the rest is on-call plumbing
Four channels, one fix stream — werf's releases are mostly concurrency repairs.
PAM and PKI now take up most of the lines in Infisical's release notes.
Biome's patch train keeps adding rules — and is quietly growing a Markdown linter.
DNSControl is rewriting its record internals in public, one release candidate at a time
Fission's release feed carries only RC tags, and none of them say what shipped
See all Cursor alternatives → · See all ZoneMinder alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Cursor is currently shipping more aggressively (velocity 6.3 vs 2.5), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Cursor is currently shipping more aggressively (velocity 6.3 vs 2.5), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top Cursor alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Cursor alternatives" section above for the current picks, or visit /alternatives/cursor for the full list with editorial commentary on each.
Top ZoneMinder alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "ZoneMinder alternatives" section above for the current picks, or visit /alternatives/zoneminder for the full list with editorial commentary on each.