Skip to main content

General

Turen currently supports Claude Code. Support for Codex and other AI coding agents is coming soon.
Turen currently supports macOS (Apple Silicon and Intel). Linux and Windows support is coming soon.
No. The local proxy adds less than 5ms of latency per request. Rule evaluation takes under 1ms. 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 your Anthropic API key. It proxies requests transparently — your existing API key and account are used as normal.

Security

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.
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 which requires admin privileges. This ensures the agent runs reliably as a background service.
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.
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.
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.

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 the lifetime of your organization. Contact us if you need custom retention policies.

Billing

Contact us at sales@turen.dev for pricing information.
Contact us at sales@turen.dev to discuss trial and evaluation options.