The outcome

Run a reproducible model job without exposing keys, datasets, management ports, or persistent sensitive data.

Hyperbolic is a AI compute platform for serverless open-model inference and on-demand GPU marketplace workloads. Testing and serving open text, image, audio, and vision-language models through serverless APIs, or renting GPU capacity for controlled model and compute workloads. This guide narrows that broad capability into one repeatable outcome, with checkpoints that keep the source material and your judgment in the loop.

Before you begin

Set the boundary before the tool starts.

Choose one real task, identify who will use the result, and decide what evidence or test will make the result acceptable. Gather only the source material needed for that task. If the work contains confidential, personal, regulated, or client-owned information, confirm that the platform and account are approved before sharing it.

Troiana principle

AI should make the work easier to inspect. If the workflow removes the source, the owner, or the review step, redesign the workflow.

Step by step

A workflow you can repeat.

  1. 01

    Define the job, GPU requirement, duration, region, model and data rights, threat model, network needs, storage, output, budget, and verified teardown criteria.

  2. 02

    Create a task-specific SSH key, verify host details, restrict ingress, use a non-root account, patch the image, and never place long-lived credentials in shell history or repositories.

  3. 03

    Transfer encrypted minimal data, verify checksums, pin containers and dependencies, isolate secrets, disable public services, and record the environment before execution.

  4. 04

    Monitor GPU, process, network, disk, logs, spend, and unexpected access while validating outputs and preventing user-controlled code or prompts from reaching the host shell.

  5. 05

    Export only approved results, delete data and credentials, terminate the rental, verify billing and loss of access, rotate exposed secrets, and retain a reproducible job manifest.

Working standard

What good use looks like.

  • Use a task-specific SSH key.
  • Expose no unnecessary ports.
  • Verify deletion and termination.

OpenAI compatibility covers interface shape, not model behavior, moderation, licensing, context, or reliability. Zero-retention serverless claims do not automatically govern software and data placed on a rented GPU. Treat marketplace machines as untrusted infrastructure until verified, use SSH keys and least privilege, encrypt and delete data, pin dependencies and models, control spend, and never expose credentials or management ports.

Official references

Check the current product documentation.

Features, plan limits, availability, and data controls change. These official pages are the starting points used for this collection.