Register of Vendor Pricing · Compiled by Digital Signet · Revised 20 June 2026
Folio 043 · Apparatus Criticus

Notes to the ledger.

How this register is compiled. Sourcing rules, the brass source-mark legend, and the cadence at which entries are revisited.

Direct answer

Every ledger row carries a brass source-mark on the same line as its number. Marks resolve to one of four classes: vendor pricing page (V), G2 or PeerSpot or Gartner Peer Insights deal data (G), inferred band (I), or regulator / primary statistic (R). Inferred bands are dated and traceable to a named sourcing note; this is the only register on the open web that publishes its inference methodology row by row.

The brass source-mark legend

Each numeric claim on socpricing.com ends with a brass footnote-mark. The legend:

  • [V] · sourced from a public URL on the vendor's own site (a published list price, a marketing claim, a press release).
  • [G] · sourced from buyer-submitted deal data on G2, PeerSpot, or Gartner Peer Insights. Deals are typically anonymous; the source aggregator anchors the band.
  • [I] · an inferred band. Used when the vendor declines to publish a list price. Derivation rules are below.
  • [R] · sourced from a regulator, government statistical agency, or other primary public-data source (BLS, NIST, ENISA, CISA, AICPA, DoD CIO).

How inferred bands are derived

A band marked [I] is the registrar's best apples-to-apples estimate from publicly traceable inputs. The derivation rules:

  1. G2 / PeerSpot / Gartner Peer Insights deal data. Where buyer-submitted deal data exists in volume (5+ deals at similar profile in the last 18 months), the band is the 25th to 75th percentile of the deal range, normalised to per-endpoint or per-unit.
  2. Channel-partner price lists. Where the vendor sells via channel and partner price-book screenshots circulate publicly (Reddit r/msp, Spiceworks, Vendr), partner rates are noted distinct from end-user rates.
  3. Reddit r/cybersecurity quote dumps. Where a buyer posts a redacted vendor quote with endpoint count and tier, the rate is normalised and used as a corroborating data point, not a primary anchor.
  4. Marketplace listings. AWS Marketplace, Azure Marketplace, and Google Cloud Marketplace listings publish per-unit rates; these are typically a ceiling rather than a typical contract rate.

What we do not do

We do not synthesise a list price for a quote-only vendor and present it as the vendor's published rate. We do not aggregate marketing claims into a band. We do not republish vendor-supplied "starting at" copy without converting it to a contracted range. Where field data is too thin to defend a band, the row is marked quote-only and the inferred band is omitted entirely.

Revision cadence

The full register is revisited monthly. Vendor pricing pages are re-read on the 19th of each month and the verifiedDate field is updated; revisions to bands are pushed only when a vendor publishes a change or when field data shifts the band by more than 10 percent. The next scheduled revision is 20 July 2026.

Conflicts of interest

This register is operated by Digital Signet, an independent research and product company. We are not affiliated with any vendor mentioned. No vendor has reviewed or approved any entry. We do not accept payment for inclusion, for ordering, or for the wording of any band. We do not operate an affiliate-revenue scheme on this site.

Corrections and submissions

Send corrections, additional source data, or new vendor entries to oliver@digitalsignet.com. Buyer-submitted deal data is welcome; we anonymise on receipt and never publish customer-identifying details.

Compiled by Oliver Wakefield-Smith, Digital Signet. Last revised 20 June 2026. Next scheduled revision 20 July 2026.

Annex cross-references

AnnexRegisterReturn to the homepage ledger.AnnexVendors14 vendor entries with source URLs and verified dates.AnnexGlossaryDefinitions for the acronyms that appear on vendor quotes.