Technology changes. The need to make it easier to work with does not.
Twenty-five years is a long time in workplace technology. Operating systems change. Infrastructure moves from server rooms to cloud platforms. Employees stop working from one fixed desk and begin signing in from offices, homes and devices that may never touch the company network.
Products built for these environments have to change with them. The useful ideas underneath them do not always need to.
This year marks 25 years of Scense and five years of worXpace. They were created in very different technological eras, but both began with the same principle: people should receive the workspace they need to do their jobs, while administrators retain control over how that workspace is delivered and maintained.
The technology has changed considerably. The vision has not.
Before “workspace orchestration” had a name
When Scense began in 2001, the typical business workplace looked very different.
Most employees had an assigned desk, worked in the office throughout the week and attended meetings in rooms rather than through an on-screen grid of slightly tired faces. Hot-desking was not yet a default operating model, hybrid-working policies were rare, and nobody had to book a desk through an app before being allowed to sit at it.
There were no company-wide discussions about camera etiquette, collaboration status messages or whether a calendar block marked “focus time” should be treated as legally binding. Even the clean-desk policy was usually about tidiness, rather than ensuring the next person could occupy the desk without discovering someone else’s mug, cables and abandoned candy bar.
The workplace was simpler in some respects. It was also far more dependent on the office, the local network and the particular computer sitting on that particular desk.
Windows desktops were connected to a local domain, applications were installed or published from the company network, and the server room was quite literally a room. Remote working existed, but it had not yet become the default subject of every IT strategy meeting.
Managing a user environment often meant combining logon scripts, installation tools, policies and custom code. Each component could perform its own task perfectly well. The difficulty appeared when they all had to produce one consistent workspace.
One tool installed an application. Another created its settings. A script added a shortcut. Something else was expected to remove everything later.
Scense introduced a more structured approach. Instead of treating applications, settings and workspace actions as unrelated technical changes, it allowed administrators to manage them as parts of the user’s working environment.
The result was a system designed not merely to place resources on a computer, but to determine what should be available, to whom and under which circumstances.
Scense grew with the Windows workplace
Over the following 25 years, the workplace changed repeatedly.
Physical desktops were joined by laptops, terminal servers and virtual desktops. Application virtualization became common. Employees started working from more locations, on more devices and through increasingly complex combinations of infrastructure.
Scense evolved alongside those environments.
Today, Scense is still does what it’s good at as the on-premises workspace-management solution. It operates from an organization’s own data center and is well suited to environments centered on Windows Active Directory.
A workspace is not static. A person changes roles, joins a group, leaves a location or starts using another device. A managed environment must therefore do more than create something once. It must continue checking whether that item still belongs there.
Scense was built around that continuing relationship between the user, the device and the resources being delivered.
Then the workplace left the building
By 2021, the assumptions behind workplace management had changed considerably.
Users were no longer reliably located on the company network. Devices could be corporate, virtual or personally owned. Identity services were moving towards the cloud, and administrators increasingly expected to manage environments through a browser rather than through software tied to a particular management workstation.
The challenge itself had not disappeared. It had simply escaped the building.
WorXpace was developed to take the same workspace-management principles into a cloud-first model.
Rather than requiring the main management infrastructure to run in the organization’s data center, worXpace is operated as a cloud service. From there, it can serve devices in the office, at home or elsewhere in the world. It is positioned particularly for environments using Microsoft Entra ID (previously Azure Active Directory) and for organizations with distributed users or significant use of employee-owned devices.
The starting point changed. The objective did not.
Five years of worXpace
During its first five years, worXpace has developed into a platform combining workspace management and application delivery.
It can deliver applications from cloud storage, analyze installation packages and turn supported package formats into managed applications. These applications can then be included in compositions and assigned to the appropriate people or devices. Its management layer continues monitoring installation and removal, rather than considering the job complete as soon as setup.exe closes.
worXpace also applies the management model to the wider workspace. Applications, settings, printers and other resources can be delivered according to the person’s needs, without requiring every user to work in an identical environment.
Even thoug the system is cloud-based, the changes can be sent to connected workstations in real time. Administrators can manage the environment through a browser, inspect runtime activity and enforce application access based on assignment.
This makes the operating model straightforward:
- If an application belongs to a user, it can be made available.
- If the assignment changes, the workspace can change with it.
- If the person moves between supported devices or locations, the same management logic continues to apply.
- If an application requires supporting actions, those actions remain part of its managed lifecycle.
The application is no longer merely “something that was installed.” It remains an actively managed part of the workspace.
Two products, one continuing vision
Scense and worXpace represent two generations of the same workspace-management philosophy.
Scense remains an important part of many established customer environments. These organizations rely on it to manage complex Windows and Active Directory workplaces, often with years of carefully developed configurations, integrations and operational knowledge behind them.
worXpace carries the same underlying vision into a cloud-first architecture. It is designed for organizations adopting cloud identity, distributed working and internet-connected management, as well as for new implementations that need to fit this operating model from the start.
The relationship between the two products is therefore not a simple old and new. Scense continues to serve the customers and environments built around it, while worXpace represents the platform in which Appixoft is servicing the next generation of workspace orchestration.
Different stages, different architectures, but a clear line of continuity of vision between them.
The vision connecting 25 years and five years
Products change because the environments around them change.
Over 25 years, Scense has moved through multiple generations of Windows, application-delivery technology, virtualization and workplace architecture. During the first five years of worXpace, cloud identity, hybrid work, device diversity and real-time management have become routine requirements rather than unusual edge cases.
Yet the underlying challenge remains recognizable.
People need the right resources to do their work. Administrators need a manageable way to provide them. Access must follow organizational rules, while the user experience should remain personal and predictable.
Appixoft describes this history as a continuing effort to remove limitations for both administrators and users. Scense first brought that vision to life through structured management of user environments. worXpace builds on the same foundation while removing the requirement for heavy on-premises infrastructure and making workspace orchestration available across locations and devices.
That continuity is the real significance of these anniversaries.
Scense has spent 25 years proving that the workspace should be managed as a whole.
worXpace has spent five years showing that the same principle works from the cloud.
The technology underneath will continue to change. Ideally, the user will notice very little.
The right application appears. The workspace behaves as expected.
Scense laid the foundation, and worXpace continues the careful balance between a flexible user experience and firm administrative control.