Copado acquired Salesforce governance provider Valo.ai, the buyer announced on November 4. Valo remains available separately; integration is planned, without a rollout date.

The big change

  • Release controls and live-system access visibility address different stages of software operation.
  • Valo describes tools that help administrators investigate applications, users and permissions in Salesforce.
  • The products’ integration remains a roadmap, not a delivered combined workflow.

Why access remains a question after release

Software delivery controls help teams decide what changes enter a live system. Once those changes are running, administrators still need to understand which applications and people have access. Valo describes identifying connected applications, permissions and usage in Salesforce.

Copado’s example is an administrator reviewing an obsolete integration’s permissions before deciding whether to remove access. This is an illustrative review. Removing access without understanding its use could disrupt an application that still has a legitimate role.

Salesforce separately explains that OAuth-enabled connected apps can access a subset of data after permission is granted. Its administrator documentation describes viewing connected-app usage, revoking active sessions and blocking organization-wide access; the available actions depend on user permissions. These Salesforce controls are context for the problem, not evidence that Valo performed any particular remediation.

From a finding to a governed change

Copado plans to connect findings to tested releases with human approval and an audit trail. The company also describes broader AI-agent governance as a future direction.

The distinction matters because spotting a risk and safely changing a production system are separate jobs. A team may need to determine who owns an integration, what relies on it and how to check a proposed change before it is released.

Copado’s earlier Agentia announcement described agents across software planning, building, testing, release and operation, with governance controls. It also described a context hub drawing on environment metadata, dependencies and history. Those are company descriptions of the earlier product, not independent verification of the newly proposed integration.

Valo’s separate setup guide recommends a dedicated Salesforce integration user and describes configuring permissions and a connected app. Its guidance shows that connecting an observability tool itself requires access choices; it does not establish which settings a customer has used or prove that a deployment is secure.

Copado says existing Valo customers will retain service and support. Teams evaluating the acquisition can assess present visibility separately from the proposed connection to release workflows. BIG CHANGE has not tested either product or the planned integration. The announcement offers no independent performance measurements.