The proposed EU Space Act puts mission evidence into the business plan
The proposed EU Space Act linked access to Europe's space market with safety, cyber resilience and environmental assessment. For operators and suppliers, the implications began with mission design and the cost of documenting it.
A satellite’s business plan extends beyond its launch. Its operator has to keep control of it, avoid collisions, protect the service it delivers and account for the end of its mission. On 25 June 2025, the European Commission proposed a common framework for the safety, resilience and sustainability of space activities. For operators funded by venture capital and their suppliers, the proposal connected those engineering decisions to the conditions for serving a European market.
The EU Space Act still required negotiation by the European Parliament and Council, and its provisions could change. That limited what a founder could promise about future legal obligations. It nevertheless set out the Commission's intended approach for investments whose hardware, supplier contracts and operating architecture might be fixed years before a mission began earning revenue.
The market problem was partly administrative
The Commission identified a patchwork of national approaches as an obstacle to space activity across national borders. Its impact assessment described duplication and potential conflicts between licensing requirements, alongside uneven treatment of safety, cybersecurity and environmental effects. The proposed European framework aimed to establish a more consistent baseline, including for non-EU operators providing space services in Europe.
Scroll to view all columns
| Comparison | Proposal’s focus | Business evidence it would draw on |
|---|---|---|
| Safety | Tracking, collision avoidance and reducing new debris. | Mission trajectory, position-data arrangements and an end-of-life plan. |
| Resilience | Cybersecurity and risk assessment over the mission lifecycle. | Command access, supplier dependencies, recovery procedures and incident records. |
| Sustainability | Comparable assessment of environmental effects. | Documented materials, manufacturing, launch and operational assumptions. |
The Commission's proposed safety, resilience and sustainability requirements would draw on different parts of mission planning and engineering.
A common baseline could matter to a small company expanding across several markets. Repeating an assessment for every jurisdiction consumes specialist time that cannot also be used to build and operate a service. The proposal itself did not provide an operating licence. A startup still needed to understand the authorisations, customer contracts and national requirements governing its actual mission while evaluating how the new framework might alter later ones.
A service promise depended on control of the whole mission
The proposal’s safety measures included minimising new debris, sharing satellite position data and using collision avoidance services. These were operational issues as well as environmental ones. A mission’s remaining fuel, ability to manoeuvre and arrangements for receiving warnings could affect how much useful service it could deliver. A forecast of recurring data revenue needed assumptions about those interruptions and the resources available to respond.
Planning for the end of a mission also affected its initial design. Disposal capability, remaining power and the reliability of command links could become difficult to change after launch. For a component supplier, the commercial case could lie in demonstrating that its equipment supported a mission requirement under realistic conditions. A laboratory result alone would not establish the reliability of an integrated spacecraft, particularly where the customer needed evidence across several suppliers.
The Commission proposed tailored cybersecurity requirements and risk assessment throughout the mission lifecycle. A space service includes ground stations, mission software, communications links and the organisations authorised to send commands. The operational implication was that a secure spacecraft component could still sit inside a vulnerable service if an attacker could compromise credentials or an associated ground system.
For a young operator, incident response had to fit a mission with limited opportunities for physical intervention. Revoking access, restoring trusted software and maintaining command capability deserved attention before a customer depended on the output. Cybersecurity suppliers could contribute useful tools, but they needed to work within the mission’s bandwidth, latency, power and staffing constraints. A conventional enterprise product could require substantial adaptation before it became suitable for space operations.
Environmental records required work across the supply chain
The proposal sought a common method for assessing the environmental effects of space activities. Its factsheet described lifecycle assessment and shared databases. For an operator, a credible assessment would depend on information from manufacturing and launch partners as well as the spacecraft itself. Its assumptions needed enough detail for customers and authorities to examine and compare them.
The impact assessment acknowledged a cost. It estimated that the binding measures in its preferred option would increase manufacturing costs by 3–10% against the baseline, depending in part on existing practices. The estimate described the proposal's expected effect; actual costs would vary across companies. The assessment also expected administrative savings and operational benefits from a more consistent framework. A financial model needed to account separately for the costs, administrative savings and operational benefits, each of which depended on different assumptions.
The investable work preceded the final rulebook
The Commission proposed proportionate treatment and support for smaller businesses. A startup could prioritise preparations that already improved its mission: dependable command controls, traceable component evidence, a credible disposal strategy or better records of environmental inputs. Those capabilities could also support customer and insurer discussions even while the legislative process remained open.
For investors, the proposal sharpened the relationship between technical milestones and financing. A successful launch would not, by itself, establish a resilient operating business. The company needed sufficient capital and staff to demonstrate mission readiness, maintain the service and manage its eventual conclusion. The investment case needed to connect those costs and responsibilities to what customers would pay for a reliable service, while distinguishing proposed obligations from requirements already in force.
Investment implications
- The proposal set out common requirements while national authorisation systems remained in place.
- Safety and cyber resilience needed to be designed into the mission before launch, when changes remained practical.
Sources
Published
