Your data on your computer
Deli runs locally, but not in a vacuum: it talks to Jira and Git, and the work is done by Claude — an external service. Here is exactly what goes where.
Your computer
Deli, listening only on 127.0.0.1
- application and browser interface
- PostgreSQL database with encrypted tokens
- repository mirrors and task worktrees
- build and tests
Jira and Git
Your Jira, GitLab or GitHub
- Deli fetches tasks (read-only)
- repository fetch
- branch push, MR/PR, review comment, merge
Claude
Anthropic service
- task and comment content
- documentation and guideline excerpts
- code, diffs and build logs
- your answers and the KT conversation
The task and code content Claude needs leaves your computer. It is governed by the terms of your Claude account. If your code or tasks must not be sent to an external AI service (e.g. due to client agreements or trade secrets), Deli is not the right tool for that project — that assessment is your responsibility.
Local deployment
Backend, database and interface run on your workstation. The app port is published only on 127.0.0.1, so it is not reachable from the network.
Local login, no Deli cloud
Users and passwords live in your local database (passwords as BCrypt hashes). The app does not connect to any Deli server and sends no telemetry.
Token storage
Jira and Git provider tokens are stored encrypted in the local database. They never appear in logs or API responses. Give them the minimum scope needed.
Repository access
- Git connects only to allow-listed hosts.
- Analysis steps have no write tools and read code and docs from read-only copies.
- Implementation runs in an isolated worktree, without network access or push. Deli pushes only in the MR/PR step.
Claude integration
- Deli runs the Claude Code CLI as a subprocess, on your account. It stores no API key.
- Issue, file and diff content is passed to the model as data, with an instruction not to execute commands contained in it.
- The kill switch and budget pause stop every step that calls the model.
Permissions and approvals
- Jira read-only: no status changes or comments.
- By default the solution waits for approval; blocking questions wait for an answer.
- Merge requires your decision and a passed knowledge transfer.
- Autonomy policy in settings: an “action → policy” table.
- Every flow event goes to the Activity log.
What we do not promise
Deli is a PoC provided “as is”. The following do not exist and we do not claim they do. See also the Licence.
- security certifications or external audits
- a mode that sends no data to the AI model
- SSO, team roles and central access management
- any guarantee that code is correct — that is why there is review and your decision