Upload a metadata export. Get the truth in minutes.

No managed package, no production credentials. The scan parses your sandbox metadata offline and surfaces every component that can send email — flows, alerts, triggers, and the ones nobody remembers building.

silobase — Acme Corp UAT / new scan
New scan
Acme Corp UAT · sandbox refresh Jun 14
Drop a metadata export here
or browse — unmanaged .zip up to 200 MB
acme--uat-metadata.zip
48.2 MB
Uploaded
Parsing scan-0159
Started 12:04 · UAT
Step 4 of 5
  1. Unpack package1,914 files
  2. Index components1,482 components
  3. Detect email paths63 paths found
  4. Resolve recipients52 of 63 resolved
  5. Build manifestQueued
Any sandbox

Built for the morning after a refresh

A refresh copies production contacts and can quietly reset deliverability to “All email.” Connect every sandbox once, and each refresh shows up with its deliverability setting and open risky-path count side by side.

  • Full, partial, and developer sandboxes tracked together
  • Deliverability state read straight from the export
  • Risky-path counts per sandbox, not per org average
Explore sandbox tracking

Connected sandboxes

3 orgs · 5 sandboxes

SandboxTypeDeliverabilityRisky paths
UATPartial CopyAll email9
qa-regressionDeveloper ProSystem email only5
FullCopy-2026FullAll email7
hotfix-julDeveloperSystem email only2
dev-caseyDeveloperNo access4
Deep parse

The parser reads what setup screens hide

Workflow alerts are easy. The scan also walks flow elements, Process Builder actions, and Apex classes that call outbound mail — then resolves who each one would address the moment it fires.

  • Five sender source types covered in one pass
  • Recipient resolution against the copied data set
  • Each finding carries its component path as evidence
Explore the detector

Evidence pipeline

Last 90 days · all sandboxes

100%1,2841 Upload metadata92.8%1,1912 Parse components92.8% of prev86.3%1,1083 Detect email paths93.0% of prev51.7%6644 Review manifest59.9% of prev36.7%4715 Export evidence70.9% of prev
Scan cadence

Make scanning part of the release rhythm

Teams that scan after every refresh and before every deploy stop finding out about sandbox email from customers. The weekly view shows whether the habit is holding — across every org you manage.

  • Scan history kept per sandbox and per release
  • Failed and parsing runs visible, not swallowed
  • Re-scan any refresh in minutes from the same export flow
Explore scan history

Scans completed per week

All sandboxes · last 12 weeks

05101520Apr 13Apr 27May 11May 25Jun 8Jun 22
Scans completed
1,482
components parsed in a median sandbox scan
63
email paths surfaced from one metadata export
5
sender source types covered in a single pass

Your next refresh deserves a scan first.

Upload an export and see your first findings free. The $99 report covers one org end to end; the $39/mo ledger keeps every sandbox scanned and signed off.

    Metadata Scan — silobase — silobase