Announcing our SaaS Early Access. Read more

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.

Start deploying now Read more

Kubernetes is the standard in application deployment

Gitops

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.

Learn more

Clickops

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.

Learn more

Click to deploy this commit!

Fixing major bug

Laszlo Fogascommitted2 hours ago

Integration

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.

Learn more

Integration

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.

Learn more

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.

Learn more

What you write

image:
  repository: ghcr.io/podtato-head/podtatoserver
  tag: v0.1.1

What Kubernetes sees

---
# Source: onechart/templates/service.yaml
apiVersion: v1
kind: Service
metadata:
  name: release-name
  namespace: default
  labels:
    helm.sh/chart: onechart-0.38.0
    app.kubernetes.io/name: onechart
    app.kubernetes.io/instance: release-name
    app.kubernetes.io/managed-by: Helm
spec:
  type: ClusterIP
  ports:
    - port: 80
      targetPort: http
      protocol: TCP
      name: http
  selector:
    app.kubernetes.io/name: onechart
    app.kubernetes.io/instance: release-name
---
# Source: onechart/templates/deployment.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: release-name
  namespace: default
  labels:
    helm.sh/chart: onechart-0.38.0
    app.kubernetes.io/name: onechart
    app.kubernetes.io/instance: release-name
    app.kubernetes.io/managed-by: Helm
spec:
  replicas: 1
  selector:
    matchLabels:
      app.kubernetes.io/name: onechart
      app.kubernetes.io/instance: release-name
  template:
    metadata:
      annotations:
        checksum/config: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
      labels:
        app.kubernetes.io/name: onechart
        app.kubernetes.io/instance: release-name
    spec:
      securityContext:
        fsGroup: 999
      containers:
        - name: release-name
          securityContext: &securityContext
            {}
          image: "ghcr.io/podtato-head/podtatoserver:v0.1.1"
          imagePullPolicy: IfNotPresent
          ports:
            - name: http
              containerPort: 80
              protocol: TCP
          resources:
            limits:
              cpu: 200m
              memory: 200Mi
            requests:
              cpu: 200m
              memory: 200Mi

Configuration

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.

Learn more

app: test-app
env: staging
namespace: staging
chart:
  repository: https://chart.onechart.dev
  name: onechart
  version: 0.36.0
values:
  containerPort: 9000
  image:
    repository: ghcr.io/gimlet-io/test-app
    tag: "{{ .SHA }}"
  ingress:
    ingressClassName: nginx
    host: "test-app.staging.turbopizza.net"

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.

Learn more

Enable for free SSL certificates!

⬅️Ingress

Nginx

CertManager

📑 Logging

Loki

🔢 Metrics

Prometheus

.
├── dependencies
│   └── namespace.yaml
├── flux
│   ├── deploy-key.yaml
│   ├── flux.yaml
│   └── gitops-repo.yaml
├── helm-releases
│   └── ingress-nginx.yaml
├── helm-repositories
│   └── ingress-nginx.yaml
├── manifests
│   └── grafana-dashboard-nginx.yaml
└── stack.yaml

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

Or self-host Gimlet