I’m sad to announce that, effective January 31, 2017, Omniref will be shutting down. This isn’t how we hoped things would turn out, but unfortunately, we were never able to find a sustainable business model that justifies the (considerable) expense of running the site. Because of the large number of developers who have come to depend on our services, we’ve kept things running for as long as we possibly could, but unfortunately, there no practical path forward from here.
We’re so grateful to all of you who have supported and encouraged us over the years. While we had different ambitions when we first created Omniref — we actually set out to create a code search engine! — we’re proud of what the site became, and are sad that it has to end this way.
I don’t want to turn this into a post-mortem (that will come later). For now, here are the practical details:
For both of our sites (Omniref Docs, Omniref Pro), we’re turning off new account creation and repository import, effective immediately.
For paying customers: we have already stopped charging renewal fees in anticipation of the shutdown (several months ago). We’ll be in touch with our active users to arrange for data export and migration on an individual basis. If you have any questions or concerns, please contact us directly: support@omniref.com.
For our free users: the site will continue to operate until the end of January. Signups will be disabled effective immediately, but we’ll continue to allow new annotations, questions and comments for existing users until January 15th. On January 15th, we’ll disable new content creation for all users of all sites.
If you have any questions or concerns, please contact us at support@omniref.com, and we’ll do our best to work with you to address them.
Again, thank you all for your support over the years. Happy holidays.