The Shippable Blog

Shippable, rebranded.

Happy Friday!

We are excited to introduce you to our new aye-aye mascot, inspired by a type of Madagascar lemur. He is fun, playful, and you will frequently see him doing the things we do.

aye aye activities                    

It’s been an eventful couple of years since Avi and I started Shippable and yesterday’s Geekwire bash brought it all together. Two years ago, Avi entered the ping pong tournament looking for some PR for our 3 person startup. Two years later, we were a proud sponsor attending with 10+ Shippers from our Seattle office. What a journey! More on that in a blog post coming up soon.

Having grown beyond being an ingenue, we’ve been looking for a way to represent our personality to the outside world. Our old branding and logo was hastily put together in late 2013 just in time for Techstars demo day and it no longer represents the company we've become. 

Shippable Employee Spotlight: Meet Charlie Crawford

Each month, we will feature a Shippable employee or customer through our blog and newsletter. This month, we spoke with Shippable's newest employee, Charlie Crawford, who has joined us as technical evangelist. In his role, Charlie is our chief blogger and responsible for bringing you product updates, how-tos, and a behind-the-scenes look at your CI/CD system. Feel free to reach out to Charlie via email or on Twitter. 

When did you join Shippable and what’s your role at the company?
I joined the Shippable team in early Febuary. I'm the company Technical Evangelist/Writer, wearer of many hats, and the voice of the customer! I've been having a great time defining what it means to be the company's technical evangelist, but at the same time, the fluidity of the role is half of the fun :)

What’s your favorite feature about Shippable?
A CI and CD solution that actually works. Furthermore, I don't have to
spend more time setting up my CI/CD, than I spent developing the actual application!

What is the biggest problem with the way software development is done right now?
That the amount of friction involved in writing software is regarded as acceptable. If it takes your new hire two weeks to make a build of your software... you're doing something wrong!

Shippable Secures $8M Series A Funding to Containerize and Democratize Continuous Integration and Delivery

Led by Madrona Venture Group, funding will fuel expansion of Shippable's platform into the enterprise and support a rapidly growing user base

SEATTLE--(November 6, 2014)— Shippable, Inc., a containerized continuous integration and delivery platform, today announced that it has raised $8 million in Series A funding. Coming on the heels of a successful $2 million seed round in December, the new funding will be used to further accelerate growth of the company and to drive adoption of its innovative platform into the enterprise. 

Continuous integration and delivery (CI and CD) is the holy grail for companies looking to innovate faster. It helps teams identify bugs instantly, improve quality and reduce risk in their release cycles. Shippable has reimagined this concept by leveraging containers and created a platform that delivers speed, performance, ease-of-use and cost-effectiveness for customers, both in hosted public environments and private data centers.

Madrona Venture Group led the round, with participation from existing investors including Paul Allen’s Vulcan Capital, Divergent Ventures and Founders Co-Op. As part of the financing, Tim Porter, managing director at Madrona Venture Group, will join the board.

Faster builds by caching containers

Shippable V2 - What works differently from V1?

Thanks to all our customers who were patient with us as we ironed out the migration from our V1 platform to V2 platform. We hit some unexpected road bumps due to key management, expired tokens, etc but most of the resulting chaos has settled down now and we’re (mostly) back to business as usual. 

I am sure you will love all the new stuff that V2 brings to the table, but I will write another blog post for that very shortly. In this one, I want to focus on explaining some changes between V1 and V2 and why we made them.