Architecture

A Universal Technology Knowledge Graph

Design the universal data model now, launch with a few hundred products, and grow to ten million by expanding taxonomy, attributes, sources and search — not by rebuilding.

BestToolsX Core

One catalog. Multiple discovery dimensions.

Universal Entity Registry

Stable IDs for every offering.

Hierarchical Taxonomy

Governed domains & subcategories.

Dynamic Attribute System

Core model + type-specific schemas.

Relationship Graph

Integrations, dependencies, alternatives.

AI Classification Engine

Suggestions with evidence & confidence.

Search & Comparison

Keyword, facets, synonyms, semantic.

Review & Trust

Reviews on canonical records only.

Catalog Governance

Versioned, logged, reversible.

Dimension 1

Universal entity types

Every listing has one primary type and may carry additional types. One company can own many offerings; one offering can have many capabilities.

TypeExamples
Software ApplicationVS Code, Photoshop, VLC
SaaS ProductNotion, Slack, Jira
Developer ToolPostman, Docker Desktop
API / API ServiceStripe API, Twilio API
Library / PackageNumPy, Lodash, React
FrameworkDjango, Spring Boot, Next.js
PlatformAWS, Azure, Vercel
CLI Toolkubectl, Terraform CLI
SDKAWS SDK, Firebase SDK
AI ModelLlama, Gemini model families
Database / Data EnginePostgreSQL, Redis, MongoDB
Infrastructure ComponentKubernetes, Envoy Proxy
…plus Website, Plugin, AI Agent, Runtime, Template, Digital Service
Dimension 3

Shared core + specialized attributes

A SaaS product needs subscription pricing. A Python library needs versions and dependencies. An API needs auth, endpoints and rate limits. One shared core model, plus type-specific attribute schemas — aligned with Schema.org SoftwareApplication and SoftwareSourceCode.

Common fieldsSpecialized fields
Name, description, websiteAPI authentication & limits
Publisher / ownerPackage manager & dependencies
Primary typeProgramming languages
Categories & tagsDeployment models
License / commercial modelSDK support
Last verifiedCloud & infrastructure support
Source evidenceSecurity advisories
Reviews & ratingsVersion & release data
Database architecture

PostgreSQL logical data model

One catalog_items row per unique offering, with every other dimension in its own table. Libraries and packages also store a Package-URL (PURL) — a standard identifier across npm, PyPI, Maven and more — to prevent duplicates.

catalog_itemsitem_typesitem_categoriesitem_attributes item_relationshipsitem_versionsitem_sourcesitem_reviews item_integrationscategoriescategory_relationstypes organizationsattribute_definitionsaliasessource_evidence

Conceptual model — not the complete production schema.

-- One canonical record per offering
CREATE TABLE catalog_items (
  id            UUID PRIMARY KEY,
  slug          TEXT UNIQUE NOT NULL,      -- canonical URL
  name          TEXT NOT NULL,
  primary_type  TEXT REFERENCES types(id),
  org_id        UUID REFERENCES organizations(id),
  website       TEXT,
  purl          TEXT UNIQUE,               -- pkg:npm/react
  attributes    JSONB DEFAULT '{}',       -- type-specific schema
  status        TEXT DEFAULT 'draft',
  last_verified TIMESTAMPTZ
);

-- Stable category IDs; names may change
CREATE TABLE categories (
  id         TEXT PRIMARY KEY,             -- 'cloud.kubernetes'
  pref_label TEXT NOT NULL,
  parent_id  TEXT REFERENCES categories(id),
  status     TEXT DEFAULT 'proposed'
);

-- Many-to-many: one item, many categories
CREATE TABLE item_categories (
  item_id     UUID REFERENCES catalog_items(id),
  category_id TEXT REFERENCES categories(id),
  confidence  NUMERIC(3,2),               -- AI suggestion score
  PRIMARY KEY (item_id, category_id)
);

-- Typed edges of the technology graph
CREATE TABLE item_relationships (
  from_item UUID REFERENCES catalog_items(id),
  rel_type  TEXT CHECK (rel_type IN ('part-of','integrates-with',
            'depends-on','alternative-to','competes-with',
            'built-with','sdk-for')),
  to_item   UUID REFERENCES catalog_items(id),
  PRIMARY KEY (from_item, rel_type, to_item)
);
Taxonomy Management System

The admin panel behind the catalog

Category changes are versioned, logged, reversible and tested before publication. AI may propose new categories; each must pass duplicate, synonym and scope checks.

Category Manager
Create, merge, rename, deprecate
Entity Type Manager
Listing types & type-specific schemas
Attribute Manager
Searchable / filterable attributes
Product Manager
Create and edit catalog records
Duplicate Detector
Identify and merge duplicates
AI Classification Queue
Review machine-suggested assignments
Source Manager
Imports, provenance, permissions
Data Quality Dashboard
Missing, stale or conflicting data
Relationship Manager
Alternatives, integrations, dependencies
SEO Manager
Indexable categories & product pages
SEO at millions of URLs

Avoid the faceted-navigation trap

A large taxonomy can accidentally generate millions of near-identical filter URLs that waste crawl budget and slow discovery of important content.

  • One canonical URL per catalog item
  • Index category pages only when they add real value
  • Keep arbitrary filter combinations out of the index
  • Redirects whenever categories merge or rename
  • Structured data appropriate to each listing type
  • No thin auto-generated product × type × feature pages
Scale targets

From MVP to 10 million+

PhaseListingsCategories
MVP1,000100
Phase 210,000300
Phase 3100,0001,000
Phase 41 million3,000
Long-term10 million+As required

Proposed architectural targets, not current catalog size. Capacity must be validated through load testing — and accuracy, discoverability and real use matter more than raw listing counts.

See the model in action

Explore the catalog with adaptive filters, or open a canonical listing to see all five dimensions.