FAQ

Questions about running compute jobs with ON? You’ll find the answers here.
Don’t see yours? Reach out!
What payment options are available for Ocean Network?
Payments follow a pay-per-use escrow mechanism. Funds are held in an escrow and are released only after the job is marked as completed Payment Options: -USDC deposits on Base Network
How do I check resource availability in the Ocean Network dashboard?
The Ocean Network dashboard shows live resource availability per node and environment, so you can pick where to run your compute job. You can see what capacity is free versus in use, like GPU, CPU, memory, and storage, plus environment limits like max job duration and runtime details. Use it as a quick reality check before you submit so your job matches the resources you selected.
What are the login options for Ocean Network?
You can log in with a Web3 wallet, or sign in with Email or Google, which automatically creates a smart wallet for you.
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 happens if a node fails during my job?

Ocean Nodes are designed to manage failures locally, keeping compute job execution predictable and controlled. If a node goes down mid-run, the job can be restarted on the same node once it becomes available again. Funds are released from escrow only when the node explicitly marks a job as "finished" - be it succesful or failed. That means, you only pay for the time the resources were engaged to run your job.

Rerouting is handled by the user, in line with the Ocean Network ethos of giving users full control over which resources are used.

This differs when a failure is caused by the algorithm itself. In that case, the job is treated as unsuccessful because the execution failed, not because the node was unavailable. See the dedicated FAQ for algorithm failures.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.