Glossary

Advanced job view: a tenant feature flag that gives users CPU and RAM selectors in the submission form. Without it the scheduler sizes both.

Booked: a job with a node and a start time assigned, not yet running.

Bucket: a folder users can mount into a container. The only storage object users see directly.

Free token mode: tokens tracked but not enforced. Settable per tenant and platform-wide.

Global node / global queue: a node or queue shared across tenants, owned by a superadmin. A tenant admin can enable or disable it, not edit it.

Hybrid queue: a queue accepting both interactive and non-interactive jobs; the user chooses per job.

Immutable: a node or queue flagged so tenant admins cannot change it.

Interactive job: has a runtime and a shell. Ends when the runtime expires.

Impersonation: a superadmin acting as a specific user of a tenant, with that user’s permissions.

Job: what you submit. Holds one or more services, and is what you book, extend, cancel and pay for. The REST API calls it a job group: its ID is jobgroupid, under /jobs/<id>. The MCP tools call that ID job_id.

Mount: attaching a bucket to a path inside a container.

No-DNS mode: a relay setting that disables private port proxying for jobs on that relay’s nodes.

Node: a machine that runs containers, connected outward to the central server.

Non-interactive job: runs a command and exits. A command is required; the runtime field is disabled.

Priority: a user group’s scheduling weight. Higher goes first when competing for capacity.

Project: a shared token budget with a membership. Jobs charged to it draw on its balance.

Proxy: a route from outside into a port your container listens on. Public or private.

Queue: what you submit to. Decides eligible nodes, resource limits, reachable storage and cost.

Tenant: a tenant. One organisation’s users, jobs, queues, storage and nodes, sealed from every other tenant.

Tenant admin: an ordinary user with administrative rights over one tenant.

Relay: the component carrying traffic between the central server and remote nodes.

Requeue: resubmitting selected jobs with their original settings.

Service: one container inside a job. Has its own image, hostname and resources. The REST API calls it a job: its ID is jobid, under /job/<id>. The MCP tools call that ID service_id. Job IDs and service IDs are separate number series, so the same number can be one of each.

Storage: a physical location backing buckets: a path on a node, or a shared backend. Admin-facing only.

Storage Bucket Collection: a group of buckets inside a storage, with a shared path prefix. Admin-facing only.

Superadmin: administers the installation and every tenant. Not a member of any tenant.

Token: the unit of billing. Spent per minute on resources held.

User group: carries the limits and permissions its members inherit. Nearly every permission lives here rather than on the user.