Nodus
Team invitation
You have been invited
Checking your invitation...
Once you join, work you start here uses the team's shared billing and monthly limit. Your existing teams and work stay separate.
Nodus Compute
Console
Enter the Nodus console.
With Google, creating an account and signing in are the same step.
or
Benchmark report
Compare observed results across your hardware matrix. Open each workload to inspect its output and ledger.
Runs
Start a run, follow its progress and find your results.
Recent runs
| Run | Status | Cost | When |
|---|---|---|---|
| Loading… | |||
Select a run to see how it is going and what it costs.
New run
Use your project below, or start from a prepared environment.
The draft saves your command and run settings. Choose code and datasets separately.
BYOCompute
Your infrastructure, usage, and costs in one place.
Cloud accounts
Connect your cloud account
Choose your provider. We’ll guide you through connecting your resources, usage, and costs.
Ask a team administrator to connect your cloud.
Read-only access. No agent needed. Your infrastructure stays in your control.
View data status
Your connection is saved. This view updates automatically after collection. Each data source has its own status.
Your cloud at a glance
Last 30 complete days · UTCWhat you have
Resource metadata visible to this connection. VM usage is collected separately.
Data coverage
Scroll horizontally for all resource details.
| Resource | Type | Location | Observation | Tags |
|---|
What is included?
The connected account, project, or subscription is scanned across the resource types its inventory API supports, including compute, storage, databases, networking, containers, serverless, and AI services. Resources the provider does not index cannot appear. Index updates can lag changes in your cloud. Read failures, missing AWS replication, and incomplete pages appear in data status.
Discovery reads resource metadata. VM usage includes CPU, network, and disk metrics. Other resource types currently have inventory and service-level cost coverage. GPU activity and guest memory need host telemetry. Stored file contents, database records, and secret values are not read.
Usage & spend
Daily costs and machine activity.
Host poolsDevice telemetry and workload routing
Loading your pools...
Create your first pool
Group your GPU hosts in a pool, then enroll each machine with a read-only agent. An account admin can get you started.
Last 7 days · Hourly · UTC
Totals cover recorded ready device time. Missing hours stay marked as no data.
Where your capacity goes
Device-secondsLoading the measured ledger...
| Metric | Device-seconds | Meaning |
|---|
Foreign allocations
Observed onlyProcesses running outside Nodus remain under your control. Observed devices are shown even when utilization coverage is incomplete.
Host utilization
One cell per hour · UTCColor shows busy capacity. Summaries cover retained ready device time, not continuous host coverage. Outlined cells contain observed foreign allocation. Focus a cell or use arrow keys to inspect its measurements.
Predict
Advisory onlyLoading account pricing...
Forecasts and recommendations work with your existing scheduler. No per-device fees. The full current UTC calendar month is charged on first activation, with no proration. Renewal continues each calendar month while any pool has Predict enabled.
Disabling retains cached forecasts and does not reverse the current month's charge. Turn Predict off for every pool to stop future account renewals.
Loading forecast state...
Demand forecast
Hourly allocated demand in device-hours, including foreign workloads. The band is an estimate, not a guarantee.
Issued forecast calibration
Advisory burst price
An hourly market rate for compatible capacity. This is not a workload completion quote or an authorization to rent capacity.
Action policies
Recommend uses Predict. Approve and auto require funded Predict and active Route. Saving a policy does not apply an action. Auto needs a recent trusted 168-hour shadow cycle for the exact window and parallelism. Only idle reclaim currently supports trusted shadow capture.
Loading action policies...
UTC window: minute hour * * weekday. Use integer lists, ranges or *. Sunday is 0. No steps or named days.
Shadow observations
Shadow mode observes without applying. Gaps remain visible and cannot qualify auto.
Recommendations
Recommend onlyReview the evidence and make any changes in your own scheduler. Recording an outcome does not execute an action or create a charge.
Loading advice...
Action approvals
Funded Predict and Route are required. Review retained evidence before approving. Approval, execution and measured savings are separate states.
Loading action inbox...
Burst approvals
Review workload requests for market fallback. Approval records intent at the quoted expected cost. The quote is not a billing cap. Workload spending controls still apply. Route is required. Predict is not required.
Loading approval inbox...
Route on your infrastructure
Loading Route settings$0.02 per active customer device-hour
Pay as you go for Route, including optimization and apply. No supplier rental fee is charged for your own hosts. Market capacity has separate compute charges.
Loading host execution modes...
Enable execution for each existing host in the Hosts tab before it can run Nodus work. Enabling Route does not change host permissions.
Device inventory, health, and measured utilization. Your jobs stay under your control.
Review account pricing, forecast bands, and advice in the Forecast tab.
Review execution permissions, price consent, and waiting settings in the Route tab.
Hosts
Refreshes every 30 seconds| Host | Health | Devices | Last heartbeat | Actions |
|---|
Enroll a host
Read-only agentConnect a Linux host from your infrastructure provider or data center. Your scheduler keeps control of your jobs.
Copy this token now. It enrolls one host and will not be shown again after you leave this panel.
Run this in Bash on your Linux host, then paste the token at the hidden prompt. Keep the token out of logs and shell history.
Insights
Your team's spend, completed work, and time to results.
Spend over time
Run outcomes
Runs that finished in this period. Cancelled runs are shown separately.
Highest-cost runs
Recorded charges in this period. Open a run to review it.| Run | Status | Recorded cost |
|---|
Sandbox
- State
- Loading
- Recorded cost
- Current spend rate
- Not available
- Last command output
- Not reported
- Reported network usage
- Not reported
Resource history
Waiting for a measurement
Lifecycle events
| When | What happened |
|---|
Results
What it ran
Where it ran
Recorded machine placements and their outcomes.| # | Machine | Chosen as | Ready in | Saved | Cost | How it ended |
|---|---|---|---|---|---|---|
| Loading… | ||||||
Billing
Manage team credits, payment details and spending limits.
Available credits
USD
Credit breakdown
Pending usage awaits final accounting. Reserved credits cover accepted work. Credits are shared by your team.
Payment method
CheckingChecking your payment method.
Adding a card does not purchase credits or change your starter balance.
A workspace admin can manage the payment method.
Credit purchases
| Date | Amount | Status | Documents |
|---|
Monthly limit
An optional limit on your team's monthly usage. Changing it does not add credits.
Predict subscription
One account subscription covers your enabled pools. Charge records below are separate from credit purchases and invoices. An active period can include an accepted postpaid charge and does not mean an invoice has been paid.
| Period (UTC) | Charged (UTC) | Funding | Amount (USD) |
|---|
Invoices
| For | Amount | Status | |
|---|---|---|---|
| No invoices yet. | |||
Billing contact
Credit purchase receipts and spending alerts go to this address.
Team
Share work, data and GitHub access. Admins manage invitations, connections and the team spending limit.
Members
| Person | Role | Runs | Recorded cost | Last sign-in | |
|---|---|---|---|---|---|
| Loading… | |||||
Invitations
Connected agents
Manage your agents' access to this team.
Connections appear after browser approval. A successful tool call confirms your agent can use Nodus. Disconnecting prevents new access and download links. Existing workloads continue.
Local installations use your saved API key. Manage those credentials under API keys. Repair local setup
Connections
Connect external databases and W&B to your team's workloads.
| Name | Kind | Scope | Region | Details | Live | Verified | Actions |
|---|
Deleting a connection leaves its stored credential and external data unchanged.
Activity
Who did what on this account. What each run did is on the run itself.
Loading…
API keys
Create your own key for the SDK or CLI. Usage counts toward your team's shared balance and spending limit. Admins can manage all team keys.
Active keys
| Name | Key | Created | Last used | |
|---|---|---|---|---|
| Loading… | ||||
Webhook
Optional. Send run events to your app, including completion and failure.Your signing secret. Copy it now — it is shown once and cannot be recovered.
Settings
You and this account.
GitHub connections
Connect accounts or organizations and choose repositories to share with everyone in this team. Only admins can change connections.
You
Account
Leave team
You will lose access to this team and your API keys for it will stop working. Workloads and cost history stay with the team. Your account and other teams are kept.