trench

Overview of trench

What it is

Trench is an open-source event tracking system built on Apache Kafka and ClickHouse. It is designed to handle large event volumes and provide real-time analytics. Trench is no-cookie, GDPR, and PECR compliant, giving users full control to access, rectify, or delete their data. It was built to scale up the real-time event tracking pipeline at Frigade. The project is MIT licensed and available as a single production-ready Docker image.

Key features

• Compliant with the Segment API (Track, Group, Identify)
• Deploy quickly with a single production-ready Docker image - Process thousands of events per second on a single node - Query data in real-time - Connect data to other destinations with webhooks - Open-source and MIT Licensed

Use cases

Trench is positioned as open-source analytics infrastructure. The README states it can be used to build product analytics dashboards, LLM RAGs, observability platforms, or any other analytics product. It is also described as no-cookie, GDPR, and PECR compliant, giving users full control to access, rectify, or delete their data. The project originated from scaling the real-time event tracking pipeline at Frigade.

Getting started

Trench Self-Hosted requires Docker and Docker Compose. The README recommends at least 4GB of RAM and 4 CPU cores for production. To start the local development server: sh git clone https://github.com/frigadehq/trench.git cd trench/apps/trench cp .env.example .env docker-compose -f docker-compose.yml -f docker-compose.dev.yml up --build --force-recreate --renew-anon-volumes The server runs at http://localhost:4000. The README also shows how to send a sample event, query events, and execute raw SQL queries via the /events and /queries endpoints.

License and pricing

Trench is open-source and MIT Licensed. Trench Cloud is a fully-managed serverless solution with zero ops, autoscaling, and 99.99% SLAs; pricing is not stated in the README.

Based on the project's public README and repository metadata.