Plaszma OS is a full-featured operating system that enables applications to take advantage of the ZMS processor's media-processing capabilities. A multi-tasking operating system, Plaszma OS supports a rich set of industry standard APIs, CODECs, Web 2.0 browser, 2D/3D graphics, audio and a multi-touch gesture user interface. Plaszma SDK provides developers with the tools, libraries, documentation and samples needed to create the next generation of media-rich networked applications. Plaszma OS runs on a range of Plaszma development platforms, including the Zii EGG.

There is no hierarchical structure in the Plaszma OS Cell Framework. Instead, the Cell Framework APIs communicate with the Plaszma Core Software. This abstraction ensures changes in the underlying hardware do not affect applications. At the same time, it allows applications to benefit from the native 'close-to-the metal' acceleration. The API library is an important part of the Plaszma OS. Organized into Cells, Plaszma OS libraries enable access to the powerful features of the Plaszma hardware platform and ZMS processor. Each Cell contains a group of related libraries and APIs that make it easy to identify components required to build an application. Where possible, the libraries are based on widely used, industry-standard APIs and developer accessibility to the Cell Framework APIs. The Plaszma Core Software has two functions: it drives the underlying media-processing array through highly optimized low-level libraries and makes calls to the underlying Linux drivers and services. Applications employ the Applications Cell and Graphics Cell to integrate with the Plaszma Desktop and User Interface. The remaining Cells provide access to core features such as HD media playback, 3D acceleration and network services.

The Plaszma application user interface is based on one or more windows containing UI components or widgets. A standard set of widgets is included in the UI toolkit for a unified look and feel across applications—specifically, applications with user interaction handled by the event mechanism. Non-code resources such as images and text tap on the supplied resource manager and compiler, providing localization support, easing resource management.