We are moving to Discord

Hasura is moving from Slack to Discord to manage its developer community

tl;dr: https://reactjs.org/blog/2015/10/19/reactiflux-is-moving-to-discord.html 😉

Hasura manages a fairly large and extremely active developer community. The community is made up of Hasura users worldwide and Hasura fellows selected from IMAD, Asia’s largest MOOC. Most members of our community, especially the Hasura fellows who work remotely, collaborate on projects using Hasura and used our Slack group as their headquarters for all things related to development and their fellowship. This leads to a lot of err…“chatter” in group/individual DMs, which is a great thing for a developer tool company that fosters collaboration on fast moving application development projects.

Given the volume of messages generated by the community and the fact that we were on Slack’s free tier, our messages kept getting archived. Sometimes, within the space of a few minutes. Maybe Slack’s pricing works well for small teams, but for those managing communities it is prohibitively expensive. We would have continued on Slack for our internal team, but having two communication apps to use on a daily basis did not excite anyone.

We did a little bit of research (see https://reactjs.org/blog/2015/10/19/reactiflux-is-moving-to-discord.html and http://www.jordanhawker.com/posts/131477030371; oh and discord now has search too!) and found out that Discord scored well on most of the features we were looking for (fingers crossed for conversation threads; summoning the spirit of the IRCs of yore in the meanwhile!). Discord makes it really easy for users to be a part of multiple servers and this is truly great for our GraphQL developer community, who are usually part of Reactiflux, Vue Land etc. too.

Discord is now the new home for the Hasura community. See you there: https://discord.gg/vBPpJkS.


Hasura is an open-source engine that gives you realtime GraphQL APIs on new or existing Postgres databases, with built-in support for stitching custom GraphQL APIs and triggering webhooks on database changes.