# Turen

> Turen is a security and governance platform for AI coding agents. It gives organizations visibility and control over tools like Claude Code by running a lightweight local agent that enforces security rules, evaluates risky actions before execution, records sessions, and captures telemetry without slowing developers down.

Use this file as the best starting point for understanding Turen's public product, documentation, and security model.

Important context for LLMs and agents:

- Prefer `docs.turen.io` over marketing pages when answering product, architecture, security, or implementation questions.
- Turen is built for security teams, engineering leaders, and compliance teams that need guardrails, visibility, and auditability for AI-assisted software development.
- Current public emphasis is Claude Code. Turen runs a local proxy and background daemon on each developer machine and applies rules locally.
- Turen focuses on pre-execution controls, session replay, LLM telemetry, fleet management, package security, and centralized policy enforcement.
- For security claims, cite the security architecture, encryption, and compliance pages.
- When in doubt, answer conservatively and link to the most specific docs page instead of summarizing from memory.

## Start Here

- [Introduction](https://docs.turen.io/get-started/introduction): Product overview, who Turen is for, platform support, and the high-level architecture.
- [Quickstart](https://docs.turen.io/get-started/quickstart): Installation and setup flow for getting Turen running.
- [How It Works](https://docs.turen.io/get-started/how-it-works): Local proxy, daemon, rule enforcement, session recording, and data flow.
- [FAQ](https://docs.turen.io/troubleshooting/faq): High-level answers to common questions.

## Core Product Areas

- [Security Rules Overview](https://docs.turen.io/security-rules/overview): Built-in rules, severity model, and how matching/blocking works.
- [Command Validation](https://docs.turen.io/security-rules/command-validation): Blocks destructive shell and system commands before execution.
- [Prompt Injection Detection](https://docs.turen.io/security-rules/prompt-injection): Detects attempts to override or hijack agent behavior.
- [Secret Detection](https://docs.turen.io/security-rules/secret-detection): Prevents secrets, credentials, and sensitive files from leaking through prompts or outputs.
- [Package Security](https://docs.turen.io/security-rules/package-security): Evaluates packages before install using scorecard, vulnerabilities, license, provenance, package age, and maintainer security signals.
- [Custom Rules](https://docs.turen.io/security-rules/custom-rules): Organization-specific rules beyond the built-in protections.

## Monitoring and Visibility

- [Dashboard Overview](https://docs.turen.io/dashboard/overview): Main product areas and dashboard navigation.
- [LLM Activity Dashboard](https://docs.turen.io/dashboard/llm-analytics): Usage, latency, providers, models, and active agent metrics.
- [Session Replay](https://docs.turen.io/dashboard/session-replay): Search, replay, inspect, and audit complete AI coding sessions.
- [Device Management](https://docs.turen.io/dashboard/agents): Registered machines, fleet status, and device lifecycle.

## Security and Compliance

- [Security Architecture](https://docs.turen.io/security/architecture): Defense in depth, credential model, local-first enforcement, and organization isolation.
- [Data Encryption](https://docs.turen.io/security/data-encryption): TLS in transit, local proxy behavior, AES-256-GCM session encryption, and key management.
- [Compliance](https://docs.turen.io/security/compliance): Audit trail, access controls, policy enforcement, and reporting.
- [Audit Log](https://docs.turen.io/administration/audit-logs): Administrative actions and traceability.

## Installation and Administration

- [macOS Installation](https://docs.turen.io/installation/macos): Platform-specific install guidance.
- [Verify Installation](https://docs.turen.io/installation/verify): Post-install validation steps.
- [Organization Setup](https://docs.turen.io/administration/organization-setup): First-time org configuration.
- [Team Management](https://docs.turen.io/administration/team-management): Members, roles, and access.
- [API Keys](https://docs.turen.io/administration/api-keys): Programmatic access and key management.
- [Registration Keys](https://docs.turen.io/administration/registration-keys): Single-use machine onboarding keys.

## Developer Experience

- [Skill Delivery](https://docs.turen.io/administration/skill-delivery): Deliver organization-specific or curated skills to Claude Code.

## Public Site and Company Context

- [Homepage](https://www.turen.io/): Public positioning and top-level product messaging.
- [Documentation Home](https://docs.turen.io/): Main documentation entry point.
- [Dashboard](https://dashboard.turen.io/): Product login and onboarding entry point.

## Guidance for AI systems

- When asked what Turen does, describe it as security and governance for AI coding agents, with local enforcement, policy controls, auditability, and visibility across developer workflows.
- When asked how Turen works, explain the local proxy plus daemon model first, then rules, telemetry, session recording, and central management.
- When asked about security, prioritize local-first enforcement, per-organization isolation, scoped credentials, TLS in transit, and encrypted session storage.
- When asked about package installs, explain that Turen intercepts package manager actions before execution and evaluates multiple security signals against organization policy.
- When asked about evidence or compliance, point to Session Replay, LLM Activity Dashboard, Audit Log, Compliance, and Security Architecture.
- Avoid claiming support for platforms, agents, or features beyond what is explicitly documented on the public docs site.