Mohammed Bukhari

01AynX02Tamara03SCET04Achievements05Off hours06Contact

Contact

01Space safety

AynX

A rocket’s trail curves into an orbit, where two satellites pass above the dim edge of the Earth.

AynX lets satellite operators agree on who moves out of the way, sharing only what they must.

As its co-founder, I took it from a competition paper to a clickable prototype.

Role
Co-founder
Team
Co-founders
When
Co-founded October 2025, the paper December 2025, the prototype spring 2026
Result
Reached the finals of the Saudi Space Agency’s DebriSolver

Status Prototype built on sample data. Paused.

Context

Satellites in low orbit get collision warnings every day. Working on the Saudi Space Agency’s DebriSolver competition convinced me that spotting the risk is not the hardest part.

Agreeing on who moves is harder when the two operators are competitors, or answer to different governments, and neither wants to share precise orbit data with the other.

What I built

I co-founded AynX in October 2025 to turn a hard coordination problem into a workflow: low-Earth-orbit operators avoid collisions without disclosing who owns which satellite. I wrote the final paper on my own, wrote the specs and directed the build.

  • The paper. AynX reached the finals of the Saudi Space Agency’s global DebriSolver competition, and I wrote the final paper on my own that December.

  • The identities. Rotating cryptographic identities for pseudonymous, verifiable sharing of conjunction data.

  • The engine. An ML-backed engine that determines who maneuvers and when.

  • The prototype, spring 2026. It reads collision-warning files, sorts events into risk tiers on a 3D globe, walks through a scripted session between two pseudonymous operators and suggests a maneuver.

  • The repositioning, April 2026: from a privacy layer for every operator to a decision tool for operators who can’t or won’t share data.

AynX prototype recommendation card for pseudonymous satellite SAT-7D8F: radial-in maneuver, delta-v 0.1965 m/s, fuel cost about 0.024 kg, new miss distance over 2000 m, new collision probability under 4.00e-7.
Prototype with sample data and a simulated second operator. Object names hidden.
Code to comeThe code behind the AynX prototype.A link to its repository, with keys and private data removed.

The decision

In April 2026 I changed who AynX was for. The first version was a privacy layer for every operator. But operators who are willing to share data already have services built for them. The open gap was operators who can’t or won’t share.

The tradeoff was a smaller near-term market and longer government sales cycles, and the pseudonym design moved into the background. There is also no public data on how operators actually maneuver, so deciding who moves, and when, became the engine’s job.

The protocol

This is the design from my paper, drawn for this site. It borrows an idea from connected cars, which sign safety messages with short-lived pseudonyms: each satellite would carry an identity that changes every 6 to 24 hours. One authority would vouch that it is real, and a separate coordinator would run the conversation, so neither side learns more than it needs to.

In the prototype’s sample event, a 35 m miss distance grows to 2 km after the suggested maneuver. That 2 km is the target the prototype’s rule aims for, not a prediction.

  • Certify. A certification authority gives each satellite a bundle of short-lived pseudonyms, each valid for 6 to 24 hours.

  • Warn. A warning arrives for two pseudonyms, with the time of closest approach, the miss distance and the collision probability.

  • Verify. The coordinator checks both certificates. Each operator learns only that the other side is a real, certified satellite.

  • Agree. The coordinator proposes who moves, in which direction and by how much. Both sides accept or counter.

  • Rotate. Pseudonyms change when their window ends, so sessions are harder to link over time.

  • Exception. Revealing who owns a pseudonym takes both authorities together, for example after a collision.

  • Simulated in the 2026 prototype, with sample data
  • Designed in the paper, not built

  1. 1 Certify

    Each satellite gets short-lived pseudonyms, valid 6 to 24 hours.

  2. 2 Warn

    A collision warning names two pseudonyms, not two owners.

  3. 3 Verify

    AynX checks both certificates. Each side learns only that the other is real.

  4. 4 Agree

    One satellite moves. In the sample event, 35 m becomes 2 km, the prototype's rule.

  5. 5 Rotate

    SAT-5EA3 becomes SAT-91C0 when its window ends, so sessions are harder to link.

Certification authority
Knows who owns each pseudonym.
AynX, the coordinator
Knows what happened, not who.
Each operator
Knows only that the other side is certified.
Design proposed in my DebriSolver paper, December 2025, drawn for this site. The 2026 prototype runs the session on sample data. Inspired by connected-car security, which uses more authorities than this.

Outcome

  • Reached the finals of the Saudi Space Agency’s global DebriSolver competition.

    SourceMohammed Bukhari’s résumé, October 2026

  • Selected after the initial-idea round to develop the solution, in October 2025.

    SourceDebriSolver team email, October 14, 2025

  • Sole author of the final paper, submitted in December 2025.

    SourcePaper byline; DebriSolver deadline emails, December 2025

  • Clickable prototype deployed in spring 2026, running on sample data.

    SourceDeployment records, April 1, 2026

What’s next

AynX is paused for legal reasons. It has no users, pilots or customers. The prototype is a proof of concept. If AynX restarts, these are the parts of the design still to build.

Proposed, not yet done

  • Encrypted operator chat, as designed in the paper.

  • Generating warnings from operators’ own orbit data, instead of reading existing warning files.

  • Training the engine on maneuvers that operators approve.

Links

Credits

Paper
Sole author, December 2025
Competition
Saudi Space Agency’s DebriSolver, 2025