Your infrastructure
Install a Kubernetes platform on suitable Linux servers, with infrastructure you choose and control.
Built by Labb Consulting / Open source
Kubernetes.
Within reach.
Kipper brings Kubernetes installation, a web console and application deployment together on infrastructure you choose. We built it to make the platform easier to work with.
Built and maintained by Labb Consulting. Used across our own projects.
Built here. Run here.
The platform behind our own work.
We have spent a long time building Kipper. Today, almost everything we run is on it. Our latest project migration is complete, and we use the same platform we help others adopt.
The remaining workloads need multi-node setups. They stay on their current platforms until Kipper supports what they need.
How an install runs
Three commands. From server to app.
Install the CLI, prepare a server and deploy an application. This scripted example shows the starting point; server access, configuration and operational requirements are part of the setup.
$ curl -sL https://getkipper.com/install | sh ✓ kip installed $ kip install --host 203.0.113.10 --ssh-key ~/.ssh/id_ed25519 ✓ cluster ready https://c-7f2a.kipper.run $ kip app deploy --name shop --image ghcr.io/acme/shop:1.4 ✓ shop is live https://shop.c-7f2a.kipper.run
One platform, from deployment onward
Install it. Ship on it. Keep it running.
Kipper brings the work around an application into one place, with a CLI for delivery and a console for visibility.
Application delivery
Deploy your applications through the CLI and manage them in the same platform.
A console with context
See applications, cluster health and platform components together, instead of piecing together separate views.
Day-to-day operations
Work with application logs, services and backups as part of the platform.
Open source by design
Read the code, follow development and use Kipper under the Apache 2.0 license.
Help from the builders
Work with the engineers developing and using Kipper to assess fit, plan a migration and support your setup.
Where we are going
More of our work. More ways to run it.
Our single-node workloads
Kipper already hosts nearly all of our projects. Running it ourselves keeps development close to the practical work of deploying and maintaining applications.
Multi-node support
Support for multi-node setups is planned. It is the next step for the applications and client environments that we have not yet moved. Our intention is to migrate those too, once their requirements are supported.
Multi-node support is not available yet. For workloads that require it today, we can help with an existing Kubernetes platform.
Before we talk
A few good
questions.
Do you run Kipper yourselves?
Yes. Almost everything we run is now on Kipper, including our latest project migration. The remaining workloads need multi-node setups, which are on the roadmap.
Does Kipper support multi-node clusters?
Not yet. Multi-node support is planned. We will assess your current requirements rather than base a deployment on a future feature.
Can you help us move an existing application?
Yes. We can assess the workload, its data and dependencies, and plan the installation, migration and ongoing operation.
Do we have to use Kipper to work with Labb?
No. We also work with managed cloud Kubernetes and existing platforms without Kipper.
Where can we check the current capabilities?
The Kipper website, documentation and public GitHub repository describe the current release, installation requirements and limitations. Kipper is open source under Apache 2.0.
A good place to start
What are you
working on?
A new product, a platform that needs attention, or an AI idea worth exploring. Let's talk it through.
Book a 30-minute call(opens in a new tab)
info@labb-consulting.comTalk with an engineer. Reply within one business day.
Weekdays, 8:00–18:00 CET.
info@labb-consulting.comTalk with an engineer. Reply within one business day.
Weekdays, 8:00–18:00 CET.