Containerize Your Applications
Easy to Use. Application templates and the new Desktop Import wizard allow painless migration of applications. Or, use setup capture to virtualize custom applications.
#1 in Compatibility. Turbo handles the apps others can't. Virtualize both 32-bit and 64-bit applications, complex interconnected app suites, databases such as SQL Server, services such as IIS, as well as DCOM and SxS.
Run .NET Without .NET. Easily embed runtime dependencies such as .NET, Java, and SQL directly into virtual applications. Launch reliably on any desktop, regardless of underlying component installs.
Package Once, Publish Anywhere. Deploy in standalone EXEs, traditional MSIs, on intranets with Turbo Server, or over the cloud with Turbo.net integration.
Filesystem and Registry Virtualization
Turbo Studio lets you easily design and configure virtual filesystem within application containers. Virtual files are accessible by the containerized application but isolated from native applications installed on the host device based on configurable isolation semantics.
With Turbo, virtual files can reside in privileged directories without permissions, and shared DLLs in the virtual filesystem do not interfere with those installed by native applications on the host.
Turbo Studio allows quick viewing, editing, and import or export of virtual registry contents. Like the virtual filesystem, Studio offers a range of configurable isolation semantics.
Turbo Studio supports configuration of all isolation modes supported by Turbo VM, that define interaction between the containerized and host environment.
Full: Only values from the virtual filesystem or registry are accessible to the containerized application, even if a corresponding value exists on the host device. Writes to the registry are redirected to the sandbox. This mode completely isolates the container application from the host device.
Write Copy: Values from both the host device are accessible to the container application. If a value exists on both the host device and virtual registry, the virtual value takes precedence, but writes to the virtual environment are redirected to the sandbox. This mode allows containerized applications to see host data but pretects the host from changes.
Merge: Data from both the host device and the virtual registry are accessible to the container application, with virtual values taking precedence if a conflict exists. Any changes are written out to the host device. This mode allows the containerized application to interact with the host device.
Hide: Attempts to read or write values in the subfolder will fail and the values will not be visible to the containerized application. This mode prevents the application from accessing data on the host device that might cause issues with its execution.
Turbo Studio provides full configurability of the Turbo network virtualization layer. Containerized applications can have application-specific network configurations as well as defined inter-container communication routing rules.
Proxy: Route network traffic from the container through a specified proxy. This allows system administrators to monitor application activity and prevent data leaks.
DNS: Configure Domain Name System (DNS) records within the container. Redirect traffic for specified hostnames to administrator-defined IP addresses. This is valuable in development and legacy application scenarios where a required hostname cannot be changed and updating network records is undesirable.
IP Restrictions: Create network rules for specific addresses, ports, adn protocols to be accessible or blocked from the container. Lock down vulnerable legacy applications to specific application servers safe from malware attacks on external networks.
Services and DCOM
Configure services within a virtualized Service Control Manager. Turbo Studio supports virtualization of servers such as SQL Server, MySQL, IIS, and nginx. Studio also allows configuration of remote DCOM servers, which arise in many advanced Windows applications.
Studio automatically captures services during the application snapshot or container commit stages of an application build.
Turbo Hub Integration
Turbo Studio has access to the vast repository of images on the Turbo.net Hub, allowing you to pick from thousands of known working application configurations and customize them for your needs.
Our automated build system, Turbo CI, detects when updates are available and builds the latest application version using our publicly available scripts. Before making the update available on the Turbo.net Hub, an automated test is performed to make sure the application is working.
Publish applications directly from Turbo Studio into any of the supported deployment mods, including standalone EXEs, MSIs, Turbo Server, and the Turbo.net cloud.
Turbo Studio's Install panel lets you configure Desktop and Start Menu shortcuts, file associations, and other shell integration features.