> For the complete documentation index, see [llms.txt](https://help.fovus.co/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.fovus.co/docs/workstation/workstation-overview.md). # Overview Understand what a Fovus Workstation is, when to use one, and how workstation lifecycle states and costs work. When your workflow requires a graphical interface, licensed desktop software, or hands-on interaction with results, a batch Job isn't the right fit. Fovus Workstations give you a full virtual desktop in the cloud — streamed securely to your browser — so you can run interactive workloads on demand without managing any infrastructure. ## What is a Fovus Workstation A Fovus Workstation is a cloud-hosted virtual machine that mirrors the desktop experience. You connect to it through your browser using [Amazon DCV](https://aws.amazon.com/hpc/dcv/), a high-performance remote display protocol, and interact with it just like a local computer. The workstation runs on cloud hardware you choose — CPU or GPU, various memory sizes, and local SSD storage — and Fovus provisions it automatically when you create one. ## Environment types Every workstation runs one of two software environments: * **Monolithic** — commercial or licensed software hosted by Fovus as a single installed application (for example, Ansys or MSC Adams). You bring your validated license; Fovus provides the pre-installed application. * **Containerized** — an environment that packages all dependencies, libraries, and runtime together. Typically used for open-source, in-house, or customized software that does not require a commercial license. The workstation runs Ubuntu Linux with built-in support for Docker or Apptainer, and you launch containers from inside the workstation once it is running. ## When to use a workstation vs. a Job | | Workstation | Job | | --------------------- | ------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------- | | **Interaction model** | Interactive — you drive the session in real time | Batch — Fovus runs the computation automatically | | **Typical use cases** | Licensed software (CAD, FEA pre/post-processing), 3D visualization, exploratory analysis, container debugging | Parametric studies, design-of-experiments, large parallel simulations | | **Connection** | Browser-based desktop via Amazon DCV | No desktop session; outputs sync to Fovus Storage | | **Parallelism** | Single machine | Many tasks run in parallel across multiple machines | | **Auto-stop** | Configurable walltime stops the workstation after a set number of running hours | Walltime per task; job terminates if walltime is exceeded | Choose a workstation when you need a GUI, hands-on interactivity, or software that requires a desktop session. Choose a Job when you want Fovus to run and manage a computation without your involvement. ## Workstation lifecycle A workstation moves through the following states during its lifetime: | State | What it means | Compute charges | Scratch storage charges | | -------------- | ------------------------------------------------------------------------------- | ---------------- | -------------------------------------- | | **Running** | Workstation is active and accessible via your browser | Yes | Yes | | **Stopping** | Transitional — workstation is shutting down after you click **Stop** | Brief transition | Yes | | **Stopped** | Compute is paused; all SSD data is preserved and the workstation can be resumed | No | Yes (typically much less than compute) | | **Resuming** | Transitional — workstation is starting back up after you click **Resume** | Brief transition | Yes | | **Terminated** | Workstation is permanently deleted; all SSD data is lost | No | No | {% hint style="danger" %} Terminating a workstation is irreversible and deletes everything on its local SSD. Transfer any data you want to keep to Fovus Storage before you terminate. See [Access Fovus Storage from a workstation](/docs/storage/access-storage-from-workstation.md). {% endhint %} **Walltime** is an optional automatic stop that shuts down the workstation after it has accumulated a configured number of running hours. The default is 6 hours, and the counter only runs while the workstation is in the **Running** state — time spent **Stopped** does not count. When walltime is reached, the workstation is stopped (not terminated), so your data remains intact and you can resume when ready. See [Stop, resume, and terminate](/docs/workstation/manage-workstation.md) for how to adjust walltime. ## Fovus Storage access Fovus Storage is automatically mounted on every workstation at `/fovus-storage/`. Files you access are cached on the workstation's local SSD for performance. No manual configuration is required — the mount is ready as soon as the workstation reaches **Running** status. Because all local SSD data is permanently lost when you terminate a workstation, save any work you want to keep to `/fovus-storage/` before terminating. See [Access Fovus Storage from a workstation](/docs/storage/access-storage-from-workstation.md) for details on browsing, uploading, and downloading files between the workstation and your storage. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.fovus.co/docs/workstation/workstation-overview.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.