Changelog2026-10-01Changed

Moving from Nodus Compute 0.x

Nodus 1.0 replaces Nodus Compute 0.x on one cutover date, which your billing contact and admins receive by email 14 days ahead.

• What moves for you. Your sign-in (the same email and password; Google and GitHub users sign in again), each 0.x account as an org with its members and roles, unspent purchased credit to the micro-dollar and still refundable, unspent promotional credit as a credit grant named migrated-0x, and your saved cards and invoices. After the cutover you get an email with the amounts that moved.
• What you recreate. API keys (nk_… keys stop working; run nodus login or create a key in the console), runs, Sandboxes and 0.x workspaces. Download any files you need first: the 0.x API serves reads for 30 days after the cutover.
• BYOC. Pools and their routing settings move as Pool objects. Hosts re-enroll with a new enrollment token, and AWS and GCP accounts reconnect as CloudAccount resources.
• Billing. Rented machines are billed from creation until their deletion is confirmed, not from the moment your command starts, so the same run can cost more than on 0.x. The estimate shows each part before you launch.
• Tools. nodus-compute 0.12 warns on import and on every command. 1.0 keeps the package, import and command names, accepts NODUS_BASE_URL with a warning, and the 0.x GitHub Action is replaced by nodus-compute/run-action@v1.

See Migrate from Nodus Compute 0.x for the timeline and each step.