FAQ

Questions about running compute jobs with ON? You’ll find the answers here.
Don’t see yours? Reach out!
Who is Ocean Network designed for?
Ocean Network is for two groups: those who want GPU compute and Compute-as-a-Service without spinning up servers, and GPU providers who want to monetize idle GPUs by running paid compute jobs for real users, including teams looking to rent GPU capacity when demand spikes.
How is Ocean Network different from Ocean Nodes?
Ocean Nodes collectively form the Ocean Network. They are the workers that execute containerized compute jobs, enable Compute-to-Data, store and index data, and support peer-to-peer communication. Ocean Network is a decentralized ecosystem that enables resource sharing, monetization, and AI compute across the nodes.
What is Compute-to-Data (C2D)?
Compute to Data, also called C2D, is a computation where your algorithm runs in an isolated container where the data lives, so data is downloaded inside an ephemeral container that is torn down after execution, and only outputs are returned as compute.
What is Ocean Orchestrator?
Ocean Orchestrator is an extension compatible with VS Code, Cursor, Antigravity, and Windsurf that enables developers to run Compute to Data style jobs from their editor using a simple workflow
What happens if my algorithm fails during execution?
Within Ocean Network, if your algorithm is faulty and breaks mid-job, you will only be billed for the time it actually ran, not the full runtime window. Check the algorithm logs to see what failed and where.
How can I check the status of my compute job?
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
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.