Congrats on the launch. As a fellow Ruby/Rails developer I love seeing great open-source Ruby/Rails apps in a world where everyone seems to be trending to what's "sexy" now instead of what's tired and true.

Remember when folks called RoR "sexy" and CGI tried and true? Or swap any two nearly similar stacks.

Stack don't matter, it's not the wand, it's the wizard and time makes fools of us all.

https://www.youtube.com/watch?v=YZeZsZEEpno These two actually made me hate the language/framework which is why I never gave it a shot.

What's that last jar supposed to represent?

Looks like gasoline/petrol which is sometimes used by people to huff (inhale) to get high.

The whole "serverless" trend feels (felt? Did the fad die out?) like coming full circle back to (Fast)CGI.

interesting spin on 'tried and true.' also works and made me smile.

unless it was a typo.

You'll never make everyone happy... For me the fact that it's RoR as opposed to, say Go or Elixir is a big turn off, because I know it will be slow and eat up lots of RAM. For me tried and true would be Java.

> It failed due to a couple of obvious reasons.

Would you mind elaborating? Would love to hear why. Seems like a good chat-focused alternative. Was the competition from Freskdesk too stiff (assuming you're based in Bangalore)?

Anyway congrats on breathing new life into the project!

Good job. I hope it gets traction. I've scheduled it to be featured on the homepage of SaaSHub for next Monday.

Chatwoot Co-Founder here: Just saw that its up on SaasHub. thanks a lot for featuring.

No worries. Just keep up the good work.

I'd also suggest, asking some of your users to leave you a review on SH.

Amazing to see your vision coming to life by open sourcing the code and getting so many contributors! No small feat. And great to see the project is being done in Rails. I’ve spent hours looking for a a good product in this space for our company so will definitely give this a try. Two questions - do you have a way to author FAQs and is email an accepted channel?

Thanks and can’t wait to see Chatwoot grow.

Thanks for the kind words. Please see my response below.

> do you have a way to author FAQs

Right now, we don't support it. We have FAQs and a documentation website in the pipeline.

> is email an accepted channel?

Honestly speaking, it is not completely done yet. Emails from support desk mail can be seen in the dashboard, but you cannot respond to it now from our dashboard. Hopefully, we would be able to complete it sooner.

Congratulations on the release. Wish you all the best with it, and will not hesitate to recommend it … but first, email 100% has to be supported. Should be as good as Intercom's user-facing email flow.

Email and twitter DMs are IMO more important for people looking for a support channel than "live agent" chat boxes. Live agent boxes are often adblocked and can't ever be the sole point of contact for a company that cares about having a support channel.

Chatwoot Co-Founder here: Thanks a lot for the support.

Totally agree. email is currently our top priority item and the development is halfway through. We are also actively working on twitter DM as a channel.

Stay posted for updates.

Would like to let you know the hamburger menu currently doesn't work on mobile (clicking it does nothing)

Hey, thanks for letting me know. I will fix it soon :) Looks like I forgot to add the action on the hamburger button.

Related, the chat window that pops up on android is off screen about 15 to 20% but still workable.

I am very familiar with Intercom, and this looks comparable at first glance. Nice start.

A full demo or feature list would be nice. For comparison to other options out there.

Chatwoot Co-Founder here: We are working on the feature comparison and roadmap pages. It will be up on the website in a day or two.

just record a 1 to 2 minute demo of you walking thru standard use cases. it will only take a couple hours and is well worth it.

What were the reasons for failure? It would be great to learn more about your experience.

There are a couple of things which I can tell, most important is that we were naive and we were not patient enough to see the project grow organically and reach the users and find its USP. We wanted instant gratification which is not always available in the startup world.

A lot of first-time entrepreneurs need to listen to this comment.

Nice project! Curious: has any organization started using Chatwoot to provide customer support?

There are no other organizations which are using the project other than us. We use it on our homepage chatwoot.com and for our Facebook pages.

That will change soon. :) Awesome project!

Chatwoot Co-founder here: Do let us know if you face any issues. Will be glad to help.

> It failed due to a couple of obvious reasons. We built on Vue.js and Rails

I read it with a comma instead of fullstop between the sentences :D

Haha! I did the exact same thing I was wondering what was wrong with either of those stacks

Nice job! Have you done any load testing on it? Curious how much server to buy to run an instance with some usage.

Chatwoot Co-founder here: We haven't done a full-scale load testing yet. But we were able to handle the HN traffic using Heroku's free tier.

omg I love you. I probably wont switch til you have a hosted version where I can pay you, sorry. Maybe you can launch one on heroku for me as a beta user and I'll pay you?

Chatwoot Co-founder here: Thanks a lot for the support. A hosted version will be up by end of this month. Meanwhile, you can deploy the repo easily to heroku. Will be happy to assist if you face any issues.