Self-hosted reviews
Run the Gittensory review service on your own infrastructure, with your own data store, GitHub App, AI provider, enrichment service, observability, and private repo policy.
What this section covers
Self-hosting is a major product path, not a single install command. The service can run as a quiet advisory reviewer, a private maintainer copilot, or a full review operator. The docs are split by operating concern so you can onboard gradually.
- Core service
- The same review engine as the hosted Worker, served from a Node container with self-host adapters for data, queue, cron, metrics, and webhooks.
- Private policy
- A mounted GITTENSORY_REPO_CONFIG_DIR lets maintainers keep review thresholds, autonomy, and notes out of public repos.
- Optional intelligence
- AI, RAG, and REES are additive. Each has its own enablement switch, prerequisites, and fail-safe behavior.
- Operator control
- Dry-run, advisory, and live modes let you phase in behavior without exposing contributors to unfinished automation.
Recommended reading order
- Start with Quickstart to get a local instance healthy.
- Read Configuration before enabling repo review features.
- Set up GitHub App and Orb so webhooks and installation tokens are correct.
- Add AI providers, REES enrichment, the REES analyzer reference, and RAG indexing only after the deterministic path is stable.
- Use Operations, Backup and scaling, and Security before exposing the service to production traffic.
Pages
Bring up the container, smoke-test readiness, and confirm the GitHub webhook path.
Understand env vars, private repo config, feature flags, and safe baseline defaults.
Choose a direct GitHub App or brokered Orb enrollment and set the right permissions.
Wire Anthropic, OpenAI-compatible, Ollama, Claude Code, or Codex safely.
Run external analyzers, configure REES_ANALYZERS, and understand where results show up.
Review every analyzer name, input, finding shape, network call, and token requirement.
Configure embeddings, Qdrant, indexing jobs, and cold-index behavior.
Health checks, logs, metrics, dashboards, jobs, queues, and daily operator routines.
SQLite, Litestream, Postgres, Redis, restores, and multi-instance tradeoffs.
Official images, tags, source maps, upgrade cadence, and local custom builds.
Secret handling, private policy, public output boundaries, network exposure, and auth.
Review not firing, REES silent, AI unavailable, RAG empty, queue stuck, and webhook failures.
How self-hosting fits with hosted docs
The hosted maintainer workflow still applies: review modes, gate settings, safety rules, and privacy boundaries are the same concepts. Self-hosting adds infrastructure choices, deployment secrets, private config, and local operating responsibility. Use Tuning your reviews for gate semantics and this section for running the service yourself.