← Back to home
Comparison · Infra & APIs

Scrypted vs Pacemaker

A side-by-side editorial comparison of Scrypted and Pacemaker — release velocity, themes, recent moves, and the top alternatives to consider.

Scrypted vs Pacemaker: at a glance

FeatureScryptedPacemaker
SectorInfra & APIsInfra & APIs
Velocity score0.06.3
Sparks · 30d01
Top themeshome automation, camera server, cluster mode, gpu inferencehigh availability, cluster security, tls authentication, dual branch releases
Last editorial update3h ago3h ago
WebsiteVisit →Visit →

What is Scrypted?

Scrypted spent a year making its camera server run as a cluster, then went quiet.

Scrypted publishes releases as raw commit dumps, so the arc has to be read from the commits themselves. Through 2025 they cluster around three things: cluster mode and the worker addressing needed to make it real, GPU inference plumbing for NVIDIA on Proxmox and Intel runtimes, and a steady stream of per-camera fixes for battery, sleeping, and NVR devices. The most recent tag in this feed is from November 2025, so the visible record stops there rather than continuing to the present.

Read the full Scrypted trajectory →

What is Pacemaker?

Pacemaker is putting TLS and X509 auth between its cluster nodes, then hardening the wire code.

Two branches ship in parallel: the 3.0.x line carrying new work and 2.1.x taking backported fixes. The 3.0 series added TLS for Pacemaker Remote nodes, X509 authentication, TLS certificates for remote CIB operations, and then PSK authentication for those same operations, alongside large-IPC and multipart message support. The most recent releases on both branches are the same security train, fixing CVE-2026-10649 and a set of integer overflows and size checks in the remote message code.

Read the full Pacemaker trajectory →

Scrypted vs Pacemaker: editorial side-by-side

S
Scrypted
INFRA · APIS
0.0

Scrypted spent a year making its camera server run as a cluster, then went quiet.

◆ Current state

Scrypted publishes releases as raw commit dumps, so the arc has to be read from the commits themselves. Through 2025 they cluster around three things: cluster mode and the worker addressing needed to make it real, GPU inference plumbing for NVIDIA on Proxmox and Intel runtimes, and a steady stream of per-camera fixes for battery, sleeping, and NVR devices. The most recent tag in this feed is from November 2025, so the visible record stops there rather than continuing to the present.

◆ Where it's heading

The direction through the tracked window is a home camera server growing into distributed infrastructure: cluster mode, cluster-aware media management, worker addressing, and detection work moving onto custom models and fp16 math. Integration breadth continues alongside it, with HomeKit audio, ONVIF PTZ, text overlays, and PIR sensors. Because the feed has not produced a tag in months, any read on current direction should be treated as the state at the last release rather than today.

◆ Prediction

The entries do not support a confident prediction; the feed has been silent since November 2025, and a stale release stream is not evidence of what the project is doing now.

P
Pacemaker
INFRA · APIS
6.3

Pacemaker is putting TLS and X509 auth between its cluster nodes, then hardening the wire code.

◆ Current state

Two branches ship in parallel: the 3.0.x line carrying new work and 2.1.x taking backported fixes. The 3.0 series added TLS for Pacemaker Remote nodes, X509 authentication, TLS certificates for remote CIB operations, and then PSK authentication for those same operations, alongside large-IPC and multipart message support. The most recent releases on both branches are the same security train, fixing CVE-2026-10649 and a set of integer overflows and size checks in the remote message code.

◆ Where it's heading

The cluster's internal transport is being rebuilt on the assumption that the network between nodes is not trusted. Authentication and encryption arrived first, and the fixes that followed, overflow guards and a maximum remote message size, are the hardening pass on the same code paths. Release discipline is heavy and visible: each version ships a release candidate with an identical commit set days earlier, and every 3.0 release documents the regressions it introduced and where they were fixed.

◆ Prediction

Remote CIB operations now support both X509 certificates and PSK, and the recent fixes all sit in message framing and size limits; further work is most likely to continue in that message-handling code rather than adding another authentication mechanism.

Alternatives to Scrypted and Pacemaker

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 Scrypted or Pacemaker.

See all Scrypted alternatives → · See all Pacemaker alternatives →

Recent activity from Scrypted and Pacemaker

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 11d agoPacemaker3.0.3: CVE-2026-10649 and remote message overflow fixes
  2. 28d agoPacemaker3.0.2: PSK auth for remote CIB operations
  3. 28d agoPacemaker3.0.1: TLS and X509 authentication for Pacemaker Remote
  4. 28d agoPacemaker3.0.3-rc1: release candidate for the CVE fix set
  5. 1mo agoPacemaker2.1.11: CVE-2026-10649 backported to the maintenance branch
  6. 1mo agoPacemaker2.1.11-rc1: release candidate for the 2.1 CVE backport
  7. 9mo agoScrypted0.143.0: NVIDIA on Proxmox fixes and HomeKit audio repairs
  8. 1y agoScrypted0.141.0: custom detection models and fp16 inference
  9. 1y agoScrypted0.139.0: video text overlays and PIR sensor support
  10. 1y agoScrypted0.137.0: cluster manager address fixup
  11. 1y agoScrypted0.135.0: cluster worker address plumbing
  12. 1y agoScrypted0.133.0: battery and sleeping camera fixes

Frequently asked questions

What is the difference between Scrypted and Pacemaker?

They serve adjacent needs but don't currently overlap on shipped themes. Pacemaker is currently shipping more aggressively (velocity 6.3 vs 0.0), 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.

Is Scrypted better than Pacemaker?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Pacemaker is currently shipping more aggressively (velocity 6.3 vs 0.0), 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.

What are the best alternatives to Scrypted?

Top Scrypted alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Scrypted alternatives" section above for the current picks, or visit /alternatives/scrypted for the full list with editorial commentary on each.

What are the best alternatives to Pacemaker?

Top Pacemaker alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Pacemaker alternatives" section above for the current picks, or visit /alternatives/pacemaker for the full list with editorial commentary on each.