The console
What the console at portal.clusy.io/app shows, page by page.
Warnings and limits
- Portal is open to anyone with an active Clusy account and a verified email address.
- Changing settings, approving machines and cleaning up leaked resources are an Owner's, in the console only. The CLI and coding tools cannot do them on hosted Portal.
- Adding a connection, storing a secret, changing settings or making an agent token needs a Clusy sign-in from the last 5 minutes.
- Costs and savings in the console are estimates from recorded rates and running times, not provider invoices.
portal dashboard --linkprints a one-time sign-in link that signs in whoever opens it first. Never paste it into a chat or a log.
Open it
Go to portal.clusy.io/app and continue with Clusy. From the CLI, in your own terminal:
portal dashboardopens the console already signed in. Its pages: Runs, Usage, Machines, Connections and Settings, with r, u, m, c and s as keyboard shortcuts.
Runs
Every job with its project, state, estimated cost, savings, progress and current machine. A run's page shows its machines in order, its moves and checkpoints, its events, CPU, memory and GPU charts, its log, and its cost and savings with how they were reckoned. From there you can suspend, resume, move or stop it, and download its outputs once it has ended.
Usage
Spend per UTC day and per connection for a period (today, 7, 30, 90 or 365 days, or all), each connection's cap, the machines running now, and totals per project with their savings. The spend counts every run of the period, including runs you deleted from the history with portal rm: under it the page says "including $292.87 in 1,038 deleted runs created in the period, counted toward spend caps" when there are any, since no listing shows them (the spend counts by the day it was charged, the deleted runs by the day they were created). See Savings.
Machines
Every machine Portal runs now, on every connection: its lease, rate and job, and whether its node is connected. Your enrolled machines are listed with their approval and hardware. An Owner runs the audit here and cleans up leaked resources.
Connections
The providers you connected, with their state, method, region and cap, and the names of stored secrets (never their values). Add a connection from the Connect page; it lists each provider's methods and fields. Your own machines are added here too: Add connection, Your machine.
Settings
| Section | What it holds |
|---|---|
| Account | your Clusy account and this workspace |
| Policies | what Portal does on its own: spot, return, cheaper, out of memory, lifetime, rightsize, budget, idle and time limit |
| Controller | the baseline provider, checkpoint encryption, Google Cloud's notice, lifetime and regions, and your Modal plan |
| Agents | the CLI's and coding tools' sign-ins, and agent tokens, with Revoke |
See Settings for each setting and its default.
Approvals
When you run portal login or portal setup, the CLI opens an approval page in the console. With --device, compare the code the terminal shows with the one on the page before you approve.