Skip to content

Workspace and sign-in ​

Everything in Yi Cloud belongs to your workspace: the balance, projects and keys, sandboxes and VMs, and usage. Each person has one workspace of their own and owns it. Who you are comes from your Yi Labs account, never from anything the browser sends.

There are no organizations, members or roles to manage in Yi Cloud.

Your workspace ​

Your workspace is set up the first time you sign in, and you can use it at once. Usage is paid from the paid credit in your Yi Labs account. See Billing and receipts.

If we suspend a workspace, the console shows "Workspace suspended" and API keys get 403 forbidden. Running sandboxes are deleted and running VMs are stopped. Contact us if this happens.

Sign in ​

Open the console at https://cloud.theyilabs.com, click the sign-in button, and sign in with your Yi Labs account.

  • A sign-in lasts at most 8 hours. Using the console doesn't extend it.
  • Every 60 seconds the console checks with your Yi Labs account that your sign-in is still valid. If it isn't, access stops at that check.
  • If that check can't be made, access stops until it can.
  • The browser holds only a random session handle. Your identity and the account's token stay on the server, the token encrypted.

Your email, your workspace and "Sign out" are at the bottom of the sidebar, with the language switch. Signing out ends your Yi Cloud session only.

When sign-in fails ​

MessageWhat to do
"The sign-in expired or was started in another browser. Please sign in again."Sign in again from the same browser.
"You cancelled the sign-in."Sign in again.
"The sign-in did not finish. Please try again."Try again. If it keeps happening, contact us.

Settings ​

The Settings page shows your workspace, its status, its egress trust tier and your email. It is read-only. Your sign-in and profile are managed in your Yi Labs account.

The trust tier sets how many resources you can run at once and how long they can live. See Quotas and network.

API keys ​

API keys act on their own. Whoever holds a key can do what its "Use for" allows, and what it spends comes from your workspace. Give a key only to people and programs you trust. See API keys and limits.