SyncOnAI360

Metadata Repository

Every Salesforce org's configuration and source, one search away.

SyncOnAI 360 keeps a fast, searchable copy of each connected org's metadata, with full source, so people and AI can explore the org without clicking through Setup.

Explore your org freeBook a demo

Knowledge Hub

Documentation, patterns, your orgs and pages

  • [1] Salesforce documentationFault connectors and error handling in Flows
  • [2] Your orgCase_Intake_Route: 2 elements without a fault path
  • [3] DependenciesEscalate_High_Priority runs after it on save
  • [4] PagesRunbook: Service automation standards

In one paragraph

The SyncOnAI 360 Metadata Repository is an indexed copy of each connected Salesforce org's metadata, including the full source of Apex, Flows and Lightning Web Components. It refreshes incrementally every six hours and on demand, and it powers search, the AI chat, health, the audit and the dependency graph. Salesforce stays the authority.

Metadata types read, with full source where Salesforce allows
20+Metadata types read, with full source where Salesforce allows
Automatic refresh, plus a Refresh button
6hAutomatic refresh, plus a Refresh button
Later syncs fetch only what changed
DeltaLater syncs fetch only what changed
CRM records stored
0CRM records stored

01The problem

Why exploring a Salesforce org is so slow

Setup shows one component at a time. Answering a simple question, where a field is used or which classes touch an object, means opening page after page or retrieving metadata into an IDE first.

  1. 01

    Setup is one screen at a time

    There is no single place to search across Flows, Apex, components and configuration together.

  2. 02

    Retrieval needs tooling

    Getting the full source of an org usually means a developer, a project file and a retrieve command.

  3. 03

    Copies go stale

    A one-off export is out of date by the next deploy, and nobody knows how stale.

  4. 04

    AI has nothing to read

    Without the org's metadata in reach, AI assistants answer from general knowledge.

02what

What does the Salesforce metadata repository hold?

Objects, fields, record types, layouts and Lightning pages; Apex classes and triggers with full source; every file of each Lightning Web Component; 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 org's last test run.

Managed package code that its publisher hides is shown as hidden, never as missing. Your records, accounts, contacts, cases and the rest, are not read into the repository; record queries run live against the org when they are needed.

  • Configuration and full source together
  • Package code shown as hidden by its publisher
  • Records stay in Salesforce

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.

03fresh

How does the repository stay current?

The first sync of a large org can take several minutes and runs in the background, with progress by stage and counts per metadata type, and an estimate based on the org's own previous syncs. When no estimate can be made honestly, it says so. A running sync can be cancelled.

Later syncs fetch only what changed and are much faster. Every org refreshes automatically every six hours, Refresh runs a sync at any time, and components deployed through SyncOnAI 360 are read back straight after a successful deploy so the repository reflects them immediately.

  • Background syncs with progress by stage
  • Incremental after the first
  • Six-hour refresh, or on demand
  • Deploys read back immediately

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

04explore

How do you search and explore Salesforce metadata?

Search a component by name in the Knowledge Hub and open it to its full analysis, or ask the chat in plain language: which classes reference Opportunity, which Flows run on Case, what writes to a field. Each answer shows the tools it used, so you can see it came from the repository.

Open any component in Lineage to see what uses it and what it uses, or compare metadata between two orgs, or between snapshots of the same org, to see how environments differ before a release.

  • Name search in the Knowledge Hub
  • Plain-language questions in chat
  • Compare between orgs or snapshots

Knowledge Hub

Documentation, patterns, your orgs and pages

  • [1] Salesforce documentationFault connectors and error handling in Flows
  • [2] Your orgCase_Intake_Route: 2 elements without a fault path
  • [3] DependenciesEscalate_High_Priority runs after it on save
  • [4] PagesRunbook: Service automation standards

05powers

What does the metadata repository power?

Everything that needs to know the org works from the same copy: the AI chat and agents, the health score, the audit, the dependency graph and lineage, the builders, the change history and the read-only MCP connection for Claude and Cursor. One copy means every view agrees with every other.

Coverage equals what the last sync retrieved, and the platform treats it that way: the absence of a record in the repository is not taken as proof that something does not exist in the org.

  • One copy behind the AI, health, audit and graph
  • Read by Claude and Cursor through MCP
  • Absence never treated as proof

SyncOnAI 360

AI architect for Salesforce

Ask SyncOnAI to build flows, rules, Apex, or SOQL...

06How it works

How the repository is built

From OAuth to a searchable org.

  1. 01

    Connect

    Authorise a sandbox or production org with Salesforce OAuth.

  2. 02

    First sync

    Configuration and source are read in the background with progress by stage.

  3. 03

    Explore

    Search, ask the chat, open lineage or compare orgs.

  4. 04

    Stay current

    Incremental syncs every six hours, on demand, and after every deploy.

07Before and after

Exploring an org, with and without a repository

Without

With SyncOnAI 360

Setup, one screen at a time

One search across the whole org

Retrieve commands to see source

Full source already synced

Exports that go stale

Incremental refresh every six hours and after deploys

Different tools disagreeing

One copy behind every view

AI with no org to read

AI and MCP clients reading the same copy

08Who uses it

Who relies on the metadata repository

Salesforce adminsAnswer where a field is used, which Flows run on an object or what a profile grants in one search, instead of an afternoon in Setup. Plain-language questions in the chat work for admins who do not read Apex.Salesforce developersRead the full source of Apex, Flows and every Lightning Web Component file without a retrieve command or a project file, and compare a sandbox with production before a release to see exactly what differs.ConsultanciesConnect a new client's org on day one and have a searchable copy of everything in it within minutes, so discovery starts from the org itself rather than from interviews and screenshots.Your own AI toolsClaude Desktop, Cursor and other MCP clients read the same copy through a read-only, scoped and logged connection, so their answers are about your org rather than Salesforce in general.

09Questions

Frequently asked questions

A searchable copy of an org's metadata: its configuration and the source of its code and automation. SyncOnAI 360 keeps one per connected org and refreshes it automatically.

No. It is a working copy for understanding and changing the org. Salesforce remains the authority, records are not included, and it is not a backup or restore product.

More than twenty, including objects, fields, record types, layouts, Lightning pages, Apex, Lightning Web Components, Flows, validation rules, permission sets, profiles, email templates, value sets, approval processes, queues, reports, dashboards and sharing rules.

Several minutes for a large org, in the background. Later syncs only fetch what changed and are much faster.

Every six hours automatically, whenever you press Refresh, and immediately for components deployed through SyncOnAI 360.

Where Salesforce hides it, no. Those components are listed and shown as hidden by their publisher, never as missing.

Yes. Metadata can be compared between orgs or between snapshots of the same org.

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

Yes. Every plan includes every feature. Free covers one user and one production org with its sandboxes.

10Keep exploring

Related

Org IntelligenceUnderstand every org down to its sourceLineage and ImpactWhat breaks before you change itKnowledge HubDocs, patterns and your org in one searchSalesforce MCPClaude, Cursor and any MCP client, read onlyOrg HealthHealth, confidence and coverage for every orgPricingEvery 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