Kubernetes tooling packaged for small businesses, agencies and growing startups.

Gimlet is a gitops based developer platform that gives you the best of open-source out of the box. The platform you would build, given enough time.

Kubernetes is the standard in application deployment

But most developers are not empowered to use it efficiently. Teams that embark on their Kubernetes journey are rushing to fill the void that is called Kubernetes developer experience.

As former cloud consultants, we've built platforms featuring the best tools of the cloud native landscape. We are also members of cloud native communities, and everybody confirmed to us that bridging the Kuberenetes experience gap takes multiple person to build and then maintain. Covering deployment and dev guard rails first, only years in the project you reach the much sought after disaster recovery and security usecases.

That's why we started Gimlet in 2020, to build a gitops based developer platform on top of the de-facto standards of the industry, FluxCD and Helm. To give developers and small devops teams tooling that much larger platform teams would build.

Laszlo Fogas
Laszlo Fogas
Founder of Gimlet
Gimlet screenshot


Keep everything in git - it's gitops.

Gimlet only interacts with git. It writes your Kubernetes manifests to git when you release, and processes the git history for you to know who did what and when. Gimlet comes with conventions so you don't have to come up with a git repository structure. It also scales out of the box.


Dashboards should not be scary - it's clickops.

Gimlet gives you a dashboard where you can operate your application. You don't have to worry about configuration drift. Every action you take on the Gimlet dashboard is backed by a git commit.
You prefer the command line? The Gimlet CLI has got you covered.
Click to deploy this commit!
Laszlo Fogas

Fixing major bug

Laszlo Fogascommitted2 hours ago


Plays well with your CI.

You can keep organizing your CI workflows as you desire, and call Gimlet's API whenever you need to perform a gitops operation. We have CI plugins for Github Actions, CircleCI, Gitlab and Woodpecker CI.


Bring your own cluster.

Or namespace. Gimlet is not magic hosting.
So bring your own cluster or namespace as Gimlet only interacts with git and leaves the gitops paradigm to manage your applications. Gimlet remains decoupled from your cloud setup.
If you launch a managed Kubernetes cluster, or have a dedicated namespace, you are good to go. Heck, Gimlet works even with Minikube, k3s or kind running on your laptop.

Yaml Authoring

No boilerplate.

Our generic Helm chart allows you to write only a minimal configuration. All common web application usecases are covered so you don't have to look up the Kubernetes documentation or blog posts every turn. Plus you can make sure that your application yamls are following a common blueprint.
What you write
repository: ghcr.io/podtato-head/podtatoserver
tag: v0.1.1


Declarative environment configuration.

Declare your staging and production configs in your application source code. Reference any Helm chart, add plain K8s manifests, or use Kustomize patches for postprocessing.
The Gimlet manifest also supports variables.

Application Platform

Turn your cluster into an application platform.

You can't do much with an empty Kubernetes cluster. Equip it with the must have components to make it a real application platform. Pick your preferred ingress controller, log collector, metrics tool and more from a curated list of open-source components and let Gimlet back it with a gitops repo. Gimlet will deliver a stream of updates whenever new versions are available.

Ready to give it a try?The SaaS version takes just a few clicks.