Show HN: Papercups – Open-source alternative to Intercom
papercups.io
papercups.io
Just recently reached out to Kam, founder of Papercups, on LinkedIn as I had read his article about them going through YC. I wanted to know more about people's experiences with remote YC batches, and Kam responded very quickly and set up a call with no hesitation.
If you're looking for great chat solutions made by great people, check this out :)
Creates a short-lived channel per chat. It works well in terms of sharing responsibilities with a team and allowing people to jump in easily.
I did feel a bit of unease with having customers in the same place as our "private" conversations.
We ship a web-embeddable Matrix client. The users' browser connects directly with a Matrix server of their choice (or a default one).
[1]: https://cactus.chat
and auto-prune to delete all messages after X number of hours - a new project could happen quickly with this.
Is it encrypted? in transit? data at rest?
I see 'enterprise option' for self clouding - guessing this means data is sent to third parties - is that hosted in the USA?
Really like the screensharing bit - is this share either screen? (site admins and or site visitor?) - is that encrypted? Is that (or any info) stored? (by site owner or and third parties ie papercups.co
We have papercups-eu.io which is hosted in Frankfurt and is encrypted at rest.
For those who are more privacy contentious we have a self hosted solution. Where we collect logs and anonymized data to make our product better and debugging purposes.
To reiterate some of the differences, or why people might choose us at the moment:
- A lot of our users really like our Slack integration. For small teams, this means they don't even really have to use our dashboard if they don't want to, because they can do everything from Slack. [0]
- We offer a live screen sharing feature [1]
- We're working on a library to offer complete customization of the chat UI on your website [2]
[0] (We need to set up a better recent demo video of our Slack integration, but if you skim our changelog you'll probably get the gist: https://github.com/papercups-io/papercups/blob/master/CHANGE...)
In the meantime, here are some screenshots from our GitHub wiki: https://github.com/papercups-io/papercups/wiki/Features
And our demo page: https://app.papercups.io/demo
One downside of Discord is that we use threads in Slack to manage conversations, and I don't think Discord has great support for threading. But I know some solutions have worked around this by spinning up a new channel for every new conversation... still need to figure out the ideal UX.