SyncOnAI360

Understand

Understand any Salesforce org down to its source.

Before anyone changes an org, SyncOnAI 360 reads it whole, scores it from evidence, maps what depends on what and records what changed, so every decision starts from the real org.

Understand your org freeBook a demo

Acme Production

Org health · synced 4 minutes ago

82

Health · B

Health

82

Confidence

74

Coverage

91

Apex coverage 78%, from the org's last test run

  • 3 Flows on Case run on the same trigger
  • 11 Apex classes below 75% coverage
  • Managed package source hidden by Salesforce: 2 packages

In one paragraph

SyncOnAI 360 Org Intelligence is the understanding layer of the platform. Each connected Salesforce org is synced into a searchable metadata repository with full source, then scored for health, audited, mapped into a dependency graph, ranked for technical debt, described architecturally and tracked over time, all from evidence.

Metadata types read with their full source
20+Metadata types read with their full source
Automated audit checks on every refresh
55Automated audit checks on every refresh
Automatic refresh, plus on demand
6hAutomatic refresh, plus on demand
CRM records copied; configuration only
0CRM records copied; configuration only

01The problem

Why nobody fully understands their Salesforce org

A Salesforce org is years of decisions by admins, developers, partners and packages, most of them undocumented. Teams change it by memory and by habit, and find out what they missed when something breaks.

  1. 01

    Inherited orgs

    A new admin, a new partner or a merger hands someone an org with hundreds of Flows and classes and no map. The first months go on discovery.

  2. 02

    Knowledge in people's heads

    Why a field exists, which automation depends on it, who built that permission set: the answers leave with the people who knew them.

  3. 03

    Tools that see a slice

    Health scanners, dependency viewers and change logs each show part of the org, in different tools, with no shared picture.

  4. 04

    AI with no context

    Assistants that cannot see the org guess at it, which turns AI from a shortcut into another thing to check.

02repository

What does SyncOnAI 360 keep from a Salesforce org?

Each sync reads objects, fields, record types, layouts and Lightning pages; Apex classes and triggers with full source; every Lightning Web Component file; Flows, validation rules, permission sets and profiles; and email templates, value sets, approval processes, queues, reports, dashboards and sharing rules, along with Apex coverage from the last test run.

The result is a searchable repository of the org that every other part of the platform works from: the AI, the health score, the audit, the dependency graph and the builders. Syncs run in the background with progress by stage, fetch only what changed after the first, refresh every six hours and read deployed components back straight after a deploy. Records stay in Salesforce.

  • Full source for Apex, Flows and Lightning Web Components
  • Incremental syncs every six hours and on demand
  • Deployed changes read back immediately
  • Managed package code shown as hidden, never missing

Workspace security

Settings · Security

  • Configuration onlyMetadata and code. CRM records stay in Salesforce.
  • Isolated per customerEnforced by the database and tested every release.
  • Keys in Google Cloud KMSCredentials encrypted under a per-customer key.
  • Second admin for productionThe author can never approve their own change.
  • Hosted in the United StatesEvery subprocessor listed with its region.

03health and audit

How healthy is the org, and what should be fixed first?

Org Health scores how well the org is built from evidence, with confidence and coverage kept as separate numbers so an org Salesforce partly hides is never mistaken for a healthy one. Apex coverage comes from the org's own last test run, and says Not recorded rather than 0% when there is none.

The org audit goes deeper: 55 checks across automation, Apex, permissions, fields, limits, packages, change history, adoption, compliance and AI readiness. Every finding has its evidence, an effort band and an estimated cost to fix, and the org gets a letter grade. Findings turn into work items, a statement of work or an AI-drafted fix in one step.

  • Health, confidence and coverage kept apart
  • 55-check audit with evidence and a letter grade
  • Findings priced by effort, not severity
  • One step from finding to work, SOW or fix

Org Audit

Acme Production · last run 6 minutes ago

Grade C

C

74 / 100

Fair, technical debt accumulating

Automation & Flows

64

Permissions & Security

71

Apex & Code

78

Fields & Data Quality

82

Limits & Performance

91

Change Intelligence

69

55 checks run · 37 open findings · 2 checks skipped, with the reason shown

04dependencies

What depends on what in the org?

Relationships are parsed from the org's source and combined with Salesforce's own dependency data into one dependency graph, where every link traces to evidence. Lineage turns it into a plain-language answer for any component: what uses it, what it uses and what to watch.

The same graph drives impact analysis before a change, the blast radius on every proposal, and detection of duplicates, overlapping automation and unused metadata. Nothing is reported as unused unless the source needed to prove it was read.

  • One evidence-based dependency graph per org
  • Plain-language lineage for any component
  • Impact and blast radius from the same map
  • Unused only when the evidence is complete

Lineage: Case.Priority

Acme Production · what uses it, what it uses

05context

How has the org changed, and how is it built?

The Changes lens shows what changed in the org and when, and whether it came through SyncOnAI 360 or somewhere else, and the audit flags production changes made outside the release process. The Architecture lens describes how the org is built: its automation style, layers, naming and sharing. The Canvas lens draws the data model.

The Knowledge Hub puts it all in one search beside Salesforce documentation and your team's notes, and the Command Center lines every connected org up on one screen. Your own AI tools can read the same picture through the read-only MCP connection.

  • Change history by route: through 360 or elsewhere
  • Architecture and data model views
  • One search across org, docs and notes
  • Every org together in the Command Center

Command Center

Org portfolio

5

Connected orgs

78

Average health

3

Need attention

  • Global Sales · ProductionProd

    12 open findings · Deploy approved 2h ago

    86

  • Service EMEA · ProductionProd

    31 open findings · Change made outside pipeline

    71

  • Partner Portal · ProductionProd

    18 open findings · Audit finished 20m ago

    79

  • Global Sales · UATSandbox

    14 open findings · Proposal validated

    84

  • Service EMEA · DevSandbox

    36 open findings · Sync running

    68

06estate

How do you understand many Salesforce orgs at once?

Every connected org, production or sandbox, gets its own repository, health score, audit, dependency graph and history. Sandboxes can be linked to their production org, and linked sandboxes do not count against the plan, so a full estate of production and sandbox orgs stays affordable to understand.

The Command Center lines up every org with its health score, a feed of syncs, deploys and audits, and a prioritised action queue. Metadata can be compared between orgs or between snapshots of the same org, which makes drift between a sandbox and production visible before a release rather than after it.

  • A repository and score for every org
  • Linked sandboxes free alongside production
  • Compare metadata between orgs or snapshots
  • Every org together in the Command Center

Command Center

Org portfolio

5

Connected orgs

78

Average health

3

Need attention

  • Global Sales · ProductionProd

    12 open findings · Deploy approved 2h ago

    86

  • Service EMEA · ProductionProd

    31 open findings · Change made outside pipeline

    71

  • Partner Portal · ProductionProd

    18 open findings · Audit finished 20m ago

    79

  • Global Sales · UATSandbox

    14 open findings · Proposal validated

    84

  • Service EMEA · DevSandbox

    36 open findings · Sync running

    68

07How it works

From connection to full understanding

The first sync does in minutes what discovery workshops do in weeks.

  1. 01

    Connect

    Authorise sandbox and production orgs with Salesforce OAuth. Linked sandboxes are free.

  2. 02

    Sync

    Configuration and source are read into the repository, with progress by stage.

  3. 03

    Score and audit

    Health, confidence and coverage, then 55 audit checks with evidence.

  4. 04

    Map

    Dependencies, lineage, technical debt, architecture and change history.

  5. 05

    Ask

    Question the org in chat, in the Knowledge Hub or from Claude and Cursor.

08Before and after

Understanding an org, with and without SyncOnAI 360

Without

With SyncOnAI 360

Weeks of discovery workshops

The whole org read and scored after the first sync

Separate tools for health, dependencies and changes

One repository that every view works from

A health score that hides what it could not see

Health, confidence and coverage reported apart

Unused fields guessed from missing references

Unused only when the evidence is complete

AI that has never seen the org

AI working from the same repository as everyone else

09Questions

Frequently asked questions

Org intelligence is a complete, evidence-based understanding of how a Salesforce org is built and how it changes: its metadata and source, health, risks, dependencies and history. SyncOnAI 360 builds it from a synced repository of each connected org.

The first sync of a large org can take several minutes, after which health, the audit, dependencies and history are available. Later syncs only fetch what changed.

It stores metadata: configuration, automation and code, and their relationships. Records such as accounts, contacts and cases stay in Salesforce, and record queries run live.

More than twenty, including objects, fields, layouts, Lightning pages, Apex, Lightning Web Components, Flows, validation rules, permission sets, profiles, queues, reports, dashboards and sharing rules.

Managed package components are listed, and what of yours uses them is mapped. Code that its publisher hides is shown as hidden and lowers confidence rather than inflating health.

Yes. Every connected org has its own repository, health, audit and history, and the Command Center shows them side by side. Paid plans cover 3, 10 or 30 production orgs, each with its sandboxes.

Yes. Claude Desktop, Cursor and other MCP clients can read connected orgs through a read-only, scoped and logged connection.

Orgs refresh automatically every six hours and on demand, and components deployed through SyncOnAI 360 are read back immediately.

Yes. Every plan includes every feature. Free covers one user and one production org with its sandboxes, on your own AI key.

Yes. Metadata can be compared between orgs, or between snapshots of the same org, so drift between environments is visible before a release.

10Keep exploring

Related

Org HealthHealth, confidence and coverage for every orgOrg Audit55 checks, priced findings, a letter gradeLineage and ImpactWhat breaks before you change itKnowledge HubDocs, patterns and your org in one searchSalesforce MCPClaude, Cursor and any MCP client, read onlyPlatformUnderstand, build, ship and deliver in one workspacePricingEvery feature on every plan

Start in 5 minutes. No card required.

Connect your Salesforce org. Run your first health scan. Ask your first question. See what you've been missing.

Start free, connect my orgBook a demo with SyncOnAI
  • Anthropic
  • OpenAI