Legal
Subprocessors
The third parties a deployment depends on, read from the running system.
How this list was compiled
What each one is for
| Subprocessor | What it does here |
|---|---|
| Supabase | Authentication, the application database and file storage |
| Anthropic | The model a Session runs on, called through the control plane |
| OpenAI | Text embedding for knowledge search |
| Weaviate | The vector index behind knowledge search |
| Upstash | Cache and rate limiting |
| Sentry | Error reporting from the application and the services |
| Resend | Transactional email, such as an invitation |
| PostHog | Product analytics, loaded only after consent — see the control in the footer |
Connected by you, not by us
These are reached only because a customer connects them, and only within the scope that customer grants: GitHub, Jira, Linear and Slack. Each integration page states what it triggers, what DevByte writes back and what permissions it needs: GitHub, Jira, Linear, Slack.
Hosting
Compute for the control plane, the services and the per-Task pods. The region and the operator are agreed per deployment, which is also why the retention position is per deployment rather than a product tier.
Privacy · DPA · Enterprise