Your Salesforce org
isn’t telling you everything.

Not by default: no outbound flow is active at delivery. All computation and storage live inside your org. Four families of flow can then be opened, one by one, by your administrator: health aggregates to the external viewer — no personal data, hosted in the European Union — alert channels to Slack, Teams, PagerDuty or webhook, ITSM integration to ServiceNow or Jira, and SIEM export to Splunk or Microsoft Sentinel. Each one goes to a destination you choose, and each is revocable at any time.

The interface is in English: over 4,000 packaged labels are declared en_US. Finding messages are now stored in English and recomposed at display time from a 697-phrase language pack (version 2026.09.1): 109 classes set a message key rather than a sentence, and rendering picks the user’s language. Two reservations, and we would rather write them down: the pack currently carries French only, and a sentence translates all or nothing — if one fragment is missing, the stored English sentence comes out, never a blank and never a mix. If you need another language, say so when you request the trial.

Uninstalling a managed package destroys its objects and all their data: findings, handling history, metrics, signed attestations. Salesforce keeps neither a recycle bin nor a restore. Before uninstalling, export what you want to keep from the console — findings and attestations as CSV, configuration as JSON — and rehearse once on a sandbox to measure what you actually get back. Nothing is retained on our side: by default, no data ever left your org.

The installed package keeps running inside your org: it depends on no external service to scan, alert and export. Only the optional hosted viewer would go dark — and it only holds aggregates your org already owns. The licence stops being renewed, not being executed. A source code escrow is not in place today; if your procurement policy requires one, say so — it is a clause we know how to write.

Ten minutes to install. The recurring scan schedules itself the first time you open the console, and the first findings arrive within the hour that follows: on an org that has never been audited, there are always some.

Yes. The collectors are designed for Salesforce limits (bulkified mode, circuit breakers, quotas) and bounded by construction: COUNT and GROUP BY aggregates rather than row-by-row reads, explicit row ceilings per collector, and a collector that hits its ceiling says so in its finding instead of going quiet. We have not yet published a measurement on an org of several million records: if that is yours, say so when you ask for the trial. Pricing follows size: each tier has its own single price, detailed in the pricing table above.

No — OrgGuardian is a complement, not a replacement. It goes far beyond Health Check, which is point-in-time, technical, and carries no financial exposure — its only native alert is a weekly notification when the score drops. Against Security Center, it brings what that product does not cover: DORA/NIS2 compliance article by article, monitoring of integrations and limits, risk quantified in euros, and the external viewer. The two complement each other; we publish no price comparison, as Salesforce does not make its own public.

You choose a plan, or you fall back to Discovery (free, 7-day retention). Export your posture BEFORE falling back to Discovery: beyond 7 days the history is purged, and that purge is permanent — taking a paid plan again does not restore it. The export stays available at any time while you are on a plan.

No, and be wary of anyone who promises it. OrgGuardian measures the technical posture of your org and produces the evidence. Compliance remains a company-wide effort, with your DPO and your counsel. The trickiest NIS2 points of interpretation were, moreover, settled by a compliance expert’s verdict, displayed in the product itself.