Skip to main content

Workspace

An isolated compute environment with its own persistent storage, preinstalled libraries, and resource allocation. Where your sessions and clusters run.

An organization owns one or more workspaces. Storage and resource limits follow the workspace boundary, which is why deciding that boundary early matters.

WorkspacesFundamentals

Related terms

  • Organization: The top-level account that owns one or more workspaces and is the unit of billing. Members belong to an organization and hold roles within it.
  • Persistent storage: Workspace storage that survives between interactive sessions. Files saved elsewhere in a session are lost when it ends.
  • Interactive session: A running EugoIDE instance attached to your workspace. It is where you write code; a cluster is what runs it at scale.
  • Pricing plan: The tier assigned to a workspace, which governs its resource limits and concurrency: how much can run, and how much can run at once.
  • Activity log: The record of actions taken inside an organization: who created a workspace, changed a role, or launched a cluster.
  • EugoIDE: The browser-based notebook environment where you write and run Python on Eugo. Built on JupyterLab, connected to compute in your workspace.
  • Member: A user who belongs to an organization. What a member can do is governed by their assigned role.
  • Object storage: Storage reachable by every node in a cluster. Inputs must live here, or in workspace storage, rather than on one machine’s local disk.