[jpallen]

DataJoy Co-founder here. A lot of the DataJoy code IS available (https://github.com/sharelatex/web-sharelatex/tree/datajoy). Our other product ShareLaTeX has an open-source version that you can run locally and is very similar to the version we host at sharelatex.com. DataJoy naturally shares a lot of code with ShareLaTeX (if you look at the two products, you'll see they're very similar). However, with DataJoy, we never got the product to a stage where we felt it made sense to invest time into 'good open source' (documentation, installation guides, etc), but the 'code dump open source' version has always been there.

The main thing that isn't open source with DataJoy is our backend for running code. At the moment this is so tied into Docker, S3, and how we deploy it in our infrastructure, that I don't think it would be much use to anyone else. The innovations here have been in how we deploy and provision it, not in the code itself.

[chii]

if it's innovative, putting it up is still useful as a case study on how to perform said innovation. It's not bringing you any revenue anyway, so it's not like you'd lose anything. Just take out all of the keys and passwords etc from the repo!

[ianleeclark]

I'm sorry to hear y'all are shutting down, I've been a big fan of Sharelatex for going on two years now and have always used it to build my resumes.

[Drdrdrq]

I think they are only closing down Datajoy.

[jpallen]

Indeed, and one of the reasons is the success of ShareLaTeX means that it takes our team's whole attention to keep up with the growth of ShareLaTeX, and keep investing in feature development to keep up with demand. ShareLaTeX isn't going anywhere.

[infinite8s]

So that sounds like success (even though it's sad for datajoy users)! You guys tested the waters with 2 products, one has found product-market fit, and now you guys are focusing on growing that one.