"We have microservices" is not a sizing input. Twelve services in one Compose file is a different job from twelve services that each own a manifest, a route, and a health check. Flisk is opinionated about which of those jobs it wants.

This is the decision table I wish every "should we adopt this" thread started with.

Three sizes, three tools

Your actual stack Better default Why

2–5 services, already containerized Docker Compose One file, no new abstraction, everyone already knows it

You already love your Tiltfile Plain Tilt Flisk's job is to write that file. If it exists and works, leave it

Local must match the cluster kind, minikube, Skaffold, DevSpace, Garden Those tools target Kubernetes. Flisk does not

10–50+ services, painful Compose, agents rewriting Dockerfiles Flisk One service.json per service, flisk up <stack> , generated Tilt loop, no local cluster

You need a platform, SSO, and an SLA tomorrow Not this, yet Four listed adopters, small community, optional Premium at $19/dev/month.…