Skip to content
HIPS
  • Earn with your GPU
  • Pricing
  • Docs
Sign inJoin early access
01Own models, imported_

Your model with a clearer path to inference

Join early accessExplore always-on capacity

Import a supported model from Hugging Face, choose an execution pool, and use the HIPS SDK to run inference across supported model types beyond language models. For compatible open-weight language models, use a supported provider-style client. Choose always-on GPU capacity when the model needs to remain loaded.

Join early accessExplore always-on capacity

We are inviting early-access interest while we develop the platform.

  1. 02Where your model runs
  2. 03Weights apart from request data
  3. 04Two workloads
Sheet01 of 04

General notes

You have trained a model for a reason. HIPS is being built to help you put it to work.

02Where your model runs_

Choose where your model runs

Choose between the Community pool and the Certified pool. Compare the quoted price, current availability, and model-access conditions before deploying.

Cross-pool fallback will be off by default. If you enable it, it must still respect your region and data-use rules.

Personal GPU supply is intended to provide a lower-cost option. The actual quote will depend on the model, eligible capacity, and the selected pricing mode.

Customer models will run in the Certified pool first. The Community pool will follow later, only for supported ONNX models and only for deployments you opt in. If you opt in, the device owner’s machine will hold your model’s weights while it serves your requests.

Keep your weights separate from request data

Your model weights will never be used to train other models, on any plan.

Request inputs and generated outputs are governed separately. HIPS never trains on, retains or logs your prompt data. For anyone, on any plan: no prompt, file, result or response is used to train any model, and none is kept or written to a log. This includes requests processed by customer-owned models.

Execution-pool choice also matters. Before deployment, you will need to understand the model-access conditions of the selected pool. Encryption in transit and at rest does not by itself prevent a GPU operator from accessing data or weights while a workload runs.

Read Security and Data
03Weights apart from request data_

Match capacity to the workload

A model used occasionally and a model serving steady traffic may need different deployment choices. HIPS will profile supported customer models before assigning a tariff, accounting for more than memory fit alone.

Always-on capacity keeps a model loaded between requests and is charged by allocated time. Usage-based access, where supported, follows the applicable model tariff.

04Two workloads_

Tell us what you need to run

Join early access with your model’s architecture, approximate size, task, and expected traffic. These details help us assess support without requiring you to upload model weights during enrollment.

Join early access

Product

  • Inference
  • Models
  • Deploy your model
  • Always-on GPU capacity
  • How it works
  • Use cases
  • Pricing

Developer

  • Docs
  • Quickstart
  • Migrate to HIPS
  • HIPS SDK
  • Batch jobs
  • API reference

Provider

  • Earn with your GPU
  • Register GPU interest
  • Download for Mac
  • Download for Windows
  • Download for Linux

Resource

  • Security and Data
  • Resources
  • llms.txt

Compare

  • OpenRouter alternatives
  • Together AI alternatives
  • Groq alternatives
  • All comparisons

Company

  • About
  • Contact
  • Affiliate program
  • HIPS Payments

Legal

  • Legal
  • Consumer Health Data Privacy Policy
  • Report content
  • Cookie preferences

Support

  • Contact HIPS
  • Looking for payments support?

HIPS. AI inference for builders.

hips.com

Hyperscale Inference Processing Systems OÜ