It is unfortunately time to close the doors, turn out the lights, and shut off the servers at RunCodeRun. After nearly a year and a half of builds, thousands of awesome projects, a tremendous amount of effort, and quite a bit of learning, we’re ready to say that RunCodeRun has run its course. As of April 15th, RunCodeRun will be no more — not for paying customers, and not for open source users.
We’ve never felt the need to be cagey about our service, or our intent. We won’t start now. We can honestly report that we’ve been unable to find the right monetization strategy, one that allows for us to provide the level of service that our users require. For our paying customers, the grand majority ended up at a price point that was barely above hosting cost, leaving very little on the margin for the level of support required. Our open source users need far less support, but they still require it, and of course there is no margin on free. But it would be an incomplete truth to lay our decision solely at the feet of money.
In the end, what we have built is simply a commodity, but without the simplicity. Consuming RunCodeRun is a commodity, with the pricing, support requirements, and need for consistent, uninterrupted service that it entails. But providing RunCodeRun is anything but a commodity, requiring a lot of specialized support and custom effort. There is a negative price arbitrage built into such an arrangement, but worse, a negative emotional one as well. Large scale hosted continuous integration is consumed as a commodity but built as a craft, and the rewards, both emotional and financial, are insufficient to support the effort.
Our team is dedicated to building great systems that solve our customers’ needs, provide real, measurable value for them, and satisfy our urge to make. RunCodeRun is an imbalanced example of that; one whose users are made most happy when the application is quietest, and one whose aspiration and goals no longer rise to match our own. It is best to say proudly but sadly that it is time to focus our resources on the next great project. We bid a fond farewell to RunCodeRun.
We urge you to keep on testing your code and doing so continuously; we can highly recommend the following tools:
Thanks to everyone who shared their code with us; keep kicking ass and writing excellent code.
Note: If your company or organization is interested in taking over hosting and support for RunCodeRun and making the necessary changes for it to be consumable as an open source project, please contact us directly.