They live as columns on the host row. When Netlify changed its build minute pricing on the Pro tier, that was one cell edit, and every comparison page that mentioned Netlify updated on the next cache cycle. Set a quarterly reminder to audit pricing pages, since hosts tend to announce changes on their own blog without sending notifications.

Yes. The host sheet is the source of truth. One page group at /{host_a}-vs-{host_b}/ generates pairings, another at /jamstack-host-for/{slug}/ generates per-need rankings, a third at /{host}/ generates per-host overview pages. Three page groups, one provider sheet, no duplicated maintenance.

Status column. SleekRank can flag a host as deprecated, surface a banner on its comparison pages, and conditionally noindex pages that lean on a dying provider. When Heroku changed its free tier, sites running ranked comparisons demoted Heroku across the corpus with one column edit.

Track region_count as a number and edge_pop_count as another number, with optional notes columns. Comparison tables render numerics directly. Updating Cloudflare's PoP count from 275 to 330 is one cell, and every page that surfaces the figure updates on cache refresh.

The base template can include client-side filtering (price under X, supports framework Y) since the data is rendered as a structured table. That is a frontend enhancement, not a SleekRank feature, but it works because the data is already structured rather than buried in prose.

Pay-per-invocation hosts like Cloudflare Workers do not map cleanly to "build minutes" pricing. Maintain both pricing_model and headline_cost columns. The comparison table can conditionally render different cells based on pricing_model, so a Workers comparison surfaces invocations and a Vercel comparison surfaces build minutes.

Yes. Each host row can carry a long_review markdown column that renders below the structured table on /jamstack-host-for/{slug}/ and on per-host overview pages. Top hosts get the deep treatment; long-tail entries live with just the structured data.

Add a category column: jamstack, full_stack, edge_runtime, container_host. Use it to filter which hosts appear in which page groups. /jamstack-host-for/{slug}/ pulls only jamstack-category hosts; /fullstack-host-for/{slug}/ pulls full_stack hosts. One sheet, multiple curated audiences.