Trust and Security
Last updated: November 2026
For security and procurement review. Dagu runs on your infrastructure; this page lists every connection it can make outward, how to verify what you install, and how Dagu Cloud handles the data it receives.
1. What leaves your network
Dagu has no telemetry. A Dagu server makes only the outbound connections below, and each one follows from a choice an administrator makes. With none of them turned on, Dagu runs fully offline or air-gapped, including with an offline license file.
| Connection | When | What is sent |
|---|---|---|
| License check-in to console.dagu.sh | Hourly, only for servers connected to Dagu Cloud with a license key | License ID, server ID, server name, Dagu version, and a per-server secret |
| Monitoring reports to console.dagu.sh | Off by default; an administrator chooses a level | Health: Dagu version and which services run. Run status adds each run's DAG name, run ID, attempt ID, status, trigger, and timestamps, plus failed step names. Errors adds each failed step's error message. Logs and outputs are never sent. |
| Remote access from Dagu Cloud | Off by default; an administrator chooses the highest role | Calls from members of your Dagu Cloud workspace arrive over a WebSocket the server opens to relay.dagu.sh and reach only its MCP endpoint. Viewer reads DAGs, runs, and logs; Operator also starts, retries, and stops runs; Developer also changes DAG definitions. Approving waiting steps is a separate opt-in. Dagu Cloud passes answers on without storing them. |
| Webhook relay through relay.dagu.sh | Off by default; only while an administrator gives a webhook a public URL | The webhook requests sent to that URL |
| Release check against GitHub | Only when someone runs dagu upgrade | A request for the latest release |
| OpenTelemetry export | Only if you configure a collector | Traces, to your own collector |
2. Release integrity
Every release archive carries a GitHub build provenance attestation and is listed in the release's SHA-256 checksums file. The source is public, so the code you run can be reviewed before deployment. To verify an archive before installing it:
gh attestation verify dagu_<version>_linux_amd64.tar.gz --repo dagucloud/dagu
sha256sum --check --ignore-missing checksums.txt3. Vulnerability handling
Report suspected vulnerabilities privately as the security policy describes, not in a public issue. Security fixes ship for the current development branch and the latest stable release series. The site publishes a security.txt with the contact address.
4. How Dagu Cloud handles data
- Dagu Cloud runs on Google Cloud in the us-central1 region.
- PostgreSQL row-level security keeps each workspace's data separate from every other workspace.
- Data is encrypted in transit and at rest.
- Console sign-in supports two-factor authentication, which each user can turn on in settings.
- Payment card details stay with Stripe; Dagu Cloud does not store them.
- Alert destinations such as Slack, Microsoft Teams, and PagerDuty receive alerts only when you add them.
- Monitoring data is kept for set periods: runs for 30 days, daily totals for 13 months, and resolved alerts for 90 days. A server that stops reporting for 30 days is deleted with what it reported.
- A public webhook request is kept only until the server takes it, at most 7 days. Each URL's token is kept only as a hash.
- For remote access, Dagu Cloud keeps no log of calls and does not store answers. Each server records the calls it receives in its own audit log.
- Dagu Cloud signs each remote call for that request alone. Each server sets the highest role, can turn remote access off at once, and records every call in its own audit log.
- What an MCP client reads through Dagu Cloud also reaches the client's provider, such as Anthropic or OpenAI, under its terms.
- Retention and deletion of account data follow the Privacy Policy.
5. Subprocessors
| Provider | Purpose |
|---|---|
| Google Cloud Platform | Hosting for Dagu Cloud and its database |
| Cloudflare | DNS, network edge, the relay, and hosting for dagu.sh |
| Stripe | Payments and billing records |
| Auth0 | Sign-in and identity |
| Resend | Email delivery, including alert emails |
| PostHog | Website analytics after consent, and limited console account events |
| Google Analytics | Website analytics after consent |
| Calendly | Booking intro calls |
| OpenRouter | Model calls for Kitewell (Kitewell only) |
| Serper | Web search for Kitewell (Kitewell only) |
6. Documents
A data processing agreement is available on request from company@descarty.com.
Company
- Company
- Descarty, Inc. (Descarty株式会社)
- Address
- 1-10-8 Dogenzaka, Shibuya-ku, Tokyo (Shibuya Dogenzaka Tokyu Bldg. 2F-C)
- Representative
- Yota Hamada
- Business
- Development and operation of workflow automation software.
- Corporate number
- 2011001156613
- Invoice registration number
- T2011001156613
- Telecommunications carrier notification
- A-06-21879