Keep the operating model stable while providers change underneath it.
The site should explain provider support as an adapter concern. Teams should be able to swap models, environments, or cost profiles without rewriting how planning, implementation, review, and previews are organized.
Repo-backed content with typed sections.
This page now renders from JSON files in the repository instead of route-local placeholder copy.
Provider choice should stay operational, not architectural.
The page content should frame the tradeoff space clearly enough that a team can choose different defaults for different roles.
- Latency-sensitive review or triage roles can bias toward faster inference.
- Long-context planning or repo synthesis can bias toward context window and reasoning quality.
- Sensitive environments can route selected roles through local or self-hosted backends.
Provider support belongs behind a narrow integration surface.
This page is intentionally managed as content, not custom code, so the messaging can evolve as providers and positioning shift.
The product story is stronger when the workflow model stays fixed and the provider layer remains interchangeable.
That also keeps the admin system honest: copy changes should live in the repo, while backend integrations stay behind interfaces.