Yes. A pricing_model enum with values like credits, on_demand_bytes, node_hours, dbus_per_hour, capacity_based, and editions covers the common cases, and a free-text pricing_note exposes the vendor's wording. The template renders both side by side so readers see the canonical unit and the vendor's own framing without forcing a fabricated dollar comparison.

Use a concurrency_limit column with the documented limit per warehouse size or tier, plus a concurrency_model column for terms like multi-cluster, slot-based, or queue-based. The template renders the limit as a stat and the model as a badge, so readers can compare the raw number and the underlying scaling pattern.

Yes. The workloads sheet has its own ranking and verdict per workload. Per-warehouse pages handle solo views, and the workload ranking drives the ordered list on each /data-warehouses/{workload}/ page. Empty rankings can fall back to a templated rank derived from columns like concurrency_limit and serverless_support.

Add a category column with values like cloud_native, lakehouse, mpp, real_time_olap, and embedded_olap. Render a /data-warehouses/lakehouse/ subset page filtered on the category, and let per-warehouse pages cover the long tail. The same row data drives both views, with the lakehouse page concentrating on teams considering Databricks SQL or Iceberg-native engines.

Use a supported_clouds JSON column with values like aws, gcp, azure, and on_prem, plus a regions_count column per cloud. The template renders chips per supported cloud and a regions stat where available, so a reader can compare cloud coverage and regional breadth at a glance.

Yes. The pricing_model enum supports a bundled_with_platform value, and the template renders a clear bundled callout instead of a fabricated standalone price. The pricing_note exposes the unit and the platform it bundles with, so readers see honest framing rather than an apples-to-oranges dollar number.

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

Add a sql_features JSON column per warehouse with feature slugs like merge, qualify, window_functions, array_agg, json_extract, and recursive_cte. The template renders a feature grid with supported and unsupported chips, so readers see structured parity instead of editorial summaries that age out as vendors close the gap.