Phoenix Initiative / PNXI

The origins of the Phoenix Initiative trace back to the year 2438, fifty-eight years after the transition from the UNE to the UEE. Humanity’s first contact with the Banu reshaped the political landscape and forced the Empire to confront a new reality: threats beyond human space were no longer theoretical. The Imperial Senate shifted its strategic priorities accordingly, placing long-term external defense at the forefront of policy and military planning.

Five centuries later, in the aftermath of the Siege of Tiber, three UEE Marines witnessed firsthand how strained the Empire’s defensive structures had become. Their concerns were confirmed months later in the Virgil System, where collapsing front lines made it evident that the system, along with its billions of civilians, could not be saved. Confronted with these failures, the Marines left the UEE Marine Corps and founded what would become the Phoenix Initiative, a private military company designed to provide disciplined, rapid-response support where the Empire’s own forces were overstretched.

The Phoenix Initiative opened its first training camp on Vega III in 2944, establishing its headquarters adjacent to the local residential zone. Due to Vega’s classification as a high-risk system, contracts from the UEEN followed quickly. When the Vanduul launched their assault on Vega II on 04.10.2945, the Phoenix Initiative deployed under direct UEEN tasking, supporting both planetary and naval defense.

Siege of Vega II

During the Vanduul offensive on Vega II, the Phoenix Initiative was pushed to the front much earlier than anticipated. In a critical engagement, the PMC intercepted and disrupted a Vanduul spearhead advancing toward the planetary defense grid. The result came as a surprise to the UEEN Admiralty, given the PMC’s limited materiel and lack of reinforcement options. The success temporarily relieved the overextended planetary defenders, allowing them to reorganize positions, reinforce vulnerable sectors, and evacuate key civilian zones. For several hours, Phoenix Initiative forces held the line against continuous assaults, stabilizing a sector that had been moments from collapse.

However, the wider situation continued to deteriorate as Vanduul pressure intensified. The gains achieved by the PMC were soon overtaken by the scale of the enemy offensive. When the UEEN ordered a full withdrawal of naval and ground units, the Phoenix Initiative was assigned to cover the retreat. Operating with depleted strength and no incoming support, the PMC maintained its position long enough for the evacuation to succeed. The cost of this action was severe: two-thirds of the Phoenix Initiative’s carrier fleet were destroyed, and many of its most experienced personnel were lost.

Following Vega II, the Phoenix Initiative reassessed its operational doctrine. While rebuilding its strength, it shifted its focus toward reconnaissance, intelligence gathering, and long-range communications, roles that allowed the PMC to remain operationally effective despite its losses.

A New Beginning

Eight years after the fall of Vega II, the Phoenix Initiative has rebuilt its capabilities and restored its reputation among the displaced Vega population and regional administrations. The PMC once again operates under formal UEEN contracts, supporting crisis response operations such as those conducted during the Siege of Orison in the Stanton System and contributing to anti-piracy and anti-crime campaigns across multiple sectors.

Identity

With more than a decade of operational history, the Phoenix Initiative operates as a strictly hierarchical private military company. All members are required to follow lawful orders issued by authorized superiors, and the PMC maintains neutrality toward all external entities except the UEE and UEEN, to whom it is contractually bound.

Members may act independently when circumstances require it, and they are authorized to request PMC support, provided the request is coordinated with the appropriate command authority. Leadership personnel exercise active command responsibility and ensure that directives remain aligned with the PMC’s operational standards and regulations.