Skip to content

About Biebie

Desktop tools for engineers who work across many environments.

What we build

Biebie makes desktop applications for people whose work spans several organisations at once. That covers consultants, managed service providers, contractors and platform teams who look after environments belonging to more than one group.

There are two applications. Biebie Kube is a Kubernetes client that keeps every cluster you manage in one window, organised by the customer it belongs to. Biebie Access organises the VPN profiles and login identities used to reach those environments; it is still in development.

Why they are desktop applications

Tools that manage infrastructure tend to become infrastructure themselves. A hosted dashboard needs credentials to reach your clusters, which means those credentials have to be stored somewhere you do not control, and the dashboard becomes something else to run, upgrade and secure.

Both Biebie applications run on your machine and connect directly to the systems you point them at, using the credentials already on that machine. There is nothing to deploy into a cluster, no agent to install, and no Biebie service in the path between you and your infrastructure.

The principles

Work with what is already there

Biebie Kube reads your existing kubeconfig files where they already live, and does not rewrite or relocate them. Biebie Access drives the VPN clients you have already installed rather than asking you to replace them. Adopting a tool should not mean rearranging everything around it.

Be careful with destructive actions

Clusters can be marked as production, and destructive operations on them require the resource name to be typed out in full. Applying an edited manifest carries the resource version you loaded, so a concurrent change is rejected rather than quietly overwritten.

Say what the tool actually does

Where a capability is partial, we describe it as partial. The supported-clients table on the Biebie Access page distinguishes clients that can be connected programmatically from those that can only be detected and launched, because the difference matters when you are deciding whether the tool fits your work.

Where to find things

  • Downloads — current installers for every supported platform.
  • Release notes — every published Biebie Kube version and what changed in it.
  • Blog — writing about Kubernetes tooling and multi-customer workflows.
  • GitHub — where releases are published and issues are tracked.