Menu
Products

Nistro AI Inference

Run any open-weight model from Hugging Face on GPUs with cost-effective pricing, behind an OpenAI-compatible endpoint.

Paste a model id, pick a location, and Nistro AI finds the most cost-effective GPU, deploys the model and gives you an endpoint and API key. Your existing OpenAI code works by changing the base URL and key.

Quick start#

  1. In the console, open Inference Deployments and select Create.
  2. Choose the On-Demand plan, enter a Hugging Face model id such as google/gemma-4-26B-A4B and pick a Location.
  3. Select Recommend hardware, then View pricing, then Deploy.
  4. When the deployment is ready, open its Call the API tab, set your key and send a request:
Shell
export NISTRO_API_KEY='<api-key>'
curl https://<endpoint>/openai/v1/chat/completions \
  -H "Authorization: Bearer $NISTRO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model":"<model>","messages":[{"role":"user","content":"Hello"}]}'

Plans#

On-DemandScaleEnterprise
HardwareA fractional or single GPU, matched to your modelDedicated GPU machines, including multi-GPUDedicated GPU machines in your own cloud account
PlacementA location: US, EU, Asia or AnyThe location, cloud, region and instance type you chooseYour cloud account, region and instance type
ScalingScales to zero when idle and back up on the next requestMultiple replicas, scaled on demandMultiple replicas in your account
Quantization and context lengthYesYesYes
Private and gated Hugging Face modelsYesYesYes
High availability controls—YesYes
Custom LoRA adapters——Yes
Platform supportBasicSLA-backedEnterprise-grade

You pay for the GPUs you run, not per token. Prices are on the pricing page.

Enterprise runs Nistro AI Inference inside your own AWS, Google Cloud, Azure or Nebius account, so your data and inference traffic stay in your perimeter and run on your existing cloud commitments. Connect the account under Cloud Accounts, then pick the Enterprise plan when you create a deployment. See Cloud accounts.

Create a deployment#

Open Inference Deployments and select Create, then pick a plan.

Choose a model#

Enter a Hugging Face model id, such as google/gemma-4-26B-A4B, or paste its huggingface.co URL. The console finds the model as you type and shows its architecture, data type and maximum context length.

The model field with a detected Hugging Face model

Nistro AI serves models in Safetensors, PyTorch and GGUF formats.

Under Advanced you can also set:

  • Quantization: Auto uses what the repository provides, or pick one of the variants the repository offers.
  • Context length: defaults to the model's full context, or set a shorter one.

On-Demand plan#

  1. Enter the model and choose a Location.
  2. Select Recommend hardware. Based on your model, context length and location, Nistro AI finds the most cost-effective GPU that meets your requirements.
  3. Select View pricing, review the deployment, then select Deploy.

Create from your terminal with the Inference On-Demand CLI commands.

Scale plan#

  1. Enter the model, choose a Location and set the number of Replicas. Each replica runs on its own dedicated GPU machine.
  2. Optionally pick a GPU type under Advanced, or keep Any.
  3. Select Recommend hardware, then choose the cloud, region and instance type from the machines that fit your model.
  4. Select View pricing, review the deployment, then select Deploy.

Create from your terminal with the Inference Scale CLI commands.

Enterprise plan#

  1. Connect your cloud account first.
  2. Enter the model, then under Placement choose your Cloud account, the Region and the Instance type.
  3. Review the deployment, then select Deploy. It runs in your account.

The deployment's page opens and shows its progress.

Call the API#

A ready deployment shows its OpenAI-compatible endpoint on the Overview tab. The Call the API tab shows its API key, labelled API key (NISTRO_API_KEY), and ready-to-copy requests with your endpoint and model filled in.

  • The API's base URL is your endpoint followed by /openai/v1.
  • Send the key as a Bearer token in the Authorization header.
  • Use the model name shown in the Call the API examples.

Store the key in an environment variable:

Shell
export NISTRO_API_KEY='<api-key>'

Chat completions#

Shell
curl https://<endpoint>/openai/v1/chat/completions \
  -H "Authorization: Bearer $NISTRO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model":"<model>","messages":[{"role":"user","content":"Hello"}]}'

Streaming#

Shell
curl https://<endpoint>/openai/v1/chat/completions \
  -H "Authorization: Bearer $NISTRO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model":"<model>","messages":[{"role":"user","content":"Hello"}],"stream":true}'

The streaming examples reuse the client from the chat completions example above.

Other endpoints#

List the deployment's models:

Shell
curl https://<endpoint>/openai/v1/models \
  -H "Authorization: Bearer $NISTRO_API_KEY"

Text completions:

Shell
curl https://<endpoint>/openai/v1/completions \
  -H "Authorization: Bearer $NISTRO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model":"<model>","prompt":"Hello","max_tokens":64}'

Scale to zero#

On-Demand deployments scale to zero when they're idle, so you aren't paying for GPUs you don't use. The Live status card shows Idle, and the deployment scales back up automatically on the next request, showing Scaling up until it's serving.

Scale deployments keep dedicated replicas ready to serve at all times.

Monitoring#

The Overview tab updates live while the deployment runs:

  • Live status shows the ready and total replicas, the replica range and when the deployment was last active.
  • Live metrics show in-flight and waiting requests, tokens per second, p50 and p95 latency and KV cache usage.
  • Charts track throughput, in-flight requests, end-to-end p95 latency and KV cache utilization over time.

Across all your deployments, Alerts flag what needs attention and notify you by email or Slack, the Activity Log records what changed, and Usage shows usage and cost.

Replicas#

On Scale, change the number of replicas from the Replicas card on the Overview tab. The deployment shows updating while the change rolls out.

Delete#

Select the delete icon in the deployment's header, or Delete deployment on the Danger tab, and type delete to confirm. Deleting can't be undone.