← Directory

Sablier

Sablier is a lightweight Docker-aware middleware that automatically starts and stops containers based on incoming requests.

  • Infrastructure
  • Tools & Utilities
Sablier is a lightweight Docker-aware middleware that automatically starts and stops containers based on incoming requests. It integrates with reverse proxies such as Traefik and helps reduce resource consumption by stopping unused applications.

Platform availability

Available on 2 of 9 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

78/100 Good

Maintained
100last commit 15 days ago
Popular
703,005 GitHub stars
Easy to install
452 install platforms, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today, links checked 13 days ago

GitHub stars
3,005
Open issues
67
Last commit
2026-09-29
Latest release
v1.18.0
License
AGPL-3.0
Activity
declining

Checked 7 days ago - source: GitHub (sablierapp/sablier)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 17 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Set up the background service with make install Run make install once; it copies the Sablier config and the systemd unit files (Linux service-start instructions) to ~/.config/systemd/user and starts the user service. If you skip or lose those files, Sablier won't run as a background service. source
  • Install Docker Compose before running examples For the example make commands, install Docker with Compose (the Docker tool that starts a set of containers) and curl if the README asks for it. Without those tools, make up may fail before Sablier can start the demo. source
  • Keep port 10000 open for session requests Many examples use local network port 10000 (a numbered connection point) to ask Sablier to start a session, so make sure it is reachable. If that port is blocked, Sablier won't receive the start request and the demo will time out. source

Fetched 16 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How does Sablier work with a reverse proxy?

Sablier integrates with reverse proxy plugins for Traefik, Caddy, Nginx, Envoy, and other supported systems. The plugin intercepts incoming requests, wakes the sleeping workload, and shows a waiting page until it is ready.

How do you run Sablier as a Linux background service?

Run make install once so it copies the Sablier config and systemd unit files to ~/.config/systemd/user. It then starts the user service; if you skip or lose those files, Sablier will not run as a background service.

What port do many Sablier examples require for session requests?

Keep port 10000 open because many examples use it to ask Sablier to start a session. If the port is blocked, Sablier will not receive the start request and the demo can time out.

What tools must be installed before running the example make commands?

Install Docker with Compose, and curl when the README asks for it. Without those tools, make up may fail before Sablier can start the demo.

Answers sourced from github.com, github.com, github.com, github.com

Community

Collected 9 days ago - public community threads