The summary: Cloudsmith provides a way for vendors to sell, license and distribute software as packages. To any customer, anywhere in the world, across a reliable and performant infrastructure, and handling all licensing and invoicing / billing challenges. As most of the readership of this blog will know, a huge proportion of the software developed around the world is dependent upon the third-party packages and libraries we integrate into our projects.

At Cloudsmith, we are all about automation and we believe that the Cloudsmith CLI is an essential part of your DevOps toolkit.

We’ve added production instances in two new locations: US-WEST-2 (Oregon) and AP-SOUTHEAST-2 (Sydney). These are just the first of many, but together they deliver serious performance improvements for our customers around the globe.

What distributed development teams need is this: A ‘single source of truth’ for software assets, one that is available to any team or individual, anywhere on the planet, whilst maintaining the highest levels of performance for all.

We don’t have a customer support team. We have an engineering team, who talk to customers every day. We believe that the best people to help our customers use the product are the people who wrote it.

At Cloudsmith, we are always looking for new ways to make our customers’ lives easier, more efficient and more highly automated. With this in mind we are extremely excited to announce that we have developed an official Cloudsmith Zapier integration!

We now support the upload of Cargo packages to the Cloudsmith platform using the native Cargo publish command.

To ensure that Cloudsmith is and remains a ‘universal’ package management solution, we continue to add formats and extend the scope of the platform. Hence the launch today of our support for CocoaPods.

We’ve been busy over the last week rolling out new product features that make the cloud feel and perform as if it was right there in the building with you - specifically geographic storage and edge caching.

As developers, we need to get back to being diligent - and consistently diligent - about questions of security, provenance, reliability and availability when it comes to packages and dependencies.