The Shipa Developer Hub

Welcome to the Shipa developer hub. You'll find comprehensive guides and documentation to help you start working with Shipa as quickly as possible, as well as support if you get stuck. Let's jump right in!

Get Started    Changelog

Introduction

Shipa provides an application-centric way to develop, deploy and manage cloud-native applications without requiring any Kubernetes expertise

The Driver for Shipa

If you’re like most developers, you don’t have a ton of spare time (and perhaps also not much desire) to learn how to create and maintain Kubernetes objects. Where developers are required to manage Kubernetes, slower application delivery is often the result. In these scenarios, platform and DevSecOps teams must also work to support developers’ Kubernetes efforts and cope with ever-greater chances that deployed applications will suffer from misconfigured objects. Platform teams are usually tasked with creating an extra platform layer, adding to costs, and making maintenance and scaling more difficult (while also increasing the potential for failure).

Shipa is an Application Management Framework designed to make it simpler for developers to run their code on Kubernetes in production. As an application management framework, Shipa abstracts underlying cloud and Kubernetes infrastructure so that developers can forget about clusters and objects and focus on the application deployment. Shipa introduces the concept of landing pads called “frameworks,” representing the destination where a CI/CD pipeline is to deliver application code. When code arrives, these frameworks create the necessary application objects across multiple Kubernetes clusters. They also run security scans, attach policies, manage resource limits, produce application metrics, etc.

In this way, Shipa offers a simplified solution for delivering cloud-native applications across heterogeneous clusters and cloud environments, supporting developers, and accelerating application delivery. Specifically, teams can hook Shipa frameworks into their CI/CD pipelines and deploy application code instead of objects, relying on the framework to create all objects required by the application across the different clusters.

Overall, Shipa enables more focus on application development and faster delivery by taking infrastructure concerns off the table, no matter what environment or environments are used.

What Do We Want?

Our goal at Shipa is to allow Platform, DevOps and Development teams to:

  • Think Applications
  • Not Containers
  • Not Clusters
  • Not Ships

👍

Developers

Push code, not containers, not yaml files, not objects

👍

Operations

Continuous, controlled and secure operations

Updated a day ago


Introduction


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.