pickfit

BrowseInfra & DevOps tools

Tilt

Tilt automates the dev loop for microservice apps on Kubernetes: watching files, building container images and updating the environment.

Use it

Before you install: known vulnerabilities

pickfit found 8 known high or critical vulnerabilities in the packages a fresh install brings (OSV.dev, 16 Nov 2026). Weigh this before you install it.

  • go:github.com/containerd/containerd/v2 v2.2.1 containerd CRI checkpoint restore CDI annotation smuggling (GHSA-33vj-92qq-66hc, high, fixed in 2.2.5)
  • go:github.com/klauspost/compress v1.19.1 Panic on two-block frames in github.com/klauspost/compress (GO-2026-6865, high, fixed in 1.20.2)
See 6 more

Linux x86_64

  1. download install.sh

    curl -fsSL https://raw.githubusercontent.com/tilt-dev/tilt/master/scripts/install.sh -o /tmp/tilt-install.sh
  2. run installer (puts tilt 0.37.9 binary in ~/.local/bin)

    bash /tmp/tilt-install.sh

Check that it works

tilt version

The output should contain “v0.37.9”.

First thing to try

tilt version

Run tilt version to confirm the install, then run tilt ci in a folder that has a Tiltfile.

What it does

  • Define your dev environment in a Tiltfile
    How to use it
    1. Create a file named Tiltfile in your project folder and add resources, such as local_resource('<name>', cmd='<command>', deps=['<file>']).
    2. Run tilt ci --port <port> from that folder.
    3. Check that the output ends with "SUCCESS. All workloads are healthy."
    Tested
  • Add features to a Tiltfile with extensions
    How to use it
    1. Put the extension's own Tiltfile in a folder, and register it with v1alpha1.extension_repo(name='<repo>', url='file://<folder>') and `v1alpha1.extension(name='<ext>', repo_name='<repo>', repo_path='
    2. Load it with load('ext://<ext>', '<function>') and call the function in your Tiltfile.
    3. Run tilt ci --port <port> and check for "SUCCESS. All workloads are healthy."
    Tested
  • Rebuild container images when files change
    Not shown working

How far pickfit got

Linux x86_64

  1. Installs
  2. Starts
  3. 2 of 3 features work
  4. Works offline

macOS and Windows: the project says it runs there; pickfit hasn’t tried it.

Good for

  • run a complete local dev environment for microservices on Kubernetes
  • automatically rebuild container images on code changes

An alternative to docker-compose.

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

Linux x86_64

Its main function works

  • Replayed from scratch
  • Works offline
  • Checked on 15 Nov 2026
  • Version v0.37.9, built 2026-11-14

Differences the test machine hit

  • README: Tilt automates ... building container images ... Think docker build && kubectl apply
    In the test: No Docker daemon or Kubernetes cluster here, so only local_resource workloads could be tested. Tilt warns that it cannot reach /var/run/docker.sock but keeps running.
  • README: curl -fsSL .../install.sh | bash
    In the test: The script downloaded the pinned release tarball (v0.37.9) into ~/.local/bin without needing sudo, because ~/.local/bin is on PATH. Otherwise it falls back to sudo mv into /usr/local/bin.

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.