Skip to main content

General

Turen fully supports Claude Code on macOS, Linux, and Windows. OpenAI Codex is supported in preview: telemetry, session replay, package security, skill delivery, and plan-limit reporting work the same way, and command, injection, and secret detections now appear in the dashboard for Codex. Local rule enforcement is available but does not yet cover every Codex tool path, so treat it as an added layer of defense rather than a complete boundary. Support for Cursor and GitHub Copilot is coming soon.
Turen supports macOS (Apple Silicon and Intel), Linux (x86_64 and arm64, on systemd-based distributions like Ubuntu/Debian and RHEL/CentOS/Fedora), and Windows 11 (amd64 and arm64). See the macOS, Linux, and Windows installation guides.
No. Turen doesn’t sit in the path of your LLM requests: Claude Code connects directly to Anthropic, so there’s no added network latency. Security checks run as Claude Code hooks and complete in milliseconds. Developers won’t notice any difference.
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.
Yes. Turen doesn’t replace or intercept your Anthropic API key. Claude Code connects directly to Anthropic using your existing key and account, exactly as before.

Security

Turen reads Claude Code’s local session transcripts, which include prompts, responses, and tool calls. This data is used to record sessions and derive usage telemetry; secrets are redacted before anything is uploaded. Session recordings (which include conversation content) are encrypted with your organization’s unique key before storage. Turen staff cannot access your session content.
All data is stored in AWS us-east-1 (Northern Virginia). Session data is encrypted at rest with AES-256-GCM. See Data Encryption for details.
No. All data is isolated by organization. There is no mechanism for cross-organization access. See Security Architecture.
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.

Installation

Yes. The Turen agent installs a LaunchDaemon on macOS, a systemd service on Linux, or a Windows Service on Windows 11, all of which require admin privileges. This ensures the agent runs reliably as a background service.
Yes, if you use the desktop app. Install the agent (on Linux the one-line installer includes the Turen desktop app), then launch the desktop app as your normal user and sign in or create an account. The app registers the machine over local IPC, so no registration key or environment editing is needed. This is the recommended first-run flow.Registration keys are still the path for headless, fleet, or CI installs where no one signs in on the machine. In that case, generate a key in the dashboard and set TUREN_REGISTRATION_KEY before starting the agent. Either way, once the machine is registered the key is no longer needed.
Yes. If your account has an authenticator app (TOTP) enrolled, the desktop app prompts for the 6-digit code during sign-in. Both email/password and Google sign-in support it. You enroll and manage your MFA factors in the dashboard under User Settings, not in the desktop app.
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.
Install Turen on the new machine and register it. On a desktop machine, just launch the Turen desktop app and sign in (no key needed). On a headless machine, generate a registration key in the dashboard and supply it at install time. Optionally, revoke the old machine’s agent from the dashboard.

Dashboard

Only members of your organization who have been invited by an admin. Access is controlled through email-verified accounts with role-based permissions.
Yes. You can use the API to programmatically access events, sessions, and analytics data.
Session data is retained for 90 days. Contact us if you need custom retention policies.

Billing

Pricing can be found here https://turen.io/#pricing
Turen offers a 14-day free trial.