What are Model Presets?
Model presets are named bundles of model selection rules. Instead of wiring a specific model ID into every flow or agent, you reference a preset by its handle — likecost or performance — and the platform picks the best available model at runtime based on your active providers.
Presets decouple your AI logic from specific model versions. When a provider
releases a better model or you switch vendors, you update the preset once and
every flow using it automatically benefits.
- A ranked list of models — tried in order, falling back to the next if unavailable.
- Required capabilities — e.g.
vision,function_calling,reasoning. Only models satisfying all requirements are considered. - Exhaustive mode — try every model in the list before failing, rather than stopping at the first success.
- Data center fallback — whether to allow cross-region fallback when no model is available locally.
Preset Types
Noxus ships with a set of built-in presets and lets you create your own.- Default
- Internal
- Custom
Platform defaults — the two core presets every workspace gets:
cost and performance. Always available, cannot be deleted. Editing one creates a workspace-scoped override while the original is preserved.Managing Presets
Navigate to Organization Settings > Model Presets to view and manage your workspace’s presets.Editing a Preset
Click Edit on any preset row. For Default and Internal presets, this creates a Custom workspace override — the original is never modified. You can configure:- Title, subtitle, and description — labels shown across the product.
- Icon — visual identifier in model selection menus.
- Model list — the ordered set of models tried at runtime. Only model IDs registered with active providers are accepted.
- Required capabilities — restrict selection to models that support specific features.
- Sort order — controls position in model selection dropdowns.
- Active / Inactive — inactive presets are hidden from users but remain usable by existing flows.
Creating a Custom Preset
Click New Preset and fill in the form. The handle is a URL-safe identifier used in API calls and flow configs (e.g.my-coding-preset) — it cannot be changed after creation.
The model list must contain at least one valid model ID. Unknown model IDs are rejected at save time. Disabled models are silently dropped — if all models in a preset are disabled, the preset will return no results at runtime.
Resetting to Default
For workspace overrides of system presets, Reset to Default deletes the override and restores the original. For purely custom presets with no system counterpart, the preset is deleted entirely.Built-in Handles
Flows and agents reference presets by handle. The platform ships with the following:| Handle | Purpose |
|---|---|
cost | Lowest-cost models available |
performance | Highest-quality models available |
reasoning | Models with extended reasoning capabilities |
ocr | Vision-capable models for document extraction |
chat-quality | High-quality conversational models |
chat-cost | Cost-efficient conversational models |
chat-balanced | Balanced cost/quality for chat |
rag-performance | High-quality models for retrieval-augmented generation |
rag-cost | Cost-efficient RAG models |
multi-modal-cost | Cost-efficient vision + text models |
multi-modal-performance | High-quality vision + text models |