Ceedo Enterprise: Application Virtualization and Managed Portable Workspaces

This restored page documents a historical product. Ceedo Enterprise was an application virtualization and managed portable workspace product launched by Ceedo Technologies in June 2008. It is no longer sold or supported, and the company behind it stopped operating years ago. Everything below is reconstructed from archived copies of Ceedo's own website, the original press releases, and contemporary trade coverage from 2008 onward.

Where the surviving record is thin or where sources disagree, this article says so rather than smoothing the gap over.

What Ceedo Enterprise Was

Ceedo's archived product page, captured in December 2008, opened with a one-line definition: Ceedo Enterprise was a complete application virtualization solution designed to meet the needs of the enterprise. The same page described the core idea as virtualizing multiple applications together to create a virtual work environment — separating applications, application settings, and data from the operating system, while still allowing those applications to interact with one another.

That last detail is the one that distinguishes Ceedo from a simple portable-app launcher. Ceedo's pitch was not "run one isolated program from a stick" but "carry an entire configured application workspace" — mail client, browser, VPN, line-of-business software — with the pieces still able to talk to each other, on top of whatever Windows installation happened to be in front of you.

The archived page's own meta description summarized the marketing position: Ceedo's virtualization technology created a portable virtual desktop that launched on any Windows host PC with no need to pre-install software, drivers, or agents. Read that as a period marketing claim rather than a verified technical specification — the qualifications come later in this article.

What It Was Not

Ceedo Enterprise was not a virtual machine, and Ceedo did not claim it was. There was no guest operating system, no hypervisor, and no emulated hardware. Ceedo's own technology page made the distinction a selling point: the portable virtual desktop ran on top of and leveraged the existing Windows OS on the host PC, which Ceedo argued eliminated both the licensing cost and the disk footprint of a full virtualized OS.

This matters for understanding the product honestly. Ceedo virtualized the application layer — chiefly file system and registry access — and nothing below it.

The June 2008 Launch and Enterprise Positioning

The launch announcement carried the headline "Ceedo Launches an Application Virtualization Solution for the Enterprise," with a subhead stating that Ceedo Enterprise gave IT administrators the ability to virtualize standard Windows applications without packaging, making it easy and cost effective to create, deploy, and remotely manage complete application workspace environments.

There is a small but real dating discrepancy worth flagging. The press release's own dateline reads Rosh-Haayin, Israel, June 3, 2008, and the trade coverage on Virtualization.com and VMblog is dated June 3, 2008. But Ceedo filed the item in its own press room under a June 6 slug: press-room/jun-6-2008-ceedo-launches-an-application-virtualization-solution-for-the-enterprise.html. Both the /press-room/ and an earlier /company/ version of that URL survive in the Internet Archive. The most reasonable reading is that June 3 was the wire date and June 6 was when Ceedo posted it to its own site, but no source states this explicitly.

The positioning was cost-and-management-led rather than security-led. Ceedo listed the scenarios it was targeting as application portability, remote management, business continuity, and disaster recovery. The company claimed its underlying technology was already deployed on over four million devices worldwide — a figure that came from its consumer and OEM storage-bundle business, not from enterprise deployments.

Opher Dubrovsky, then VP Marketing and Business Development at Ceedo, framed the value in the release as letting IT administrators streamline workspace deployments, improve business continuity, restore user environments quickly after disasters, and keep better control of application licensing.

How Contemporary Coverage Received It

Reception was modest rather than enthusiastic. Writing in Datamation on June 19, 2008, Amy Newman noted Ceedo's proven track record but pointedly qualified it as being in less demanding environments, and characterized Ceedo's approach as device-heavy compared with VMware ThinApp's agentless model. She treated Ceedo as complementary rather than a standalone challenger, and closed on the broad observation that it remained unclear which of the era's desktop virtualization approaches would take hold.

A telling negative data point: when Virtualization.com published an application virtualization comparison chart on June 20, 2008 — barely two weeks after the launch — it covered Microsoft SoftGrid 4.2, VMware ThinApp, InstallFree Bridge, Citrix Application Streaming, Symantec AppStream, and Xenocode Virtual Application Studio. Ceedo was not included. Whatever Ceedo's technical merits, it was not in the analyst set of the day.

How Ceedo Enterprise Differed From Ceedo Personal

Ceedo published a direct comparison chart, archived from August 2008. Both Ceedo Personal and Ceedo Enterprise shared the same underlying engine: a virtualized application workspace for a single drive, the automatic virtualized setup process, support for Windows 2000, XP, 2003 and Vista, and installation on a portable device.

Everything that distinguished Enterprise was about scale and control. Per that chart, only Ceedo Enterprise offered:

• Installation on a local or network drive (not just a portable device)
• Deployment of a single image to multiple devices
• A single license covering multiple devices
• Backup and restore
• The Ceedo Management System
• Central management of Ceedo workspaces
• Remote application updates
• Client management and client enforcement

Ceedo Personal was also explicitly labelled "for personal use only." The engine was common; the management plane, licensing model, and deployment flexibility were the product difference.

Ceedo Application Virtualization: What Actually Got Virtualized

This is the part most worth getting right, and Ceedo's own technology documentation is detailed enough to describe it precisely.

At the center was what Ceedo called the Ceedo Virtualization Layer, which the company described as a mini operating system for the virtual workspace. It loaded into memory when the workspace launched and intercepted Win32 API calls made by the guest applications, handling them through a set of pre-defined rules. Ceedo's technical overview grouped intercepted calls into three categories: registry operations (including DLL and COM registration), file system operations, and everything else (memory, processes, visual elements, peripherals).

Interception was selective. Ceedo described a policy-based hooking mechanism driven by a state machine: calls that needed no interception passed straight through to Windows, while flagged calls were redirected into the virtualization layer. Ceedo attributed its claimed performance overhead of roughly 2–3% to this selectivity. That figure is a vendor claim; no independent benchmark of Ceedo Enterprise appears to survive.

Virtual File System and Virtual Registry

Two structures did the real work:

• Virtual File System (VFS) — mimicked the expected Windows directory layout so applications saw a normal file tree. Applications could read host files, but writes were redirected into the virtual environment rather than to host storage. Resource lookups searched the VFS first, with conditional fallback to the host.
• Virtual Registry — worked the same way asymmetrically. Reads could consult both the virtual and host registries under rule-based logic; all writes went exclusively to the virtual registry.

So the honest one-sentence technical description is: Ceedo Enterprise was file and registry redirection for the application layer, plus an inter-application layer to make redirected apps behave as a coherent workspace.

What Still Depended on the Host Windows Installation

Everything else. Ceedo's own materials are unusually clear about this, and its disaster recovery page listed "full utilization of the local PC" as a benefit, naming network connections, graphics cards, and printers explicitly. The technology page likewise stated that each guest application interacted directly with the host OS for events such as visualization, memory, and printing.

Concretely, the host Windows installation still supplied:

• The Windows kernel — Ceedo ran entirely in user mode and installed no drivers or system services
• All device drivers
• The display and graphics stack, including DirectX and the graphics card
• The network stack and the machine's internet connection
• CPU and RAM
• Printers and other peripherals

Ceedo's secure workspace page put it plainly: the workspace used the host PC's operating system and hardware resources — internet connection, printer — without altering the host PC itself. A compromised or malware-infected host was still a compromised host underneath the workspace.

The Independent Counterpoint on User-Mode Limits

Running purely in user mode bought Ceedo its headline capability — no admin rights required — but it also imposed hard limits. Discussion among Wikipedia editors comparing Ceedo with the rival MojoPac product noted that Ceedo did user-mode virtualization only, and consequently could not virtualize any application requiring a custom Windows service to be installed, and could not run software depending on kernel-mode drivers (the example given was games with kernel-mode anti-cheat). Contributors reported success with older Office versions (2000, 2003, XP) and Photoshop 7, while newer releases of those suites were said to fall outside what Ceedo could handle.

Treat that as informed user testimony, not a controlled evaluation — it is community discussion rather than a formal test report. But it is the clearest surviving independent commentary on where Ceedo's model broke down, and the limitation follows logically from the architecture Ceedo itself documented.

The Ceedo Setup Virtualization Engine

The Ceedo Setup Virtualization Engine was the launch announcement's single biggest differentiator, and it addressed the most-hated chore in 2008-era application virtualization: packaging.

With Microsoft SoftGrid/App-V or VMware ThinApp, getting an application into a virtual package meant sequencing it — running the installer on a clean reference machine under a capture tool, letting the tool record every file and registry delta, then building and testing a package. It was skilled, slow work, and it had to be redone for every application and every update.

Ceedo's claim was that it removed this step entirely. Per the press release, the Setup Virtualization Engine used the original standard setup files of an application to perform the virtualization automatically. Administrators pointed Ceedo at an ordinary Windows installer and the engine virtualized the installation as it ran.

Install Mode and Run Mode

Ceedo's technical documentation explains the mechanism through two execution modes:

• Install Mode — the layer deliberately hid existing host DLLs and components from the setup program. Because the installer could not see host copies of shared dependencies, it was forced to copy its own complete set into the virtual environment. This is what made the resulting workspace self-contained and portable to machines that lacked those components.
• Run Mode — read-only access to host resources was permitted, which let applications use host graphics and hardware for performance while writes stayed contained.

That Install Mode trick is genuinely clever, and it is the technical heart of the "no packaging" claim. Note a terminology wrinkle: the June 2008 press release brands this the "Setup Virtualization Engine," while Ceedo's longer technology overview refers to a Runtime Virtualization Engine handling standard setup files. The surviving documents are not perfectly consistent in naming.

The practical consequence Ceedo advertised was that virtualizing an application no longer required a specialist. The release stated that even untrained end users could add applications and plug-ins to their workspace — if IT policy allowed it.

Cross-Application Bus and Compatibility Layer

Two supporting pieces made a set of virtualized apps behave like a desktop:

• A cross-application bus let workspace applications recognize each other's COM objects and file associations. Ceedo's example: if an email arrived containing a web link, the layer ensured the mail client opened the browser inside the Ceedo workspace rather than the host's browser.
• A compatibility layer translated between what applications expected and the host OS version, which Ceedo said allowed applications virtualized on Windows XP to run on Vista and later.

Ceedo Enterprise Clients

"Ceedo Enterprise Clients" was the term for the deployed endpoint component — and it was also the licensing unit, which is why the phrase shows up in the pricing line of the press release.

Ceedo's own "Basics" page described Ceedo Enterprise as three components:

• A Windows client running in user mode, which ran even on a locked-down PC where the user had no administrator status, and which acted as a gateway to the full set of virtualized applications
• A back-end console for managing deployed application workspaces
• An online programs directory from which users could add applications to their workspace

The client had two presentation modes, per the archived product page: it could run fully integrated into the Windows UI for a seamless look, or use a separate Ceedo interface presenting an isolated environment distinct from the host desktop. In practice this surfaced as the movable Ceedo Menu Bar — a toolbar of large application icons described in the Citrix announcement.

Centralized Administration and Remote Management

The management back end was the Ceedo Client Management System (CCMS). Its stated purpose was remotely managing Ceedo Enterprise clients in the field so enterprises could deliver and continuously maintain portable computing environments.

Per the archived CCMS pages, administrators could create workspace images and populate them with required applications, set client policies, deploy images to USB drives or via a download page for user self-installation, and then — after deployment — remotely update the Ceedo software itself, update installed applications, install new applications, remove applications, change client settings, add or remove files and forms, and maintain a "Programs Directory" of approved software for end-user installation.

Later CCMS documentation described the workspace lifecycle in three stages — creation and provisioning, deployment, and update management — with per-image configuration of UI settings, update options, usage limitations, and user-group associations such as finance or sales. Additional administrative features included Windows shell integration, password rules, and host checking, plus "gold master" image files for hardware replication and site- or group-level control of client updates. Self-service deployment used Ceedo's proprietary installer technology, abbreviated CII.

By around 2011 the management tooling had been reorganized: Ceedo Enterprise Manager appears as the client-side console for creating and pre-configuring images, alongside CCMS as the back end and Ceedo Package Creator for application packaging.

Deployment Models: Managed and Unmanaged PCs

Ceedo Enterprise supported several delivery routes, and the flexibility was a large part of the pitch. From the launch release and the Citrix announcement, a workspace could live and run from:

• A folder on a local PC — installed to managed enterprise notebooks and desktops
• A network drive or file share
• A USB flash drive or portable hard drive
• A web page or web server, downloaded on demand
• A logon script push

The "unmanaged PC" case was central. Ceedo's secure workspace page described the target reality as employees working from home or the road, contractors arriving with external PCs, and mergers, branch openings, or partner scenarios where the machine or operating system could not or should not be managed by corporate IT. Because the client needed no administrator rights and installed no drivers, Ceedo argued a corporate workspace could be delivered onto a machine IT did not own or control. "Unmanaged PC" here is Ceedo's own framing for that scenario, and the security caveats below apply to it.

USB and Removable Device Deployment

The USB route is the one Ceedo Enterprise is most remembered for. Installing Ceedo to a USB device, per the launch release, made the installed applications work together and become portable for use on any Windows PC. Combined with an encrypted drive, this became Ceedo's "laptop alternative" — equipping contractors, temps, partners, and sales channels with business applications without provisioning and managing a laptop.

The 2008 Alvecon deployment described in the press release is the concrete example: the German insurance and financial broker distributed Ceedo Enterprise on encrypted USB hard drives to field brokers.

Web-Delivered Workspaces

Ceedo could also be deployed from a web server, delivering a complete working application workspace to employees or contractors in the field. This later grew into a streaming story: Ceedo SmartPlay, an application delivery layer used with Ceedo Package Creator, split a packaged application into components stored on a web server and streamed it to the workspace on demand over standard HTTP on port 80 — chosen, Ceedo said, to avoid opening additional firewall holes. Applications could then be upgraded server-side and propagated automatically to user workspaces.

Offline Use

Sources on offline operation are thinner than for other features, and no 2008 document found for this article addresses it head-on. The clearest statement comes from a later page (circa 2011) comparing Ceedo to VDI, which said the virtual workspace allowed users to work either offline or online and still stay up to date with applications and data.

Two 2008-era details support the same conclusion indirectly. The disaster recovery page anticipated communications being disrupted and proposed handing out USB drives so users could plug into any Windows PC and start work — which only makes sense if the workspace itself ran without a network. And the architecture required it: applications executed locally on the host CPU against a local VFS. What needed connectivity was management — remote updates, streaming, and policy changes — not execution.

Business Continuity and Disaster Recovery

Ceedo devoted an entire solution page to disaster recovery, and the argument was sharper than most of its marketing. The page observed that DR plans typically focus on restoring critical servers and databases on the assumption that a business unit only needs somewhere to go, a phone, and a PC connected to the data center — and argued that restoring the desktops needed to resume business is in reality lengthy and time consuming.

Ceedo's proposed answer: pre-build and pre-test one workspace image during the planning stage, hand it out to employees, and have them use it day to day rather than waiting for "D-Day." If disaster struck, users either downloaded the workspace from a web link or received USB drives and plugged into any standard Windows PC. The stated components were the Ceedo Enterprise Client with the management system, standard Windows applications preinstalled by IT, a VPN client if needed, employee data, and any in-house applications.

The customer testimony in the launch release makes the same point from the field. Joachim Kolodzie of Alvecon described laptop recovery that had previously taken days becoming, in his account, as simple and fast as plugging the USB drive into a new PC. He also mentioned that application incompatibilities stopped occurring in the virtual environment. This is a vendor-supplied customer quote in a vendor press release — genuine, but not independent verification.

Corporate Applications for Contractors and Remote Workers

Ceedo's use-case pages consistently return to people outside the corporate perimeter.

The employee-owned PC page framed three problems — security, manageability, and supportability — and cited a Gartner projection that 10% of companies would require employee-purchased notebooks that year. Ceedo's answer was isolation between corporate and personal environments on the same machine, with the employee able to switch between them, plus central management of the corporate side.

The work from home page proposed that employees leave the laptop at the office and carry the work environment home on a USB drive, with the image created, controlled, and managed by the enterprise. The listed solution bundle included the Ceedo client with Office applications, an Outlook mail client, an encrypted flash drive, sync software to synchronize data from the work PC to the drive, and a VPN client if needed.

The setup and teardown benefit in the launch release was aimed squarely at contractors: workspaces could be stood up and torn down easily, which Ceedo said was especially useful for subcontractor and vendor environments and for reclaiming application licenses once a workspace was no longer needed.

Sandboxing and Isolation Claims — and Their Limits

Ceedo used the words "sandboxed," "secure workspace," "zero installation," and "isolation" freely. All of these are period marketing terms, and they need qualifying.

What the architecture genuinely provided. Because all file and registry writes were redirected into the virtual environment, virtualized applications did not modify the host's registry or program directories. Ceedo's employee-owned PC page described isolation from the employee's personal software and settings — registry, DLLs, file paths — and argued this cut support calls caused by conflicts with personal applications. The zero-installation and package-creator pages made a related and quite credible claim: sandboxing during packaging often resolved conflicts between applications sharing a workspace, the classic "DLL hell" problem. Ceedo also described its containment as preventing leakage through application logs, cookies, and temporary files.

What it did not provide. This was application-compatibility isolation, and calling it a security boundary is a much stronger claim than the architecture supports:

• The layer worked by hooking Win32 API calls in user mode. User-mode API hooking is a containment mechanism that code running at the same privilege level can potentially bypass — it is not a kernel-enforced boundary like a hypervisor or a Windows integrity level.
• Virtualized applications could read the host file system and host registry. Isolation was asymmetric by design, protecting the host from writes rather than protecting workspace data from the host.
• Nothing protected the workspace from the host. On a machine with a keylogger, a compromised kernel, or a malicious driver, a Ceedo workspace offered no defense — the host owned the keyboard, the display, the memory, and the network stack.
• The user-mode design that enabled "no admin rights" is the same design that made a strong security boundary impossible.

Ceedo's materials mention host checking before workspace launch, but no published independent security assessment of Ceedo Enterprise's isolation appears to survive. No source found for this article verifies Ceedo's sandboxing claims through independent testing. They should be read as the vendor's description of its own product.

Encrypted Portable Hardware

Ceedo's real security story was largely delegated to hardware partners, and the company was fairly candid that the encryption came from the drive rather than from Ceedo. Its business solutions page described Ceedo Enterprise as a remotely-managed secure virtual desktop environment carried on encrypted hardware.

Documented encrypted-hardware and security partners across the archived site include IronKey, MXI Security, RSA (the security division of EMC, announced March 2010), SafeNet, McAfee, and BlockMaster. The IronKey pages describe hardware-encrypted storage, advanced authentication, application verification, secure key management, and always-on AES 256-bit hardware encryption. The MXI pages describe multi-factor authentication validated in the device hardware itself — strong password, biometric fingerprint, or CAC/PIV card — with AES-256 hardware encryption unlocking applications and data after authentication.

These were integrations. The encryption, authentication, and key management were the hardware vendors' technology, not Ceedo's.

Application Updates and Synchronization

Keeping deployed workspaces current was the main ongoing justification for the management system. Documented mechanisms included remote update of the Ceedo client software itself, remote update of installed applications, remote installation and removal of applications, remote policy and settings changes, and remote addition or removal of files and forms — all applicable simultaneously to clients already in the field.

Ceedo also described automatic update-on-launch, with workspaces updated each time they were launched, and SmartPlay-based streaming that detected and downloaded application updates automatically and could replace corrupted or deleted components. Update control could be scoped at site and group level.

Data synchronization, as distinct from application updates, was handled outside the core product: the work-from-home page lists sync software as a separate bundle component for synchronizing data between the work PC and the USB drive.

Licensing and Historical Pricing

The pricing line in the June 2008 release reads that Ceedo Enterprise Clients were available immediately at $89 per seat perpetual license, with discounts available for large volume purchases.

This figure holds up better than a single-source claim. It appears in at least four places: Ceedo's own press release; the June 3, 2008 Virtualization.com report; Amy Newman's June 19, 2008 Datamation column; and again in the August 5, 2008 Citrix announcement, which priced Ceedo Enterprise for Citrix XenApp at the same $89 per seat perpetual license with volume discounts.

Two honest caveats. First, the trade reports are close paraphrases of the same press release, so this is really one primary source with corroborating republication, plus the independent recurrence in the later Citrix release. Second, $89 covered the client seat only. No archived source found for this article gives the price of the Ceedo Client Management System, the server-side components, support contracts, or the encrypted hardware — which in a real deployment would likely have dominated the cost. The comparison chart's note that Ceedo Enterprise offered a single license for multiple devices suggests seat-based rather than device-based counting, but the licence terms themselves do not survive in the archive.

Integrations: Citrix and Avaya

Neither Citrix nor Avaya owned, acquired, or developed Ceedo. Both were integration partners, and Ceedo remained an independent Israeli company throughout.

Ceedo Enterprise for Citrix XenApp

Announced August 5, 2008 over Marketwire, Ceedo Enterprise for Citrix XenApp virtualized and packaged the Citrix XenApp client — formerly the Presentation Server or ICA client — so it could run from any PC without installation and without administrative rights. Ceedo joined the Citrix Ready program, and the release states that compatibility of the XenApp Plugin for hosted applications with Ceedo's technology was demonstrated through Citrix's testing program. That is a compatibility verification, not an endorsement of Ceedo's broader security claims.

The practical scenario: administrators could launch XenApp directly from a web page, or users could carry the XenApp plugin on a portable drive and get access on locked-down machines — the release names internet cafés and hotel business centers. Applications published from the Citrix server appeared as large icons on the movable Ceedo Menu Bar, and users could add personal applications alongside XenApp. Ceedo's later partner page extends OS support for this integration to Windows 2000, XP, Vista, 7, and Server 2003.

Avaya Secure Portable Office

Sources here are noticeably thinner, and this section should be read with more caution than the rest. No Ceedo or Avaya press release about this partnership was recovered for this article, and it does not appear in Ceedo's archived press room index.

What surviving third-party product documentation indicates is that Avaya's Secure Portable Office (SPO) was a USB-based remote access solution providing VPN gateway access from a public or private PC, with the drive protecting corporate data and preserving the host PC's configuration. Application Virtualization by Ceedo appears in Avaya reseller catalogs as separately licensed functionality used in conjunction with SPO, requiring one licence per pen drive.

That is consistent with Ceedo's general OEM pattern — supplying the application virtualization layer inside another vendor's secure USB product, as it did with IronKey and MXI. But the primary announcement material has not survived in an accessible form, and the exact dates, product versions, and scope of the Avaya relationship could not be confirmed.

Comparison With VMware ThinApp and Microsoft App-V

Ceedo Enterprise arrived at a crowded moment. Microsoft had acquired Softricity in July 2006 and was rebranding SoftGrid as Microsoft Application Virtualization (App-V) around 2008; VMware shipped ThinApp 4.0 in 2008. Ceedo was much smaller than both.

Packaging. This was Ceedo's clearest differentiator. App-V required sequencing and ThinApp required a capture-and-build step, both performed by trained staff on clean reference machines. Ceedo's Setup Virtualization Engine claimed to work directly from the vendor's original setup files with no separate packaging phase — and, unusually, permitted end users to add applications themselves under policy. Contemporary reporting on the launch highlighted exactly this contrast, noting that competing products' sequencing could take days for some applications.

Workspace versus single application. ThinApp's model centered on producing an isolated, often single-executable package per application. Ceedo virtualized a set of applications into one workspace with a cross-application bus letting them interact — closer to a portable application environment than to independent packages.

Isolation depth. Ceedo was purely user mode, with no drivers and no services, which is why it needed no admin rights but also why applications requiring their own Windows services or kernel drivers were out of reach. Competing solutions of the era generally used system-level components and correspondingly had broader application compatibility.

Portability emphasis. Ceedo's orientation toward USB and encrypted portable hardware had no real equivalent in ThinApp or App-V, which were oriented to corporate networks and managed desktops. Newman's "device-heavy" characterization in Datamation captures this — a differentiator and a limitation at once.

Market position. Ceedo's absence from Virtualization.com's June 2008 comparison chart, and the general scarcity of independent enterprise evaluations, indicate it never achieved the analyst standing of the larger vendors. Xenocode (later Spoon) occupied a somewhat similar niche of lightweight, low-friction application virtualization; a direct period comparison between Ceedo and Xenocode was not found for this article.

What Happened to Ceedo Enterprise

The archived record shows the product continuing to evolve for a few years past launch. Copyright lines advance from 2008 to 2011, the management tooling is reorganized into CCMS plus Ceedo Enterprise Manager plus Ceedo Package Creator, partner integrations expand to McAfee, SafeNet, and BlockMaster, and the marketing repositions from "application virtualization" toward "workspace virtualization" and an explicit VDI alternative pitch. Windows 7 support appears on later pages.

Then the enterprise virtualization line fades. Per Ceedo's Wikipedia entry, the company went through a hiatus and resumed operations in 2016 with its focus switched to cybersecurity, building on the same containerization technology — the later products being MalwareLocker, the Ceedo Cloud Management System, and CeedoVault. Startup database listings state that Ceedo Technologies ceased to operate in January 2020, though this article found no primary announcement confirming that date.

The broader market moved on. Portable workspaces on USB drives were overtaken by cloud-delivered applications, browser-based software, VPN and VDI maturity, and eventually widespread laptop provisioning — which removed most of the cost pressure Ceedo was built to relieve. The specific problem Ceedo Enterprise solved so neatly in 2008, delivering a managed Windows application environment to a PC you did not control, is now generally handled by SaaS, virtual desktops, or managed-device programs.

One caution for anyone researching this history: the ceedo.com domain no longer belongs to Ceedo Technologies, and material published on it today — including this page — is not an original Ceedo Technologies document. This article is a historical reconstruction assembled from the archived sources cited throughout, not a surviving vendor page.

Frequently Asked Questions

Was Ceedo Enterprise a virtual machine?

No. Ceedo Enterprise had no guest operating system, no hypervisor, and no emulated hardware. It virtualized the application layer only — primarily by redirecting file system and registry writes — and ran on top of the host's existing Windows installation. Ceedo promoted this as an advantage, arguing it avoided the OS licensing cost and disk footprint of full virtualization.

What exactly did Ceedo virtualize, and what did it not?

It virtualized file system and registry access for applications inside the workspace, via a Virtual File System and Virtual Registry, plus inter-application plumbing so those applications behaved as one environment. It did not virtualize the kernel, drivers, the display or graphics stack, the network stack, CPU, RAM, or printers — all of those came from the host PC, which Ceedo's own documentation stated openly.

What was the Ceedo Setup Virtualization Engine?

It was the component that let administrators virtualize an application using its ordinary Windows installer instead of a separate packaging or sequencing process. In Install Mode, Ceedo hid the host's existing DLLs from the setup program so the installer was forced to copy a complete set of dependencies into the virtual workspace, making the result self-contained and portable.

How much did Ceedo Enterprise cost?

The June 2008 announcement priced Ceedo Enterprise Clients at $89 per seat as a perpetual licence, with volume discounts. The same $89 figure appears in the August 2008 Citrix XenApp announcement and in contemporary trade coverage. That price covered the client seat only; no surviving source gives pricing for the management server, support, or the encrypted hardware.

Which Windows versions did Ceedo Enterprise support?

The 2008 materials cite Windows 2000, XP, Server 2003, and Vista. Later partner documentation adds Windows 7. The product page from December 2008 lists Windows 2000, XP, and Vista, while the launch release and comparison chart also include Server 2003 — a minor inconsistency across Ceedo's own pages.

Was Ceedo Enterprise actually secure?

Ceedo described the workspace as sandboxed and isolated, and the write-redirection design did genuinely stop virtualized applications from modifying the host. But this was user-mode API hooking, not a kernel-enforced security boundary; workspace applications could read host files and registry keys; and nothing protected the workspace from a compromised host. No independent security evaluation of Ceedo Enterprise was found for this article, so the isolation claims should be treated as vendor statements rather than verified behavior. Data-at-rest security came mainly from partner encrypted drives.

Did Citrix or Avaya own Ceedo?

No. Ceedo Technologies was an independent Israeli company. Citrix was an integration partner — Ceedo joined the Citrix Ready program and shipped Ceedo Enterprise for Citrix XenApp in August 2008. Avaya appears to have licensed Ceedo's application virtualization as an add-on to its Secure Portable Office USB product, though the primary documentation for that relationship is sparse.

Could Ceedo Enterprise run any Windows application?

No. Because it ran entirely in user mode with no drivers or services, it could not virtualize applications that required installing their own Windows service or kernel-mode driver. Independent user reports from the period describe success with older Office and Photoshop releases and failure with newer versions that depended on services. This was an architectural consequence of the same design choice that let Ceedo run without administrator rights.

Did Ceedo Enterprise work offline?

Direct 2008 documentation on this is thin. A later Ceedo page comparing the product to VDI states the workspace allowed users to work offline or online. The architecture supports that: applications ran locally on the host CPU against a local virtual file system, so execution needed no network. Connectivity was required for management functions — remote updates, application streaming, and policy changes.

Is Ceedo Enterprise still available?

No. It is a discontinued product from a company that is no longer operating. Ceedo shifted to cybersecurity products after resuming operations in 2016, and startup databases record the company as having ceased operating in January 2020. This page is a historical restoration, not a product listing.