Name: yantr
Availability: InStock
Author: besoeasy

GitHub Website

Install

Updated10 hours ago

LanguageVue

Setup difficultyModerate

Stars: 198
CPU: 1 Core
RAM: 140 MB
Port: 5252 (Web UI)
Requires: Linux kernel with user namespaces, Loginctl (user lingering), Podman, Subuid/subgid ranges, Systemd, Uidmap (newuidmap/newgidmap)

Docker

ghcr.io/besoeasy/yantr

Install with Linux

What is yantr?

This tool adds a self-hosted application layer to your existing Linux computer — desktop, laptop, Raspberry Pi, NAS, or server — without replacing the operating system. It operates entirely rootless through Podman in user namespaces, avoiding any background daemon, and relies on systemd Quadlet for service management and automatic startup. The web interface on port 5252 presents a curated catalog of over 129 applications spanning AI, media, downloads, cloud storage, security, development tools, and other categories, featuring one-click deployment, per-instance environment configuration, port conflict detection, Cloudflare Tunnel integration, a volume browser, and a REST API for automation. Applications requesting the Docker socket get automatically redirected to the rootless Podman user socket. Setup uses a single curl|bash script that installs Podman, configures subuid/subgid ranges, enables user lingering, and creates the Quadlet unit; a manual podman run command is also provided. Personal and homelab usage is free under a noncommercial license, while commercial use is prohibited.

Should you self-host yantr?

yantr scores 44/100 on selfhost.directory (how scoring works) and ranks #12 of 20 in Application Management. It has 198 GitHub stars.

It shipped 10 stable releases in the past year. The latest, 2026.10.28.2, came out on 28 October 2026.

Setup is moderate: expect some configuration beyond a single command. An official Docker image is available. It is Other-licensed and written mostly in Vue.

Its closest alternative on selfhost.directory is raspiblitz (47/100, 21 stars). It scores higher overall, so compare the two before you pick. See yantr vs raspiblitz side by side.

Features

Curated app catalog
Daemonless architecture
Docker socket translation
Host metrics dashboard
One-Click App Deployment
Per-deployment environment control
Port conflict detection
REST API
Volume Browser

FAQ

Is Yantr free? Can I see the source?

Yes, the source is public on GitHub. Personal and homelab use is free. Commercial use is not allowed under the PolyForm Noncommercial License.

Can I access apps remotely?

Yes. Yantr is local-first, and you can securely expose apps with tools like Cloudflare Tunnel when you need remote access.

Where is my data stored?

App data stays in standard named Podman volumes on your own machine or server, keeping ownership clear and migration straightforward.

Do I need Podman experience to use Yantr?

Not much. Yantr handles app installation, updates, and compose management through a simple interface while still using standard Podman and named volumes under the hood.

Why use Yantr instead of manual Podman Compose?

Yantr applies Compose changes atomically: every step succeeds together, or nothing is changed, reducing broken deployments and partial updates.

Does Yantr replace my operating system?

No. Yantr runs on top of your existing Linux setup using rootless Podman and systemd Quadlet. Your host OS remains unchanged.

What is 'rootless' and why is it better for my homelab?

Rootless means Yantr and all deployed containers run under your standard unprivileged user account without sudo. The Linux kernel maps container UID 0 to an unprivileged host UID, so even a container escape traps the attacker in an unprivileged sandbox without access to host system files, credentials, or rootkits.

Why does Yantr use Podman instead of Docker?

Docker runs as a monolithic root daemon (dockerd) where the docker group equals passwordless host root. Podman runs completely rootless in unprivileged user namespaces without any background daemon, integrates with systemd via Quadlet, doesn't tamper with host firewall rules, and leaves zero footprint on the host OS.