Security & data handling

Clear boundaries for a security-sensitive tool.

Dokima runs in your workspace and delegates analysis to the AI runner you configure: Claude, Codex or OpenCode. Review state and local reports stay on your computer. Findings and status are uploaded for visibility to the rest of your team only if you explicitly approve private team publishing. With hosted models, source and prompts are processed by the configured provider. OpenCode also supports privately hosted local models; where data goes depends on your endpoint and configuration. Here is what your team controls.

Dokima controls

Local orchestration and state.

  • Workspace configuration under .dokima/
  • Scheduler state, run history and coverage records
  • Accepted findings and finding annotations
  • Generated static HTML reports
  • Read-only state protection during runner execution

Your runner controls

How AI analysis is processed.

  • Where source and prompts are processed
  • Provider retention and training terms
  • Account, organisation and model configuration
  • Usage limits, billing and regional availability
  • Any provider-specific security commitments

Runner permissions

Analysis is configured for read-only source access.

Shipped runner profiles use read-only or sandboxed modes where the runner supports them. Dokima snapshots its state, makes it read-only during a run and rejects work if a runner attempts to change canonical state directly.

A customer can override runner configuration for its own environment. Any such override should be reviewed against the customer’s security requirements.

Private team publishing

Team uploads require your explicit approval.

Dokima does not upload findings or review status to your team until you explicitly confirm private team publishing and approve the installation in your team account. Once enabled, publishing keeps your team’s private reports up to date; you do not need to approve each individual finding.

Choose local HTML reports only to keep findings on your computer. You can change your publishing choice in Settings, and local HTML reports remain available with either choice. See team reportsfor setup and sharing details.

Give agents read-only access to findings.

Organisation owners and admins can create named, expiring API keys for agents that need to review hosted findings. Each key can read reports from the selected organisation, including evidence and source excerpts. It cannot upload or change reports, manage members or access billing. Only a hash of the secret is stored, and admins can revoke access at any time. Read the agent API guide.

Practical controls

01

Supported systems

Dokima release binaries are provided for Linux and macOS.

02

Updates

dokima update retrieves the latest private release and refreshes shipped prompts.

03

Backups

State snapshots are created before mutating runs and after successful progress.

04

Removal

Remove the binary, .dokima/ state and generated report when you no longer need them.

Policies and termsKnow the rules before you activate.

Review the Privacy Notice,Subscription and Software Licence Terms,Trial Terms andAcceptable Use Policy for data handling, permitted use and licence obligations.

See what Dokima finds

Review the setup with your own security requirements in mind.

Start a full-product 21-day trial for your engineering team. No payment card required.