Use an execution_model enum with values like task_based, asset_based, flow_task, block_based, and declarative_yaml, plus a feature_flags JSON column for partial features like partitions, sensors, and dataset_uris. The template renders the enum as a badge and exposes the flags as chips, so readers see both the headline model and the partial-feature coverage.

A supported_runtimes JSON column carries values like python, sql, dbt, spark, kubernetes, and ecs, and a language column captures the primary authoring surface (Python, SQL, YAML). Per-orchestrator pages render chips for runtimes and a badge for language, and a /orchestrators/{runtime}/ cut page can rank orchestrators by runtime support.

Yes. The patterns sheet has its own ranking and verdict per pattern. Per-orchestrator pages handle solo views, and the pattern ranking drives the ordered list on each /orchestrators/{pattern}/ page. Empty rankings can fall back to a templated rank derived from columns like execution model and asset support.

Add a domain column with values like data, ml, workflow, and ipaas. Render a /orchestrators/ml/ subset page filtered on ml, and let per-orchestrator pages cover the long tail. The same row data drives both views, with the ML page concentrating on tools like Flyte and Metaflow alongside ML-friendly Dagster and Prefect setups.

A hosting JSON column carries values like managed_cloud, managed_paas, oss_self_hosted, hybrid, and bring_your_own_compute. The template renders chips on per-orchestrator pages, and a /orchestrators/self-hosted/ subset page concentrates on teams that need to run the orchestrator themselves with their own compute.

Yes. A pricing_model enum supports values like seats, runs, capacity_based, free_oss, and quote_only. The template renders the structured value as a badge, and the pricing_note exposes the vendor's wording, so readers see honest framing instead of a forced dollar-per-run figure.

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

Add an observability JSON column with values like logs, metrics, lineage, alerts, sla_management, and run_history. The template renders a feature grid on per-orchestrator pages, and a /orchestrators/observability/ cut page can rank orchestrators by observability depth for teams that prioritize incident response.