SeaPRwire – The experiment Satlyt ran earlier this month used exactly one computer in space. It sat aboard a spacecraft, worked through a simulated network of four computing hosts, four users and eight services, and sent its answers back to Earth. The other three machines in the scenario existed only as numbers on that one.
What the run establishes is narrower than the phrase “space data center” implies, and more useful than a demo. The software produced a scheduling plan on orbit, using the compute that was actually available where the hardware physically was, instead of modelling the problem on a ground machine and calling that a result. Thirteen months of engineering went into reaching that point.
The scheduling model works through declarations rather than approvals. Operators set permissions, priorities and operating limits, and the software assigns tasks inside those bounds. Afullo’s description of it is precise on this point: users “will only need to define permissions, priorities, and operating limits.” Nobody signs off on each assignment. The operator writes the fence, and the system stays inside it.
That design choice carries the main unresolved question for this class of software. A fence wide enough to be useful is also wide enough to permit an assignment the operator would have refused if asked. The test did not probe that boundary, because probing it requires workloads and hardware that the single-computer setup did not have.
The result Afullo reports is a trade-off instead of a win. One of the approaches available to the scheduler performed best and consumed more computing power than the alternatives. On a spacecraft, where power and thermal headroom are the binding constraints and neither can be upgraded after launch, “best” and “affordable” rank differently. A scheduler that ignores the difference produces plans the satellite cannot execute.
The test also turned up a defect of the kind that a ground simulation tends to hide. The software was stamping communication delay by arrival time, the moment data showed up, rather than by elapsed delay, how long it took to get there. The two numbers diverge exactly when a scheduler has to decide between waiting for a link and reassigning the work to another computer. Afullo treats the fix as a correction, not a failure, and the record supports him: development, onboard execution and the return of outputs all completed.
Context for how much of the problem this solves: NASA already operates a network built to move data through space when links are delayed or intermittent. It went into use earlier this year and has been tested on aircraft. That layer answers whether bits arrive. Satlyt’s layer answers who computes what, and its answer has to change as the link changes. The second question is only interesting once the first has a working answer, which is roughly where satellite operators are now.
The wildfire example is the one Afullo reaches for, and it is a fair illustration of the economics rather than a description of a deployed product. A spacecraft that sees a fire can send raw imagery down and wait for a ground team, spending a communication window on pixels, or it can run detection onboard and send a shorter answer. Earth observation operators have been doing onboard processing for years. What Satlyt is selling is not detection; it is the coordination layer that would let one job be split across several spacecraft when no single one has the compute or the connectivity to finish it alone.
Its software is on three satellites in orbit. The research behind the test was NASA-funded and run with the University of Houston, and the agency has not selected Satlyt for a mission or chosen to deploy the technology. That distinction matters for reading the result. This is a company validating its own planning component inside an agency-funded research project, not an operational system whose output anyone depends on yet.
The list of what remains, in Afullo’s own account, is specific: usable communication links, permission from the operators of participating spacecraft, secure transfers between them, resource scheduling across a fleet, and recovery when a node drops out. The first item on that list is not a software problem, and the second is not either. Cross-operator compute sharing asks satellite owners to accept that another company’s scheduler will direct work on their hardware, under limits they wrote but cannot watch in real time.
Multi-spacecraft transfer is the untested part. Every result so far comes from a single physical machine reasoning about machines that were not there. Satlyt says it will test its software under various workloads, hardware and connectivity conditions before attempting that, and it is researching applications beyond low Earth orbit, including 4K video streaming from the Moon through the NASA-funded work.
The company raised $8 million and reached the top five of TechCrunch Disrupt Battlefield this year, which is a reasonable amount for a scheduling layer and a small amount for a constellation. The longer-term ambition Afullo describes is the standard platform argument: developers write applications for orbit without rebuilding infrastructure for each mission. It is also the hardest version of the argument to deliver in a domain where the hardware is fixed at launch and the network topology changes with orbital mechanics.
Hardware heterogeneity is the constraint that has not been priced. A scheduler assigning work across spacecraft has to model what each node can do, and satellites launched in different years carry different processors, different power budgets and different thermal designs. The test avoided this by simulating four hosts that were interchangeable. Operators running a mixed fleet, which is most of them, would be asking the software to plan across machines it has never benchmarked, and the plan is only as good as the assumptions behind it.
The next milestone is a demonstration that spans separate spacecraft. Until one exists, the accurate description of Satlyt’s software is a scheduler that has been shown to generate a plan on one computer in orbit, and has not yet been shown to work as a network.