UniPipe Service Broker

Offering Services the GitOps Way

UniPipe service broker is a tool for offering services on OSB API compliant marketplaces. It's key features are:

• Fast deployment using terraform: Get up and running with your first service broker in < 30 Minutes
• Easy operations: The service broker container is stateless. Service Instances and bindings are stored in a git repository. The container is broken? Just terraform apply again!
• GitOps workflow: Don't have all the automation yet? Just read out service requests via unipipe list and unipipe show from the git repository and provision the service manually, then update the status via unipipe update.
• Built for automation: The interface for integrating automation is the git repository and unipipe CLI makes working with it easy. Use whatever automation tooling you are most productive with!

🎬 Getting Started

Pretty much everything in the UniPipe universe can be done with unipipe cli. 🕹️ How to install unipipe cli.

After installing unipipe cli, dive into the Tutorials for getting hands-on experience.

For understanding how everything fits together check out Understanding the UniPipe universe or watch this video! ⤵️

)

📚 Wiki

All documentation is available in our Wiki

💡 Why UniPipe service broker?

At meshcloud we have years of experience in building cloud foundations in large organizations with our cloud governance platform meshStack.

We see that teams often struggled to offer services for self service consumption. UniPipe service broker was developed to make iterating on service offerings easy. By using a git repository as the main interface, teams can offer services directly after defining the service catalog. The first few orders of the service don't involve any automation, but are simply executed by hand. This way, service owners build up a good understanding of the problem at hand while already providing value to their customers. After a few orders, service owners might start to automate common steps and work with a Pull-Request workflow that allows them to work with partial automation, while still doing some tasks by hand. Eventually the remaining manual tasks might be automated and the service is 100% automated.

After building the first 100% automated service (say on-prem connectivity), teams often start to help other teams to offer their services (managed CI/CD platform, managed Key Vault, kubernetes cluster as a service, you name it ...) the same way, thus moving the whole organization closer to the cloud operating model.

This way, UniPipe service broker becomes the starting point for the transition from IT services to a cloud foundation.

If you want to understand where your are on your cloud journey, try out our Cloud Foundation Maturity Model. It is a tool that you can use to identify gaps in your cloud setup, define a roadmap and understand where you can save cost by improving efficiency.

Made with ❤️ by meshcloud