Show HN: Knock – Notification Infrastructure for Developers
Hey HN! I’m Chris – one of the co-founders at Knock (https://knock.app).
Knock is notifications infrastructure for developers. We provide a set of flexible API primitives you can use to power complex notification systems, without having to roll your own notifications infrastructure in-house. In short: we built notifications so you don’t have to.
We learned about scaling notifications systems the hard way. Previously, my co-founder and I worked together at Frame.io, where we saw the upside of product notifications as well as the pain involved in building and maintaining them. With Knock, we’re building the product we wish we had then.
Knock gives you:
- Faster time to market. Our customers have used Knock to ship real-time in-app feeds and 3rd-party chat integrations (Slack, Discord, Teams) in under an hour. - A flexible notification engine. Power use cases such as batched notifications, conditional sends based on read or device status, and per-user preferences. - A toolkit built for product notifications. Knock comes with isolated environments, versioning, and complete observability from API request, workflow execution, to notifications sent.
We’re excited to share Knock with you today and to get your feedback on what we’ve been building. The best place to start is in our docs (https://docs.knock.app/).
You can learn more about what we’re up to in this Twitter thread: https://twitter.com/samseely/status/1504462708095262724?s=20&t=nIv6QpdMJ-scflu8i1Z2gA. Clickable https://knock.app/ and from FAQ >If I use Knock, do I still pay for downstream messaging services such as Postmark and >Twilio? >Yes. Can’t tell you how frustrating it is to build a notifs service from scratch in house. Can’t wait to try this out and add capacity to our sever team