HackerTrans
トップ新着トレンドコメント過去質問紹介求人

LordKode

no profile record

投稿

[untitled]

1 ポイント·投稿者 LordKode·3 か月前·0 コメント

Ask HN: Why still embed heavy 3rd-party iFrames for simple social proof?

4 ポイント·投稿者 LordKode·3 か月前·0 コメント

[untitled]

1 ポイント·投稿者 LordKode·3 か月前·0 コメント

Show HN: Reviewskits – Open-source, headless, and self-hostable social proof

reviewskits.com
6 ポイント·投稿者 LordKode·3 か月前·2 コメント

コメント

LordKode
·3 か月前·議論
[dead]
LordKode
·3 か月前·議論
[dead]
LordKode
·3 か月前·議論
Hey HN!

I’m building Reviewskits (https://reviewskits.com).

Most startups today use 3+ different tools to manage user feedback: one for testimonials (Senja/Testimonial.to), one for feature voting (Canny), and another for bug reports. It’s a mess of different invoices and fragmented data.

We are building a unified platform for all customer sentiment, starting with a headless testimonial engine.

Why Reviewskits?

    Headless & Dev-first: Instead of heavy, slow iFrame widgets that mess with your CLS, we provide clean APIs and SDKs (React, Vue, Svelte). You keep 100% control over the UI/UX.

    Open-Source: You can self-host it to own your data or use our managed Cloud version.

    Consolidated: One tool for testimonials today, feature requests and feedback loops tomorrow.
The project is early-stage and fully open-source. We’d love your feedback on the architecture or the "Headless" approach for social proof.

Repo: https://github.com/reviews-kits-team/reviews-kits Cloud Waitlist: https://reviewskits.com/

If you like the vision of an open-source, unified feedback stack, we’d appreciate a on GitHub!
LordKode
·3 か月前·議論
Yes, that's a great point. I'm realizing more and more that this is the point I need to emphasize. Thank you for your feedback!