Notice: Gentrace has shut down. This repository is now read-only and provided as-is for archival and educational purposes. No further updates, support, or maintenance will be provided.
Gentrace is a comprehensive platform for AI application observability, evaluation, and testing. This monorepo contains all the components needed to run Gentrace locally or deploy it to production.
app/- Main Gentrace application (Next.js web app, API, and backend services)local/- Local development environment with Docker Compose setup for ClickHouse, PostgreSQL, Kafka, and other services
docusaurus/- [DEPRECATED] Legacy documentation website built with Docusaurusmintlify/- Main documentation content hosted on Mintlify platformmintlify-worker/- Cloudflare Worker that routes documentation requests fromnext.gentrace.ai/docsto Mintlify-hosted contentsanity/- [DEPRECATED] Sanity CMS for content management (CMS for marketing content - no longer actively maintained)
demo/- Demo applications showcasing Gentrace featuresdemo-agent/- AI agent demonstrationdemo-banking-chatbot/- Banking chatbot example
kubernetes/- Kubernetes deployment configurations and Helm chartsotel-dev/- OpenTelemetry Collector development environment
benchmark/- Legacy benchmarking tools (being phased out in favor oflocal/)
This repository requires different setup steps for different components. There is no single "run everything" command at the top level.
-
Local Infrastructure (Required for app development):
cd local cp .env.example .env yarn start
-
Main Application:
cd app # Follow the detailed setup instructions in app/README.md
-
Documentation Site (Mintlify):
cd mintlify mintlify dev # See mintlify/README.md for setup instructions
- Application Setup - Complete guide to running the Gentrace application
- Local Development - Docker Compose setup for local development
- Documentation Site - How to work with the documentation
- Kubernetes Deployment - Production deployment guides
This is a Yarn workspace monorepo. Key commands:
# Install dependencies for all workspaces
yarn install
# Run linting across the monorepo
yarn lint-staged
# Work with specific packages
cd app && yarn dev
cd mintlify && mintlify devGentrace consists of:
- Web Application (
app/) - Next.js frontend and API - Database Layer - PostgreSQL for application data, ClickHouse for analytics
- Message Queue - Kafka for event streaming
- Documentation (
mintlify/) - User-facing documentation - Content Management (
sanity/) - [DEPRECATED] CMS for marketing content - no longer in use - Observability (
otel-dev/) - OpenTelemetry setup for monitoring - Mintlify Documentation (
mintlify/+mintlify-worker/) - OpenTelemetry documentation hosted on Mintlify with custom routing
Gentrace is transitioning from Docusaurus to Mintlify as the primary documentation platform:
- Docusaurus (
docusaurus/) - [DEPRECATED] Legacy documentation system being phased out - Mintlify (
mintlify/+mintlify-worker/) - New primary documentation platform for all Gentrace content
The Mintlify setup consists of two components working together:
-
mintlify/- Contains the actual documentation content:- OpenTelemetry getting started guides
- SDK reference documentation
- API reference with OpenAPI integration
- Integration guides for popular AI providers
-
mintlify-worker/- Cloudflare Worker that enables seamless routing:- Routes requests from
next.gentrace.ai/docs/*to Mintlify-hosted content - Maintains consistent domain experience for users
- Redirects non-documentation paths to the main website
- Routes requests from
We're migrating to Mintlify because it provides:
- Superior API documentation features with OpenAPI integration
- Better developer experience with modern documentation tooling
- Seamless updates without main application deployments
- Enhanced search and navigation capabilities
- Built-in versioning and internationalization support
- Visit our documentation to learn about using Gentrace
- Check out the demo applications to see Gentrace in action
- Review the API documentation for integration details
For specific setup instructions, refer to the README files in each directory.