The workspace project provides a portable, file-based working environment with a modular structure for developers and users. It allows tools, applications and services to run within a workspace using predefined paths and configurations, while attempting to avoid changes to the host system.
Stored on a virtual disk, the workspace can be attached, detached and transferred between Windows installations on different machines. A Windows-based abstraction layer handles the mounting and management of this disk, allowing all operations to take place within the logically isolated workspace. Path, configuration and environment separation are used to maintain consistent runtime conditions and reduce unintended interaction with the host file system and registry.
Difference to PortableApps.com and portapps.io
This project focuses on the virtual drive as the execution platform. Applications and services run inside the virtual drive with defined paths and configurations. The goal is not to provide portable applications, but to provide a logically isolated workspace stored as a single file.
PortableApps.com and portapps.io can be used within the workspace, but the project does not aim to provide an application repository or an ecosystem for portable software.
The Workspace project consists of the platform, launcher, startup and inventory components. The platform manages the workspace lifecycle, including virtual disk creation, attachment, detachment and maintenance. It creates a configured, ready-to-use workspace containing the launcher, startup and inventory tools, including the required directory structure and configuration. The launcher provides keyboard-optimized access to workspace applications, the startup tool executes workspace initialization scripts, and the inventory tool analyzes file system and Windows registry changes to support the creation of portable applications. All three tools are standalone applications and can also be used independently. A module concept for integrating additional tools exists as a proof of concept but is not the current focus of development.
BitLocker-encrypted virtual disks are supported for environments where encryption requirements apply.
- Virtual disk as a single file containing the entire workspace
- Usable from local storage, external drives or network locations
- Single-file structure simplifies copying, transferring and sharing
- Snapshots and versioning supported by Windows VHD/VHDX mechanisms
- Multiple workspaces attachable in parallel on the same system
- Switching between workspaces by attaching/detaching virtual disks
- Consistent paths with freely selectable drive letters
- Host file system and registry usage reduced by operating inside the workspace
- Centralized maintenance by distributing updated VHD/VHDX files
- Identical paths and configurations enable reproducible automation workflows
- Support for VHD and VHDX virtual disks, including optional BitLocker encryption
- Commands to create, attach, detach, manage and compact the workspace
- Predefined structure that makes the workspace usable immediately after creation
- Integrated launcher with keyboard-based navigation for accessing programs
- Configuration of the workspace and applications through a separate key-value file
- Platform implemented with low resource usage
- Operation inside the virtual drive to reduce usage of the host file system and registry
- Customization through configuration files and startup scripts
- Centralized distribution by providing updated virtual disk files
- Consistent paths and configurations enabling reproducible automation workflows
Seanox Software Solutions is an open-source project, hereinafter referred to as Seanox.
This software is licensed under the Apache License, Version 2.0.
Copyright (C) 2026 Seanox Software Solutions
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
https://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
- Microsoft Windows 10 or higher
- Microsoft .NET 4.8.x or higher (for runtime)
- Microsoft .NET 4.8.x Developer Pack or higher (for development only)
- Seanox Workspace 3.7.0
- Seanox Workspace 3.7.0 Update for an existing workspace
- Download the latest release of seanox-platform.zip
- Extract the archive to any location in the local file system.
- Rename
platform.exeto the name that will be used for the workspace and drive
Then the program can be used as follows:
usage: platform.exe <drive>: [create|attach|detach|compact|shortcuts]
platform.exe B: create
Creates a new workspace as a VHD/VHDX virtual disk to be used as drive B:.
platform.exe B: shortcuts
Creates shortcuts for the workspace on drive B:.
platform.exe B: attach
Attaches the workspace as drive B:.
Configure Startup.cmd in the root directory of the workspace and add the
desired programs and services. It is recommended to use a launcher so that the
environment variables are available to the called programs. Detach should also
be started via the launcher if programs and services are terminated when
detaching and the environment variables are needed for this.
platform.exe B: detach
Detaches the workspace from drive B:.
platform.exe B: compact
Compacts the workspace virtual disk.
A ready-to-use workspace is provided as a template. It contains a configured development setup with tools for AWS, Kubernetes, Terraform, Java, Python, Node.js, a customized Eclipse installation, a PostgreSQL database including pgvector, and additional utilities.
- Extract the archive.
- Create shortcuts for the workspace on drive B:.
workspace.exe B: shortcuts - Attach and start the workspace as drive B: using either the shortcut or the
command line.
workspace.attach workspace.exe B: attach - Open the launcher with the Win + Esc keyboard shortcut.
- To close the workspace, click Detach in the launcher. Applications started from the workspace are closed before drive B: is detached.
The workspace can be used directly after attaching. All required directory structures, configurations and tools are included inside the virtual drive.
If you want to create your own workspace based on the template:
- Rename
workspace.exe,workspace.iniandworkspace.vhdxto the desired workspace name. - (Optional) Change the virtual disk label (disk properties).
- (Optional) Adjust the volume name in
AutoRun.inf. - Modify
Startup.cmdinside the virtual drive to start your own tools and services.
Version 3.6.0 contained outdated components due to a merge issue.
The release was withdrawn and replaced by version 3.7.0.
BF: Review: Optimization and corrections
BF: Settings: Correction to ignore invalid paths in section [FILES]
BF: Platform: Optimization and corrections
BF: Platform: Names of environment variables are case-sensitive
BF: StartUp: Optimization and corrections
BF: Launcher: Correction/optimization
BF: Launcher: Correction when using custom scaling
CR: Platform: Omission of the steps recorder (deprecated by Microsoft)
CR: Platform: Simplification of the terminal action
CR: Platform: Optimization and corrections
CR: StartUp: Optimization
CR: Launcher: Optimization and corrections
CR: Launcher: Added additional environment variables for the tile action