Self-hosting & Deployment
tripl ships as one image that serves the JSON API and the built React SPA from a single process. The same image is reused for the API, a one-shot database migration, and the Celery worker and beat scheduler — only the launch command differs. The default compose.yaml runs the published release image; there is no source build on the deploy host.
Configuration Reference
tripl is configured entirely through environment variables. The backend reads
Release Process
This page is for maintainers cutting a release. tripl ships as one image
Operations Runbook
Operational procedures for running the self-hosted tripl stack defined in
Operator CLI
tripl is a small command-line client for a tripl instance. Most of it talks to
Security & Hardening
This page is for operators and security reviewers running a self-hosted tripl instance. It documents what the application enforces today, the two secrets you must manage, how to rotate each one (and what breaks when you do), and a pre-production hardening checklist.
AI & search providers
tripl ships with two optional feature groups that reach out to an external,
Running a public demo
A public demo is part of the Enterprise edition: the
Telemetry
Tripl can send one small, anonymous ping a day, so the people who build it