Local-first desktop app for Salesforce teams

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.
SF Analyzer — Demo Org (Connected)

AccountHandler

Verified
ApexClass
Summary

Orchestrates core account business logic. Executes validation checks, calculates account health tier, and updates associated contacts on billing address change.

Local Dependencies
Calls (Outbound)AccountServiceContactRepository
Called By (Inbound)AccountTriggerAccountAPI
Dati org e sorgente salvati localmente su ~/.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.

Org knowledge lives in heads
Legacy Salesforce orgs often rely on tribal knowledge, scattered Confluence pages and stale architecture diagrams.
Cloud tools raise data questions
Customer metadata, Apex, Flows and object schemas can be sensitive. Sending them to another SaaS is often a blocker.
Manual As-Is documentation does not scale
Inventory, dependency checks, reports and technical documents take days when teams must inspect metadata by hand.

How it works

From local connection to technical document drafting in four steps.

01

Connect the org locally

Authenticate with the Salesforce CLI from the desktop app. Tokens and org data stay on the user's machine.

02

Retrieve metadata and runtime shape

Build a local snapshot with source files, metadata inventory, limits, licenses, record counts and object describe data.

03

Generate the As-Is wiki

Use the user's AI key to document custom components and produce Markdown pages inside the local project wiki.

04

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.

Clear data boundary
Designed for teams that cannot copy Salesforce metadata and code into another SaaS assessment platform.

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.

wiki/
├── overview.md (Org shape synthesis)
├── architecture/ (Data model & automations)
├── components/
├── apex/ (Apex classes skeleton & docs)
├── flows/ (Automation mapping)
└── triggers/ (Db events mapping)

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.

Org overview
Record counts, limits, licenses and installed package context for a fast environment readout.
Metadata presence
Custom-first inventory across Apex, automation, data model, security and UI components.
Delta evidence
Git-backed analysis history highlights what changed between assessment runs.
org-overview-report.json
evidence
Salesforce Org Shape
Organization Name:
Client Sandbox
Is Sandbox:
true
User Licenses:
11 Active (Full Salesforce)
Metadata Count & Delta (from git history)
Apex Classes:
42 (+2 added, +1 changed)
Apex Triggers:
6 (no changes)
Flows:
14 (+1 added)
Custom Objects:
12 (no changes)
Target Limits Utilization
DailyApiRequests48,203 / 5,000,000 (0.9%)
DataStorageMB1,240 / 5,000 (24.8%)

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

Does SF Analyzer upload customer Salesforce metadata to its cloud?
No. The desktop app retrieves metadata locally and stores snapshots, source files, wiki pages and generated documents on the user's computer.
Who pays for the AI model usage?
The user brings their own provider key. The desktop app calls that provider directly, so usage and data controls remain with the customer.
Is the first public download signed?
The current distribution is an unsigned preview build. The download page calls this out explicitly and links to the latest release artifacts.
Can it help with technical documents, not only wiki pages?
Yes. The Document Agent Harness guides TDD and impact-analysis drafts with read-only tools over local code, wiki pages and org schema evidence.

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.