VERIFYBASE PROTOCOL · CONTINUOUS AUDIT LEDGER
Grounded in VerifyBase Protocol · About this registry
Verified Entity Benchmark / VerifyBase

Freshsales

Category: CRM  ·  Tier: Listed

Freshsales

Data Status: SOURCE_LINKED Automated extraction only
Pipeline: Initial Scrape API Validation Conflict Resolution Final Review

Pricing data as of 2026-04-24 ·  Type: SoftwareApplication

Integrity: Hash 13fa7a89…f943 source-verified

Core Metrics

Metric Value Source Captured
Pricing Tier $9/user/mo (Growth) · $39/user/mo (Pro) · $59/user/mo (Enterprise) —
Market Presence Tier 2 — Freshworks Suite CRM Node — Mid-Market Growth Segment —
Core Methodology AI-Assisted Lead Scoring (Freddy AI) with Pipeline Workflow Automation —
Data Architecture Shared Multi-Tenant SaaS (EU / US / AU Data Residency) —
API Maturity Index 80.4/100 (REST v2 — API Key + OAuth 2.0, Webhook Support) —

About this data: Values come from the company's official pages or are supplied by the company, and each is checked against its official source (see the source links and dates on this page).

Pricing History — Change Log

Status: Daily Monitoring Active
1 snapshot captured · Tracking since 2026-04-24
◉ Baseline Captured 2026-04-24

Baseline pricing data captured. Monitoring for changes.

◌ No pricing changes detected yet. This section will update automatically when plan prices, additions, or removals are detected by the daily scraper.

Pricing telemetry · Freshsales · 1 snapshot

Data Integrity Fingerprint

Cryptographic proof chain for this entity's data. The canonical hash is computed from a deterministic RFC 8785 (JCS) representation of the snapshot payload, signed with Ed25519, and submitted to the Sigstore Rekor public transparency log. Anyone can independently verify this data without trusting the frontend.

Canonical Hash SHA-256 · RFC 8785 JCS · canon_version: jcs-1
13fa7a8919c67e043c28130bd1fa2bf8ab8bfebfc5beda45f9d942991bc3f943

Captured:

Signature pending — will be applied on next deploy
Transparency log pending — will be submitted on next deploy

How to verify independently:

  1. 1. Fetch canonical JSON: curl https://verifybase.org/api/v1/snapshots/13fa7a8919c67e043c28130bd1fa2bf8ab8bfebfc5beda45f9d942991bc3f943
  2. 2. Run the verify endpoint: curl https://verifybase.org/api/v1/snapshots/13fa7a8919c67e043c28130bd1fa2bf8ab8bfebfc5beda45f9d942991bc3f943/verify
  3. 3. Fetch public key: curl https://verifybase.org/api/v1/trust/keys
  4. 4. Verify Ed25519 sig with openssl: echo -n "<hash>" | openssl pkeyutl -verify -pubin -inkey pubkey.pem

Data Conflict Resolution Log

No entity-specific conflict events recorded

This entity's data passed all verification checks without requiring manual intervention. System-wide resolution history is maintained in the Conflict Resolution Ledger.

Related Entities

Related entities in the VerifyBase registry, ranked by category proximity.

Same Category Copper CRM CRM View Report
Same Category HubSpot CRM View Report
Same Category Insightly CRM View Report

This record is checked against primary vendor documentation and cross-referenced with the VerifyBase open data protocol. All data points link to their primary source URL for independent verification.