GravityKit
GravityKit ships weekly across a whole plugin suite, with an MCP server now part of the lineup.
Comparison · Infra & APIs
Knock vs LibreSpeed
A side-by-side editorial comparison of Knock and LibreSpeed — release velocity, themes, recent moves, and the top alternatives to consider.
Knock vs LibreSpeed: at a glance
| Feature | Knock | LibreSpeed |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 6.3 | 2.5 |
| Sparks · 30d | 1 | 0 |
| Top themes | notification-infrastructure, data-sources, agent-native, workflow-orchestration | self-hosted, speed-test, frontend-redesign, docker |
| Last editorial update | 11h ago | 1h 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 LibreSpeed?
After a two-year redesign, LibreSpeed is adding tests instead of polishing pixels.
LibreSpeed is a self-hosted speed test that spent roughly two years landing a new frontend design, shipped it behind a feature switch, then promoted it to default in 6.0.0. With that out of the way, 6.2.0 turns to capability: a standalone connection-stability test with live latency charting, packet-loss tracking, alerts and CSV export, plus PWA metadata so the tool can be installed from a browser. Docker deployment has been reworked in parallel, including a port change and PHP limits that were silently rejecting default upload chunks.
Knock vs LibreSpeed: 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.
LibreSpeed
2.5INFRA · APIS
After a two-year redesign, LibreSpeed is adding tests instead of polishing pixels.
◆ Current state
LibreSpeed is a self-hosted speed test that spent roughly two years landing a new frontend design, shipped it behind a feature switch, then promoted it to default in 6.0.0. With that out of the way, 6.2.0 turns to capability: a standalone connection-stability test with live latency charting, packet-loss tracking, alerts and CSV export, plus PWA metadata so the tool can be installed from a browser. Docker deployment has been reworked in parallel, including a port change and PHP limits that were silently rejecting default upload chunks.
◆ Where it's heading
The redesign was the blocker; now that it is default, releases are moving outward — a second measurement mode, installability, better multi-server list handling. The Docker thread runs alongside and is where the breaking changes live: default port moved from 80 to 8080 in preparation for rootless operation, post_max_size raised to accept the tool's own 20 MiB chunks, Alpine base updated. Much of the recent throughput comes from outside contributors and automated agents rather than a single maintainer.
◆ Prediction
Expect the stability test to gain the configuration and server-side plumbing the main speed test already has, and the rootless-container work that the port change was preparation for to land next. Nothing in the entries suggests a change to the project's self-hosted, no-backend-dependency positioning.
Alternatives to Knock and LibreSpeed
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 LibreSpeed.
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.
GoCD
GoCD's changelog is one maintainer keeping a 2010s CI server running on current runtimes.
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.
See all Knock alternatives → · See all LibreSpeed alternatives →
Recent activity from Knock and LibreSpeed
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 agoLibreSpeedStandalone connection-stability test and installable PWA support
- 15d agoKnockRedesigned template editor
- 22d agoKnockBranch rebasing
- 3mo agoLibreSpeedBugfix on classic design
- 3mo agoLibreSpeedNew design is main now
- 6mo agoLibreSpeedHotfix for SQLite database matching in the Docker entrypoint
- 7mo agoLibreSpeedPre-release puts the new design behind a feature switch
- 7mo agoLibreSpeedFinal 5.x release moves the Docker port to 8080
Frequently asked questions
What is the difference between Knock and LibreSpeed?
They serve adjacent needs but don't currently overlap on shipped themes. Knock 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.
Is Knock better than LibreSpeed?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Knock 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.
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 LibreSpeed?
Top LibreSpeed alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "LibreSpeed alternatives" section above for the current picks, or visit /alternatives/librespeed for the full list with editorial commentary on each.