Repository navigation
Installation
Outpace ships as prebuilt binaries, as a multi-architecture container image, and as source you
can build yourself. All three run the same program: outpace serve starts the daemon.
-
Releases (
vX.Y.Ztags) are the stable choice. The latest is v0.9.0. -
edgefollowsmainand includes features newer than the latest release. It islinux/amd64only and changes with every merge. Don't use it where you need predictable upgrades.
See Releases and Versions for which features are in which build.
Every release publishes archives named outpace-<version>-<target>.<ext> and one SHA256SUMS
file on the releases page.
| Platform | Target | Archive |
|---|---|---|
| Linux x86_64 | x86_64-unknown-linux-musl |
.tar.gz |
| Linux ARM64 (aarch64) | aarch64-unknown-linux-musl |
.tar.gz |
| Linux ARMv7 hard-float (Raspberry Pi 2/3 class) | armv7-unknown-linux-musleabihf |
.tar.gz |
| Linux ARMv6 hard-float (Raspberry Pi Zero/1 class), from the next release | arm-unknown-linux-musleabihf |
.tar.gz |
| Linux RISC-V 64, from the next release | riscv64gc-unknown-linux-musl |
.tar.gz |
| FreeBSD 14 and 15 x86_64, from the next release | x86_64-unknown-freebsd |
.tar.gz |
| macOS Intel | x86_64-apple-darwin |
.tar.gz |
| macOS Apple silicon | aarch64-apple-darwin |
.tar.gz |
| Windows x86_64 | x86_64-pc-windows-msvc |
.zip |
| Windows ARM64 | aarch64-pc-windows-msvc |
.zip |
The Linux binaries are statically linked (musl) and run on any reasonably recent distribution.
Download, verify and install on Linux or macOS. Set target to the row for your platform from
the table above:
version=0.9.0
target=x86_64-unknown-linux-musl # e.g. aarch64-apple-darwin on Apple silicon
artifact="outpace-${version}-${target}.tar.gz"
base="https://github.com/jamezrin/outpace-stream/releases/download/v${version}"
curl -LO "${base}/${artifact}"
curl -LO "${base}/SHA256SUMS"
awk -v a="$artifact" '$2 == a { print }' SHA256SUMS | grep -q . \
&& awk -v a="$artifact" '$2 == a { print }' SHA256SUMS | shasum -a 256 --check \
&& tar -xzf "$artifact" \
&& sudo install -m 0755 "outpace-${version}-${target}/outpace" /usr/local/bin/outpace \
&& outpace --versionOn Windows, unzip the archive and run outpace.exe serve from a terminal.
From the next release there is a FreeBSD x86_64 binary. It uses the same archive layout, so
the commands above work with target=x86_64-unknown-freebsd and version set to a release
that includes it (v0.9.0 does not). Use sha256 -c or
shasum -a 256 --check to verify. The binary is built against FreeBSD 14 and is tested on 14
and 15. That also covers pfSense and OPNsense, but install it with care on a firewall: keep the
API on 127.0.0.1 and open only the peer port. To run it as a service, see
Deployment.
There are no NetBSD or OpenBSD builds. On those systems, build from source on the machine itself.
SHA256SUMS proves an archive wasn't corrupted, but it comes from the same release page as the
archive. Releases newer than v0.9.0 also carry signed
build provenance,
which proves that this repository's release workflow built the archive from the tagged commit.
With the GitHub CLI:
gh attestation verify "$artifact" --repo jamezrin/outpace-streamThe same works for release images, including the -minimal ones, by tag or digest:
gh attestation verify oci://ghcr.io/jamezrin/outpace:<version> --repo jamezrin/outpace-streamedge images and v0.9.0 and older releases have no attestations.
ARMv7 builds cover hard-float ARMv7 Linux (Raspberry Pi 2/3, older NAS boxes). From the next release, ARMv6 builds cover hard-float ARMv6 (Raspberry Pi Zero and 1, older ARM routers and NAS boxes), and RISC-V 64 builds cover 64-bit RISC-V boards. Soft-float ARM is not supported. The container image doesn't cover ARMv6 or RISC-V 64 yet: use the binaries. Expect lower throughput and fewer simultaneous streams on 32-bit ARM than on 64-bit hardware. On 32-bit targets each in-memory pool, such as the piece cache or the timeshift budget, is capped at about 512 MiB. A conservative start for a small device:
OUTPACE_CACHE_TYPE=disk \
OUTPACE_SEED_STORE_BYTES=67108864 \
OUTPACE_SESSION_BUFFER=64 \
outpace serveOutpace doesn't bundle the precompiled Android libraries that break some other engines on 16 KiB-page kernels, but 16 KiB-page support has not been verified on real hardware. If you run one (for example some Asahi Linux or Raspberry Pi 5 kernels), please report whether it works.
The image is ghcr.io/jamezrin/outpace.
| Tag | What it is | Architectures |
|---|---|---|
0.9.0 (any X.Y.Z) |
A release. Pin this in production. |
linux/amd64, linux/arm64, linux/arm/v7
|
latest |
The most recent release. | same as releases |
X.Y.Z-minimal, minimal
|
The same release in a minimal scratch image, from the next release. |
linux/amd64, linux/arm64, linux/arm/v7
|
edge |
The current main branch. |
linux/amd64 only |
sha-<commit> |
One specific main commit. |
linux/amd64 only |
What the image sets up:
- It runs as an unprivileged
outpaceuser. - Data lives in the
/var/lib/outpacevolume. - The default command is
outpace serve. - It sets
OUTPACE_BIND=0.0.0.0:6878,OUTPACE_RTMP_BIND=0.0.0.0:1935andOUTPACE_DATA_DIR=/var/lib/outpace, so the listeners are reachable through published ports. - It exposes
6878/tcp(HTTP),1935/tcp(RTMP ingest) and8621/tcp(peers).
docker run -d --name outpace --restart unless-stopped \
-p 127.0.0.1:6878:6878 \
-p 127.0.0.1:1935:1935 \
-p 8621:8621/tcp \
-v outpace-data:/var/lib/outpace \
ghcr.io/jamezrin/outpace:0.9.0Publish HTTP and RTMP on 127.0.0.1 unless a firewall or authenticating proxy protects them.
Only the peer port is meant to face the internet. Outpace has no UDP listener, so there is
nothing to publish for UDP.
The image doesn't include FFmpeg; see FFmpeg below.
From the next release, every release image also comes as X.Y.Z-minimal (and minimal for the
newest). It is built FROM scratch: the same static binary, its licence, and a data directory,
with no shell, package manager or curl. It is about a fifth of the size of the Debian image.
- It runs as user and group
10001, so a bind-mounted data directory must be writable by that ID. - Its built-in health check runs
outpace healthcheck, because there is nocurl. In Compose, override the health check (see Deployment). - You can't extend it with
apt. To add FFmpeg, start from the Debian image. - Everything else matches the Debian image: environment, ports, volume and default command.
The repository's
compose.yml and
.env.example give you a
production layout with a health check, log rotation and safe port bindings:
curl -LO https://raw.githubusercontent.com/jamezrin/outpace-stream/main/compose.yml
curl -L -o .env https://raw.githubusercontent.com/jamezrin/outpace-stream/main/.env.example
# edit OUTPACE_IMAGE in .env to the release you want, e.g. ghcr.io/jamezrin/outpace:0.9.0
docker compose up -d --waitCompose forwards only some settings into the container. Deployment explains which ones, and how to pass the rest.
You need git, a C toolchain (build-essential on Debian/Ubuntu, Xcode command-line tools on
macOS) and rustup. The repository pins its Rust version in
rust-toolchain.toml, and rustup installs it automatically.
git clone https://github.com/jamezrin/outpace-stream.git outpace
cd outpace
git checkout v0.9.0 # or stay on main for the newest features
cargo build --release --locked -p ace-engine --bin outpace
./target/release/outpace --versionThe binary is target/release/outpace.
Release binaries use a slower, smaller dist profile (link-time optimisation, one codegen unit,
symbols stripped). It roughly halves the binary, which helps on routers and boards with little
flash. To build the same way, from source newer than v0.9.0:
cargo build --profile dist --locked -p ace-engine --bin outpace
./target/dist/outpace --versionTo build the container image yourself:
docker build -t outpace:local .SRT ingest is an optional compile-time feature. It isn't in the
release binaries or any published image. It needs native Linux (cross-compiling isn't supported),
pkg-config, and an encryption-enabled system libsrt 1.5.7 or newer with development
headers:
cargo build --release --locked -p ace-engine --bin outpace --features srtSRT is newer than v0.9.0, so build from main.
Outpace doesn't need FFmpeg to play, package HLS or broadcast. It only runs FFmpeg when you turn
on audio normalisation with OUTPACE_HLS_AUDIO_NORMALIZE (all versions) or
OUTPACE_LIVE_AUDIO_NORMALIZE (unreleased: edge and builds from main only); see
HLS Output. With both off, it never looks for FFmpeg.
If you turn normalisation on:
- Install an FFmpeg with MPEG-TS mux/demux, the native AAC encoder, MP2/MP3/AC3 decoders and pipe support. Distribution packages normally include all of these.
- Outpace checks the FFmpeg at startup and runs a short test conversion before it opens any listener. Startup fails if the check fails.
- Point
OUTPACE_FFMPEG_PATHat the executable if it isn't onPATH. It must be FFmpeg itself, not a wrapper script that starts other processes. - The published image doesn't contain FFmpeg. Build a derived image, for example:
FROM ghcr.io/jamezrin/outpace:0.9.0
USER root
RUN apt-get update && apt-get install -y --no-install-recommends ffmpeg \
&& rm -rf /var/lib/apt/lists/*
USER outpaceOUTPACE_DATA_DIR holds:
| Path | Contents | Back it up? |
|---|---|---|
identity.seed |
This node's stable peer identity. | Yes |
broadcasts/ |
Signing keys and piece reservations of your broadcasts. These files are private keys. | Yes, and protect them |
cache/ |
The disk piece cache, when enabled. Wiped on start. | No |
The default is the platform data directory plus outpace: ~/.local/share/outpace on Linux and the BSDs,
~/Library/Application Support/outpace on macOS, and %APPDATA%\outpace on Windows. In the
container it is /var/lib/outpace. Run only one daemon per data directory.
- Getting Started: play something.
- Deployment: systemd, Compose and reverse proxies.
- Configuration: every setting.
This wiki is generated from docs/wiki/ in the main repository. To fix or improve a page, open a pull request there; the wiki is republished automatically when it merges, and edits made in the wiki web UI are overwritten.
Start
Watching
Publishing and peers
- Broadcasting
- Seeding and Peers
- Engine Camouflage
- NAT and Port Mapping
- Private Peer Mode
- Outbound Proxy
Running it
- Deployment
- Routers and Small Devices
- Migrating from AceStream Engine
- Support Sources and Operations
- Troubleshooting
- Releases and Versions
Success stories