Skip to content

Migrate from Nodus Compute 0.x

View Markdown

Nodus 1.0 carries over your account, sign-in and organization memberships. The public starter-credit offer has ended. Runs, Sandboxes and API keys must be recreated.

From 0.x In Nodus 1.0
Email/password, Google or GitHub sign-in Your existing sign-in method
Your account and organization memberships An org with a default project and your mapped member role
An account without an organization Your sign-in is preserved; create your first org during onboarding

The old billing system used sandbox payments. Its balances, debt, saved cards, payments and invoice history do not carry over. Add a payment method in the new console when required to run work.

Migration does not create a new free starter grant for external accounts. Add prepaid credit or redeem an approved offer to fund work. See credit grants for the treatment of existing starter balances and the exemptions for paying customers and Nodus internal organizations.

Follow the announced cutover dates for pausing work and downloading outputs. The old service is kept available for the announced read-only window; running work and stored outputs are not copied into the new platform.

  • API keys. 0.x keys (nk_…) stop working. Sign in with nodus login or create a new key in the console.
  • Runs, Sandboxes and 0.x workspaces. They are not copied. Download any files you need before the cutover date in your notice; the 0.x API keeps serving reads for 30 days afterwards. Recreate workspaces as Workspace resources.
  • BYOC pools and hosts. Recreate pools and enroll hosts in the new platform.
  • Cloud accounts. Re-connect AWS and GCP accounts as CloudAccount resources and remove the old role or grant.
  1. Upgrade the SDK and CLI. pip install -U nodus-compute installs 1.0 under the same package, import and command names. The 1.0 API is new: a 0.x Workload becomes a Job, and nodus run replaces the 0.x submit commands. On first run, 1.0 moves an old ~/.nodus config aside to config.0x.bak.
  2. Sign in again. Run nodus login. NODUS_BASE_URL still works as an alias of NODUS_API_URL for this major version, with a warning.
  3. Reconnect coding agents. Hosted MCP clients prompt you to authenticate again; local clients follow the setup at /connect.
  4. Update CI. The 0.x GitHub Action fails with a migration message. Use nodus-compute/run-action@v1 with a new API key.

Review the current estimate and your spending limits before starting work.

Links to 0.x docs pages redirect to their 1.0 equivalents, and old console links open a page that helps you find the object in the new console.