Table of Contents

Races | Technology | Buildings & Organizations

NEW KOUROU ROBOTICS SYNDICATE (NKRS)

Overview

The New Kourou Robotics Syndicate (NKRS) emerged in the immediate aftermath of the crash landing (Day Zero) as a critical institution for Exohuman survival and recovery. With most robotic units destroyed or damaged during the crash, NKRS was founded to restore, maintain, and manage the remaining Service Bots — including agricultural, manual labor, and domestic models. Unlike the military-focused Guarding Bots as well as Medical Bots, which were excluded from their purview, NKRS focused on essential civilian robotics.

By offering bots on a rental and maintenance basis, NKRS introduced a subscription-based system to ensure fair access to limited robotic resources while securing control over the highly sought - after Quantum Fusion Batteries (QFBs) required to power them.

History

Origins Aboard the Last Frontier

On the Last Frontier, Service Bots were a standard part of daily life — accessible to all passengers regardless of status. These bots supported manual labor, medical services, housekeeping, room service, and logistical management. The vast majority of physical tasks were handled by bots, freeing Exohumans to focus on education, science, and cultural development.

The Crash Landing and Survival Phase (2624–2625)

The crash devastated the bot fleet: Of the original 520 units, only 263 survived the impact and subsequent fires. These remaining Service Bots became essential tools in the settlers' early survival—used for shelter construction, resource extraction, basic farming, and emergency healthcare.

To stabilize recovery efforts, the newly formed Free State of Settlers declared the surviving Service Bots state property, recognizing them as critical infrastructure. However, the Free State, still in its infancy, lacked the administrative structure to oversee large-scale maintenance, distribution, and technical support.

To solve this, the Free State issued a special operational license to Dr. Elora Venn, allowing her to found the New Kourou Robotics Syndicate (NKRS) in late 2625. The NKRS was officially recognized as the exclusive service and distribution partner of the state for non-military or medical Service Bots.

Dr. Venn built her team by recruiting engineers, surviving AI technicians, and data recovery experts from the crash. Her organization took over maintenance, repair, and subscription-based distribution of Service Bots, ensuring settlers across VOI 700 D had continued access to robotic labor despite the post-crash limitations.

The Beta Age: Limited Supply and Strategic Control

As Exohumans lacked the capacity to manufacture new QFBs, the existing battery supply became a strategic resource. NKRS quickly monopolized access to QFBs for civilian bots, asserting control over distribution and replacement. This led to rising tensions between settlers, especially in fringe settlements who felt neglected.Settlers could only use Service Bots by subscribing to the NKRS, receiving scheduled maintenance, firmware updates, and limited usage quotas based on available energy.

NKRS constructed 100 additional Service Bots using salvaged ship components, repurposing scrap materials to meet planetary needs. These units were hardier, built to withstand planetary conditions such as mud, wind, and temperature fluctuation.

Despite limited resources, NKRS introduced a rotating distribution model — some farms and facilities would receive bot support on weekly cycles, ensuring that labor was spread across multiple settlements. However, disputes over energy allocation and service priority created a black market for bot power cells and off-grid repairs.

The Gamma Age: Ban and Underground Survival

With the formation of the Federal Confederation after the Great War, the use of Service Bots was officially banned under the terms of the Peace Treaty, which placed strict limits on energy consumption to ensure planetary sustainability.

Legacy and Impact

Tactical Advice for Dungeon Masters

Further information about the respective Service Bot-models: