People
8Node types
Contacts · roles · positions · interviews
The Product Graph
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.
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
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.
Node types
Contacts · roles · positions · interviews
Node types
Companies · teams · workspaces · segments · locations · countries · industries
Node types
Products · categories · features · releases · reviews
Node types
Deals · evaluations · orders · pipelines · subscriptions · contracts · campaigns · cadences · battlecards · assessments
Node types
Transactions · postings · ledgers · periods · budgets · forecasts · filings
Node types
Ideas · requirements · issues · projects · roadmaps · cycles · objectives · capabilities · processes
Node types
Communications · chats · channels · events
Node types
Documents · discussions · articles · snippets · sheets · slides · notebooks · canvases · forms · files · folders · transcripts
Node types
Datasets · catalogs · connectors · transformations · prompts · agents · runs · models · experiments · metrics · signals · dashboards
Node types
Repositories · branches · commits · credentials · settings · activities · devices · alerts · applications · policies · services
The relationships
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
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 companyproduct_fkis about a productcontact_fkinvolves a personreview_fkcites a reviewThe 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_categoryIndustry
industry_sectorindustry_groupindustrysub_industryCountry
regionsub_regioncountryRole
role_modulerole_functionrole_arearole_focusProduct
product_categorymodulecapabilityfeatureLayer 2 · Dynamic relationships
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-offeature_ofcapability_ofincludesin_catalogHierarchy
parent / childmember_ofsubsidiary_ofteam_ofchild_ofClassification
tagged / categorizedtaggedmentionsin_categoryin_industryAssociation
related / similarrelated_tocompetes_withalternative_tosimilar_toProvenance
sourced-from / evidenceauthored_byacquiredderived_fromevidence_forOwnership
owns / managesleadsowned_byassigned_togrants_access_toDependency
depends-on / blocksintegrates_withdepends_onblocksrequirement_forTransaction
pays / invoicesowns_dealpaid_bytransaction_forcontract_withLifecycle
replaces / on-roadmapreplaceson_roadmapin_releaseprecedesEngagement
works-at / reviewed-byworks_atinterview_withparticipant_ofenrollsEach 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
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.
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?
Product marketing
Positioning, launches, and battlecards that hold up.
Explore
Competitive & market intelligence
Catch every move and brief the company on it.
Explore
Strategy & corporate development
Choose where to compete next, with sources.
Explore
Product management & operations
Decide what to build with the market in the room.
Explore
Sales operations & RevOps
Target lists, territories, and a pipeline you can plan from.
Explore
Sales & enablement
Battlecards, comparisons, and RFP answers in the deal.
Explore
Customer success
See churn coming while you can still stop it.
Explore
AI & data teams
Models and agents on the graph.
Explore