Full visibility across every org you own
Full Scan inventories technical debt, security exposure, configuration risk and dormant metadata in every org, then shows you the trend release over release. Our engine runs outside your org, so we do not consume your limits.
Complete inventory
Most Salesforce estates grow faster than anyone documents them. Full Scan gives you the actual contents of every org you own, not the version in the runbook.
Health over time
A single scan tells you where you are. The trend tells you whether your team is winning. Debt created against debt cleared, per release, per team, per org.
Score trend by org. Debt created against debt cleared per release. Findings by severity over time. Which orgs are diverging from the standard.
Release readiness
“Can we go live” should be an evidence question, not a judgment call made at 6pm on a Thursday.
Quality Gates give you a defined pass condition per pipeline stage, using your rules rather than ours. The release either meets the gate or it does not, and the record of why sits in the audit trail. Works with Copado, DevOps Center, Flosum and custom CI.
Dormant and unused
Every Salesforce org accumulates things nobody will admit to owning. Fields no report references, Flows that superseded other Flows nobody deactivated, permission sets granted once for a migration in 2021.
Full Scan identifies unused fields, dormant automation and abandoned customization, so decommissioning is a decision based on evidence rather than nerve.
Key person risk
When the developer who built your quoting logic leaves, the standard stays in the rule library and the history stays in the scan record. The next person inherits a documented estate rather than an archaeology project.
Multi vendor accountability
Most orgs have an internal team, at least one partner, and a managed service provider deploying into them. Findings are attributed by author and by team, so you can see which one is introducing risk before the renewal conversation rather than after it.
Ask the estate
Insights Agent answers the questions a platform owner actually types.
Which orgs have Apex classes with no test coverage on a critical path? What changed in the sales org between the last two releases? Which managed packages are we paying for that nothing references?
Independent engine
Our engine runs outside your org, so governance never competes with your users for capacity or API limits.
Ask the estate a question. In your own words.
Insights Agent answers questions about your orgs in plain language. No report builder, no ticket to the admin team, no waiting for someone to export it. Ask it from your own LLM, from any MCP capable client, or from inside Agentforce.
312 metadata changes across 4 orgs, from 18 developers. Nine introduced high severity issues, most of them in Apex triggers on Opportunity.
84 custom fields have had no read or write in twelve months, and 12 Flows have never been triggered. Ranked by how many dependencies you would have to unpick first.
Three orgs are drifting from the standard faster than they are being cleaned up. The gap is widest in the org your partner team delivers into.
Sample answers shown. Every real answer is grounded in the scans you already run, and every number opens into the findings behind it.
The standard is yours, and so is the record.
Full Scan tells you what is in there. Governance is what stops it coming back. The inventory is the starting point, not the product.
Rule Builder
Your conventions written in plain English, then versioned like code. Naming, architecture, the pattern the team agreed and has quietly stopped following.
Rulesets per project
A project groups related Salesforce orgs under one context. The main org carries the ruleset and the rest inherit it, and developer access is managed once for the group rather than environment by environment. It is how governance stays coherent as the estate grows.
Quality Gates
Set the bar once and it applies in the pull request and in the pipeline. You decide whether a failed gate blocks the promotion or simply reports.
Write-offs and peer review
Exceptions carry a reason and an approver and propagate across orgs, so nobody argues the same finding twice.
Every finding carries a disposition. Every write-off carries a reason and an approver. Every rule change is recorded, with what changed and who approved it.
You now have agents changing your orgs.
Agentforce and the agents your team builds generate metadata and logic continuously, and they do not wait for a review window. Anything that speaks MCP can call Quality Clouds mid-loop, so the agent is handed your rules before it writes rather than a rejection afterwards.
agent proposes → Quality Clouds returns the applicable rules and the violations → agent corrects → change lands
AI Agents, AI Agent Templates, AI Topics and Prompt Templates are scanned configuration in their own right, so the agents your team ships are governed the same way the code is. The question is no longer who wrote it, but whether the standard was enforced when it was written.
Related articles
Stay ahead of the curve in Salesforce
Salesforce
DevOps & CI/CO
AI Code Governance
The Case for Native AI Code Governance in Modern Salesforce DevOps
Javier Luesma
5 min read
Discover why your governance must live inside your DevOps stack—not alongside it
Salesforce
AI Code Governance
Interview with Francis Pindar — AI Code Governance After Headless 360
Mariona Valero
6 min read
Salesforce MVP Francis Pindar explains how to build a governance framework that keeps pace with AI-generated code and configuration
AI Code Governance
Agentic AI
Salesforce
AI Finds Zero-Days Autonomously. Who Is Accountable When AI Ships One into Production?
Albert Franquesa
5 min read
ServiceNow Build Agent will quadruple usage in twelve months. The CISO’s question has shifted from detection to accountability