Configuration

This section describes the configuration options available when creating a new inference endpoint. Each section of the interface allows fine-grained control over how the model is deployed, accessed, and scaled.

Endpoint name, model and organization

In the top left you can:

name-org-model

Hardware Configuration

The Hardware Configuration section allows you to choose the compute backend used to host the model. You can select from three major cloud providers:

hardware

You must also choose an accelerator type:

Additionally, you can select the deployment region (e.g., East US) using the dropdown menu. Once the provider, accelerator, and region are chosen, a list of available instance types is displayed. Each instance tile includes:

You can select a tile to choose that instance for your deployment. Instances that are incompatible or unavailable in the selected region are grayed out and unclickable.

Security Level

This section determines who can access your deployed endpoint. Available options are:

security

Autoscaling

The Autoscaling section configures how many replicas of your model run and whether the system scales down to zero during inactivity. For more information we recommend reading the in-depth guide on autoscaling.

autoscaling

Container Configuration

This section allows you to specify how the container hosting your model behaves. This setting depends on the selected inference engine. For configuration details please read the Inferernce Engine section.

Environment Variables

Environment variables can be provided to customize container behavior or pass secrets.

Each section allows you to add multiple entries using the Add button.

env-vars

Endpoint Tags

You can label endpoints with tags (e.g., for-testing) to help organize and manage deployments across environments or teams. In the dashboard you will be able to filter and sort endpoints based on these tags. Tags are plain text labels added via the Add button.

tags

Advanced Settings

Advanced Settings offer more fine-grained control over deployment.

advanced

< > Update on GitHub