Local-first Salesforce Org assessment
Analyze your org metadata, object relationships, and technical debt. All evidence and source files stay 100% on your local machine.
- Local
- Snapshots, code and wiki stay on the user's PC.
- BYO-key
- AI calls go directly to the selected provider.
- Evidence
- Reports and documents link back to local metadata.
AccountHandler
VerifiedOrchestrates core account business logic. Executes validation checks, calculates account health tier, and updates associated contacts on billing address change.
~/.sf-analyzer/Why we built SF Analyzer
Teams need an org inventory, technical documentation and impact context before they can safely modernize or hand over a Salesforce implementation.
How it works
From local connection to technical document drafting in four steps.
Connect the org locally
Authenticate with the Salesforce CLI from the desktop app. Tokens and org data stay on the user's machine.
Retrieve metadata and runtime shape
Build a local snapshot with source files, metadata inventory, limits, licenses, record counts and object describe data.
Generate the As-Is wiki
Use the user's AI key to document custom components and produce Markdown pages inside the local project wiki.
Review reports and draft documents
Navigate the wiki, inspect reports and use the read-only document harness for TDD or impact analysis drafts.
The Local-First Data Boundary
Your Salesforce data never touches our cloud portal.
Salesforce source files, snapshots, wiki pages and exported documents stay in the local ~/.sf-analyzer workspace.
The cloud portal stores account, license, limits and operational telemetry only.
AI calls go directly from the desktop app to the provider selected by the user with a locally stored key.
Product Architecture
SF Analyzer focuses on the parts that matter in a customer org: custom development, automation, data model, deltas and evidence-backed documentation.
Designed from the ground up to analyze, document, and verify Salesforce architecture.
Traditional tools dump everything into massive spreadsheets, drowning custom architecture in standard Salesforce noise. SF Analyzer filters out the boilerplate, letting your AI model document only what you built, while keeping the data safely on your machine.
Custom-first metadata inventory
Filter standard and managed-package noise while preserving Apex, Triggers, Flows, LWC, fields and customer customizations.
BYO-key AI wiki
The desktop app calls the configured AI provider directly. SF Analyzer cloud does not proxy customer prompts or source code.
As-Is reports
Surface org overview, metadata presence, deltas between analyses and local evidence for architecture conversations.
Document Agent Harness
A guided, read-only AI workflow drafts sections with local code, wiki pages, dependencies, schemas and guarded SOQL queries.
Assessment Reports
Use the generated reports to align teams on org shape, metadata coverage, runtime limits and changes between analyses.
Document Agent Harness
The harness guides an AI agent through local code search, wiki pages, dependency context, object schema and guarded read-only SOQL.
Investigate
The agent reads only approved local sources and reports which components it analyzed.
Draft
Sections are generated step by step, then reviewed before they become part of the final document.
Guard
Coverage and SOQL guards keep the workflow explicit, read-only and evidence-oriented.
Frequently Asked Questions
Get early access to SF Analyzer.
Join our preview program. We'll invite you to download the desktop app and run your local-first Salesforce analysis as soon as slots open up.