Trust and Security

Last updated: October 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.

ConnectionWhenWhat is sent
License check-in to console.dagu.shHourly, only for servers connected to Dagu Cloud with a license keyLicense ID, server ID, server name, Dagu version, and a per-server secret
Monitoring reports to console.dagu.shOff by default; an administrator chooses a levelHealth: 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 CloudOff by default; an administrator chooses the highest roleCalls 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.
Webhook relay through relay.dagu.shOff by default; only while an administrator gives a webhook a public URLThe webhook requests sent to that URL
Release check against GitHubOnly when someone runs dagu upgradeA request for the latest release
OpenTelemetry exportOnly if you configure a collectorTraces, 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.txt

3. 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.
  • Retention and deletion follow the Privacy Policy.

5. Subprocessors

ProviderPurpose
Google Cloud PlatformHosting for Dagu Cloud and its database
CloudflareDNS, network edge, the relay, and hosting for dagu.sh
StripePayments and billing records
Auth0Sign-in and identity
ResendEmail delivery, including alert emails
PostHogWebsite analytics after consent, and limited console account events
Google AnalyticsWebsite analytics after consent
CalendlyBooking intro calls
OpenRouterModel calls for Kitewell (Kitewell only)
SerperWeb search for Kitewell (Kitewell only)

6. Documents

A data processing agreement is available on request from company@descarty.com.

Unternehmensangaben

Unternehmen
Descarty, Inc. (Descarty株式会社)
Anschrift
1-10-8 Dogenzaka, Shibuya-ku, Tokyo (Shibuya Dogenzaka Tokyu Bldg. 2F-C)
Vertretungsberechtigte Person
Yota Hamada
Geschäftstätigkeit
Entwicklung und Betrieb von Software zur Workflow-Automatisierung.
Unternehmensnummer
2011001156613
Rechnungsregistrierungsnummer
T2011001156613
Meldung als Telekommunikationsanbieter
A-06-21879