Models & Providers

Noxus provides a unified interface to access leading AI models from multiple providers. Connect your provider credentials once and manage all your models, embeddings, and presets from a single settings page.

​

Model Configuration

All model and provider management lives under Settings > Models. The page is organized into four tabs:

---

​

Supported Providers

Noxus supports a wide range of cloud AI providers. Click Add provider to see the full list and connect a new one.

---

​

Connecting a Provider

​

Provider Details

Click any provider row to open its details drawer. Here you can see:

• Connection info — name, active toggle, linked model counts
• Health status — last check time, current status, and a Test connection button

---

​

Health Monitoring & Model Lifecycle

Noxus continuously monitors your provider connections and model availability through automated health checks that form the model lifecycle system.

​

Provider Health Statuses

These statuses appear on the Providers tab and reflect the overall health of a provider connection:

​

Model Health Statuses

Individual model–provider links (shown on the LLMs and Embeddings tabs) have their own lifecycle:

​

Connection Testing

When you test a provider connection, Noxus runs a multi-step health pipeline that validates each aspect of your configuration:

• Authentication — are your credentials valid?
• Permissions — do you have the right access level? (Vertex IAM, Bedrock invoke permissions)
• Regional access — for multi-region providers, each configured region is tested individually

Each step reports pass, fail, or skip, with actionable hints when something goes wrong. Results stream in real-time so you can see progress as each step completes.

​

Automatic Lifecycle Management

Noxus runs periodic health checks on all provider connections and model links in the background. Based on results, models transition automatically between lifecycle states:

1. A healthy model starts failing → after several consecutive failures it becomes suspended and is excluded from routing.
2. If failures persist → the model is deactivated and fully removed from routing.
3. Periodic recovery probes test deactivated models → if a probe succeeds, the model is restored to healthy.

This means transient provider outages are handled automatically without manual intervention. You can also manually reactivate a deactivated model at any time from the LLMs or Embeddings tab.

---

​

Model Selection in Flows and Agents

When configuring an AI node in a flow or an agent, you select models through the Model tab in the configuration drawer.

​

Preset Selection

By default, nodes use a model preset — a named bundle of models tried in priority order. If the first model encounters an error, the next one is used automatically. Click the preset dropdown to switch between presets or choose Custom models for manual selection.

​

Custom Model Selection

When you choose Custom models, a model browser opens showing all available models across your connected providers. Each model appears once per provider connection, so if you’ve connected both OpenAI and Azure OpenAI, you’ll see separate entries for each. The model browser includes:

• Search — find models by name
• Filters — narrow by provider, speed, quality, location, and capabilities (vision, function calling, reasoning, etc.)
• Speed & Quality gauges — visual indicators to compare models at a glance
• Model details — hover over a model to see its full specs: speed (tokens/sec), quality score, context window, release date, and capabilities
• Fallback chain — selected models are ordered by priority. The first model is the default; others are fallbacks

---

​

Local & Custom Models

For organizations with strict data residency requirements or proprietary models, Noxus offers deep integration for self-hosted infrastructure.

​

Seamless Local Integration

• Private Endpoints: Connect to on-premises inference servers (e.g., vLLM, Ollama, TGI) via secure private networking using custom base URLs on OpenAI-compatible providers.
• Unified Interface: Local models appear alongside cloud providers, allowing for seamless switching in flows and agents.

​

Custom Model Providers

You can extend the platform to support any proprietary or specialized model through our plugin system.

• Custom Inference: Build plugins for internal model servers or niche providers.
• Fine-tuned Models: Easily integrate your organization’s fine-tuned models into the standard workflow.

---

​

Observability Providers

In addition to model providers, you can connect observability backends to trace and monitor all AI model calls. See Observability Providers for details.