Packages / tindra

APT repository · deb.freshdeb.com/tindraprinted 28 Oct 2026, 11:40 UTC

tindra

Tindra, self-hosted error tracking with performance, uptime and cron monitoring. It works with Sentry SDKs and runs as one binary with one PostgreSQL database, serving its web UI itself. One release line for Debian 12 and 13, Ubuntu 22.04, 24.04 and 26.04 on amd64 and arm64.

Tindra is our own product: Blendbyte makes it and maintains freshdeb. It's built, tested and published here like every other package.

Componentmain

follows every upstream release, minors and majors included. Currently 1.2.0.

Release line
Deliver to
tindra 1.2.0-1+freshdeb~deb13

1Trust the signing key (once per machine)

sudo install -d -m 0755 /etc/apt/keyrings
curl -fsSL https://deb.freshdeb.com/freshdeb-archive-keyring.gpg \
  | sudo tee /etc/apt/keyrings/freshdeb-archive-keyring.gpg >/dev/null

Fingerprint 3BBD F03A 9C0B F890 F8CA 9510 7595 CC55 468F 3161. How to verify.

2Add the source

sudo tee /etc/apt/sources.list.d/freshdeb-tindra.sources >/dev/null <<EOF
Types: deb
URIs: https://deb.freshdeb.com/tindra
Suites: $(. /etc/os-release && echo $VERSION_CODENAME)
Components: main
Signed-By: /etc/apt/keyrings/freshdeb-archive-keyring.gpg
EOF

With auto, the shell reads the codename from /etc/os-release on the machine you paste this into.

3Install

sudo apt update && sudo apt install tindra
apt policy tindra   # expect 1.2.0-1+freshdeb~…

Before you install tindra

Neither Debian nor Ubuntu ship tindra. Install postgresql with it (recommended) for a local database, or give debconf a DATABASE_URL. Tindra isn't started until it has a public URL and a database. It serves plain HTTP, so put a TLS reverse proxy in front: /usr/share/doc/tindra/README.Debian has Caddy and nginx examples. Purging removes /etc/tindra and /var/lib/tindra, not the database.

tindra 1.2.0-1+freshdeb~deb13

How it's packaged

No distribution packages tindra, so the packaging is ours, written the way Debian would. The build, the defaults and the layout follow upstream's wherever upstream has them.

Build
Upstream's release build: CGO_ENABLED=0, -trimpath, -s -w, the pinned Go toolchain, vendored modules verified against go.sum, and the version and commit stamps.
Web UI
The built web UI from the release, checked against its sha256 (also in upstream's SHA256SUMS) and embedded in the binary, as in upstream's release binaries.
Setup
debconf asks for the public URL, the port, the reverse proxy, the database and the first account, and sets up a local PostgreSQL database itself. dpkg-reconfigure tindra changes the answers, and preseeded answers work for unattended installs.
Layout
Configuration in /etc/tindra/tindra.env, data (source maps, attachments) in /var/lib/tindra, the tindra user and a systemd unit. systemctl reload tindra applies changed limits without a restart.

Packing list

Every release line of tindra and the distributions it's built for. Each line is its own APT component and only gets the releases it follows (main: every upstream release, minors and majors included). After upstream end of life it stops building but stays installable. Hatched cells have no build: usually that distribution already ships the same or a newer version itself.

LineComponentCurrentbookwormDebian 12trixieDebian 13jammyUbuntu 22.04nobleUbuntu 24.04resoluteUbuntu 26.04Support
main main 1.2.0 built: 1.2.0-1built: 1.2.0-1built: 1.2.0-1built: 1.2.0-1built: 1.2.0-1 –

Versions follow <upstream>-<revision>+freshdeb~<distro>, distro being deb12, deb13, ubuntu22.04, ubuntu24.04 or ubuntu26.04, for amd64 and arm64. Published versions are never rebuilt or replaced.

Contents

tindra
The server and its CLI, with the web UI built in, and shell completions.

Origin

Upstream
github.com/blendbyte/tindraBlendbyte's own project, release tags pinned to commit hashes
Packaging
our own, in Debian's styleno distribution packages tindra
Built for
bookworm, trixie, jammy, noble, resoluteamd64, arm64, built natively
Files
package.yaml · debian/ · report an issuepackage.yaml explains every change

Also in Monitoring

Maintained by Blendbyte

Blendbyte builds cloud infrastructure, web apps, and developer tools. We've been shipping software to production for 20+ years.

These packages run in our own stack, which is why we keep them maintained. Issues and PRs get read. Good ones get merged.

Also from Blendbytenginx-modules.com: pre-built nginx dynamic modules (Brotli, GeoIP2, ModSecurity and more) for nginx.org's nginx, on the same Debian and Ubuntu releases.

Tindra: self-hosted error tracking and monitoring that works with Sentry SDKs. Packaged here, like everything else.