Cloudpaging is a foundational technology framework that transforms native software delivery, deployment and provisioning from the Cloud – public, private/on-premises or hybrid.

Cloudpaging was founded around application virtualization technology and further enhanced to bring further capabilities and robustness to application delivery. Cloudpaging is so much more than application virtualization, only 1/3rd of the technology is traditional application virtualization – even that legacy technology is more robust on Numecent’s Cloudpaging technology.

Cloudpaging delivers a new paradigm: Native Application Containers that are delivered from the cloud to end users – instantly.

Numecent holds 32 battle tested patents on Cloudpaging and related technology. Continuous R&D investment ensures Cloudpaging is the most robust, compatible and scalable application delivery technology.

Numecent’s goal is to make native software delivery simple, agile, rapid and as friction-free as a single click on a website. Our mission is to be to software, what Cloud Storage solutions are to data – yet with the license control the rights-holders need to protect their assets.

6 Reasons to start cloudpaging now

Instant deployment of applications without traditional application installation, requiring as low as 10% of the application to run

Lowers application deployment costs and time need to deploy applications

Higher compatibility than other application deployment technologies

Support for Private, Public and Hybrid clouds along with support for user desktop technologies like VDI and DaaS

High Scalability allowing for high number of users per server or service instance

Full license control of applications ensuring only authorized users have access to applications.

How it Works

One of the benefits of cloudpaging is that it can reduce the digital delivery time of any native application by between 20x and 100x by pre-virtualizing the asset to be delivered.

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 in a transient manner.

This isn’t pixel remote graphics, the application is run natively on the end users physical device or VDI virtual machine. Pixel remote graphics technologies can still work in conjunction with cloudpaging – hosted virtual machines leverage cloudpaged applications and deliver graphics to user endpoints.

One unique point of Cloudpaging is BOTH native and VDI users can be supported from one deployment, allowing VDI users with good network links access to desktops and Cloudpaged applications while also allowing users who aren’t VDI capable (poor networking or latency) to still leverage the SAME cloudpaged applications.

Cloudpaging in 3 steps


Cloudify all apps

First, the application is ‘cloudified’ using our Cloudpaging Studio tool. This is an almost automatic process and does not require any changes to the application nor requires any access to the source code. This process pre-virtualizes the application, encrypts it and divides it into small fragments called ‘pages’.

Cloudification is done once per asset by the ISV, service provider or the admin. It can take 30 minutes for a program like Adobe Photoshop or can take many hours for a huge program like Avid’s Media Composer.

Unlike legacy offerings, we can cloudify and deliver 99.9% of Windows Applications and even cloudify and deliver plug-ins separately to the base application. Cloudpaging can even deliver the operating system and very large Virtual Machines.


Publish and patch with live license control

The cloudified application is then published securely on a server hosting our Cloudpaging Server component. Here, the service admin or the ISV can impose license control as they see fit. This is a ‘live’ license control system where licenses can even be revoked in real-time. The admin can also apply real-time patches and upgrades transparently to all the users or to a select few.


Deliver 20x to 100x faster than downloads

The cloudified application is then fetched by the user’s computer, a page at time over HTTP/S, by deploying a Virtual MMU (Memory Manager Unit) using ‘demand paging’. This Virtual MMU is part of our Cloudpaging Player which is a small client installed on the user’s computer and incorporates a virtualization sandbox.

Once enough pages have been fetched (typically 5% or less), the application starts executing inside this sandbox – without actually requiring any installation. We call this initial fetch a ‘partial’ and cloudpaging exploits the fact that to run an application you actually need very little as shown in the following video.

As a result, users don’t have to wait for very large downloads to complete and can start using the application once the partial is cloudpaged from the server. Because of virtualization, applications delivered this way do no require any installation – this means users do not have to confront installation issues or resource conflicts, which often plague software deployment.


Run without installation at native speeds – even offline

Subsequent accesses to the previously fetched pages are locally stored in an encrypted cache so that the performance remains as good as a natively executing application. This allows cloudpaged applications and content to be off-lined and even used without a network connection – all still under license control.