> ## Documentation Index
> Fetch the complete documentation index at: https://docs.turen.io/llms.txt
> Use this file to discover all available pages before exploring further.

# FAQ

> Frequently asked questions about Turen

## General

<AccordionGroup>
  <Accordion title="What AI agents does Turen support?">
    Turen currently supports **Claude Code**. Support for Codex and other AI coding agents is coming soon.
  </Accordion>

  <Accordion title="What platforms does Turen run on?">
    Turen supports **macOS** (Apple Silicon and Intel) and **Linux** (x86\_64 and arm64, on systemd-based distributions like Ubuntu/Debian and RHEL/CentOS/Fedora). Windows support is coming soon.
  </Accordion>

  <Accordion title="Does Turen slow down Claude Code?">
    No. The local proxy adds less than 5ms of latency per request. Rule evaluation takes under 1ms. Developers won't notice any difference.
  </Accordion>

  <Accordion title="Does Turen work offline?">
    Partially. Once policies are synced, security rules are enforced locally even without network access. However, session uploads, telemetry, and check-ins require connectivity to the Turen cloud.
  </Accordion>

  <Accordion title="Can I use Turen with my own LLM API key?">
    Yes. Turen doesn't replace your Anthropic API key. It proxies requests transparently: your existing API key and account are used as normal.
  </Accordion>
</AccordionGroup>

## Security

<AccordionGroup>
  <Accordion title="Can Turen read my code?">
    The Turen proxy sees the LLM API traffic passing through it, which includes prompts and responses. This data is used for rule evaluation and telemetry. Session recordings (which include conversation content) are encrypted with your organization's unique key before storage. Turen staff cannot access your session content.
  </Accordion>

  <Accordion title="Where is my data stored?">
    All data is stored in AWS us-east-1 (Northern Virginia). Session data is encrypted at rest with AES-256-GCM. See [Data Encryption](/security/data-encryption) for details.
  </Accordion>

  <Accordion title="Can other organizations see my data?">
    No. All data is isolated by organization. There is no mechanism for cross-organization access. See [Security Architecture](/security/architecture).
  </Accordion>

  <Accordion title="What happens if the Turen agent is compromised?">
    Agent secrets are encrypted with machine-bound keys and cannot be extracted to another machine. Each agent has minimal permissions: it can only check in, upload sessions, and sync policies for its own organization. It cannot access other agents' data or modify policies.
  </Accordion>
</AccordionGroup>

## Installation

<AccordionGroup>
  <Accordion title="Do I need admin (root) access to install?">
    Yes. The Turen agent installs a LaunchDaemon on macOS or a systemd service on Linux, both of which require admin privileges. This ensures the agent runs reliably as a background service.
  </Accordion>

  <Accordion title="Can I install Turen without a registration key?">
    No. A registration key is required for first-time setup. It links the machine to your organization. After registration, the key is no longer needed.
  </Accordion>

  <Accordion title="What happens if I clone a VM with Turen installed?">
    Turen detects VM cloning through machine fingerprinting. The cloned instance will be flagged as a potential clone in the dashboard, and your admin can take appropriate action.
  </Accordion>

  <Accordion title="How do I move Turen to a new machine?">
    Generate a new registration key in the dashboard and install Turen on the new machine. Optionally, revoke the old machine's agent from the dashboard.
  </Accordion>
</AccordionGroup>

## Dashboard

<AccordionGroup>
  <Accordion title="Who can access the dashboard?">
    Only members of your organization who have been invited by an admin. Access is controlled through email-verified accounts with role-based permissions.
  </Accordion>

  <Accordion title="Can I export data from the dashboard?">
    Yes. You can use the [API](/api-reference/overview) to programmatically access events, sessions, and analytics data.
  </Accordion>

  <Accordion title="How long are sessions retained?">
    Session data is retained for 7 days on Solo and 30 days on Teams. Contact us if you need custom retention policies.
  </Accordion>
</AccordionGroup>

## Billing

<AccordionGroup>
  <Accordion title="How is Turen priced?">
    Pricing can be found here [https://turen.io/#pricing](https://turen.io/#pricing)
  </Accordion>

  <Accordion title="Is there a free tier?">
    Turen offers a 14-day free trial.
  </Accordion>
</AccordionGroup>