You can run containerized compute jobs like embeddings, model inference jobs, data cleanup, batch processing, and fine-tune model workloads that finish within the job window and produce outputs you can download.

To check your job status and history, open the Ocean Network dashboard, go to Profile, and view Job Status to see all current and past jobs. Users can also check job status in Ocean Orchestrator and Ocean-cli

Paid jobs charge per run based on resource time and environment selection

No. This is no server setup and serverless GPU compute: you choose a preferred Ocean Node with the resources you need, submit a containerized job, and get results back without managing servers or infrastructure

Compute is the resource you spend in order to get your code to run, like model inference, embeddings, fine tune model runs, and data processing. Decentralized compute means that resource comes from many independent machines in a P2P compute network, so your job can run on distributed GPU or CPU capacity and return outputs. With Ocean Network, you select the Ocean Node and resources you want, submit the job, and get results back without managing servers, using a serverless style workflow across that distributed capacity.

We use a pay-per-use model with an escrow protection mechanism, meaning you pay for compute only when jobs are actually running, not for idle capacity. What this means for you: only good things. With Ocean Network, there’s no stress about being conservative with time estimates. You can safely overestimate your job duration or escrow cap, because you’ll only ever be charged for jobs that complete successfully. No wasted budget, no penalty for playing it safe.