Use a semantic_layer column with values like native_lookml, datasource_model, datasets, models, dbt_integrated, and none, plus a free-text semantic_note that exposes the vendor's wording. The template renders the structured value as a badge and shows the vendor's framing in a tooltip, so readers see both the canonical category and the vendor's own claim side by side.

A pricing_model enum carries embedded-specific values like per_viewer, per_session, per_embed, capacity_based, and platform_bundled, plus a starting_price_usd and a pricing_note for the vendor's exact framing. The template renders the unit as a badge and exposes the vendor's wording, so readers see honest framing instead of an apples-to-oranges dollar figure.

Yes. The use-cases sheet has its own ranking and verdict per use case. Per-tool pages handle solo views, and the use-case ranking drives the ordered list on each /bi/{use-case}/ page. Empty rankings can fall back to a templated rank derived from columns like embedded support and AI features.

Add an ai_features JSON column with values like natural_language_query, generative_summary, copilot, ai_explanations, and forecasting. The template renders chips on per-tool pages, and a /bi/{ai-feature}/ cut page can rank tools by support. As vendors add or rename AI features, the matrix evolves through column edits rather than rewrites.

A deployment column with values like managed_cloud, oss_self_hosted, hybrid, and on_prem captures the hosting options. Render a /bi/open-source/ subset page filtered on oss_self_hosted, and let per-tool pages cover the long tail. The same row data drives both views, with the OSS page concentrating on teams that need to run BI themselves.

A supported_data_sources JSON column carries source slugs per tool, and a /bi/{source}/ page group joins every tool that connects to a given warehouse, lakehouse, or transactional database. Per-tool pages render a source chip grid, and per-source pages rank tools by depth of integration.

Yes. Map an image URL column to og:image via the meta type, so each per-tool page renders its own social card. For per-use-case pages, the template can compose a use-case badge OG. Pairing with SleekPixel lets the OG render on the fly from row data, overlaying tool name, semantic layer badge, and embedded pricing model on a styled background.

Add a status column with values like active, deprecated, sunset, and merged, plus a deprecated_features JSON column for partial sunsets. The template renders banners via selector mapping when status is not active or when features are sunset, so readers see live and deprecated coverage clearly across the catalog.