oiyaiOpen console
GPU CLOUD / DEVELOPER PREVIEW01 — THE POSSIBILITIES ARE YOURS

Computefor whatcomes next.

OIY / COMPUTE ENGINEINTERACTIVE 3D ↗
BUILT FOR BUILDERS

Your models.
Your environment.
Room to build.

Start building
LESS INFRASTRUCTURE. MORE POSSIBILITY.

GPU compute and persistent workspaces.
One considered developer experience.

Launch your workspace
02 / THE PLATFORMFROM IDEA TO EXECUTION

A little less setup.
A lot more building.

Bring your container. Choose your compute. Keep your work. Oiy connects the pieces so you can stay close to the thing you’re making.

01

Compute on your terms.

Start with CPU or choose a GPU profile. Adjust resources as your workload changes.

Explore compute
02

Your work stays yours.

Keep models, datasets, and checkpoints in a persistent workspace. Reuse independent volumes across services in the same placement.

Understand storage
03

Rest. Resume. Repeat.

Pause compute between sessions. Wake it when you need it. Protect long-running jobs with explicit activity tracking.

Meet idle sleep
04

One workflow. Your tools.

Use the console or HTTP API. Connect the source-distributed Python SDK, CLI, and MCP server to your own workflow.

Developer tools
03 / THE COMPUTE COLLECTIONBUILT AROUND YOUR WORKLOAD

Small experiments.
Expansive thinking.

From partitioned GPUs to full-device profiles. Find the right amount of headroom for what you’re building.

NVIDIA / BLACKWELL
24 / 48 / 96GB
MEMORY PER DEVICE / SUPPORTED PROFILE

MIG partitions or a full GPU. Choose the memory your workload needs.

Read the GPU guide

Profiles describe supported configurations. Live inventory, placement, and pricing determine availability. Check the console ↗

04 / A WORKSPACE THAT STAYS WITH YOUCREATE → BUILD → PAUSE → RESUME
COMPUTE CAN REST. YOUR WORK CAN STAY.

Your next session
starts here.

An environment you can come back to.

  1. 01

    Bring your environment

    Choose a template or use your own container image. Set resources, a command, and environment variables.

  2. 02

    Make something worth keeping

    Save your models and checkpoints in /workspace. Independent storage can outlive an individual service.

  3. 03

    Pick up where you left off

    Pause and wake compute around your workflow. The workspace persists; your processes restart.

Follow the quickstart
05 / FOR THE WAY YOU BUILDCONSOLE / API / PYTHON / MCP

Keep your tools.
Expand your reach.

Call the API directly. Protect a Python task. Let an MCP client help manage your workspace. It all connects to the same services.

Explore the developer guides
SDK + CLI + MCP: SOURCE DISTRIBUTION
PACKAGE REGISTRY RELEASES NOT YET AVAILABLE
task.py / PYTHON SDK
from oiy_ai import Client

client = Client()

# Protect a running task from idle sleep.
with client.task("SERVICE_ID", name="Training"):
 train()
Illustrative task wrapper. Run your own training function.
OIY / INSIDE THE POSSIBILITYSCROLL TO EXPLORE

A new dimension
for your ideas.

01 / THE HARDWARE

Start with silicon.

The right resources for the idea in front of you. Choose a supported GPU profile, or begin with CPU compute.

Explore the profiles
HARDWARE → ENVIRONMENT → YOUR WORKLOAD
06 / A FEW GOOD QUESTIONSCLARITY BEFORE COMPUTE

Good to
know.

Run container-based AI workloads: model experiments, inference services, notebooks, and training jobs. You choose the image, resources, environment, and persistent workspace. Workload compatibility depends on your image and the available runtime.

07 / YOUR NEXT CHAPTEROIY AI — DEVELOPER PREVIEW

What will you
make possible?

Open your workspace Read the docs