Cloudpaging for Superior Application Compatibility 2018-03-06T00:47:14+00:00

Cloudpaging Fundamentals

Cloudpaging is a foundational technology framework and represents our vision to transform native software delivery, deployment and provisioning from the Cloud, both public and private, and on-premise.  Some of the largest companies in the world, including leading providers of cloud services, global financial institutions, engineering software firms, leading universities, and health sciences laboratories, use Cloudpaging to migrate, manage, and run all of their applications. Cloudpaging’s advanced automated application provisioning capabilities put it in a class above traditional tools such as application virtualization tools which only solve part of the application compatibility problems many companies face. This patented technology makes it possible to lift and shift existing client applications to a new operating environment without all the hassle and expense of upgrading to new versions of your existing software.

The world-class team of inventors and software engineers here at our offices in California, many of them from the University of California, Irvine where the co-founder invented and started the company, are also the inventors of application virtualization and streaming.  The company has been awarded 51 foundational patents, all in this field and continues to be awarded more.  There is a very high probability that you are already using our technologies today in other company’s products.  Cloudpaging embodies everything we have learned about applications and incorporates a much broader set of new and disruptive technologies to make that vision a reality.

How it works

The Cloudpaging methodology relies on two key technology components: The VMMU and its Cloudpaging container.  The VMMU (virtual memory management unit) works by paging a pre-virtualized image and virtualized instruction set of the application and then directly paging those instructions onto our Cloudpaging container residing on your local or virtual machine.  Our Studio product reformats the software application into those pre-virtualized instructions, encrypts it, and divides them into code fragments called ‘pages’.  Those pages are then placed in our cloudified format so that it can be consumed by the VMMU.  With the optional use of our Server product, those cloudified pages can be delivered over the Cloud or from an on-premise server.  The cloudified application is then fetched by the user’s computer, by the VMMU and paged into our container.  When the VMMU requests to start an application, it knows what needs to be pulled down to get the application running, which is typically 1/20th of the size of the application in the beginning.  As the application executes, the VMMU is smart enough to pipeline additional instructions which are required to run before the CPU is required to execute them.  This VMMU is part of our embedded Player (under 3MB) running in the kernel of the user’s computer and incorporates our Cloudpaging container.

Our container technology works in conjunction with the VMMU and its DRM (digital rights management) component.  Our container consists of configuration information about the system and applications, and an LRU (Least Recently Used) cache which can be set up to persist (or not) between sessions depending on the configuration.  The container itself has patented technologies called layers which we also invented to handle conflicts between applications and the operating system.

The VMMU and the Cloudpaging container provides two main benefits.  First, it reduces the digital delivery time of any native application by 20 to 100 times by virtualizing the asset to be delivered in the Cloud (read further below).  Unlike traditional remoting solutions, Cloudpaging does not transmit pixels from the cloud like RSH and RDSH, nor do we execute the application on a server. In fact, many of our largest customers use Cloudpaging as their key technology to improve their remoting solutions.  Cloudpaging transmits pre-virtualized software instructions from the Cloud (a page at a time and on-demand) which are then executed on the user’s machine transiently.  Our protocol and technology allow running applications over bad, high-latency Internet and WAN connections such as mobile and wireless connections a practical reality. Secondly, Cloudpaging technology can be used to deliver many types of digital assets, including Windows applications, Android applications, Operating Systems, and more while providing the highest level of compatibility between all applications and the operating system.

Cloudpaging’s VMMU Maximizes Performance

One of the benefits of Cloudpaging’s VMMU is the enhanced application performance that end users will experience.  One of the reasons for the accelerated speed at which an application can launch with Cloudpaging is that only the page fragments required to run an application are delivered from the Server to the Player immediately at startup.  Once the app is running, the remaining page fragments are sent to the Player as needed.  The result is a faster experience for the application user.  In fact, independent software vendors are often interested in Cloudpaging technology to enhance their end users’ experiences with their applications, while enterprises and IT departments enjoy the benefits of increased productivity and decreased support tickets.

Did you know that only five to ten percent of a software app is required to launch?

With Cloudpaging’s patented technology, applications can launch up to 95% faster and lighter.  The reason for this is that Cloudpaging only delivers the page fragments required to launch an application on the Cloudpaging Player. In fact, the application is never installed on the end user’s device.  What this means for your bottom line is that fewer resources and less storage are required for an organization’s end users to launch and run their “Cloudified” software.

Cloudpaging’s Container Configuration Improves Compatibility

Cloudpaging’s configuration solves the application compatibility problems many companies face. During the application packaging process, Cloudpaging creates unique dispositions for isolating or integrating software and the end user’s operating system. This results in maximum application compatibility and functionality, whether the end-users’ desktops are virtual or physical.

Did you know that Cloudpaging technology does NOT use traditional layers or containers?

Cloudpaging technology is unique because it combines the benefits of layers and containers, without any of the challenges and conflicts.  Its distinct combination of dispositions allows your apps to run on any virtual or physical desktops with a Windows OS. During the initial packaging process, application files and registry keys are assigned to any of three dispositions. The first disposition is an isolated “layer” wherein assets are paged into a “container” and only visible to the application itself.  This method of isolation is similar to the traditional application virtualization technology as seen in App-V and ThinApp®, products of our partners, Microsoft® and VMware®, respectively.  The advantage of the isolated disposition is the low risk of conflicts between the app and the OS. The second disposition is an integrated “layer” wherein the assets are paged into a container, yet visible to the local system and other traditionally installed or paged apps.  This patented disposition is unique to Cloudpaging, allowing apps to behave as though they are natively installed, yet easy to lift and shift.  The third disposition is an installed “layer” which is also unique to Cloudpaging.  This physical disposition actually pages assets from the app onto the OS and restores original content upon deactivation, eliminating the need for cumbersome workarounds and scripts.  The result of these dispositions is superior application compatibility.

Cloudpaging Components

Cloudpaging Studio


Cloudpaging Studio

Package once. Deploy infinitely.  Cloudpaging Studio allows any Windows® application to be converted into a “cloudified” application with granular-level controls for permissions and behaviors.

Cloudpaging Server


Cloudpaging Server

The packaged software is uploaded to the Cloudpaging server (in the cloud or on-prem), and is provisioned, administered, and monitored for the end user.

Cloudpaging Player


Cloudpaging Player

Within seconds of launching the Cloudpaging player, end users can access applications as though they were installed natively, without any of the complications associated with pixel streaming.

The Cloudpaging system contains three components that deliver a native desktop application experience to end users without a traditional installation.  The three components that work together are the Cloudpaging Studio, Server, and Player.

The Cloudpaging Studio is where the science begins in the form of application packaging.  The Studio prepares the application for automated deployment, updates, and access settings based upon the predetermined permission levels within your organization.  Something special about the Cloudpaging Studio is that you can package an app for the lowest common denominator of Windows OS, and you won’t need to repackage that same app when you move operating systems.  For example, you can package your apps for Windows 7 and easily lift and shift them over to Windows 10.

The Cloudpaging Server is where your apps will reside after they’ve been packaged and where the provisioning and monitoring take place.  The Server can be in the Cloud of your choice, or your company’s own on-premises server.  A recent popular option for late Cloud adopters has been a hybrid option of on-prem and Cloud configurations.  Perhaps the greatest value and quickest way to get up and running on Cloudpaging without upfront costs would be running your apps on the Cloudpaging Content Delivery Network (CCDN,) a global, secure Cloud infrastructure hosted by AWS. Once your apps are on the Cloudpaging Server, your IT department can use virtually any provisioning tool, including Microsoft® System Center Configuration Manager, also known as SCCM or ConfigMgr, for managing the application deployments and updates to your workforce on their virtual or physical devices.

The Cloudpaging Player is the unique piece of software that “plays” the provisioned applications on the end users’ virtual or physical devices.  The Player can be configured to be visible or hidden to the end user and accessed with single-sign-on (SSO) if desired.  Either way, all of the appropriate apps for a given individual, group, or cluster will appear to the end user as though the application is installed on their device. But it’s not!  You can empower your employees with self-service options to free up your IT department with mundane requests, or you can have complete control and insight into your organization’s application usage.

The Cloudpaging system is designed to be extremely versatile to deliver what you what, when you want, to whomever you want, whenever you want.  The Cloudpaging system seamlessly plugs into existing portals and Active Directory.  Cloudpaging plays well on its own, but it’s also a stackable solution that plays well with others, without adversely affecting the momentum of your enterprise productivity.

Cloudpaging Advantages

Cloudpaging technology has many advantages over other application deployment technologies.  As Windows 7 support is winding down, more and more enterprises are gearing up for Windows 10 and preparing for what that move might mean for their apps.  With Cloudpaging, application migration success is a no-brainer.  Even difficult user mode and kernel mode apps, drivers, and multimillion-dollar line-of-business apps and ERP systems can stay with you as you change servers, devices, or operating systems.  Plus, Cloudpaging’s provisioning and management capabilities are compatible with your existing tools, such as Microsoft SCCM (ConfigMgr) and many more, so integration is seamless and your IT department doesn’t have to learn a new system.

Simplified Application Migration

Easily migrate your Windows apps in any of the following scenarios:

Superior Application Compatibility

  • User mode applications, plus drivers for services and devices

    Cloudpaging works with all your user-mode applications, plus the drivers for devices such as printers, Bluetooth and USB devices, and more.

  • Kernel mode applications

    The kernel level approach offers superior methods for dealing with application conflicts, unlike application virtualization’s user-mode approach.

  • Legacy Applications

    JDEdwards®, IBM®, Microsoft®, Oracle®, PeopleSoft®, SAP®, Siebel®… plus in-house, homegrown, custom, bespoke apps, and more! Even the most stubborn apps can be up-and-running in no time.

Seamless Integration with Your Favorite Tools

Cloudpaging’s provisioning capabilities are compatible with your existing provisioning tools, so you don’t need to learn a new system!

  • Microsoft® System Center Configuration Manager (SCCM)

  • Citrix® Management Consoles

  • VMware® Management Interface

  • IBM® Tivoli Application Dependency Discovery Manager (TADDM)

  • Oracle® Enterprise Manager

Cloudpaging System Requirements

supported on: