ReleaseGuard
Native Salesforce app · Coming to AppExchange

Know what the next Salesforce release will break — before it does.

ReleaseGuard checks your org against a curated catalog of documented Salesforce retirements, deprecations and enforcements, and turns each one into findings with evidence, the enforcement date and the steps to fix it.

Request early access See pricing
ReleaseGuard dashboard showing the next Salesforce release, open findings by severity and when each change takes effect
Readiness at a glanceOpen findings by severity, and when each platform change takes effect.
Findings table with severity, rule, component, release and date, above the outcome of every rule in the last scan
Every rule reports an outcomeFindings, passes and "no evidence" — never a false pass.
Finding detail for the SOAP API login() retirement with severity, evidence and numbered steps to fix it
Evidence and the steps to fix itWhat changed, why it matters, and a link to the Salesforce documentation.
Salesforce notification announcing that new ReleaseGuard rules are available
New rules with every updateAdmins are notified when a package update brings new checks.

Built for the changes that actually stop things working

Every rule is backed by a documented Salesforce platform change with a source link. No generic code-quality scores, no health-check noise — only what has a date attached.

Authentication retirements

Integrations still logging in with flows Salesforce is switching off, such as the OAuth username-password flow and SOAP API login(), grouped by app and user.

API version retirements

Traffic on API versions that are being retired, and components that have fallen far behind the current release.

Hardcoded instance URLs

Instanced hostnames in Apex, Visualforce, Named Credentials, CSP Trusted Sites and Remote Site Settings that stop resolving when Salesforce enforces My Domain URLs.

Retired automation

Active Process Builder processes and Workflow Rules that keep running without support or bug fixes, ready for migration to Flow.

How it works

  1. Install from AppExchange

    A managed package installed into your org. Assign the ReleaseGuard permission set to the people who run scans.

  2. Run a scan

    The scan runs in the background inside your org and reads only configuration and usage data the rules need.

  3. Work the findings

    Each finding names the component, shows the evidence and the enforcement date, and links to the official Salesforce documentation.

  4. Re-scan every release

    New rules arrive with package updates. Fixed issues close automatically when the rule checked them successfully.

Honest results

A tool that says "passed" when it could not look is worse than no tool. Every rule ends in one of five clear outcomes:

  • Has findings
  • Passed
  • No evidence in the period
  • Not evaluated — with the reason
  • Error

Rules based on activity, such as login history, report "no evidence in the last N days" rather than "passed", because a quiet month is not proof.

Your data stays in your org

  • Runs entirely inside your Salesforce org — no external servers, no data sent to us.
  • The only callout is to your own org's Tooling API, built from your org's domain at runtime, and it is optional.
  • Least privilege: access through a permission set, checked on the server.
  • No IP addresses and no source code snippets are stored as evidence.
  • Built for AppExchange Security Review.

Read the privacy policy

Who it is for

Admins and architects

One list of what needs attention before each release, with dates, instead of reading hundreds of pages of release notes.

Developers

The exact class, endpoint or process to change, and the documentation for the change.

Consultancies

A repeatable release-readiness check for the client orgs you look after.

30-day full trial — see pricing