Yes. Every environment has a maximum job duration, which keeps execution predictable for node operators. Each environment also shows its max job duration and current resource availability in the Ocean Network dashboard, so you can pick what fits your run. For bigger workloads that are not available inside the dashboard, use multi-stage pipelines so long runs become multiple separate jobs.

Install an Ocean Node using Docker and the ocean-node-quickstart.sh script, or use the Ocean Network Run a node page, which automates much of the setup. Configure your networking (open ports) and compute environment, and set up your EVM private key and admin wallet. Your node must be publicly accessible to pass the monitor checks that verify uptime, validity, and performance benchmarks (CPU, GPU, bandwidth). Rewards are paid to your node address for successful participation and completed compute work. Read more...

Test Compute lets users run small CPU test jobs without paying upfront and is meant for onboarding, not sustained production usage.

GPU benchmarking, node reputation, monitoring, and queueing policies work together to improve compute reliability over time. Benchmarked nodes receive a verified badge on the environments selection page and leaderboard tables, which increases demand; unreliable nodes are filtered out, and orchestration avoids poor environments selection choices.

Yes. But we keep it simple. Ocean Network uses Alchemy's wallet-based identity to secure access, sign transactions, and track rewards, yet you do not need to manage complex keys yourself. You can register with any email address or via Google Account and have the wallet created for you.

Ocean Network does not auto-assign your job to random machines. You pick the node or compute environment you want based on resource price limits and current availability, then submit the job to that specific resource. If it is busy, your job waits until that node becomes available. The dashboard shows availability and max duration per environment, so you can choose predictable compute up front