A familiar desktop with an original identity
Moving to a new operating system should not mean that employees have to learn how to use a computer all over again.
PhoenixCore OS is being designed with a modern KDE-based graphical environment that preserves the familiar logic of Windows 10 while developing its own visual style and organisation.
A Start menu, taskbar, system tray, convenient file manager, notifications and integrated search are planned.
An interface organised around work, not technical complexity.
Users will be able to find the tools they need through logically organised categories for documents, internet, email, business applications, communication and technical support.
Quick search is designed to bring together applications, files, settings and available organisational resources.
The visual identity of PhoenixCore OS is built around the symbol of the phoenix — a symbol of resilience, renewal and recovery.
Status: The graphical concept and visual design are in development. The final interface is yet to be integrated and tested.
Two working environments — employee and administrator
PhoenixCore OS is designed with a clear separation between ordinary day-to-day work and system administration.
PhoenixCore User will provide a simplified and consistent working environment. Employees will see the applications and actions required for their role, without the interface being overloaded with system settings and development tools.
PhoenixCore Admin will provide advanced functions for authorised IT staff, including diagnostics, configuration, system update management, recovery and technical maintenance.
Specialised profiles are also planned for activities with heightened requirements, such as accounting, financial operations, banking services and work with electronic authentication devices.
Every employee will use their own user profile, with separated permissions and access control.
Intelligent kernel management
One of the main areas of current engineering work is the management of the Linux kernel, system boot and recovery after failed operations.
PhoenixCore OS is designed so that normal updates preserve the ability to use a fallback installed kernel version.
System health checks, controlled application of updates and protected recovery procedures are planned.
During normal daily work, employees will not be burdened with technical menus for choosing a kernel or with complex recovery operations.
The system architecture provides dedicated administrative access to these functions.
The main goal is resilience against system failures and the ability to recover without unnecessary data loss.
Status: This is a system component under active development. Its final reliability will be assessed after integration and real-world fault-tolerance testing.
Centralised and controlled updates
PhoenixCore OS will use a centralised infrastructure for distributing system and enterprise updates.
We plan digitally signed packages, management of different update channels and separation of common system components from specialised administrative tools.
This allows different organisations to receive the components appropriate for them, without all workstations being treated the same way.
IT departments will be able to plan and control updates, track the results and respond when problems are found.
The system is being designed with care for cases where an update is interrupted, a package turns out to be incompatible or there is insufficient space for system files.
The goal is not simply to install new versions, but to ensure predictable management of the entire system lifecycle.
PhoenixCore IT Sentinel — an intelligent assistant for IT professionals
One of the planned development directions is PhoenixCore IT Sentinel — a specialised artificial intelligence system for technical diagnostics and system support.
It is intended for authorised system administrators, not as a chatbot for employees' everyday tasks.
PhoenixCore IT Sentinel is being designed as a centralised service that will be able to analyse permitted diagnostic data from workstations and help IT staff identify problems.
Planned capabilities include analysis of system errors, device health, driver issues, package compatibility, recurring failures and information about security updates.
The system will be able to suggest possible solutions and help technical specialists determine the cause of a given problem.
Control remains in the hands of the IT department.
Potentially risky actions will require authorisation and will be carried out through controlled system mechanisms.
PhoenixCore IT Sentinel is not intended for monitoring employees' personal correspondence, documents, keystrokes or daily activity.
The operating system will be able to function independently of the availability of the AI service.
Status: Conceptual and architectural planning. Development and pilot testing are yet to come.
Remote technical support
PhoenixCore OS provides for its own remote technical support environment, designed for corporate and institutional networks.
The goal is for IT departments to be able to help employees without every technical intervention requiring a physical visit to the workplace.
Support for Linux and Windows workstations, access management and the option for organisations to use their own server infrastructure are planned.
Access must be authenticated and controlled, with a clear distinction between the rights of the employee and the rights of the technical specialist.
Moving from Windows to PhoenixCore OS
One of the main challenges organisations face is migrating from an existing Windows environment to a new operating system.
That is why development includes the concept of PhoenixCore Migration Assistant — a tool to help technical specialists transfer user data and settings.
Mechanisms are planned for detecting existing Windows installations, recognising separate drives with user files and the controlled transfer of selected directories.
Particular attention is paid to computers that use an SSD for the operating system and a separate HDD for business data.
The source data must be preserved until successful migration is confirmed.
Migration will not be treated as simple file copying, but as a controlled process with verification and the ability to recover.
Email and office compatibility
PhoenixCore OS is aimed at real business processes, where compatibility with files already in use is critically important.
Integration with office applications for word processing, spreadsheets, presentations and PDF documents is planned.
Special attention is paid to exchanging files with Microsoft Office, including documents with complex formatting and spreadsheets.
Among the planned migration capabilities is transferring email from Microsoft Outlook to Thunderbird, including working with existing mail archives where the format and available data allow it.
Compatibility will be verified in practice. It is not assumed in advance that every document or format will be reproduced identically.
Qualified electronic signatures and authentication devices
For many organisations, the electronic signature is not an add-on feature but a daily necessity.
As a direction of development, PhoenixCore OS includes support for qualified electronic signatures, smart cards, USB tokens and the corresponding authentication software.
Among the solutions under consideration are StampIT and BORICA B-Trust, which are used in Bulgaria.
The goal is to study and verify real working scenarios, including signing PDF documents, working with official portals, browser integration and the use of authentication devices.
Support will depend on the specific devices, drivers and software components, and compatibility will be confirmed through testing.
Organisational applications and phone directory
PhoenixCore OS is being designed so that each organisation can receive its own set of business tools and resources.
Among the planned applications is a centralised staff phone directory providing information about departments, employees and internal extensions.
Organisational data will be updatable independently of the core operating system, through controlled distribution mechanisms.
Quick links to internal portals, information systems, administrative services and technical support centres are also planned.
In this way, the employee receives a ready-made working environment tailored to the specific organisation.
Printers, peripherals and local devices
PhoenixCore OS will pay special attention to the peripherals that organisations use every day.
This includes printers, scanners, external storage, network devices and specialised equipment, insofar as the necessary drivers and integrations allow.
A clear mechanism for safely removing USB devices is planned, with confirmation once the necessary write operations have completed.
Specific compatibility profiles will be built and tested for printers and other specialised devices.
Running on modern and older hardware
PhoenixCore OS is being developed with the idea that organisations should not necessarily have to replace all of their equipment in order to move to a modern working environment.
One of the goals is to support computers from the Windows 10 generation, including systems with older processors and limited hardware resources.
At the same time, the architecture must allow the use of more powerful workstations and specialised configurations.
Mandatory TPM 2.0 is not a baseline requirement in the current concept, although available hardware security features can be used.
Actual minimum and recommended system requirements will be published after hardware testing.
A distinct look for every organisation
One of the key ideas behind PhoenixCore OS is the ability of a single technology foundation to serve different institutions and enterprises.
It is planned that an organisational profile can be selected during installation or initial configuration.
It will determine the applicable settings, the available business resources, the visual identity and certain administrative policies.
In this way, different organisations will be able to use the common technology platform without the need to develop an entirely separate operating system for each of them.
Enterprise server and licensing
PhoenixCore OS provides for its own system for managing enterprise licences and authorised installations.
The installation media will be usable for deploying the system on different devices, while access to licensed enterprise features will be controlled separately.
Organisational licences for authorised internal infrastructure are being considered, as well as individual licences for remote business devices.
Management is planned to be carried out through a specialised server service and a centralised activation infrastructure.
Final commercial terms will be presented in preparation for public distribution.
Independence from a permanent internet connection
The core functions of PhoenixCore OS are being designed so that they do not require a permanent connection to external cloud services.
Everyday work with local files and applications must remain possible even during a temporary loss of internet access.
Centralised services, updates and enterprise management will use network connectivity as needed, but must not become a mandatory condition for the operating system to start normally.
Security and information protection
Security is a guiding principle in the architecture of PhoenixCore OS.
The project provides for separation of administrative rights, protection of system settings, authentication of updates, controlled recovery and careful management of user data.
Development places emphasis on preventing damage resulting from interrupted system operations and faulty updates.
The technology solutions will be subjected to resilience testing, including simulations of adverse conditions and attempts to breach system policies in isolated test environments.
Development and testing
PhoenixCore OS is a real software project in development.
Current engineering work is focused on core system mechanisms, kernel management, installation integration and protected recovery processes.
Once the relevant integration stages are complete, large-scale testing in virtual environments will follow.
Behaviour will be tested in cases of interrupted installations, failed updates, system component failures, corrupted configurations and other critical scenarios.
The aim of these tests is to find and fix defects before moving to wider use.
Reliability and security will be assessed on the basis of practical evidence, not solely on successful automated checks.
An open foundation, our own technology development
PhoenixCore OS uses Debian GNU/Linux and other open-source components, complying with their applicable licences.
Our own development is focused on integration, system mechanisms, enterprise tools, user experience, organisational services and the future commercial platform.
In this way, the project combines the advantages of free software with the development of specialised solutions for professional use.
PhoenixCore OS
EN
FilesDocuments and folders
DocumentsWrite and review
SoftwareApproved apps
