2017 - A Look Back at the Last Year

2017 has been an exciting and busy year for Nanobox. It's crazy to think back to where we were just a year ago and how far we've come. So much has changed. 2017 has been all about proving the market for Nanobox, stabilizing the product, building our business plan, and charting a path forward. Join me as I take a look back at the last year.

Private Beta

At the beginning of 2017, we were about 3 months into our 5 month private beta. Based on feedback and data received early on in the beta, we were in the midst of a major refactor of the Nanobox workflow. Users were confused by the many different commands needed to get an app running locally and the workflow departed a little too much from what devs were already familiar with (Docker, Docker Compose, Vagrant, etc.). We refactored the workflow to be a little less command-intensive and more closely aligned with workflows many devs were already using. It proved to be a good move.

We left private beta on February 7th and opened the doors to everyone.


Since leaving private beta, we have seen steady growth with surges of new users as posts have trended on Hacker News, Reddit, and other channels. With the recent release of the new pricing model, the growth rate has increased.

Nanobox User Growth


Community Growth

Not only has our user-base grown, but the number of those actively participating in the Nanobox community has drastically grown. We've put a ton of effort into fostering an enthusiastic and helpful community and we thank everybody for contributing. We're now 2000+ strong in Slack and growing.

Team Growth

We've been really excited to add a few names to the Nanobox roster in the last few months. Dan Hunsaker officially joined the Nanobox team in October, but had essentially been working for us for a few months. Needless to say, we were happy to make him official. Logan McPhail joined us at the beginning of December and has already made a huge impact. Thanks to him, you can look forward to a new "Elm-ified" Nanobox dashboard in the next month or two.

New Providers

The first cloud provider we officially integrated with was DigitalOcean, mainly because this is where we chose to deploy our underlying servers. If you didn't know this already, Nanobox is deployed and managed using Nanobox (App inception! Dogfooding FTW). Since then, thanks to many contributions from the Nanobox community, we've officially integrated with AWS, Linode, Google Cloud Platform's Compute Engine, Vultr, Azure, Packet, OVH, and Scaleway with others on the way.

Much of the credit goes to @danhunsaker, @jjkester, and other communinity members for defining patterns and building out the LibCloud Nanobox adapter which has allowed us to quickly release support for new cloud providers.

New Data Service Support

In regard to data services, we launched with support for what we called "The Big 6": Postgres, MySQL, MongoDB, Redis, Memcached, and UNFS. This year we added RethinkDB and Elasticsearch with a few others in the works.

Pricing Evolution

The early days of any startup are spent figuring out what value you offer, who will pay for it, and what they'll pay. Nanobox was and is no different. We've seen two major pricing changes this year; the first based mainly on assumptions and the 2nd, most recent based on direct user feedback and data. We're still collecting data and modifying our offering to better suit both your needs and the market.


This November marked a major milestone for our company – we closed our first round of funding, something that was about 6 months in the making so our team was really excited when the round closed. We'd like to thank Kickstart Seed Fund, Prelude Ventures, and the Gem State Angel Fund for sharing our vision and helping bring it to life.

2017 has been an exciting year and 2018 is looking to be even better. This is a really high-level overview of 2017 and major events that have happened in the Nanobox world. For a more granular, sequential look, checkout the timeline below.


Posted in Nanobox