GravityKit
GravityKit ships weekly across a whole plugin suite, with an MCP server now part of the lineup.
Comparison · Infra & APIs
Knock vs GoCD
A side-by-side editorial comparison of Knock and GoCD — release velocity, themes, recent moves, and the top alternatives to consider.
Knock vs GoCD: at a glance
| Feature | Knock | GoCD |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 6.3 | 5.0 |
| Sparks · 30d | 1 | 0 |
| Top themes | notification-infrastructure, data-sources, agent-native, workflow-orchestration | ci server, maintenance mode, java baseline, container images |
| Last editorial update | 11h ago | 2h ago |
| Website | — | Visit → |
What is Knock?
Knock is wiring both ends of the messaging data loop, then putting an agent on top
Knock has spent the last month building around its notification engine rather than inside it. Two new inbound data sources, Amplitude and Clay, let product events, cohorts, and enriched account rows land in Knock without customers writing sync code, while message and engagement events flow back out to the warehouse. The dashboard work alongside it, a rebuilt template editor, saved views and tags, schema management, and passkeys, reads as hardening for teams rather than individual developers.
What is GoCD?
GoCD's changelog is one maintainer keeping a 2010s CI server running on current runtimes.
The visible work is almost entirely platform upkeep, and nearly all of it is authored by a single contributor. The baseline has been walked forward repeatedly — Java 17 minimum, then building and packaging on Java 21, then Java 21 as the hard minimum with macOS x64 support dropped — while container images moved from Alpine and CentOS Stream to Wolfi and Chainguard, Rails went from 6.1 through 7.1, and Hamcrest was replaced by AssertJ across the test suite. 26.1.0 is the exception in substance: it carries security fixes described as affecting all prior GoCD versions, with an explicit recommendation to upgrade as soon as possible.
Knock vs GoCD: editorial side-by-side
Knock
6.3INFRA · APIS
Knock is wiring both ends of the messaging data loop, then putting an agent on top
◆ Current state
Knock has spent the last month building around its notification engine rather than inside it. Two new inbound data sources, Amplitude and Clay, let product events, cohorts, and enriched account rows land in Knock without customers writing sync code, while message and engagement events flow back out to the warehouse. The dashboard work alongside it, a rebuilt template editor, saved views and tags, schema management, and passkeys, reads as hardening for teams rather than individual developers.
◆ Where it's heading
The direction is away from a notification API you call and toward the system that holds the messaging state. Ingesting cohort membership and enriched contact data is CDP-adjacent territory, and the wait-for-event function turns linear sequences into event-driven orchestration. The Knock agent then adds a natural-language layer over performance data, so the platform answers questions instead of only exporting rows.
◆ Prediction
Expect more data sources on the same pattern, warehouse and CRM-side connectors that keep audiences in sync without customer glue code. Whether the agent moves from reading analytics to editing workflows directly is the open question these entries do not yet answer.
GoCD
5.0INFRA · APIS
GoCD's changelog is one maintainer keeping a 2010s CI server running on current runtimes.
◆ Current state
The visible work is almost entirely platform upkeep, and nearly all of it is authored by a single contributor. The baseline has been walked forward repeatedly — Java 17 minimum, then building and packaging on Java 21, then Java 21 as the hard minimum with macOS x64 support dropped — while container images moved from Alpine and CentOS Stream to Wolfi and Chainguard, Rails went from 6.1 through 7.1, and Hamcrest was replaced by AssertJ across the test suite. 26.1.0 is the exception in substance: it carries security fixes described as affecting all prior GoCD versions, with an explicit recommendation to upgrade as soon as possible.
◆ Where it's heading
This is a mature product in custodial maintenance rather than development. The pattern across releases is dependency deduplication, dead code removal, deprecation cleanup and base image swaps — the work that keeps a large Rails and Java codebase installable and patchable on current operating systems. Feature entries are rare enough that their absence, rather than any particular change, is the signal.
◆ Prediction
Given the security advisory in 26.1.0 covers all earlier versions and the release notes point offsite for detail, the practical next step for operators is that upgrade. The entries show no queued feature work to project from.
Alternatives to Knock and GoCD
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 Knock or GoCD.
LibreSpeed
After a two-year redesign, LibreSpeed is adding tests instead of polishing pixels.
Nautobot
A security advisory cycle forced Nautobot to break its REST API on both supported branches at once.
Gatekeeper
Gatekeeper grew a package manager for policies — and a benchmark to prove they are not too slow.
Incus
Incus settled its 7.0 LTS, then went straight back to a monthly feature cadence.
Firecracker
Firecracker's microVMs can now grow and shrink devices while running.
Recent activity from Knock and GoCD
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoKnockAmplitude data source
- 8d agoKnockAnalytics in the Knock agent ⚡
- 9d agoKnockWait for event function
- 10d agoKnockClay data source
- 15d agoKnockRedesigned template editor
- 22d agoKnockBranch rebasing
- 23d agoGoCDJava 21 minimum, macOS x64 dropped, and security fixes
- 23d agoGoCDJava 17 baseline and Wolfi container images
- 23d agoGoCDJava 21 LTS by default; CentOS Stream images removed
- 23d agoGoCDPassword toggle fix and Sass deprecation cleanup
- 23d agoGoCDDependency and container image housekeeping
- 23d agoGoCDTest suite migrated from Hamcrest to AssertJ
Frequently asked questions
What is the difference between Knock and GoCD?
They serve adjacent needs but don't currently overlap on shipped themes. Knock is currently shipping more aggressively (velocity 6.3 vs 5.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 Knock better than GoCD?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Knock is currently shipping more aggressively (velocity 6.3 vs 5.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 Knock?
Top Knock alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Knock alternatives" section above for the current picks, or visit /alternatives/knock for the full list with editorial commentary on each.
What are the best alternatives to GoCD?
Top GoCD alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "GoCD alternatives" section above for the current picks, or visit /alternatives/gocd for the full list with editorial commentary on each.