← Back to home
Comparison · Infra & APIs

DNSimple vs Pacemaker

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

DNSimple vs Pacemaker: at a glance

FeatureDNSimplePacemaker
SectorInfra & APIsInfra & APIs
Velocity score5.06.3
Sparks · 30d00
Top themesdns, infrastructure, performance, erlanghigh availability, cluster security, tls authentication, dual branch releases
Last editorial update15h ago3mo ago
WebsiteVisit →Visit →

What is DNSimple?

DNSimple's origin name servers answer a quarter faster at p90 after erldns work

DNSimple keeps tuning the Erlang stack it now runs end to end. The November 4 post says p90 query time on its origin name servers is down about a quarter, and about a third for DNSSEC queries, with roughly a third less CPU, and record changes now switch in one step so existing records never briefly disappear. It follows October's dns_erlang rewrite, which cut CPU per query by 12%, and the August finish of the migration to fully owned infrastructure. Above that layer sit the CLI launched in May, browser login from June, and Domain Trustee.

Read the full DNSimple 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 →

DNSimple vs Pacemaker: editorial side-by-side

D
DNSimple
INFRA · APIS
5.0

DNSimple's origin name servers answer a quarter faster at p90 after erldns work

◆ Current state

DNSimple keeps tuning the Erlang stack it now runs end to end. The November 4 post says p90 query time on its origin name servers is down about a quarter, and about a third for DNSSEC queries, with roughly a third less CPU, and record changes now switch in one step so existing records never briefly disappear. It follows October's dns_erlang rewrite, which cut CPU per query by 12%, and the August finish of the migration to fully owned infrastructure. Above that layer sit the CLI launched in May, browser login from June, and Domain Trustee.

◆ Where it's heading

Since owning its full DNS edge, DNSimple has turned to measurable performance work on erldns and dns_erlang, published openly. The product layer above, CLI and API clients, is moving more slowly.

◆ Prediction

Expect more erldns and dns_erlang performance posts; the entries show no sign of a new customer-facing product soon.

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

See all DNSimple alternatives → · See all Pacemaker alternatives →

Recent activity from DNSimple and Pacemaker

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

  1. 2d agoDNSimpleLower latency on our origin name servers
  2. 14d agoDNSimpleFaster DNS with dns_erlang ⚡
  3. 2mo agoDNSimpleFully Independent DNS Edge
  4. 3mo agoPacemaker3.0.3: CVE-2026-10649 and remote message overflow fixes
  5. 3mo agoDNSimpleNew case study: Always Beyond
  6. 3mo agoPacemaker3.0.2: PSK auth for remote CIB operations
  7. 3mo agoPacemaker3.0.1: TLS and X509 authentication for Pacemaker Remote ⚡
  8. 3mo agoPacemaker3.0.3-rc1: release candidate for the CVE fix set
  9. 4mo agoPacemaker2.1.11: CVE-2026-10649 backported to the maintenance branch
  10. 4mo agoPacemaker2.1.11-rc1: release candidate for the 2.1 CVE backport
  11. 4mo agoDNSimpleDNSimple CLI is now available straight from your browser
  12. 5mo agoDNSimpleDomain Trustee now available ⚡

Frequently asked questions

What is the difference between DNSimple and Pacemaker?

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

Top DNSimple alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "DNSimple alternatives" section above for the current picks, or visit /alternatives/dnsimple 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.