Skip to main content

Model Routing Controls

Chyper lets tenants guide how model requests are handled without exposing backend internals.

What You Can Configure​

  • Preferred models for different workflows.
  • Budget and usage guardrails.
  • Safety and policy constraints.
  • Fallback behavior preferences.

Governance Outcomes​

  • Consistent model behavior aligned with policy.
  • Cost-aware defaults for teams and projects.
  • Reduced risk from unsupported or unapproved model usage.
  1. Define approved model set for your tenant.
  2. Set budget and quality expectations.
  3. Apply project-specific overrides only where needed.
  4. Review usage periodically.

Security Boundary​

This page excludes internal model routing architecture and service-level implementation details.