How Lux Aeterna Is Building a Market the Pentagon Didn’t Ask For
About Brian
Brian Taylor spent about fifteen years as a mechanical engineer before he ever sat in the founder’s chair. He came up through aviation and aerospace, then landed at SpaceX, where he did development, qualification, and testing on Starlink satellites, including the structural qualification of the first stack of 60. From there it was Amazon’s Project Kuiper for high rate satellite production, then Loft Orbital.
But despite this tour d’force through a who’s who of space companies, by his own admission, Brian was never a space nerd. It really bugged him that you would work that hard on something, and unless you happen to be an astronaut, you would never see the hardware again. You do not get to iterate on it. You do not get to enjoy the fruits of your labor.
An engineer who wants his hardware back. That frustration became a company.
About Lux Aeterna
Lux Aeterna builds fully reusable satellites. While there’s been lots of attention heaped on the rockets, Brian and Lux are focused on the satellite itself. The goal is to fly the mission, survive re-entry, land intact, refurbish it, put a new payload on it, and send it back up.
Brian founded the company in Denver in August 2024. It came out of stealth in June 2025 with a $4 million pre-seed led by Space Capital, and closed a $10 million oversubscribed seed led by Konvoy in March 2026, bringing the total to $14 million.
The company’s first vehicle is called Delphi. It is roughly 200 kilograms, built around a rigid conical heat shield that doubles as the satellite’s primary structure, with a parachute assisted return. It will fly on a SpaceX Transporter rideshare in Q1 2027, with recovery at the Koonibba Test Range in South Australia through a partnership with Southern Launch. The company holds a Space Act Agreement with NASA Ames and two CRADAs supporting the re-entry and thermal protection work, and has stood up a Defense Advisory Board.
The entire payload capacity for that first mission is already sold out, across civil, defense, and commercial customers, hardware and software, small companies and large.
Also worth noting for the culture watchers: he did this interview from inside a sauna. An actual, off the shelf sauna, sitting on the production floor, because it was cheaper than the fancy sound-proof pods that Google puts all over its offices. The idiot index on that thing has to be excellent.
What follows are the five ideas from this conversation that stuck with me:
1. The best deep tech companies are built on constraints.
Building reusable satellites did not require discovery of an entirely new set of physics; rather, the project required somebody to notice that the reason why nobody was building them finally ceased to be true.
In the early days of satellites, launch was so expensive and so rare that you optimized mass above everything else. Under that constraint, a disposable satellite is the correct engineering answer. Then rideshare and Falcon 9 reusability collapsed the cost and the scarcity of launch, and the optimization function changed underneath the industry.
As Brian says, “With launch much more plentiful than it was 10, 20, 50 years ago and much lower cost, you can turn the dial on that mass optimization a little bit to get some other features like re-entry and reusability.”
This meant deliberately accepting a mass penalty (e.g., heat shield, parachute, return propulsion) to buy reentry, and therefore, reusability.
Thus there was an assumption (and a constraint) that suddenly ceased to hold.
2. If nobody wrote the requirement, nobody else is competing for it. You also own the entire burden of proof.
Brian makes a point of saying that there was no program office asking for reusable satellites.
“There’s not a requirement written, there’s not an RFP that says, ‘We want a short duration mission.’”
Which poses a pretty significant challenge, because the responsibility of making the case lays with the company (and the founder). For Lux Aeterna, the pitch connects a couple of elements the Department of War thinks about:
Picture a timeline with launch in the middle. Lead time on one side, mission duration on the other. When you need a short lead time, whether that is prototyping, development testing, or a mission specific operation, you usually have a correspondingly short mission need. You can leave the satellite parked up there afterward. But at that point, as Brian puts it, you have built a target for one of our adversaries to go inspect.
As we’ve often said on this program, if you are responding to a proposal you did not shape, somebody else shaped it, and you are already late. Category creation is just requirements shaping at the earliest and most valuable possible moment.
But Brian does not oversell it, and I appreciated that.
“The onus is on us to prove that this is a useful thing and not be a build it and they will come kind of situation.”
3. Their moat is cycle time (not re-entry).
Every satellite company on earth iterates on telemetry, which is to say, on data downlinked from hardware they will never physically touch again. Lux Aeterna gets telemetry and the vehicle back on a bench.
“You can take it apart and look at everything. You can do non-destructive testing. You can do destructive testing if you want.”
Brian sees this as a compounding internal advantage. Every single flight generates a class of ground truth that competitors structurally cannot obtain, and it feeds straight into the next generation vehicle. His thesis is that a company capable of learning from full teardowns of flown hardware is going to out-iterate a company learning from downlinked packets, and that gap will widen with every mission.
4. Your hiring rubric does not travel. Your process rubric does.
After fifteen years in engineering, Brian thought he had hiring solved. He would look for the same things in engineers: Did they study mechanical engineering; did they work as a mechanical engineer; what did they build; did it work. A clean, quantitative, and repeatable process.
Then he had to hire sales, marketing, PR, and business operations, and found out the rubric fell apart when extended to other domains.
So instead of trying to create a rubric for each function, he sought to abstract from all of them:
“The idea of the sales process, pipeline, funnel, deal stages, that’s actually applicable to a lot of respects.”
Put hires through a funnel, and “focus on filling the company with people that are much smarter than me in every respect.”
5. “We don’t want to become a prime” is a bad excuse for having no process.
Brian made the observation that lots of startups treat “process” like the thing that turns you into a prime. But he rejects the framing entirely, and gives you a test you can use tomorrow:
“If you can fit it into a couple of bullets or a half-pager and it simply gets written down, how would I teach myself to do this six months from now? That is the right amount of process.”
Or said differently, “Process is just make your life in six months a little bit easier when you have to do this and you haven’t done it in six months.”
Process and bureaucracy are bad words that do not have to be bad. We are taking them back. Process is liberating when it is not enslaving, and it gives you the confidence that if you follow the cookbook, you land in the right place.
For more on Lux Aeterna: https://www.luxaeterna.com/
Follow Brian: https://www.linkedin.com/in/brianjtaylor/
For more Crossing the Valley: www.valleycrossers.com
Follow Noah: https://www.linkedin.com/in/noahsheinbaum/
