Your development compose environment already defines all your application's dependencies, so why should you need to recreate your entire environment just to deploy to production? It not only duplicates work, but increases the likelihood of differences between environments that developers are always attempting to mitigate.

Shiplane helps you minimize any differences so that the transition from your local, development Docker environment is just another push of code to your CI.

The sheer number of Docker tools out there is staggering. While they all solve some problem, it can be difficult to decide WHICH tools you want to chain together to make your toolset as a developer new to the Docker ecosystem.

Maybe you're not as big as Google and you don't need Kubernetes right now. Maybe you just picked up Docker last week, but see it's potential as the quickest path to a pipeline despite not understanding everything just yet.

Shiplane is designed to help you move from having nothing to having a complete Docker ecosystem in a matter of minutes - not hours, days, or weeks.

Docker places a lot of power in the hands of developers to define and manage their development environments and how their code is deployed.

This is both good and bad.

The good side of things includes developers no longer being subject to the work of other groups in your company to provision and deploy. However, the downside includes things like developers having control over platform security, the keys to the kingdom, and infrastructure.

While not necessarily ensuring that you'll encounter huge issues, anything security-related is typically the domain of an infrastructure team to whom these responsibilities are specifically designated.

How can these responsibilities be delegated appropriately without taking away the power that the Docker ecosystem provides developers? There are some existing ways to solve these problems, but they require complex systems to be setup to do so.

Shiplane, however, is designed to appropriately delegate responsibilities out of the box. It specifically allows infrastructure teams to be inserted into the process before developers do any work (infrastructure/security can provide base docker images) and during the CI pipeline (so that infrastructure/security teams can manage keys). This allows you to deploy a docker ecosystem quickly and easily with Shiplane and remain confident that you start off pretty secure and are able to continue using it as your processes evolve.

Shiplane is actually designed to be easy to use early on in the process, scale with you, be easy to switch to new tools (say you want to switch from a pure Docker deployment to using Kubernetes), and yet be easy to get rid of should you decide it is no longer for you.