We built the tool we wished we had.

An always-current Salesforce dictionary, a full history of every change, and an assistant you can just ask — for the people who actually run the org.

The problem

Every Salesforce org drifts. Fields get added in a hurry, types change, and the documentation — if it exists — is a spreadsheet someone abandoned two quarters ago. When a report breaks or an integration fails, you’re left clicking through Setup trying to reconstruct what changed and who changed it.

What we built

We thought that was a strange thing to still be hard. The metadata is right there. So we built SchemaForce: connect your org and, in minutes, get an always-current dictionary of every object and field, a full history of what changed, and an assistant you can just ask — reading metadata only, never your records.

Objects OpportunitySynced 2m ago
  • AmountAmountCurrency
  • StageStageNamePicklist
  • Close DateCloseDateDate
  • RegionRegion__cText
+Region__cadded to Account · 2htracked
What we believe

What we believe shapes the product.

  • 01

    Clarity beats complexity.

    You shouldn't need a governance platform and a multi-week rollout to understand your own schema.

  • 02

    Fast and quiet.

    The experience should get out of your way — answers in seconds, not a project.

  • 03

    Trust is the boundary we never cross.

    Trust isn’t a checkbox. We read metadata only — never your records.

The boundary

We read metadata only — never your records.

It’s the line the whole product is built around. The structure of your org comes in; the contents of your records never leave it.

Metadata in

Object and field definitions, picklists, relationships, and configuration — the structure of your org.

Records stay out

We never read, store, or transmit the contents of your records. Detection runs on names and types — never values.

Say hello

We read everything. Questions, feedback, or a war story about an org gone sideways — we’d like to hear it.