Ceedo Workspace – Main Components
When installed on an endpoint, CeedoWorkspace will include the following components:
- The Container Engine
The Container Engine is in charge of the following tasks:
- Virtualizing applications by using a set of services and drivers that intercept and manipulate Kernel transactions and provide the medium that captures their result (i.e. write/read/modify file system and registry objects). This procedure is at the core of Ceedo’s Containerization process.
- Ensure endpoint compliance by checking that a host machine withstands some basic minimum security standards. Additionally the Container Engine can also close unauthorized processes and/or deny user actions (such as opening a configuration window in an application, or shutting down a VPN client while CeedoWorkspace is running).
- Container Images
One or more Virtual Hard Disk (VHD) files and their respective configuration files. The Container Image is the foundation of Ceedo’s Containers. The Container Image can be clean with no data, or contain pre-installed applications working out-of-the-box with no need to install anything outside the container.
- Application Launcher
The Application Launcher is the main interface between the user and the Container Engine. It relays user actions and configurations to the various components (services, drivers and executables) and allows for launching applications to run inside the container.
The Application Launcher can run “headless” (completely hidden from the user, with all of its functions pre-configured), or with a Graphic User Interface that allows launching applications, exploring the contents of the Container, and more.