Give customers safe buttons, not production access.
Let customers and support teams retry syncs, replay webhooks, run backfills, and fix account issues through approved actions. Dagu runs them safely in your environment and keeps a record of what happened.
Customer operations should not live in tickets and shell history.
Turn repeated customer fixes into tenant-scoped actions that Support or approved customer users can run with guardrails, visibility, and evidence.
Run where customer data lives
Keep every action inside the right tenant and security boundary.
Self-host Dagu, use Dagu as the managed action hub, or attach private workers so sensitive tenant-scoped actions run near your services, secrets, and data.
See deployment optionsLocal
Single server
Start with one Dagu server and local file-backed state for scripts, dry runs, and small-team operations.
Self-hosted
Your infrastructure
Keep server, workers, secrets, logs, and execution inside your environment with SSO, RBAC, and audit logging when needed.
Dagu
Managed operations hub
Let Dagu operate a dedicated Dagu server for workflow catalog, team access, approvals, and run visibility.
Hybrid
Managed control, private execution
Use the managed server for coordination while private workers run Docker, private APIs, and data-local steps inside your infrastructure.
Safe execution path
Dagu does not need direct access to production data when sensitive execution stays on private workers.
Start with one customer-facing safe action
The best wedge is the work customers and Support already ask engineers to run: tenant sync retries, webhook replays, customer backfills, billing checks, and account repair.
The hard part is not writing another script. It is deciding which customer can run it, which inputs are allowed, when approval is required, and what evidence remains after it touches production.
What each safe action should capture
Derived tenant context, allowed inputs, reason, and ticket URL
Dry-run estimate and customer-safe artifact before the real change
Manager or engineer approval before high-risk execution
Execution on private workers close to production systems
Post-checks, notifications, and rerunnable action history
A clear record for customers, enterprise reviews, and compliance
Customers request. Humans approve. Dagu executes.
Dagu becomes the execution boundary for SaaS operations: customer admins, Support, agents, and internal tools request bounded tenant-scoped actions instead of receiving open-ended production access.
Request the tenant-scoped action
Start from a customer portal, support form, ticket, API call, webhook, or GitHub event with tenant context, reason, and target inputs captured up front.
Dry-run and approve safely
Constrain inputs, run a dry run, require the right reviewer when risk is high, then execute inside the environment that owns the data.
Return customer-safe evidence
Keep the full audit trail internally while customers see a safe result, evidence ID, status, and approved artifacts.
Built for tenant-scoped customer operations
Dagu fits production actions that touch customer data or tenant state, need guardrails, and are too important to expose as raw scripts or copied commands.
AI-proposed operations
Let agents investigate or draft an operation while Dagu limits execution to approved tenant-scoped actions with human review.
Customer and Support safe buttons
Give customer admins and support teams safe actions for resyncs, account repair, diagnostics, exports, and recovery without shell access.
Failed sync replay
Replay webhooks, integrations, jobs, or queues for one tenant with clear inputs, retries, and post-checks.
Tenant provisioning and repair
Package tenant setup, configuration changes, entitlement fixes, and migration retries as reviewed safe actions.
Customer backfills
Run tenant-scoped backfills, imports, recalculations, and migrations with dry runs, artifacts, and approval.
Billing reconciliation
Validate usage, recalculate invoices, capture diff reports, and keep customer-safe evidence for finance and enterprise reviews.
Open source core. Enterprise control plane.
Dagu OSS remains the local-first workflow engine. Dagu adds the managed team surface for catalog, access, approvals, history, and evidence.
Run execution where your data already lives
Install, self-host, and extend the open-source engine under /oss, then add Dagu when the team needs managed coordination and enterprise controls.
Turn the next customer operation into a safe action.
Start with one operation customers already ask you to run: retry a sync, replay a webhook, run a backfill, or check billing. Dagu helps you make it safe and repeatable.