Can I have more than one workspace?

The console works one workspace at a time, and picks your first. Separate workspaces are the right boundary between, say, a production team and an experimental one, since keys, storage and the bill do not cross between them.

How do I remove someone's access?

Remove them from the Team page. Rotate any deployment key they held separately: a key is a secret, not a membership.

Does deleting a file in Storage delete it everywhere?

It removes the object. Workspace deletion is the stronger action, because it destroys the key that makes every copy readable.

Workspace, roles, keys and storage

2 min read · updated 23 October 2026

Everything in the console belongs to a workspace: deployments, fine-tunes, datasets, adapters, keys and the bill. One is created for you on first sign-in, and the rest of the console scopes itself to it.

Members and roles

Invite teammates by work email from the Team page and give each one a role. Owners and admins can invite; editors and viewers cannot.

Role	What it can do
Owner	Everything: members, billing, self-hosting licences, and all compute
Admin	Manage members other than owners, connect cloud accounts, and all compute. No billing
Editor	Create, edit and run work. No member or billing changes
Viewer	Read-only

Two kinds of API key

They are not interchangeable, and the difference matters when you are deciding what to put in an application.

Deployment keys authenticate requests to one model endpoint. One is issued when you create a deployment, shown once, and rotated from that deployment's page. This is the key your application sends.
Workspace keys, under API Keys, are for calling the platform itself: the /v1/* endpoints that drive the workspace from your own code. Create them with a label, and delete a key the moment it is no longer wanted. Anything using it stops immediately.

Both kinds are shown in full exactly once, when they are created. Store them where you keep your other secrets, and never ship either to a browser or a mobile client.

Storage

Storage is the workspace's own folder tree, holding the data going into jobs and the artefacts coming out. The broad shape:

Folder	What is in it
`shared`	Datasets, models and artefacts for the whole workspace
`finetunes`	Per-job folders: the dataset a run used, the adapter it produced, its artefacts and run records
`deployments`	Per-deployment folders: the collected KV cache audit log, and persisted cache ciphertext while the deployment exists

Upload into a folder from the toolbar, and download or delete any file from the list. Uploads and downloads go straight between your browser and the store on short-lived signed links.

Personal data and customer content are encrypted before they are stored, under a key belonging to the workspace. Deleting the workspace destroys that key, which is what makes the data unreadable in copies nobody can reach into any more.

Billing

Billing shows the month's usage with the platform fee itemised, the invoices behind it, and the payment methods on file. Cards are handled by Stripe; kvrun never sees the number.

Usage is accelerator time, so the lever you have is what is running: a deployment torn down stops costing money, and a fine-tune bills only the runtime it used.

Questions

Can I have more than one workspace?: The console works one workspace at a time, and picks your first. Separate workspaces are the right boundary between, say, a production team and an experimental one, since keys, storage and the bill do not cross between them.
How do I remove someone's access?: Remove them from the Team page. Rotate any deployment key they held separately: a key is a secret, not a membership.
Does deleting a file in Storage delete it everywhere?: It removes the object. Workspace deletion is the stronger action, because it destroys the key that makes every copy readable.