Governance as production enablement
The goal is not to block agent projects. The goal is to make them understandable enough to run, review, and improve.See the work boundary
Define what an agent can receive, what it can return, which tools it can use, and which outputs require project-specific review.
Review provider choices
Understand which model providers may be used, which policy inputs affect routing, and what data movement follows from that selection.
Define review paths
Identify which results should stop, retry, use a safer route, or move into project controls before the workflow expands beyond a pilot.
Where Duale runs and what stays customer-owned
For the managed service, application data is hosted by Hetzner in Germany, and Duale AI is a French company. Customers choose and contract with model providers; customer-managed deployment remains a design-partner roadmap topic.Shared operating signals for all teams
Engineering, security, audit, and business teams should not maintain separate narratives about the same agent task.Available task context
Use task submissions, retries, failures, terminal results, and review handoff context where captured by the integration.
Policy decisions
Review the policy inputs that shaped routing, provider selection, review paths, and operating context.
Incident readiness
Give the teams responsible for risk and reliability enough context to understand degraded providers, failed executions, and recovery paths.
Regulated work without certification overclaim
The platform is designed to expose available review inputs for security and governance reviews, but this page does not claim current product certification.European Union AI Act readiness
Use available review inputs to discuss risk management, logging, transparency, and human oversight expectations where those rules apply.
Data protection review
Use documented processors, hosting, retention, and deletion paths as the starting point for privacy and data-processing reviews.
Operational resilience
Make dependency, provider, recovery, and exit questions visible before a critical workflow becomes hard to replace.
A better relationship with delivery teams
Security and audit teams are rarely the primary buyer. They become more effective when the product already exposes the answers they need.For platform teams
Build once with the review inputs, routing, and governance context that reviewers will ask for later.
For security teams
Review the product boundary early, then monitor the available runtime signals engineering uses in production.