top of page

What Would the Universe Miss if Space Guardian Didn’t Exist?

Akshata S
Nov 4
7 min read

In November 2024, the three founders of Space Guardian, Jernej, Janez, and Luka signed up for the CASSINI Hackathon in Maribor, primarily for the experience. None of them had a background in space, and all three were already employed elsewhere.


As they explored the challenge, they noticed that satellite operators still relied on emails and phone calls to coordinate who should move when two satellites were on a potential collision course. Despite the consequences of a collision, the process for agreeing on an avoidance maneuver remained largely dependent on communication between operators.


The team won first place in Slovenia and at the European level. A few months later, what had started as a weekend project became a funded company.


The founders brought complementary expertise to the problem. Luka Zlatečan, CEO of Space Guardian, spent ten years building software-as-a-service (SaaS) products, Jernej worked on control and simulation, and Janez focused on artificial intelligence (AI). Together, these skills provided a foundation for addressing a challenge that involved software, automation, and coordination.


Their motivation was rooted in a practical question. If satellite operators already knew that collision risks existed, why was the process of coordinating their responses still so difficult?


The Challenge Beyond Collision Warnings

Avoidance maneuver planning: options ranked by risk and fuel cost before execution.
Avoidance maneuver planning: options ranked by risk and fuel cost before execution.

Space Guardian's starting point is a gap between identifying a potential collision and agreeing on what to do about it.


When a collision warning is issued, each operator receives the information, but deciding who should maneuver can still involve emails and phone calls. Luka points to an incident from 2019 involving the European Space Agency's (ESA) Aeolus satellite and a SpaceX Starlink satellite, which were on a collision course.


ESA attempted to contact SpaceX, but a bug in SpaceX's paging system meant that nobody saw the message. ESA consequently moved its satellite alone.


At the time, there were only a few thousand satellites. ESA projects that the number could reach 100,000 by 2030.


For Space Guardian, this raised a question about whether existing coordination practices can accommodate a much larger satellite population. As the number of satellites increases, operators must continue to address potential collisions and determine how avoidance decisions should be made.


The company's approach is designed to cover the stage that follows a warning. Rather than stopping at identifying a possible collision, Space Guardian aims to help operators agree on who moves, who pays for the maneuver, and how the maneuver is carried out.


Who Pays for Avoiding a Collision?

Space Guardian dashboard: an operator's satellites, collision risks and live activity in one view.
Space Guardian dashboard: an operator's satellites, collision risks and live activity in one view.

One of the less openly discussed aspects of collision avoidance is its cost. Every avoidance burn consumes fuel and reduces mission life, giving operators a reason to prefer that the other satellite moves.


This creates a stand-off in which both parties may recognize the need to avoid a collision but have competing interests in deciding who should bear the cost.


Space Guardian addresses this issue by introducing a market-based mechanism into the coordination process. On its platform, operators bid on who moves, with the operator that remains in place paying the other.


The idea is to give both parties a way to resolve the decision through an agreed process rather than leaving it to an extended exchange of messages.


By putting a price on the maneuver, Space Guardian seeks to address an issue that can otherwise complicate cooperation. The company's proposed model brings the financial implications of collision avoidance into the same process as the operational decision.


This approach also helps explain how Space Guardian distinguishes itself from companies that focus on collision warnings. The warning is only one part of the problem. Reaching an agreement and carrying out the resulting maneuver are equally important to the company's stated purpose.


Building a Reliable Foundation for Live Orbital Data

Collision avoidance bidding: two operators negotiate who maneuvers, with an AI agent in the conversation.
Collision avoidance bidding: two operators negotiate who maneuvers, with an AI agent in the conversation.

The platform depends on live orbital data, making the infrastructure that supplies this information a critical part of its operation.


In June 2026, Space Guardian experienced a failure when it overloaded a public data provider's application programming interface (API). The company lost access for a week, leaving its product without the live data on which its functions depended.


The incident exposed the importance of managing external data sources carefully. Because Space Guardian relies on infrastructure operated by others, its own system must obtain the information it needs without placing excessive demands on those services.

Luka Zlatečan (CEO)
Luka Zlatečan (CEO)

The team rebuilt its synchronization process to address the problem. The revised approach uses one environment to pull data, reuses sessions, and reduces the frequency of requests when the server signals that it is under pressure. Access was subsequently restored.


The experience also shaped the company's view of technical development. Its live data pipeline retrieves conjunction information from surveillance providers on a schedule intended to make the information useful without overloading those providers.


According to Luka, getting this pipeline right required more work than developing any customer-facing feature. It remains one of the details he is most proud of because it supports the underlying operation of the product.


The experience demonstrates how Space Guardian’s platform's intended coordination functions depend on having access to the data required to identify and respond to potential collision events.


An AI Agent for Negotiating Collision Events

Janez (Head of AI)
Janez (Head of AI)

Another part of Space Guardian's approach is an AI agent designed to negotiate on behalf of satellite operators.


The intended process allows an operator to set their limits once. The agent can then bid and settle collision events within those limits, reducing the need for operators to handle every negotiation through emails and phone calls.


The company is preparing to pilot this capability. Although collision alerts attract attention, Luka sees automated negotiation as a particularly important part of the product because it addresses the communication and decision-making work that follows a warning.


This feature reflects the broader direction of Space Guardian's work. Its focus extends from identifying potential collisions to coordinating the decisions required to manage them.


However, the company remains at an early stage of development. It is pre-revenue, and its first pilot with a satellite operator is still being prepared. As a result, the CEO does not yet have a customer story demonstrating how much the platform has saved an operator.


Space Guardian does not describe something as validated until a real operator has used it during a real event. In presentations, it uses terms such as “runs on live data” and “projected margins” rather than making stronger claims that have not yet been demonstrated.


Learning Through Setbacks and New Connections

Jernej (CTO)
Jernej (CTO)

Space Guardian's development has involved technical setbacks as well as decisions about where to invest its time.


The CEO recalls being invited to San Francisco during a month when his calendar was already full. His initial response was to decline, but he reconsidered and made the trip. He returned with a network of contacts and valuable connections.


The experience offered a different kind of lesson from the API outage. While the technical setback highlighted the need to manage infrastructure carefully, the trip reinforced the value of making room for opportunities that may lead to useful relationships.


Luka’s advice to people entering the space sector also reflects the lessons the team learned while developing its own product. He recommends speaking to customers before writing code, acknowledging that Space Guardian did things in the opposite order and lost months as a result.


He also argues that a space-industry background is not essential for tackling every challenge in the sector. Many difficult problems in space involve software and coordination, areas in which expertise from outside the traditional space industry can be valuable.


The Risk of Underestimating Orbital Congestion

Tim (COO)
Tim (COO)

Space Guardian's work is grounded in a concern about the consequences of satellite collisions and the debris they can generate.


In Luka’s words, “Space is big, so collisions are rare.”


The orbits that matter are crowded, and one collision can produce thousands of pieces of debris that contribute to further collisions. This chain reaction is known as Kessler syndrome.


The concern reinforces the importance of addressing collision risks before an incident occurs. As satellite numbers grow, the process of coordinating avoidance maneuvers becomes an increasingly significant part of managing activity in orbit.


Space Guardian's proposed role is to provide a neutral platform where operators can reach agreements about who moves and how the maneuver is handled. The company draws a comparison with the exchanges used in finance and air traffic control in aviation, pointing to the absence of an equivalent coordination mechanism in space.


Its ambition is to establish a place where operators can settle these decisions before a potential collision becomes an actual one.


What Would the Universe Miss?

“A neutral place where satellite operators agree on who moves, before anything collides. Finance has exchanges, aviation has air traffic control. Space has nothing. We’re building it.”, Luka had the most direct answer.


Its development so far has combined work on live orbital data, a market-based approach to maneuver costs, and an AI agent intended to negotiate collision events. These capabilities are still at different stages of development, with the first operator pilot being prepared and the company yet to generate revenue.


That makes the company's current position an early one, but its stated objective is clear. Space Guardian is working on the part of collision avoidance that begins after a warning, when operators must turn information about a potential risk into a coordinated decision.


The founders' journey from a hackathon to a funded company began with the realization that this process remained unresolved. Their central question continues to guide the work: if operators need to coordinate to avoid collisions, what would it take to give them a shared place to do so?


For Space Guardian, that is what the universe would miss if the company did not exist: a neutral mechanism for satellite operators to agree on who moves before anything collides.

 
 
 

Comments


bottom of page