Sablier: scaling idle workloads and choosing deployment versions
Start your containers on demand, shut them down automatically when there's no activity. Docker, Docker Swarm Mode, Podman, Kubernetes and Proxmox LXC compatible.
At a glance
- What is it?
- Sablier is an inactivity-based scaler for containers: a reverse proxy wakes a stopped workload on request and can show a waiting page until it is ready. Its documentation covers providers, health checks and observability; check the version in each example before deploying.
- Who is it for?
- sablier fits a team with genuinely idle workloads, on Docker or Kubernetes, that wants cold starts traded for cost and can put a reverse proxy in front. Read the healthcheck requirement first, because without one the tool cannot tell a started container from a ready one and every session will be wrong.
- Can I use it commercially?
- Yes, with strict conditions. AGPL-3.0 is a network copyleft licence: if people use a modified version over a network, for example as a hosted service, you must offer them its source code under the same licence.
- Is it still maintained?
- Yes. The repository last received commits 1 day ago.
- What is it written in?
- Mainly Go, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 21, 2026, and from our analysis. They are not legal advice.
Star history
- sablierapp/sablier3,147 ★ · +165
| Repository | 2026-09-24 | 2026-11-21 |
|---|---|---|
| sablierapp/sablier | 3k | 3.1k |
165 Stars in the last 58 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
Three different version numbers appear in one document
The current release is v1.18.0. The compose example uses that version inside a comment marker that release automation rewrites, so that one stays correct by construction:
services:
sablier:
image: sablierapp/sablier:1.18.0 # x-release-please-version
command:
- start
- --provider.name=docker
ports:
- "10000:10000"
volumes:
- /var/run/docker.sock:/var/run/docker.sockTwo other examples do not. Step three of the quick start starts the server from an image tagged with a version eight minor releases earlier, and the tip about verifying a downloaded binary names a tarball from a version eight minor releases earlier again. The first of those two is the command a first-time user runs, and its tag is written by hand, so nothing checks it. Following the quick start verbatim means running a much older server than the rest of the page advertises.
The healthcheck example passes options to the test container
The quick start starts a test container with Sablier labels and a Docker health check. The `--health-cmd` option belongs to Docker and invokes `/mimic healthcheck` inside the container. The single-dash options after the image name are arguments to the mimic program, which simulates running and healthy states after a delay. Sablier recommends a health check so it can distinguish a running container from one ready to receive requests.
Signature verification is documented and one of its examples names an old release
Supply-chain verification gets two tips, one for each distribution channel. For the container image the tip asks you to verify an attestation against the organisation's owner, referencing the image by its registry address and tag. For the binary it asks you to verify a tarball, this time naming the repository explicitly. Both are the right thing to do and both are one command, which makes the stale version in the second one worse rather than better: a reader who follows the instruction literally verifies a file name that no longer exists. Publishing the verified name from the current release would cost nothing and the mechanism is already there.
The Docker socket is the documented mount and there is a proxy example beside it
Both container examples bind the container runtime's socket into the Sablier container. That is what lets it start and stop other containers, and it is also equivalent to root on the host, so it is worth stating plainly rather than leaving in a volume line. The repository seems to know: the examples directory contains a directory whose name is a socket proxy pattern, which is the standard mitigation for exactly this problem. The same directory also holds a systemd example, which lines up with the system bus library in the dependency list, and a directory for reconnecting after the runtime restarts, which is the failure mode a socket-based tool has to handle.
Startup sweeps every labelled container, and anti-affinity acts across groups
Two features mean Sablier touches workloads it did not start. The first is a startup flag that stops every container carrying the enable label, on the stated reasoning that it brings the host back to the state Sablier considers correct after a restart. The second is anti-affinity, described as making a workload back off automatically while another group is active, so that a pair of jobs competing for a graphics card or memory does not run at once. Both select by label rather than by session history, which is the right design for an autoscaler and also the thing to think about before you enable either on a host with workloads you did not intend Sablier to manage.
Five generated documents are diffed during the build
The build file is mostly a set of generator and check pairs, and the check half is the interesting part. Each generator writes a document, and each check runs the same generator and compares its output against the committed file, failing with a message telling you which command regenerates it. There are five: the theme schema, the command reference, the label reference, the OpenAPI document and the metrics guide. The label reference is generated from the Go source file that defines the labels, which means the documented list of labels cannot drift from the labels the code actually reads. That is a small piece of engineering that prevents an entire category of documentation bug, and it costs one extra target per document.
A three-part language directive and five test libraries in the main block
The module declares a Go version with a patch component, setting a minimum required toolchain version; newer compatible toolchains can also be used. The dependency list is where the shape of the project shows. The container runtime client is required as two separate modules, an API package and a client package, matching the runtime's own split. Testing pulls in four container-based fixtures: the core harness plus modules for running a nested runtime, a Kubernetes distribution and a compatible in-memory store, which is also a supported server in its own right. Five libraries that exist only for assertions and mocking sit in the main requirement block rather than a test-only one, and one of them is a mock helper pinned to a bare commit from 2018. An error package from before the standard library's equivalent is also still a direct dependency.
Editorial conclusion
sablier fits a team with genuinely idle workloads, on Docker or Kubernetes, that wants cold starts traded for cost and can put a reverse proxy in front. Read the healthcheck requirement first, because without one the tool cannot tell a started container from a ready one and every session will be wrong. Review the quick-start command and pin the image tag you actually intend to run rather than the one printed in the example, and expect the tool to act on containers it did not start: both the startup sweep and the anti-affinity feature key off labels rather than on its own session history.
Frequently asked questions
What is sablier used for?
It starts workloads on demand and stops them after a period of inactivity, working with Docker, Docker Swarm, Podman, Kubernetes and Proxmox LXC. It integrates with reverse proxies such as Traefik, Caddy, Nginx and Envoy to intercept a request, wake the sleeping workload and show a waiting page until it is ready.
What does sablier require a healthcheck for?
The quick start says you should always use a healthcheck with an application that needs to be scaled to zero, because without one Sablier cannot distinguish a container that has started from a container that is ready to receive requests. The example container is given a health command and flags for when it is considered running and healthy.
Which version of sablier should I run?
The newest release is v1.18.0. The compose example in the README uses that version inside an automated marker, but the quick start's server command and the binary signature-verification tip both name much older versions, so pin the tag deliberately rather than copying whichever example you find first.
Can sablier manage containers it did not start?
Yes, by label rather than by session history. A startup flag stops every container carrying the enable label, and the anti-affinity feature makes a workload back off while another group is active, to avoid contention for a graphics card or memory.
How do I install sablier?
Four documented routes: a container image from either of two registries, a binary from the releases page, compiling from the sources with make, or the official Helm chart, which lives in a separate repository and is installed by adding its repository and running a chart install.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/sablierapp-sablier)Star history chart for your README
[](https://hysenlabs.com/projects/sablierapp-sablier)Was this useful?