Skip to main content
PYRAMYD

The Product Graph

Click any node. Focus its neighborhood.

A slice of the production graph, extracted 12 Aug 2026. 18,586 nodes. 22,903 edges. The same substrate APEX traverses: every node typed and every link checked.

250K+ products2,546 categories2.4M+ reviews99 node types431 edge types

Production slice · extracted 12 Aug 2026

18,586 nodes and 22,903 edges of the real graph — vendors, products, reviews, categories, and the links between them.

~7 MB · click any node, then show 1, 2, or 3 hops — loads on demand so this page stays fast

The 99 node types

Ten categories · every node typed.

The graph is heterogeneous · 99 distinct node types organized into ten categories. Each node type has its own canonical fields; the database checks the links between them.

People

8

Node types

Contacts · roles · positions · interviews

Companies

8

Node types

Companies · teams · workspaces · segments · locations · countries · industries

Products

6

Node types

Products · categories · features · releases · reviews

Revenue

12

Node types

Deals · evaluations · orders · pipelines · subscriptions · contracts · campaigns · cadences · battlecards · assessments

Finance

7

Node types

Transactions · postings · ledgers · periods · budgets · forecasts · filings

Operations

12

Node types

Ideas · requirements · issues · projects · roadmaps · cycles · objectives · capabilities · processes

Comms

4

Node types

Communications · chats · channels · events

Content

12

Node types

Documents · discussions · articles · snippets · sheets · slides · notebooks · canvases · forms · files · folders · transcripts

Data

14

Node types

Datasets · catalogs · connectors · transformations · prompts · agents · runs · models · experiments · metrics · signals · dashboards

Systems

16

Node types

Repositories · branches · commits · credentials · settings · activities · devices · alerts · applications · policies · services

The relationships

99 node types. 431 edge types. One typed property graph.

A node catalog is table stakes. The defensible part is the typed edges between them — expressed in two layers: hard foreign keys that the schema enforces, and a dynamic edge graph that captures the semantic relationships a column never could.

Layer 1 · Hard relationships

Foreign keys the schema enforces.

Deterministic, single-valued, and resolved at write time. The 2,111 declared links between tables are these edges. Four connect to canonical nodes:

  • company_fkbelongs to / is about a company
  • product_fkis about a product
  • contact_fkinvolves a person
  • review_fkcites a review

The five taxonomy FKs are special — they don't store an id and a name, they denormalize the entire ancestry, so any query filters at any level without a join:

Category

market_categoryfunctional_categoryproduct_category

Industry

industry_sectorindustry_groupindustrysub_industry

Country

regionsub_regioncountry

Role

role_modulerole_functionrole_arearole_focus

Product

product_categorymodulecapabilityfeature

Layer 2 · Dynamic relationships

431 typed edges. Any node to any node.

A single typed edge table makes this a true property graph — every relationship is a first-class, directed, semantic edge with 1:N multiplicity. The hard FKs are copied into the edge table by a refresh job, and the full catalog is organized into ten relationship categories — each with its own icon in the workspace:

Composition

part-of / made-of
feature_ofcapability_ofincludesin_catalog

Hierarchy

parent / child
member_ofsubsidiary_ofteam_ofchild_of

Classification

tagged / categorized
taggedmentionsin_categoryin_industry

Association

related / similar
related_tocompetes_withalternative_tosimilar_to

Provenance

sourced-from / evidence
authored_byacquiredderived_fromevidence_for

Ownership

owns / manages
leadsowned_byassigned_togrants_access_to

Dependency

depends-on / blocks
integrates_withdepends_onblocksrequirement_for

Transaction

pays / invoices
owns_dealpaid_bytransaction_forcontract_with

Lifecycle

replaces / on-roadmap
replaceson_roadmapin_releaseprecedes

Engagement

works-at / reviewed-by
works_atinterview_withparticipant_ofenrolls

Each category shows a representative slice — the full catalog is 431 canonical edge types across these ten kinds, CHECK-constrained in the database so an edge is never untyped.

Typed nodes, typed edges, denormalized hierarchies — APEX can follow real relationships between records, with vector search as a helper rather than the whole answer. This is what “graph, not vector RAG” actually means.

How the graph is built

From raw signal to typed node in four stages.

The same pipeline that built the graph on this page: 2,000+ source feeds, resolved to nodes, FK-linked, and provenance-stamped. New signals are still collected every day; scoring and matching them to nodes resume when the current pause on automated jobs ends.

13 OF 2,000+ CATALOGED SOURCESG2REVIEWSTrustRadiusREVIEWSGetAppREVIEWSCapterraREVIEWSProduct HuntDISCOVERYVendor sitesVENDORTech docsVENDORChangelogsVENDORPress releasesVENDORSEC EDGARREGULATORYCrunchbaseFINANCIALUSPTO PatentsIPLinkedIn jobsTALENTINGESTIONscrape · extract · land30,478 signals scored so farcatalog of 2,000+ sources
G2TrustRadiusGetAppCapterraSoftware AdviceProduct HuntPeerSpotVendor websitesTechnical documentationChangelogsAPI docsStatus pagesPress releasesBlog feedsInvestor relations pagesTechCrunchBusinessWirePRNewswireGlobeNewswireReutersBloombergSEC EDGAREU Commission filingsUSPTO PatentsWIPO IP databaseCrunchbaseCB InsightsFedRAMP marketplaceFINRA filingsLinkedIn jobsGreenhouse boardsLever boardsWorkable boardsIndeedAngelList TalentGlassdoorSalesforce AppExchangeHubSpot EcosystemSlack App DirectoryAtlassian MarketplaceShopify App StoreAWS MarketplaceAzure MarketplaceGoogle Cloud MarketplaceZoomInfo dataReddit (r/SaaS, r/devops, r/cscareers)Hacker NewsTwitter / XLinkedIn PulseIndustry RSS aggregatorVertical newslettersSubstack techSOC 2 attestationsISO 27001 registerHIPAA disclosuresEU AI Act Article 50 disclosuresG2TrustRadiusGetAppCapterraSoftware AdviceProduct HuntPeerSpotVendor websitesTechnical documentationChangelogsAPI docsStatus pagesPress releasesBlog feedsInvestor relations pagesTechCrunchBusinessWirePRNewswireGlobeNewswireReutersBloombergSEC EDGAREU Commission filingsUSPTO PatentsWIPO IP databaseCrunchbaseCB InsightsFedRAMP marketplaceFINRA filingsLinkedIn jobsGreenhouse boardsLever boardsWorkable boardsIndeedAngelList TalentGlassdoorSalesforce AppExchangeHubSpot EcosystemSlack App DirectoryAtlassian MarketplaceShopify App StoreAWS MarketplaceAzure MarketplaceGoogle Cloud MarketplaceZoomInfo dataReddit (r/SaaS, r/devops, r/cscareers)Hacker NewsTwitter / XLinkedIn PulseIndustry RSS aggregatorVertical newslettersSubstack techSOC 2 attestationsISO 27001 registerHIPAA disclosuresEU AI Act Article 50 disclosures

Walk the graph from your own product.

30 minutes. Bring a question. We'll start from your product, follow it to your market, competitors, and accounts, and show where every value came from.

Every prediction the engine makes is a traversal of the edges on this page. The graph is not a visual. It is the machine.

Where do you want to take this?