Persistent environments
Close your browser, fly to another city, open a new device. Your workspace is exactly where you left it—processes running, files open, tmux sessions intact.
Linux Workspaces
Secure Linux Workspaces Accessible from Any Browser
Give engineering teams managed Linux desktops without SSH tunnels, local installs, or untracked configurations. Persistent environments. Browser access. Centralized control.
The problem
Linux at scale is an ops problem
Individual developers manage Linux well. Fleets of Linux workstations across distributed teams—less so.
Desktop management at scale
Every developer's machine drifts. Package versions diverge, configurations accumulate, and reproducing a colleague's environment becomes a multi-hour exercise.
Consistent environment requirements
CI passes but local builds fail. Staging works but the developer's machine doesn't. The gap between 'the environment the code expects' and 'the environment the developer has' causes invisible time loss.
Security of local Linux installs
SSH keys on laptops. Root access by default. Unpatched kernels on personal devices. Every unmanaged endpoint is a vector the security team can't audit.
Onboarding onto standardized stacks
A new developer's first week is spent installing dependencies, configuring toolchains, and troubleshooting version conflicts instead of shipping code.
How MyWorkspace solves this
Managed Linux environments, delivered through the browser
MyWorkspace provisions pre-configured Linux workspaces that developers access from any browser. Identical environments, no local dependencies, full admin visibility.
- 1
Define the workspace template
Specify the distribution, pre-installed packages, dev toolchains, container runtimes, and resource limits. Publish the template for the team.
- 2
Developers access via browser
No SSH configuration. No VPN. No local port forwarding. Open the workspace URL, authenticate with 2FA, and get a full Linux desktop or terminal in the browser.
- 3
Admins manage centrally
Update templates, push security patches, audit active sessions, and revoke access from a single console. No per-machine intervention.
Technical advantages
Built for engineering workloads
These aren't thin virtual desktops. They're full Linux environments with the compute, storage, and tooling that development work demands.
Container-ready workloads
Docker, Podman, and containerd run inside the workspace. Build and test containerized applications without leaving the browser-based environment.
GPU passthrough support
Attach dedicated GPU resources for ML training, CUDA workloads, or rendering tasks. Direct device access at the hypervisor level—no emulation penalty.
Terminal and GUI access
Full graphical desktop for GUI applications, or terminal-only sessions for CLI workflows. Both available simultaneously, both through the browser.
SSH-free browser access
No SSH keys to manage, rotate, or lose. No port 22 exposed. Authentication happens through the MyWorkspace identity layer with 2FA enforcement.
Template versioning
Workspace definitions are version-controlled. Roll out a new toolchain version to the team. Roll back if something breaks. Audit who runs which version.
Security & trust
Secure by architecture, not by policy memo
The security posture of managed Linux workspaces is structurally different from a fleet of unmanaged developer laptops.
- Isolated environments—each workspace runs in its own boundary with no shared kernel or filesystem access between users
- No SSH exposure—zero open ports on the public internet, authentication handled entirely by the platform identity layer
- Policy-based access controls—admins define who can access which workspaces, from which networks, during which hours
- Session recording and audit trails—every connection logged with user identity, source IP, duration, and disconnect reason
- Centralized patching—OS and package updates applied to templates, propagated to workspaces on next launch or on schedule
- Immediate revocation—terminating a user account suspends all active sessions and locks workspace access within seconds
Use cases
Who runs Linux workspaces on MyWorkspace
Software development teams
Standardized dev environments with pre-configured toolchains, language runtimes, and IDE extensions. Everyone builds against the same system state.
DevOps and platform engineers
Environments with kubectl, terraform, and cloud CLIs pre-installed. Test infrastructure changes in isolated workspaces before applying to production.
Data science and ML teams
GPU-attached workspaces with Python environments, Jupyter, and CUDA libraries. Large datasets stay in the cloud—never downloaded to laptops.
CAD and simulation workloads
Graphics-intensive applications running on cloud GPUs, streamed to the browser. Engineers access simulation tools from conference rooms or home offices.
FAQ
Linux workspace questions
MyWorkspace supports Ubuntu LTS (22.04, 24.04), Debian, Rocky Linux, and AlmaLinux as base images. Custom distributions can be accommodated for enterprise agreements—contact our team with specific requirements.
Yes. Workspaces support nested containerization. Developers can run Docker, Podman, or containerd workloads inside their workspace. Resource limits are configurable per workspace template to prevent noisy-neighbor issues.
For workloads requiring GPU acceleration (ML training, rendering, simulation), dedicated GPU resources can be attached to workspace profiles. The GPU is passed through at the hypervisor level with direct device access—no emulation overhead.
Both. Users can access a full graphical desktop through the browser, or open a terminal-only session for command-line workflows. The terminal supports copy/paste, scrollback, and session persistence across disconnections.
Workspace state is fully persistent. Closing the browser tab does not terminate the session. Users reconnect to the same running environment with all processes, files, and window layouts intact—like closing and reopening a laptop lid.
Managed Linux environments. Browser access. No SSH.
See how MyWorkspace delivers Linux workspaces to engineering teams. 30-minute walkthrough with a platform engineer.