Application Workspace Deployment Models

You can deploy Application Workspace following one of two models: Cloud or Self-hosted.

Cloud - Liquit as a Service

The simplest solution for deploying Application Workspace is one where Recast hosts the system and your users can connect to it and use cloud-based apps over the Internet.

The following conditions apply for hosted zones:

  • Inactive devices are removed after 120 days
  • Events are removed after 30 days
  • Auditing events are deleted after 30 days across all zones within a Application Workspace System
  • Archived packages are permanently deleted from the recycle bin after 30 days and archived package snapshots are permanently deleted after 7 days
  • Inactive sessions are removed after 8 hours
  • Completed tasks are removed after 30 days

You can configure stricter settings within your system (zone) by adding Scheduled Tasks.

Liquit as a Service uses multiple IP addresses for outgoing traffic. All the addresses that are used can be found under the DNS entry "traffic.liquit.cloud". Most modern firewalls support DNS entries as the source.

Self-hosted

Deploy an Application Workspace System within your existing server infrastructure, either in your own data centre or within a cloud tenant in AWS, Azure or Google Cloud.

The following diagram shows the high-level logical architecture of Application Workspace components, for both cloud and self-hosted solutions.

Image