Skip to content
Back to search

tiramisu

The most advanced BitTorrent engine and FUSE virtual filesystem for live streaming to your private Plex or Jellyfin library. Hermes and Openclaw ready. Forget Real-Debrid.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/MrRobotoGit/tiramisu with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/MrRobotoGit/tiramisu'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/mrrobotogit--tiramisu/badge.svg)](/listings/mrrobotogit--tiramisu)

HTML

<a href="/listings/mrrobotogit--tiramisu"><img src="/api/listings/mrrobotogit--tiramisu/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

> Not a developer? This section explains what you actually get and why it works so well.

**The end result**: you open Infuse on your Apple TV, your entire movie library appears with posters and metadata, you press Play on a 4K Dolby Vision film and it starts in under a second. No buffering. No "downloading...". No subscription to Real-Debrid or any external service. Everything runs on a single board computer or any always-on Linux box in your home.

How the three pieces fit together

**Tiramisu** runs on your Linux device, a Raspberry Pi, a NAS, a VPS, or any always-on machine. It creates a virtual hard drive that looks completely real to the rest of your network: it contains thousands of `.mkv` files, each the correct size, each seekable. In reality, none of those files exist on disk. When anything reads a byte, Tiramisu silently fetches it in real-time from the BitTorrent network and passes it through.

**Plex** (or **Jellyfin**, or any media server) sees this virtual hard drive as a normal media library. It scans the files, downloads posters and descriptions from the internet, tracks what you've watched, and makes everything available on your home network, just like it would with a real NAS.

**Infuse** on Apple TV connects to your Plex/Jellyfin library and plays the files using Direct Play: it reads the video stream directly from the file, with no conversion or re-encoding. This is why it handles 4K HDR Dolby Vision effortlessly, even though it is coming from a torrent in real time.

Because Tiramisu exposes standard `.mkv` files on a standard filesystem, any player or media server that can read a network share works: Plex, Jellyfin, Emby, Kodi, VLC, mpv, or anything else. No plugins, no special configuration.

How your library gets populated automatically

Tiramisu includes a built-in sync engine that runs on a schedule and keeps your library up to date without any manual intervention.

Every day, the engine queries **TMDB** (The Movie Database) for the latest releases, trending titles, and popular movies. For each title it finds, it searches **Prowlarr** (with Torrentio fallback) for the best available torrent (preferring 4K Dolby Vision, falling back to 1080p). If a good torrent is found, it registers it in GoStorm and creates the corresponding virtual `.mkv` file in the library.

The next time the media server scans, it finds a new file, downloads the poster and description, and the film appears in your library ready to play.

If a better version of a film becomes available later (for example a 4K HDR release of a title you already have in 1080p), the engine replaces it automatically.

TV series work the same way: the sync engine finds new seasons and episodes, organises them in the Plex/Jellyfin-compatible folder structure (`Show Name (Year)/Season.01/`), and they appear in your library within the week.

You can also add a title to your **Plex Watchlist** from any device and it will appear in your library within the hour.

Prowlarr Integration (Resilience)

To ensure the system remains functional even when public aggregators like Torrentio are down, Tiramisu includes a **Prowlarr Adapter**. This allows you to use your own self-hosted Prowlarr instance as the primary source for torrents.

The sync engine implements a **Strict Fallback** logic: it first queries your Prowlarr indexers using IMDB IDs for maximum precision. If no results are found locally, it automatically falls back to Torrentio.

**Configuration** is done via `config.json` (or the Control Panel → **Prowlarr Indexer** section):

"prowlarr": {
  "enabled": true,
  "api_key": "your-api-key",
  "url": "http://192.168.1.x:9696"
}

See the [Prowlarr Adapter Documentation](docs/prowlarr-adapter.md) for technical details.

100% local, no subscriptions

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 321 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. <h1 align="center">
  2. <img src="docs/screenshots/tiramisu-logo.svg" alt="Tiramisu" width="240">
  3. </h1>
  4. <p align="center"><strong>BitTorrent engine and FUSE virtual filesystem that streams your torrents to Plex, Jellyfin and Infuse, live.</strong><br>
  5. 4K HDR Dolby Vision, fully seekable, starting in under a second, even on a Raspberry Pi 4. MCP ready for Hermes, OpenClaw and Claude Code. No Real-Debrid.</p>
  6. <p align="center">
  7. <a href="https://github.com/MrRobotoGit/tiramisu/releases/latest"><img src="https://img.shields.io/github/v/release/MrRobotoGit/tiramisu?label=Release&color=121518" alt="Latest release"></a>
  8. <a href="https://hub.docker.com/r/mrrobotogit/tiramisu"><img src="https://img.shields.io/docker/pulls/mrrobotogit/tiramisu?logo=docker&label=Docker%20Pulls&color=121518" alt="Docker pulls"></a>
  9. <a href="https://hub.docker.com/r/mrrobotogit/tiramisu"><img src="https://img.shields.io/docker/image-size/mrrobotogit/tiramisu/latest?logo=docker&label=Image%20Size&color=121518" alt="Docker image size"></a>
  10. <a href="LICENSE.md"><img src="https://img.shields.io/badge/License-GPLv3-121518" alt="License: GPL v3"></a>
  11. <a href="https://github.com/awesome-selfhosted/awesome-selfhosted"><img src="https://awesome.re/mentioned-badge.svg" alt="Mentioned in Awesome Selfhosted"></a>
  12. <a href="https://deepwiki.com/MrRobotoGit/tiramisu"><img src="https://img.shields.io/badge/Ask-DeepWiki-121518" alt="Ask DeepWiki"></a>
  13. </p>
  14. <p align="center">
  15. <a href="#quick-install"><b>Install</b></a> ·
  16. <a href="#docker"><b>Docker</b></a> ·
  17. <a href="docs/README.md"><b>Documentation</b></a> ·
  18. <a href="docs/configuration.md"><b>Configuration</b></a> ·
  19. <a href="#faq"><b>FAQ</b></a> ·
  20. <a href="https://github.com/MrRobotoGit/tiramisu/releases"><b>Releases</b></a>
  21. </p>
  22. <p align="center"><img src="docs/screenshots/ui-network-light-v2.gif" alt="Tiramisu live swarm: peers, torrents, piece cache, FUSE buffer and the devices that are watching, in one graph"></p>
  23. <p align="center"><sub>The live swarm: every peer, torrent, cache and player in one graph. When a peer sends bad data, Adaptive Shield lights up the pipes it protects (see Screenshots).</sub></p>
  24. ---
  25. ## Overview
  26. Tiramisu turns torrents into ordinary, seekable `.mkv` files on a FUSE virtual filesystem. Plex, Jellyfin, Infuse or any player reads them like files on a local disk, while every byte is fetched live from the BitTorrent swarm. Nothing is downloaded in advance, there are no temporary copies and no storage quota.
  27. The BitTorrent engine runs in the same process as the filesystem, so data flows from peers through RAM to the media server with no HTTP proxy in between. The result is 4K HDR Dolby Vision playback that starts in under a second from the warmup cache (2–4 s on a cold swarm) and seeks instantly, on hardware as small as a Raspberry Pi 4.
  28. ---
  29. ## Screenshots
  30. <table>
  31. <tr>
  32. <td width="50%"><img src="docs/screenshots/ui-dashboard-light-v2.png" alt="Dashboard in light mode: download speed, torrents, active streams, services, scheduler and logs"></td>
  33. <td width="50%"><img src="docs/screenshots/ui-control-panel-dark-v2.png" alt="Control Panel, Engine section in dark mode, with three pending changes in the change bar"></td>
  34. </tr>
  35. <tr>
  36. <td align="center"><sub><b>Dashboard</b>: speed, torrents, streams, services, scheduler and logs</sub></td>
  37. <td align="center"><sub><b>Control Panel</b>: every setting, with a change bar that applies them together</sub></td>
  38. </tr>
  39. <tr>
  40. <td><img src="docs/screenshots/ui-network-strict-dark-v2.png" alt="Live swarm in dark mode during an Adaptive Shield STRICT episode"></td>
  41. <td><img src="docs/screenshots/ui-control-panel-light-v2.png" alt="Control Panel, Streaming and FUSE section in light mode"></td>
  42. </tr>
  43. <tr>
  44. <td align="center"><sub><b>Adaptive Shield</b>: a STRICT episode, live</sub></td>
  45. <td align="center"><sub><b>Light, dark or automatic theme</b></sub></td>
  46. </tr>
  47. </table>
  48. <p align="center"><img src="docs/screenshots/ui-piece-map-light-v2.gif" alt="Active streams with the piece map open: a fixed playhead over a strip of pieces, ready, arriving and not yet requested, up to the download frontier"><br><sub><b>Piece map</b>: under each stream, the pieces from the player's read position to the download frontier, scrolling live</sub></p>
  49. <p align="center"><img src="docs/screenshots/ui-mobile-v2.png" alt="Dashboard on a phone, live swarm in dark mode and timeline in light mode" width="520"><br><sub>On a phone: the network view fits the first screen</sub></p>
  50. ---
  51. ## Features
  52. - **Streams, never downloads.** Each `.mkv` is a live torrent with the correct size, fully seekable. Byte ranges pass through RAM and an optional SSD warmup cache for the first and last megabytes of every file.
  53. - **A library that maintains itself.** The built-in sync engine finds new, trending and popular titles on TMDB, picks the best release from Prowlarr or Torrentio, upgrades a 1080p entry to 4K when a better release appears, follows TV series season by season, and adds anything on your Plex Watchlist within the hour.
  54. - **Music and audiobooks too.** `music/` and `audiobooks/` sit next to `movies/` and `tv/`, read-only, with MusicBrainz or ASIN identities, ready for Plex and Plexamp.
  55. - **Playback protection.** Adaptive Shield guards against corrupt data and bans bad peers, TailHedge races a second peer when one stalls, PEXChurn frees slots held by useless peers, and the read-ahead adapts to the bitrate.
  56. - **Native Plex and Jellyfin integration.** Playback webhooks switch the stream to Priority Mode, and titles are matched by IMDb id, so localized names still match.
  57. - **Control Panel and Dashboard.** Every setting in one place, and a live view of the swarm, streams, services, scheduler and logs, on desktop and phone. Each stream shows its piece map: what is ready ahead of the player and where the download frontier is.
  58. - **Library API and MCP server.** Add or remove titles over HTTP, or let an AI agent (Hermes, OpenClaw, Claude Code) search and file releases with your own scoring profile.
  59. - **Optional sign-in.** One user and a password for the Control Panel, the Dashboard and every API, plus named tokens: MCP tokens for AI agents, API tokens for apps and scripts built on Tiramisu. Keys and tokens in the config are write-only, and the GoStorm API answers on the host only.
  60. - **VPN friendly.** NAT-PMP port mapping for WireGuard and an optional IP blocklist, loaded before the engine starts when a cached copy exists.
  61. - **One binary.** GoStorm, a deeply patched fork of [TorrServer Matrix](https://github.com/YouROK/TorrServer) and [anacrolix/torrent](https://github.com/anacrolix/torrent), ships inside the single `tiramisu` binary.
  62. ---
  63. ## Contents
  64. [Overview](#overview) · [Screenshots](#screenshots) · [Features](#features) · [How It Fits Together](#how-it-fits-together-plex-jellyfin-and-infuse) · [Requirements](#requirements) · [Quick Install](#quick-install) · [Docker](#docker) · [Sign-in and Tokens](#sign-in-and-tokens) · [Documentation](#documentation) · [FAQ](#faq) · [Contributing and Security](#contributing-and-security) · [Support](#support) · [Acknowledgements](#acknowledgements) · [License](#license)
  65. ---
  66. ## How It Fits Together: Plex, Jellyfin and Infuse
  67. > This section explains what you get and how the pieces work together.
  68. **The end result**: you open Infuse on your Apple TV, your entire movie library appears with posters and metadata, you press Play on a 4K Dolby Vision film and it starts in under a second. No buffering. No "downloading...". No subscription to Real-Debrid or any external service. Everything runs on a single board computer or any always-on Linux box in your home.
  69. ### How the three pieces fit together
  70. **Tiramisu** runs on your Linux device, a Raspberry Pi, a NAS, a VPS, or any always-on machine. It creates a virtual drive that looks like ordinary storage to the rest of your network: it contains thousands of `.mkv` files, each the correct size, each seekable. In reality, none of those files exist on disk. When anything reads a byte, Tiramisu fetches it in real time from the BitTorrent network and passes it through.
  71. **Plex** (or **Jellyfin**, or any media server) sees this virtual hard drive as a normal media library. It scans the files, downloads posters and descriptions from the internet, tracks what you've watched, and makes everything available on your home network, just like it would with a real NAS.
  72. **Infuse** on Apple TV connects to your Plex/Jellyfin library and plays the files using Direct Play: it reads the video stream directly from the file, with no conversion or re-encoding. This is why it plays 4K HDR Dolby Vision without transcoding, even though the data comes from a torrent in real time.
  73. Because Tiramisu exposes standard `.mkv` files on a standard filesystem, any player or media server that can read a network share works: Plex, Jellyfin, Emby, Kodi, VLC, mpv, or anything else. No plugins, no special configuration.
  74. ### How your library gets populated automatically
  75. Tiramisu includes a built-in sync engine that runs on a schedule and keeps your library up to date without any manual intervention.
  76. Every day, the engine queries **TMDB** (The Movie Database) for the latest releases, trending titles, and popular movies. For each title it finds, it searches **Prowlarr** (with Torrentio fallback) for the best available torrent (preferring 4K Dolby Vision, falling back to 1080p). If a good torrent is found, it registers it in GoStorm and creates the corresponding virtual `.mkv` file in the library.
  77. The next time the media server scans, it finds a new file, downloads the poster and description, and the film appears in your library ready to play.
  78. If a better version of a film becomes available later (for example a 4K HDR release of a title you already have in 1080p), the engine replaces it automatically.
  79. TV series work the same way: the sync engine finds new seasons and episodes, organises them in the Plex/Jellyfin-compatible folder structure (`Show Name (Year)/Season.01/`), and they appear in your library within the week.
  80. You can also add a title to your **Plex Watchlist** from any device and it will appear in your library within the hour.
  81. ### 100% local, no subscriptions
  82. Tiramisu has no external dependency at playback time. No third-party service, no monthly fee, no data leaving your home. Your library does not depend on a third-party service at playback time, so it never disappears because a remote service went down.
  83. ### When you press Play: the full chain
  84. You tap Play on Infuse, and Infuse asks Plex (or Jellyfin) for the file. Plex
  85. reads it from Tiramisu's virtual filesystem, and at the same time
  86. the media server also fires a webhook at Tiramisu saying "user started playing
  87. this film". Tiramisu matches the event to a torrent and switches that stream to
  88. **Priority Mode**, so every spare byte of bandwidth goes to the film you are
  89. watching and background activity pauses. From there the bytes travel the only
  90. path they ever take: from BitTorrent peers into Tiramisu's memory, through the
  91. FUSE layer to Plex, from Plex to Infuse, and onto the TV. If you seek, the same
  92. machinery jumps straight to the new position in the torrent instead of
  93. re-buffering from the beginning.
  94. ---
  95. ## Requirements
  96. | Component | Details |
  97. |-----------|---------|
  98. | **Hardware** | Any `linux/amd64` or `linux/arm64` device, **Raspberry Pi 4 is the minimum tested baseline** (4 GB RAM recommended). Runs on NAS, VPS, mini-PC, or any always-on Linux box. **On amd64, AVX2 is strongly recommended** (any x86_64 CPU from ~2013 onward, Intel Haswell or AMD Excavator and later). Without it, Go's SHA1 piece verification falls back to its slowest scalar path and may not sustain real playback bitrates; Tiramisu still starts, logging a warning at boot so high CPU and stuttering have a visible cause. arm64 has no equivalent requirement: NEON is mandatory on every ARMv8-A chip, so any real arm64 device, the Pi 4 included, already clears the floor. |
  99. | **Go** | 1.26+ (`linux/amd64` or `linux/arm64`), do **not** use the 32-bit `linux/arm` toolchain. Build with `CGO_ENABLED=1`: the SQLite piece-completion layer is cgo |
  100. | **FUSE 3** | `sudo apt install fuse3 libfuse3-dev` |
  101. | **systemd** | Native install only, for service management |
  102. | **Samba** | Native install only, to share the library: `sudo apt install samba` |
  103. | **Plex/Jellyfin** | Media Server (on Synology or any network host) |
  104. | **TMDB API key** | For the sync engine. Free at [themoviedb.org](https://developer.themoviedb.org/docs/getting-started) |
  105. | **Plex token** | For the sync engine and webhooks. Settings → Account → XML API |
  106. ---
  107. ## Quick Install
  108. > [!NOTE]
  109. > Tiramisu was previously called GoStream. The binary name, config paths and systemd service name changed with the rename: when upgrading from a GoStream install, run the install script again to pick up the new layout.
  110. ```bash
  111. curl -fsSL https://raw.githubusercontent.com/MrRobotoGit/tiramisu/main/install.sh -o install.sh
  112. chmod +x install.sh
  113. ./install.sh
  114. ```
  115. The interactive installer handles everything end-to-end:
  116. 1. Installs system dependencies (`fuse3`, `libfuse3-dev`, `gcc`, `samba`, `git`)
  117. 2. Prompts for all required paths, Plex credentials, TMDB key, and NAT-PMP settings
  118. 3. Generates `config.json` from `config.json.example`
  119. 4. Creates `Tiramisu/STATE/`, `logs/`, and FUSE mount point directories
  120. 5. **Compiles the Tiramisu binary** (downloads Go if needed, detects architecture automatically)
  121. 6. Writes and enables the systemd service for `tiramisu`
  122. Once complete:
  123. ```bash
  124. sudo systemctl start tiramisu
  125. ```
  126. ---
  127. ## Docker
  128. > [!IMPORTANT]
  129. > Tiramisu mounts a FUSE filesystem at startup. Docker blocks this syscall by default. The container requires elevated privileges to run.
  130. Pre-built images for `linux/amd64` and `linux/arm64` are published automatically on every release to Docker Hub and GitHub Container Registry:
  131. | Registry | Image |
  132. |----------|-------|
  133. | **Docker Hub** | `mrrobotogit/tiramisu:latest` |
  134. | **GHCR** | `ghcr.io/mrrobotogit/tiramisu:latest` |
  135. **Pull:**
  136. ```bash
  137. docker pull mrrobotogit/tiramisu:latest
  138. # or
  139. docker pull ghcr.io/mrrobotogit/tiramisu:latest
  140. ```
  141. **Run:**
  142. ```bash
  143. docker run -d \
  144. --name tiramisu \
  145. --restart unless-stopped \
  146. --device /dev/fuse \
  147. --cap-add SYS_ADMIN \
  148. --cap-add NET_ADMIN \
  149. -v /path/to/config.json:/config.json \
  150. -v /path/to/state:/state \
  151. -v /mnt/tiramisu-mkv-real:/mnt/tiramisu-mkv-real \
  152. -v /mnt/tiramisu-mkv-virtual:/mnt/tiramisu-mkv-virtual:rshared \
  153. -p 9080:9080 \
  154. mrrobotogit/tiramisu:latest
  155. ```
  156. The full guide covers persistent state in `/state`, updates, mount propagation and the Windows installer: see [Installation → Docker](docs/installation.md#docker).
  157. ---
  158. ## Sign-in and Tokens
  159. <p align="center"><img src="docs/screenshots/ui-access-light-v2.png" alt="Control Panel, Access section: sign-in required, four named tokens, two for MCP and two for the API, with when and from where each was last used, and the signed-in browser sessions" width="720"><br><sub><b>Control Panel → Access</b>: sign-in, MCP and API tokens, browser sessions (sample data)</sub></p>
  160. Out of the box, anyone who can reach `:9080` on your network can use the Control Panel, the Dashboard and the APIs. Turn on sign-in in **Control Panel → Access** to require a password for all of them: the Control Panel, the Dashboard, every `/api/*` endpoint, `/metrics` and the MCP server.
  161. - **One user, one password.** A browser stays signed in for 30 days from its last visit. The Access page lists the signed-in browsers and can sign out all the others.
  162. - **Two kinds of token for everything that is not a browser.** Each client gets a named token (`tmr_…`), sent as `Authorization: Bearer <token>`. An **MCP token** opens only the MCP server and its library tools: give it to AI agents such as Hermes or Claude Code. An **API token** opens the HTTP API: give it to any software built on top of Tiramisu, such as a custom client or app that adds and removes titles, reads the engine status or starts a sync, the macOS menu bar app and your scripts. Neither can create or revoke tokens, change the password or turn sign-in off: that takes the Control Panel, signed in. Tokens do not expire; the value is shown once, when you create it, and you can revoke it at any time from the same page.
  163. - **Create the tokens first.** Tokens can be created while sign-in is still off: configure your clients, then turn it on, and nothing stops working.
  164. - **Plex and Jellyfin keep working.** Their playback webhooks stay open, so the media server needs no changes.
  165. - **Keys stay on the server.** Your Plex/Jellyfin token and your TMDB and Prowlarr API keys are write-only: the Control Panel shows whether each one is set, never its value.
  166. - **The engine API is private.** GoStorm's API on `:8090` listens on the Tiramisu host only, so no other device can manage torrents behind sign-in's back.
  167. ```bash
  168. # An MCP client (Claude Code) with an MCP token
  169. claude mcp add --transport http tiramisu http://<host>:9080/mcp \
  170. --header "Authorization: Bearer tmr_..."
  171. # A script with an API token
  172. curl -H "Authorization: Bearer tmr_..." http://<host>:9080/api/health
  173. ```
  174. **Forgot the password?** Stop the service, run `tiramisu --reset-auth` on the host, start it again: the user, the sessions and the tokens are cleared and sign-in is off. With Docker, start the container once with `-e TIRAMISU_RESET_AUTH=1`, then remove the variable.
  175. Every endpoint is documented inside Tiramisu too: **Reference → API** in the side menu (`/api-docs`) lists the stable API with parameters, a ready-to-copy `curl` for your own address and sample responses, and puts the MCP server address first.
  176. <p align="center"><img src="docs/screenshots/ui-api-light.png" alt="Reference, API page: the MCP server box with its address and client config, then the endpoints grouped by area, one of them open with its parameters, request and response" width="720"><br><sub><b>Reference → API</b>: the MCP server and the HTTP endpoints, documented in the app</sub></p>
  177. Sign-in is meant for your home network or a reverse proxy with HTTPS in front of it; see [Sign-in and API tokens](docs/api.md#sign-in-and-api-tokens) for the details: rate limits, reverse proxies and what happens if the state database cannot be read.
  178. ---
  179. ## Documentation
  180. | Guide | What it covers |
  181. |-------|----------------|
  182. | [Installation](docs/installation.md) | Docker in detail, Plex/Jellyfin and Samba setup, building from source |
  183. | [User Guide](docs/user-guide.md) | First-run steps, webhooks, the Control Panel and the Dashboard |
  184. | [Sync Engine](docs/sync-engine.md) | Movies, TV, Watchlist and Music sync, the dead-release reaper, Prowlarr |
  185. | [Configuration](docs/configuration.md) | Every `config.json` field, quality scoring, languages, environment variables |
  186. | [API and MCP Server](docs/api.md) | Sign-in and API tokens, Library API, MCP server for AI agents, HTTP endpoint reference |
  187. | [Architecture](docs/architecture.md) | How the FUSE layer, caches and engine work; performance figures |
  188. | [Troubleshooting](docs/troubleshooting.md) | Common problems and fixes, file locations |
  189. ---
  190. ## FAQ
  191. **What is Tiramisu?**
  192. Tiramisu is a self-hosted BitTorrent engine with a built-in FUSE virtual filesystem. It presents torrents as normal, seekable `.mkv` files to Plex or Jellyfin, and streams the bytes live from the swarm as they are read, with no download step and no temp files.
  193. **How is this different from Real-Debrid or other debrid services?**
  194. Debrid services are third-party paid subscriptions that cache torrents on someone else's servers and hand you an HTTP link. Tiramisu runs entirely on hardware you own, no subscription, no third-party server, no monthly fee. You get the same "instant playback" experience, but the BitTorrent swarm itself is the source, not a rented cache.
  195. **Does Tiramisu store or download the files?**
  196. No persistent copy of the media is kept. Byte ranges pass through RAM (and an optional bounded SSD cache limited to the first/last few MB of each file, purely to speed up the first seconds of playback) and are never written to disk as complete files. There is no storage quota to plan around because there is nothing to store.
  197. **Do I need to seed or keep uploading?**
  198. Tiramisu participates in the swarm like any BitTorrent client while a file is open, but retention drops automatically once playback stops, and no long-term seeding is required or expected.
  199. **What hardware do I need?**
  200. A Raspberry Pi 4 (4 GB RAM) is the tested minimum baseline, and it comfortably handles 4K HDR streaming. Any `linux/amd64` or `linux/arm64` machine works: NAS, VPS, mini-PC, or any always-on Linux box.
  201. **Does it work with Sonarr, Radarr, or other *Arr tools?**
  202. Not directly. Tiramisu has its own built-in sync engine that talks to TMDB, Prowlarr, and Torrentio to discover and add titles automatically, so it does not need the *Arr suite to function. There is currently no compatibility layer for those tools specifically.
  203. **Is this legal?**
  204. Tiramisu is a general-purpose BitTorrent engine and streaming filesystem. It does not host, index, or distribute any copyrighted content itself; what you do with it is your responsibility, same as with any BitTorrent client.
  205. **Can I put Tiramisu on the internet?**
  206. Not directly. Turn on sign-in (Control Panel → Access) and put a reverse proxy with HTTPS in front of `:9080`. Never publish `:8090`: it listens on the host only by default, and it has no authentication.
  207. **Is my data private?**
  208. Everything runs on your own hardware. No account, no third-party API key is required for the core engine to work (TMDB, Prowlarr, and Plex/Jellyfin integrations are optional and use your own credentials).
  209. ---
  210. ## Contributing and Security
  211. Contributions are welcome: read [CONTRIBUTING.md](CONTRIBUTING.md) before opening a pull request. To report a vulnerability, follow [SECURITY.md](SECURITY.md) instead of opening a public issue.
  212. ---
  213. ## Support
  214. Tiramisu is free and open source. If it is useful to you, you can support its development through GitHub Sponsors.
  215. [![Sponsor on GitHub](https://img.shields.io/badge/Sponsor-GitHub-121518?logo=githubsponsors)](https://github.com/sponsors/MrRobotoGit)
  216. ---
  217. ## Acknowledgements
  218. Tiramisu builds on [TorrServer](https://github.com/YouROK/TorrServer) and [anacrolix/torrent](https://github.com/anacrolix/torrent); both are embedded as patched forks.
  219. The optional peer country and network view uses the DB-IP Lite databases: [IP geolocation by DB-IP](https://db-ip.com), licensed under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/).
  220. ---
  221. ## License
  222. GNU General Public License v3.0. See [LICENSE.md](LICENSE.md).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.