GitHub
GitHub killed its model-hosting product and shipped stacked PRs in the same week.
Comparison · Infra & APIs
PocketBase vs Knock
A side-by-side editorial comparison of PocketBase and Knock — release velocity, themes, recent moves, and the top alternatives to consider.
PocketBase vs Knock: at a glance
| Feature | PocketBase | Knock |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 5.0 | 6.3 |
| Sparks · 30d | 0 | 1 |
| Top themes | backend-as-a-service, lts-backports, dependency-hygiene, supply-chain | notifications, workflow-orchestration, developer-experience, agent-native |
| Last editorial update | 2h ago | 1d ago |
| Website | Visit → | — |
What is PocketBase?
Two maintained branches, a paired-release rhythm, and a window with no new features in it.
PocketBase runs two branches in lockstep: v0.39.x current and v0.22.x, which receives an explicitly labeled backport within minutes of nearly every 0.39 patch. That doubles the apparent release count — the last four calendar dates in this window each produced two tags carrying the same change. The content is uniformly maintenance: JSVM and goja regressions, filter-expression handling, SQLite bumps, and small admin-UI fixes.
What is Knock?
Notification infrastructure grows a memory: workflows can now wait on the real world.
Knock sells notification infrastructure — workflows, broadcasts, in-app guides, and multi-channel delivery that product teams wire up instead of building themselves. July was dense and unusually broad: a rebuilt Notion-style template editor, saved views and tags, schema management for how properties surface across the dashboard, passkey login, branch rebasing, and sandbox test runs that skip delay steps. Underneath the polish, two structural additions landed — message events syncing into the data warehouse, and a workflow step that pauses until an event arrives.
PocketBase vs Knock: editorial side-by-side
PocketBase
5.0INFRA · APIS
Two maintained branches, a paired-release rhythm, and a window with no new features in it.
◆ Current state
PocketBase runs two branches in lockstep: v0.39.x current and v0.22.x, which receives an explicitly labeled backport within minutes of nearly every 0.39 patch. That doubles the apparent release count — the last four calendar dates in this window each produced two tags carrying the same change. The content is uniformly maintenance: JSVM and goja regressions, filter-expression handling, SQLite bumps, and small admin-UI fixes.
◆ Where it's heading
The recent through-line is supply-chain and runtime caution rather than feature work. v0.39.7 forked ozzo-validation after the upstream library changed ownership, with a stated intent to eventually replace it entirely, and shipped a fix for an unhandled panic in worker goroutines. v0.39.10 then reverts the CLI's automatic panic recovery to restore non-zero exit codes, deferring proper exit-code support to v0.40 or v0.41 — the only forward-looking commitment anywhere in this window.
◆ Prediction
The 0.39.x line looks like it is being held stable while v0.40/v0.41 absorbs the CLI exit-code rework, so expect continued paired patch pairs with dependency bumps until that branch opens.
Knock
6.3INFRA · APIS
Notification infrastructure grows a memory: workflows can now wait on the real world.
◆ Current state
Knock sells notification infrastructure — workflows, broadcasts, in-app guides, and multi-channel delivery that product teams wire up instead of building themselves. July was dense and unusually broad: a rebuilt Notion-style template editor, saved views and tags, schema management for how properties surface across the dashboard, passkey login, branch rebasing, and sandbox test runs that skip delay steps. Underneath the polish, two structural additions landed — message events syncing into the data warehouse, and a workflow step that pauses until an event arrives.
◆ Where it's heading
The developer-workflow half of the product is being treated like a codebase: branches that rebase onto main, tests that run in sandbox without delivering, tags and saved views for navigating a growing workspace. The engine half is moving in a different direction — toward workflows that hold state over time. A wait-for-event step, combined with the Clay data source triggering messaging as rows finish enriching, describes journeys rather than notifications. The analytics work is arriving twice over: raw events into the warehouse for teams with their own stack, and natural-language questions to the Knock agent for teams without one.
◆ Prediction
Wait-for-event is the primitive that makes journey-shaped use cases possible, so expect the next releases to address what it exposes — timeouts, observability into workflows sitting paused, and limits on how long one can wait before it becomes a support problem.
Alternatives to PocketBase and Knock
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 PocketBase or Knock.
Ably
Ably is building an agent transport layer, shipping a new AI SDK version roughly every ten days.
Parse Server
One commit per release, and most of them are closing security holes in the Cloud Code and query paths.
Icinga
Three branches patched in lockstep for an unauthenticated takeover — then patched again for the fix's regression.
Rancher
Three branches tagged on one day, with the actual release notes published somewhere else
authentik
Two supported branches, every release a bot-driven cherry-pick — authentik is in pure maintenance here
See all PocketBase alternatives → · See all Knock alternatives →
Recent activity from PocketBase and Knock
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2d agoPocketBaseCLI panic recovery reverted to restore non-zero exit codes
- 2d agoPocketBase0.22 LTS backport of the CLI exit-code revert
- 2d agoKnockAnalytics in the Knock agent
- 3d agoKnockWait for event function ⚡
- 4d agoKnockClay data source
- 9d agoKnockRedesigned template editor
- 9d agoPocketBaseFirefox bulk-select fix, goja and filter-parser updates
- 9d agoPocketBase0.22 LTS backport of the goja and fexpr bumps
- 13d agoPocketBaseJSVM state reset, admin-UI tweaks, SQLite 3.53.3
- 13d agoPocketBase0.22 LTS backport: x/* security bumps and SQLite update
- 16d agoKnockBranch rebasing
- 18d agoKnockPasskey authentication
Frequently asked questions
What is the difference between PocketBase and Knock?
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 PocketBase better than Knock?
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 PocketBase?
Top PocketBase alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "PocketBase alternatives" section above for the current picks, or visit /alternatives/pocketbase for the full list with editorial commentary on each.
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.