In short
Scott Morton, an ex-SpaceX engineer and founder of Revel, explains why industrial “control software” hasn’t improved since the 1980s/90s, how AI helps but doesn’t replace the need for specialized, safety-critical engineering, and how Revel modernizes hardware testing/control across rockets, aircraft, nuclear, and oil & gas. He also discusses lessons from Elon Musk’s “make big bets early” approach (e.g., Starship’s catch tower caught on Flight 5) and why Revel built its own runtime-safe programming language.
Guest backgrounds
Scott Morton is Founder & CEO of Revel (founded 2024). He previously worked ~10 years at SpaceX, including writing control software and participating in Starship-related software decisions. He’s also described as a mechanical engineer turned software engineer.
Key claims
Vibe coding won’t safely replace control-system development; Revel uses CI/hardware-in-the-loop so releases are validated over days. Industrial software talent shifted to internet tech, leaving hardware control stagnant. Revel’s language is “runtime safe” (if it compiles, it can’t crash) and is designed for deterministic control math.
Notable examples
Starship catch tower; internal SpaceX “viral” spread of his system; Revel’s own compiler toolchain (LVM backend for Rust, Clang for C++); customers Impulse Space and Radiant Nuclear; industrial deployments up to ~250,000 telemetry channels; same-day deployments and a bake-off where engineers switched to Revel in one day vs a week with traditional tools.
Written by AI. May contain mistakes. Listen to the episode to check what was said.
Chapters
Tap a time to open that second in VOThe Mission at SpaceX
0:00 to 0:45
Learn about the focus and goals during Scott Morton's time at SpaceX.
“SpaceX, at least when I was there, the product was getting things to orbit.”
Revel's Purpose and Impact
0:45 to 1:48
Discover Revel's innovative software platform and its applications.
“And ultimately, it was caught on Flight 5.”
Introduction to Scott Morton
1:48 to 2:11
Meet Scott Morton, the founder of Revel and his journey from SpaceX.
“Scott and I discuss the hardware renaissance, why industrial software got stuck in the 1980s, what he learned from Elon Musk, and why Revel decided to create its own programming language.”
Challenging Conventional Narratives
2:11 to 2:46
Discuss the misconceptions about AI dominating software development.
“noting the sense of Revel being almost a little bit of a narrative violation.”
Revel's Approach to Software Development
2:46 to 4:39
Explore how Revel utilizes AI while emphasizing the complexities of software for high-stakes systems.
“A lot of these, I think, kind of shallow web apps that are very easy to code, I think, definitely, I think those are maybe in trouble with the new capabilities of AI.”
The Shift in Software Engineering
4:39 to 5:13
Understand the evolution of software engineering and Revel's place in it.
“And then again, we have this kind of specialization in the area.”
State of Industrial Software
5:13 to 6:28
Analyze why industrial software has been stagnant since the 1980s and 90s.
“Maybe to take another beat and give folks a better sense of what it is exactly that that Revel does.”
Revel's Competitive Edge
6:28 to 8:00
Examine the unique advantages Revel has over its competitors in the software space.
“for all the other companies out there trying to build incredible machines?”
SpaceX's Approach to Software
8:00 to 9:11
Learn about SpaceX's decision-making process regarding in-house software development.
“been many startups in the space, but looking over the last five, 10 years, I've seen a few folks try and take a chip at it.”
Lessons from SpaceX for the Future
9:11 to 14:00
Discover the crucial lessons Scott learned at SpaceX that inform his work at Revel.
“it feels like the old set of software, you know, didn't develop because there was this massive talent problem where everyone just moves to the internet.”
Show all 34 chapters
Building at SpaceX: Insights and Challenges
14:00 to 16:00
Learn how SpaceX's unique culture fosters innovation and rapid development.
“But SpaceX, at least when I was there, you know, the product was getting things to orbit.”
The Catch Tower Concept Explained
16:00 to 19:20
Understand the innovative design behind the Catch Tower and its benefits.
“For folks that don't know, Could you tell them what the Catch Tower is?”
Decision-Making Inspired by SpaceX
19:20 to 22:40
Explore how lessons from SpaceX shape leadership and decision-making at Revel.
“And the CEO is like, let's do something more conservative.”
The Need for a Custom Programming Language
22:40 to 25:20
Discover the reasons behind developing a unique programming language for hardware control.
“They've physically been in the field building them.”
The Journey of a Builder: Early Experiences
25:20 to 28:00
Hear about the speaker's childhood projects and formative experiences that shaped their engineering journey.
Building Innovative Solutions with Limited Resources
28:00 to 29:00
Discussion on creating functional technology using available materials.
Early Experiences and Interest in Engineering
29:00 to 30:20
Reflecting on early engineering experiences and aspirations to work in space.
Combining Hardware and Software Skills
30:20 to 31:50
The importance of understanding both hardware and software in engineering.
“Uh, and so then I was like, well, I can stay here a little longer and go.”
The Drive to Succeed and Overcoming Challenges
31:50 to 33:30
Exploring the motivation derived from personal challenges and academic pressure.
“I mean, I, I joined SpaceX as a, as a 25 year old intern and I was like, I'm just going to go in and outwork everyone.”
Learning from Elon Musk's Leadership Style
33:30 to 35:00
Insights into lessons learned from working under Elon Musk at SpaceX.
“but they actually had us there like, look to your left, look to your right.”
Risk-Taking and Accountability in Innovation
35:00 to 36:30
Discussing the balance of risk-taking and accountability in high-stakes environments.
“then he got pretty involved and you know i enabling people i mean you fly close to the sun at spacex You know, you're going to have you're taking a lot of risk for sure.”
Establishing a Strong Engineering Culture at Revel
36:30 to 38:10
Building a high-performance engineering culture and product accountability.
“Yeah, I think the product has to be awesome.”
Customer-Driven Milestones and Their Importance
38:10 to 39:50
The role of customer milestones in product development and team motivation.
“to figure out what's actually the critical path.”
Navigating Complexity in Industrial Systems
39:50 to 41:30
Challenges and strategies involved in managing complex industrial systems.
“Larger scale, something like a rocket engine test site, which is a large facility on the desert.”
Performance Comparisons in Engineering Solutions
41:30 to 42:00
Comparative analysis of engineering solutions showcasing Revel's advantages.
“So we're actually now deployed at a 250 ,000 channel system.”
Revel's Competitive Edge in the Testing Space
42:00 to 43:14
Learn how Revel's innovative approach outperforms traditional engineering methods.
“Football field or several football field level.”
Building Trust with Large Companies
43:14 to 44:53
Discover strategies for a young startup to gain credibility with established firms.
“You know, there's no way we're going to run out of money.”
Hiring and Maintaining High Standards
44:53 to 46:42
Understand the challenges of scaling a tech startup while ensuring quality talent.
“We're pretty open to where people are coming from.”
The Importance of Runtime Safety in Testing
46:42 to 49:06
Learn how Revel's technology minimizes risks during testing phases.
“So if you work inside a company and you're a software engineer, you're going to work on just that company, only get exposed to that company's hardware they're building.”
Addressing Bottlenecks and Scaling Challenges
49:06 to 51:06
Explore the key bottlenecks faced by Revel as it scales and how they are addressed.
“And so you may have this simplest mistake that's probably most common is like a string interpolation error.”
Leveraging AI in Engineering Processes
51:06 to 52:43
Find out how AI can enhance control software and improve engineering workflows.
“we talked a little bit about ai building software uh and and the ways in which you know you can leverage that.”
Long-term Vision for Revel
52:43 to 54:18
Hear about the ambitious future plans for Revel and its impact on the engineering landscape.
“Like there's sort of feels like a dozen different interesting things.”
Philosophical Reflections and Book Recommendations
54:18 to 56:00
Engage with Scott's reflections on humanity's future and a thought-provoking book suggestion.
“I always like to wrap up with a thought experiment or a question or two.”
Finding Perspective in Business Challenges
56:00 to 56:40
Explore how a broader perspective can aid in overcoming the challenges of running a company.
Transcript
Automatic transcript. May contain errors.0:00Scott Morton:SpaceX, at least when I was there, the product was getting things to orbit. It was not building an incredible software platform. What we did build actually went viral internally at SpaceX. I talked to a number of other companies out there and I asked, like, what are you guys using? What are you guys doing? And they were like, oh man, it's awful. I was just thinking about the future and what is the most impact that I could have? Is that at SpaceX or is it leaving SpaceX and delivering this type of platform for all the other companies out there trying to build incredible machines? Today, Revel provides a software platform for controlling hardware systems like nuclear reactors, jet engine test facilities, systems like oil and gas refineries.
0:34Scott Morton:One of the biggest keys to SpaceX's success is just that Elon is willing to make massive bets on his team, even though everyone's like, we have no idea how this is going to work. We started building the catch tower before Starship had ever flown. Everyone at SpaceX was like, this is crazy. And ultimately, it was caught on Flight 5. One of the best parts of being at Revel is that in one day you can go to a nuclear reactor company, you can go to the most cutting-edge satellite manufacturer, and then you can go to a hypercar company. It's pretty cool.
1:06Modern AI systems have made software easier than ever to build, cooling venture capital investment in the category, and hammering public software stocks. That's what makes Revel one of 2026's narrative violations, a software startup thriving amid to chill. Founded in 2024 by SpaceX veteran Scott Morton, Revel makes testing and control software for companies building rockets, supersonic aircraft, nuclear reactors, and other complex machines. In less than two years, it's raised$180 million, won customers like Impulse Space and Radiant Nuclear, and was reportedly valued at just over$1 billion. In today's episode, Scott and I discuss the hardware renaissance, why industrial software got stuck in the 1980s, what he learned from Elon Musk, and why Revel decided to create its own programming language.
2:01I'm Mario, and this is The Generalist. It's great to have you here. I'm really excited to chat and learn more about you and Revel. Awesome. Yeah, great to be here. I think one of the interesting places to start is maybe noting the sense of Revel being almost a little bit of a narrative violation. You know, we live in a world in which the dominant narrative is that AI is sort of solving all software and that every company will sort of maybe build their own systems entirely from scratch. And you are building a software company for the most demanding buyers in many ways in the world. Where's the disconnect that people miss in that narrative that leaves the space for Revel to thrive in the way that you have?
2:45Scott Morton:The biggest thing is that I don't think anyone's really going to kind of bet their career on like vibe coding a control system for, let's say, a nuclear reactor or a rocket engine or something that's very high consequence. A lot of these, I think, kind of shallow web apps that are very easy to code, I think, definitely, I think those are maybe in trouble with the new capabilities of AI. But I think fundamentally, a company is like an asymmetric capability. You have a group of people that are really specialized in this space. And at Revel, I mean, we are fully leveraging AI tools as much as we possibly can.
3:22Scott Morton:but there is a lot more that goes into software that controls these high-stakes systems than just authoring code. We have a full CI system, so what that is is like a bunch of hardware that we control is in a lab. We have every type of hardware or kind of system that our platform supports, and anytime we do a release, it goes through a whole process that takes several days to make sure that it is all correct. When we release it to our customers, it's going to behave as we expect. Also, vibe coding only really helps with the authorship component. So with our stack, everything, every line of code is reviewed by someone that you have the right person at the company to review it.
4:04Scott Morton:And so we've seen a lot of, I mean, internally, we've seen a lot of kind of acceleration of our authorship, but not necessarily, but there's a lot more that goes into releasing correct software to control physical systems. Is there a version of the future where you think, hey, if these models get so good at this trajectory, maybe there's something we have to do very differently? Or will it always just be the case that, hey, yes, those models can keep getting better. That'll just help us deliver an increasingly better system. I think so far we're seeing it's only just enabling us to move a lot faster.
4:39Scott Morton:And then again, we have this kind of specialization in the area. Like we have people, we're a pretty tenured group so far, actually. We're pretty light on junior engineers. We do want to hire more junior engineers in the next few months, but it's kind of mostly kind of former SpaceX senior engineers. We have several from Palantir and Andrel as well. But arming these people with AI where they really know what they're doing, they know what the correct solution really looks like just kind of through their experience has been a huge accelerant for us. And I think it'll kind of continue in that direction.
5:15Yeah, I think it's part of the reason I was excited to have this conversation is that I think it's Revel feels like an example of what an amazing next gen software company could look like that you don't want to you don't want to outsource this capability in. Maybe to take another beat and give folks a better sense of what it is exactly that that Revel does. Can you sort of, yeah, give folks a little bit of the texture there?
5:37Scott Morton:Yeah, so Revol provides a software platform for controlling hardware systems. Hardware systems being like nuclear reactors, we do rocket engine test sites, jet engine test facilities, and then also kind of industrial scale systems like oil and gas refineries. And what's really exciting right now is we're kind of moving more in that direction. And the fundamental problem that we're solving is that the software in this space really hasn't made any kind of material improvements since the 1980s and 90s. I saw this problem firsthand at SpaceX. To have something great at SpaceX, we had to build it all ourselves.
6:15Scott Morton:I know it's part of the team that did that. And then I was just thinking about the future and like what is the most impact that I could have in the space? Is that at SpaceX or is it leaving SpaceX and delivering this type of platform for all the other companies out there trying to build incredible machines? I've heard you mention that, you know, the fact that this sort of state of play has been stuck in the 80s and 90s before. Like, why do you think that's been the case? And when you think about what's been stuck, has it been truly the underlying capabilities that are stuck there? Or is it more just the interface layer that is, you know, incredibly web 1.0 and just not what people are used to in terms of polish?
6:58Is it both of those things?
6:59Scott Morton:I think just all the software engineering talent got very excited about the internet technologies. You can really just see it. It's like these tools that are available really do date back. It's like 1986 is when one of the major platforms used in tests was invented and really hasn't changed much since then. And then 1993 is when the platform that's generally used in industrials was created. And then you can see then 1998, nothing, and then all the way through 2000s. And I think it's really just all the software engineering talent went and worked on the internet. And this space just kind of languished.
7:35Scott Morton:There weren't really any startups focused on this. There was no real pressure on the incumbents to really innovate. And so I think then companies like SpaceX came along and proved that you could do interesting things in hardware. And I think, you know, there's definitely Revel is kind of part of a couple of companies now that are really focused on this. And presumably it's also just a testament to how sticky these solutions are, that once they're ingrained, it's very hard to rip them out such that, you mentioned there haven't been many startups in the space, but looking over the last five, 10 years, I've seen a few folks try and take a chip at it.
8:08And it feels really hard for folks to make the sort of progress that you guys actually have done. What's that disconnect there?
8:14Scott Morton:Yeah, I had this question. Also kind of could Revel have been invented anytime in the last decade? Yeah. What's different? I think it could have. I really do. And also I think a lot of the companies that are in our space are similar in that they are actually looking to what SpaceX did and they're kind of modeling after this lighthouse finally and I think SpaceX really is it's like the ultimate proving ground uh for software for hardware they move as fast as they possibly can they will make big investments to move really quickly I was fortunate to you know write a ton of control software at SpaceX uh and then also work on how are we going to do this in the future and so I think there was just a kind of accumulation of a lot of experience.
8:54Scott Morton:And then it's that experience what we were taking forward to Revel. It's kind of, it's pretty simple. You need to have this kind of incubator to figure out what the next generation of systems look like. And then, you know, those people can then go and take that experience outside the company. So if I have to synthesize it a little bit, it feels like the old set of software, you know, didn't develop because there was this massive talent problem where everyone just moves to the internet. Plus it's super sticky. So there's, you know, not an incentive to rip it out. Then the few newcomers that come in don't have this experience where they get to see exactly how to build this from the inside of somewhere like SpaceX and learn, okay, here are all these edge cases and it's tough to get these companies to adopt it unless it's perfect.
9:38Anyway, do you kind of have a bit of a chicken and egg issue there? Is that sort of a decent distillation of some of the dynamics that Revel was walking into?
9:48Scott Morton:Yeah, I would add also that SpaceX is this pressure cooker. And we were extremely motivated to think very hard about this. And then we had Elon's backing to go and try a few things. And we also had accumulated decades of experience elsewhere inside the company. This system has to work. It has to also have evidence that it's accelerating the team. and I think the combination of those things is what kind of results in greatness. You need to have the pressure, you need to have, I think, the high-stakes situation and then that's how you, I think, discover new approaches. Yeah, you'll know about this much better than I do because of your time at SpaceX, but reading about the company and about sort of Elon's management style, it feels like there's sort of maybe a preference to in-house as much as possible, but also a lot of pragmatism where it's like, hey, if we can get the lock from the bathroom door, that's 30 bucks to work on one of our engines.
10:49We'll do that too. What was it about the old software systems that just clearly did not work for what SpaceX was doing in it such that this kind of an investment was actually worthwhile?
11:01Scott Morton:Yeah, I actually want to add to what you just said there. I think there's this big notion that SpaceX vertically integrates everything. And I think it's actually, it's not what, I mean, I was involved in a lot of these decisions totally not what I what I saw there if you were to say you know in a meeting where you're trying to decide what to do like we should vertically integrate this like you would just be like what like no one would know what you're talking about like what do you that's not why you build in-house yeah you build it axiomatic you build in-house when you look at and we did a huge survey of all the options when we're trying to figure out what to do for starship yes we looked in test it was like exhaustive yes uh and we came to the conclusion that these were not a good fit for what we needed for starship and we we looked at we had a massive trade internally and then then we started kind of looking at prototyping a few approaches that based on all experience on dragon and falcon what you know if we could just go first principles and dream up something.
12:00Scott Morton:And those kind of started to gain momentum. And then finally, we kind of got it across the kind of hump of showing it to other people and getting a lot of consensus. And then it was like, we should go try this. And even then, there were still a lot of like, why don't we just take forward what we did for Falcon? Even then, it was actually very hard, a hard sell internally to actually build it ourselves. To zoom into a little bit there, and I don't expect you to go so, so granular but when you say it wasn't a good fit for for starship like what exactly were the old systems just like too slow to you know not capable of doing the kind of testing you need to do it for this type of machinery like yeah what what didn't work we saw a number of issues some of them were just that uh software engineers could not work well with hardware engineers on that it's kind of a format that both of them could share that's another problem i think in somebody's commercially available options.
12:52Scott Morton:We also, there's a very big difference between the software that ran on the launch pad and the software that ran on the vehicle. And so we really wanted to try to take the best of both worlds, the best of all the approaches and build something that would work for both. We kind of had this objective list that we wanted. If you could just write in like a, you know, one sheet of paper, all the things that you'd like about your software, and then you take that list and you try to map it to these different solutions. And then what we thought we could build in-house and so you had sort of built some version of these systems for falcon and dragon and this was sort of like hey take these these pieces maybe and and maybe a different order of magnitude or a different level of depth uh that we can run on in a very different way yep how long did that take as a as a project to build something where really it worked in the way that you wanted to.
13:44Scott Morton:I mean, I think this is actually part of why I ended up leaving to go build Rebel is it was very, very hard to build in-house. And I actually felt like we never really took it all the way to what we could. We could see, you know, we rolled out a version of the system. But SpaceX, at least when I was there, you know, the product was getting things to orbit. It was not building an incredible software platform. Yes. And so, yeah, I think it worked quite well. What we did build actually went viral internally at space extra is actually very rare because all the all the programs are actually very siloed and isolated kind of by design because you want them to move as fast as they can without being kind of you know dragging be like oh you can't you can't do that on starship because this is how we do it yeah it's fully kind of unencumbered you can just do what's right for the program but we did build actually did spread throughout the company based on all of our experience deploying it and then scaling it up to orbital cloud ever it's the largest rocket in the world you know i thought there were there was experience there that i thought could help build something for the future for the rest of the world and that's kind of why i wanted to uh leave and i think i also you know i talked to a number of other companies out there outside of spacex that were you know startups trying to go as fast as they could and i asked like what are you guys using what are you guys doing and they were like oh man it's awful we are using either these commercial tools and we're just like it's it just doesn't feel like it's helping us out or we're trying to build in-house and similar to SpaceX, I'd say at a different order of magnitude, but they're like, this is just not going to get anywhere soon.
15:16Scott Morton:Like this is going to take forever. It's going to be actually extremely costly to make this great. You were there for almost 10 years, right? Difficult thing to do, but if you had to sort of try and distill down the most important lesson that you took from that time, is there something sort of actually quite clean that maybe almost fits in your brain as a mantra, I imagine there might be. One of the biggest keys to SpaceX's success is just that Elon is willing to make massive vets on his team, that we can do this. And even I was at certain points a little skeptical, like could we, especially I think, specifically the catch tower.
15:53Scott Morton:I mean, we started building the catch tower before Starstrip had ever even flown. And originally we were going to try to catch it on the first flight. For folks that don't know, Could you tell them what the Catch Tower is? Sure, sure. Yeah. So Starship was designed from the beginning to be, or the booster and then also the ship, to be caught by a tower. It has these arms that come out from the tower and then basically the booster and ship kind of hover in between the arms and they basically catch the vehicle. Which is this crazy idea. It's incredible. It's actually, I mean, it saves an incredible amount of mass in the vehicles.
16:29Scott Morton:You don't have to have these heavy legs down at the bottom and all the structure to support the booster in that way it's much easier to hold it from the top kind of intention you think about kind of a string holding something up versus trying to hold it up from the bottom and uh that's a much more efficient way to hold the structure and so it has massive benefits and that's i think what elon was so he was like no matter how hard this is this is the right solution long term and he was he just made a huge bet on the team we're i mean everyone at SpaceX on the Starship program. I was like, this is crazy.
17:01Scott Morton:Can we actually do, we don't even have a flying vehicle yet. Can we actually go directly to catching it? Like on top of building the largest vehicle that is designed from the beginning for reuse, you know, full reuse, both the ship and the booster. And ultimately, I mean, it was caught on flight five and just, he was right. So, but it was him, I think making that bet very early on in the program, that got us there so quickly. If we had waited till it flew and then tried to retrofit everything and change the vehicle, it'd be a huge change to how the vehicle is designed. And so making that bet at the very beginning, in hindsight, was clearly like a stroke of genius.
17:41Where does that fit into your sort of mental model on a day-to-day? Are you just trying to make your decisions with a greater speed than if you hadn't seen that, with sort of greater conviction than if you hadn't seen that?
17:53Scott Morton:I think the most tangible thing is there's two. I think one is at Rebel, we've made some bets very early on that seemed, they seemed like pretty big and difficult things to sign up for initially, but they're paying off massively now. For example? For example, we're using the compiler tool chain. So we have our own programming language that enables a lot of what we talk about, all the improvements. and we are using LVM as the back end of that, which is the compiler tool chain for Rust and the Clang compiler for C++. It was a totally foreign thing to the team. No one ever used it before, but ultimately it was clearly the right solution long-term.
18:36Scott Morton:Why was that? It's kind of just becoming the standard. It's clearly the future-proof compiler tool chain. I think everything is going to converge on using that. And it was a huge bet on my team's ability at that point you know we were like three people that we would be able to go and figure it out and then ultimately you know this is what 20 something months later it's awesome yes like the language is incredible it's a it's it's super performant the tool chain has a lot that we can leverage to make sure it's correct so that's one example for sure i think the other big thing from elon is just i think that teams are when you do that like when you sign the team up or you say we're going to go try this engineering teams are inherently often just conservative and they can't imagine what they will come up with down the road this this like the catch tower seems incredibly hard yes have no idea how we're going to solve those all the problems that we need to to make that happen and so engineers i think are just just conservative by nature uh but and they can't see kind of around the corner of what they will come up with along the way uh and so i think elon was just would always make bets on the team and continue to make bets even though everyone's like we have no idea how this is going to work like this isn't looking good you're like let's spend another month on it and you keep doing that and then people had breakthroughs that they did not foresee yes and so i think a lot of teams are just much more capable than they even than they even imagine i can i can picture like a traditional corporation they come the engineers like hey can we make a catch tower.
20:11Scott Morton:Yes. And they're like, absolutely not. And the CEO is like, let's do something more conservative. But Elon knows how to, I think, yeah, get the best out of his team. And this is, I think, a big way that he does it. Yes. I was interested in that, the fact that you guys have, you know, built your own programming language, use your own programming language. Why is that necessary or valuable for what you do? There's a few reasons. I mean, just like the kind of software platforms, there's been no new programming language designed for controlling hardware systems also in three or four decades and it's kind of the central component of a lot of these platforms is how you actually write what you want to do down in the form of a programming language meanwhile in the last three decades there's been incredible progress in i think just the software world learning about how humans can write code well.
21:04Scott Morton:Like Python wasn't even in use back then. And so I think, you know, we've taken a lot of cues from Python in our programming language. I think Python has been so successful, not because it's interpreted or other aspects of the language, just that it's very accessible, very easy to get started with. And so we've built this language to try to be just, it's kind of has several aspects. It's highly performant, it's highly accessible, and it's what we call runtime safe. So if it compiles, it cannot crash. And there's just no language out there that does all those three. How extensible is it? Does it work sort of across any possible piece of hardware that you could imagine?
21:43How do you sort of wrangle that? Yeah, I mean, fundamentally,
21:46Scott Morton:what you're doing in these hardware control systems is you are taking a bunch of inputs that are coming from the hardware system, like picture like a temperature measurement or a pressure measurement. And then you're going to do math and then you're going to write a bunch of outputs in the code. And those outputs are like turning a valve or turning on a pump or something like that. And fundamentally, so the language is designed to do that middle part extremely well. I see. Do the math on the inputs to determine what the output should be. So it is very much designed for that problem set. And that's what's made it so great for users.
22:21Scott Morton:It is specifically designed for this problem. The performance is really important for determinism, which is that every time you run it, it's going to behave the same way. And then it will finish what it needs to, to, you know, to write the outputs at the right time. Second, accessibility. This is actually a big problem in this space is that a lot of these teams are a lot of hardware engineers and they design the hardware systems. They know it the best. They know it better than anyone. They've physically been in the field building them. But they can't, but then it comes time to tell it what to do in the form of a language.
22:55Scott Morton:and they have to go at someone else. They have to tag someone else in. Yes. And then there's a massive interface there. So this person's coming in. They don't know the design at all. And then the hardware engineer has to explain in excruciating detail what they want to have done. And then there's a lot of iteration cycles with that. It takes a lot of time. It's always wrong. I was, I actually, I mean, this is exactly what I went through at SpaceX early on. Is that, so I wrote the propellant load sequence for Falcon 9 and I had to explain to someone else exactly how I wanted to work. and it took extremely long time.
23:26Extremely long being how long? Six months. Wow, really? Okay. I would have guessed when you say extremely long, like, I don't know, three weeks. It's six months for that.
23:34Scott Morton:And it was, obviously there's a lot of other things going on and I had, but there's a lot of iteration cycles with that person. And then with Rebel today, you could do it in literally an hour. Wow. That's crazy. It is extreme. I feel like when we tell people we built a programming language, it sounds like a cool software, software engineering project, hobby project and i think probably the first three or four months that revels like oh is this really going to work this seems kind of insane but what we're seeing today i mean this is like this question has been totally put to bed company like it is doing exactly what we had hoped the hardware engineers are out there using the language day to day there's probably people writing it right now running it on test stands and we've even seen we've actually had technicians uh at these companies like reading the code and even writing it and that is what i was always i was kind of always envisioning the hardware engineers yes which i have deep understanding and i was actually a mechanical engineer turned software engineer and so but it's it's awesome that it's doing exactly what we had hoped and then it's i think it's even going beyond what we had imagined which is that people that typically at companies never get access to this type of thing these are the people that typically run the tests and they are actually interacting and even updating the code do you open source the code?
24:48Why, why, why not? I think that is probably what we'll do long term. Yeah,
Read the full transcript
24:52Scott Morton:I would like to do that. I think, you know, we have to, I think in this stage, it's we're obviously still building it. So I think there will be a point in time when it's the right thing to do. Because at a certain point, you could imagine that becoming just such a powerful standard, and in the end, being extremely useful. But yeah, I imagine there's lots to figure out in getting things right. Yeah, I think we want to get it to a mature state. I think also it is, you know kind of a key part to the platform uh and so i think we want to make sure rebel gets into a good spot before we start to open source things yes that makes sense you mentioned that you you sort of had this transition from mechanical to software engineer but going even even further back what's the first thing that you remember building oh growing up yeah yeah wow yeah i i build all kinds of things with my uh my my dad so i grew up in wisconsin he had a workshop and we would just i got really into rc cars and we would i would build these like off-roading rc like mad max creations wow uh i really wanted to fully automate them but you know we didn't have rebel back then yes but yeah um was he an engineer your father no he wasn't um he worked in he worked for the state but he just was into this sort of stuff yeah he he did all kinds of like woodworking and things like that in his spare time so yeah built a lot of things growing up obviously yeah i had legos i built like an entire city uh even a space station in the basement uh of our house and yeah i i think there is there's something really it's actually what we look for in a lot of the people we're trying to hire at rebel is people that are fundamentally builders i think how you can look for that is is do they have side projects are they so into what they're doing that they're especially in college like are they also building things on the side yes and uh and that's kind of a key a key thing that if people love what they're doing uh they're going to i think just do a much better job at it um they're going to really care about the outcome it's also anything just a key to like early startups you need people that are really passionate about what they're building and see it as really uh kind of their life's work and their craft i love these proxies different founders used to find like who who is you know fit for their mission i like this side project idea what is the the history of your side projects like if you think about the sort of formative ones what what helped you level up bit by bit so i was into rc cars and legos and then i went into trying to build robots and stuff in my uh at my house and then i i didn't really know what an engineer was honestly i knew they built things and so it was really once i got into college that and then i was like I got access to this machine shop and just I went it was it was I had a lot I built all kinds of things I was to help start a few student groups and we had it was like one of them was to build a wind turbine that would um go to a community in Nicaragua uh that was super cool and yeah basically built wind turbines from scratch it was like you wanted to build it out of materials that were available in that location and so you're very much constrained because ultimately we wanted to let them um be able to to build these things yes and so that was a really interesting design constrained situation of like what materials can they get there what are the trade-offs you have to make for in nicaragua it's like engines certain engines or the magnets are hard to get so those would have to be sent there but all the rest you had to be machine you know basically to machine it out of just materials available there and i mean it was like we also made like a a solar it was like a solar panel um i forget exactly what they're called but they would basically hold the solar panel and point at the sun continuously throughout the day and we had to we built it out of just wood and like junkyard parts that's fine and then and then ultimately i ended up at a robotics lab um i always wanted to work at this robotics i finally kind of got into it my junior year and then i really really loved that experience like i was just yeah kind of similar to like building rc cars and stuff in the basement i was just but then i had like all these resources available to me i like actually had funding and i again had the the machine shop and i was building all kinds i actually yeah published a few of them did you have any you know i'm thinking of sort of the the paypal mafia building bombs in high school did you have any sort of close close shaves with things going going wrong yeah we did a little bit of that too my friends and i yeah we made like uh air guns that would you know we're actually like it would like shoot a pool cue actually oh wow like a like a harpoon well yeah we yeah all kinds of things like that yeah these are these are somehow fantastically good signals of someone being a good founder in my experience uh this sort of you know smart rule breaking uh tinkering slightly on the edge of danger were you thinking about being an entrepreneur in those days was that a like a concept you mentioned you didn't have the concept of an engineer really uh was a founder or something that you knew about honestly not really i i just knew i wanted to yeah i knew i just wanted to build stuff and if i could do it professionally that would be the best case scenario uh and so and then i did start following elon um and just what spaces was doing back in it was like sophomore year of college and just thought that was the most insane version of like that was like the ultimate at building things uh and i also just imagined they probably you know had the the best engineers to do it and so that's really why i was like okay i want to i want to try to get into space and me sneak into spacex is how i was thinking about it and yeah i ended up staying uh at minnesota a little longer than i expected i was i didn't i wanted to keep taking classes i kind of got into software side i was good the robotics lab i could you know build i could i could machine everything I could build the entire rocket design it, but I actually, I couldn't write the control software for it.
30:43Scott Morton:Uh, and so then I was like, well, I can stay here a little longer and go. And my professor said he'd sponsor me into the computer science department. Uh, and so that's actually why I ended up staying a lot longer, uh, as an, and then I had to go back and take all the prerequisite classes to take the masters, the graduate courses. And so it's kind of funny. There's a full through path there of like uh couldn't couldn't do this in for the robotics in the in the robotics lab uh and then also kind of saw the exact same problem uh later on at spacex and then and then also at rebel yeah do you know the the sort of heuristic of the fox and the hedgehog the fox is you know someone who loves finding many problems and isn't you know sort of believes that no one idea can explain the world and the hedgehog is like one problem over and over intensively obsessively you've sort of found ways to keep solving the same problem it sounds like where you're you know encountering this limit of you know hardware control and uh you know building the language for these systems to work first in college then at spacex and now and now with revel it's uh yeah it's fascinating to see that come around yeah and i think it's interesting because i think really that experience in college and then switching into computer science and being able to really understand both engineers perspective the the hardware engineer but then also the software engineer and i think that's that's really what we've tried to create is something that the hardware engineer can use but then the software engineer can also jump in and it's it's very familiar to them it's a text-based language compared to some of the other approaches out there that are graphical i say it's like it's like programming with crayons yeah um and so yeah i think i think that background is exactly has really set me up well to to to to found revel where do you think your fuel comes from when you think about your your history like where does the drive emanate i i think for whatever reason i mean i've tended to just go after it's probably both the hardest thing but also where i thought i could have the most impact.
32:45Scott Morton:I mean, I, I joined SpaceX as a, as a 25 year old intern and I was like, I'm just going to go in and outwork everyone. And that was my mentality. I was like, I, I'm going to sneak in there. I don't, I don't, I didn't think I was qualified. Uh, but I thought I would learn the most and I would really kind of see what I was made of. Honestly, that chip on the shoulder of, Hey, I have to outwork everyone. Were you the, I don't know, were you a good student, bad student? you know, the last one picked, that impulse comes from somewhere, right? I wouldn't say I was the best student in high school. I was always in like advanced math, but otherwise somewhat disinterested.
33:26Scott Morton:I think I had the same mentality going into Minnesota, honestly, as I thought, you know, joining, actually, I don't know if they do this anymore, but they actually had us there like, look to your left, look to your right. Like two of you will not make it to the program. Wow. They actually said that at the beginning at the orientation. two of you won't make it through. Yeah, gosh. It's true. I looked at the statistics on it. It's actually true. So there was some of that sense of, okay, I haven't been the best student, so now I'm going to have to prove myself extra. Yes, 100%. You mentioned that Elon's sort of maybe superpower, what he really spikes on is this ability to take these big swings and give people the confidence to do something a little outlandish, or at least it sounds outlandish.
34:06What are the parts of his mode of management that you have chosen not to take with you, that you're like, this didn't work for me or it's not the way that I want to run my company.
34:17Scott Morton:Honestly, I think overall, Elon's a credible CEO. I don't have a lot. I think extremely intense. I think, yeah, again, not for everyone. I loved it. I thrived in it. I think being challenged and I think I also was very fortunate. I was one of the first people to join Star Show. I think it was the first software engineer down in Boca Chica, Texas. No, no, no, Starbase. Yes. and um and at that point the program was really kind of this like backwater kind of like not the you know everyone really wanted to work on falcon at that time and it was kind of one of the crazy ones that would go and want to go work on early starship you know at the very beginning and i think letting people do that was awesome i mean it wasn't it was kind of a volunteer scenario but then he got pretty involved and you know i enabling people i mean you fly close to the sun at spacex You know, you're going to have you're taking a lot of risk for sure.
35:09Scott Morton:But enabling people to do that and give them a ton of agency and but also holding people accountable, I think, is the right recipe to do great things. Flying close to the sun at SpaceX means taking like a big swing on something and putting your name behind it with a lot of resources. And if that doesn't pay off, it's like, hey, then this didn't work. Is that roughly right? I mean, Elon says like you, I think he respects people that take big swings, but he also, you know, he tracks the batting average. Yeah, that makes sense. It's okay to have some misses. I think it's not okay to not like push hard.
35:42Scott Morton:If you think something is the right way to do things, you should say it. And if you, I think, kind of hang back and don't, and then it's like, it's then realized that you knew the right thing to do, but you didn't push for it. I think that wouldn't be seen very well by Elon. But yeah, I think there's high risk reward at SpaceX for sure. You're a couple of years in at this point. So I'm sure you're still sort of, you know, the CEO job is like you have to climb the skill curve every day, it feels like, I imagine. But as you think about the way that you prefer to lead, everyone interprets this job very differently.
36:18What are the places where you find you're sort of most uncompromising or maybe you want to hold the highest possible bar versus, you know, other folks that you've seen and maybe where there are places where you have more flexibility.
36:31Scott Morton:Yeah, I think the product has to be awesome. It has to do exactly what we say it will do. There's no, I have seen kind of in this space, people kind of forward selling capability or saying it can do certain things. And then that doesn't really pan out after a number of months. And that's when Rebel comes in to save the day. but yeah i think it's extremely important that uh we are very transparent with what it can do today what we plan for it to do in the future and then i think also uh i'm definitely pretty involved in making sure the product is what it it needs to be uh and uh it's still definitely best idea wins i mean i i change my mind when when there's no information all the time uh even when if i've like we just means an engineer or someone on the product side disagrees uh and then there's no information it's a clear like i was wrong i will admit it right away i mean i think that's a really really important like basically no ego is extremely important to to make the best decisions possible now i think i guess that is another thing i saw in elon is he would be extremely passionate but then presented with new information you'd be like well okay that was the quick switch that's it let's not go that direction anymore with the company we're definitely really trying to run a very tight engineering organization so i think i've seen yeah the proof is kind of clear with spacex what has happened and then you look at how the company was run and uh and it's really an execution machine i think we have to adapt some of that for revel uh it's not you know you don't have these launches that are really yes really powerful it's kind of aligning everyone we're going to launch on this day and then everyone kind of backs out uh their schedules and it's it's also a really nice tool to figure out what's actually the critical path.
38:18Scott Morton:It's a little different as a software company where you have a lot of things in motion at the same time. You have a lot of customers as well. But I think having a really strong engineering culture and that people join and they feel like, wow, I'm with the most elite. This is an elite team that has an incredible culture that is also moving really fast and delivering products. The best thing is when we deliver something for a customer and then they go and have some awesome test. Like they get through the entire hot fire on an engine and they always post it in our shared Slack channel. Like we get to kind of be part of their success.
38:55You mentioned these launches, that is something that from the outside, at least it feels like Elon does it so well as like finding these galvanizing moments, these, or sort of in some cases, maybe manufacturing even this thing that everyone has to run at, which feels like just ways of pushing energy into the system in a way. What is the version of that that works for you? Is it doing sort of the Gemba walk down the different tables and seeing what everyone's working every day? Is it something else?
39:25Scott Morton:No, I think it's some kind of customer milestone. Customer milestones, yeah. So there'll be some large test that a customer needs to do or maybe there's some new capability that they really need to do it well. So we'll kind of attach it to that timeline. and then i think the new one for us you know i think what's extremely exciting about where we're at right now is we've we're very competitive in the small scale testing world so small scale testing being like a benchtop test setup and normally with this these software for testing as you go from kind of small scale to larger scale you need different things small scale you want to be really fast, iterate really quickly, typically.
40:07Scott Morton:Larger scale, something like a rocket engine test site, which is a large facility on the desert. You want a little kind of more controls, you want more safety, but obviously you still want to move really fast. And I think what we really struck the array balance in with Revel is we're kind of both very fast to iterate with, but also still very performant and safe. And so what's awesome is we're doing very well in small scale very well in this kind of large scale facility and the next phase is industrials which is large scale systems and we're also so far we've we've seen that we are extremely competitive there as well and these are all of these different scales there's probably eight different types of software that are used and even inside of one company so at impulse they literally had eight different types of software wow and they have now uh fully standardized on revel and they're only of using Revel across tiny, even the smallest, like a circuit board testing system, all the way up to what they're using at this new site called Site1C, which they're going to use to test their entire stage.
41:06You mentioned it sort of in these steps of small scale testing, large scale testing, industrial systems. This is a very naive question, but are the industrial systems more complex versus a test because it's sort of continuous versus discrete or more inputs? Like what adds that as sort of a discrete step in your mind?
41:24Scott Morton:It is just many more, they call them tags, but they're just telemetry channels. Okay. Sort of input of some kind or another. So we're actually now deployed at a 250 ,000 channel system. Wow. 250 ,000 channels. Yeah. And so each of those channels is bringing some form of data from the system, whether that's heat or pressure or whatever that might be, across oil and gas or whatever it might be. Is that right? Correct. And that's not even, I think some of these will go up to several million channels. Okay. I don't have good calibration of what to imagine there, but that sounds extremely hard. Football field or several football field level.
42:06Yes. But just like complexity wise, like it sounds insane. Yeah.
42:10Scott Morton:It's a lot of systems. It's cool. Yeah. We just had a bake off, which I don't know if you know, it's like you kind of try two systems out and there were two engineers that were very familiar with these platforms. And so they kind of gave them the same assignment, one with the traditional approaches that they'd been using in this company. And it took them a week and then completely cold to revel, had never even seen the platform. They did it in one day. And they had been using the kind of old way of doing things for several years. And so that's when we, that kind of happened a few months ago. And that's where we're like, okay, we have something in this space as well.
42:48Scott Morton:We're both competitive, clearly in the test space, doing very well there. And then now it's clear we also have something that is extremely compelling in the industrial space as well. Do you have to convince some of these large companies that you're going to be around for a while? Because I imagine they're so used to someone, you know, this company's been around 20 plus years. You're around two years. You know, they want to know you're going to be around for 20 years, right? Yeah. Yeah. And that was part of the strategy in the latest funding round as well is that clearly we are going to be around for quite a while.
43:18Scott Morton:You know, there's no way we're going to run out of money. But I think it also comes back to the product just needs to be extremely compelling. Like I think that that's another trait is like the product is compelling enough. They will still at least try it out. And then you move from trying out, oh, it is extremely good. And then you move down the stages of. Yeah. Keep taking more off their plates in a way. Very cool. Wow. That's wild to think about. I think you've talked before about your position at Revel almost like a mini VC because you have to sort of bet on which companies to sort of resource and dedicate time to getting set up.
43:51What is the process like of taking a company in cold and saying, hey, you know, you're now ready to sort of run your next launch?
44:00Scott Morton:Yeah, I mean, this is something I think has been extremely surprising to me. We essentially can deploy our system in one day. Oh, wow. We actually have really never one actually was that very large system. It took two days. But otherwise, we have done fully same day or even like a few hours being fully deployed. So when you look at Revel the company as a machine at the moment, where do you see the big bottleneck? currently uh definitely hiring um we're i think we have at least my my bet on the company is that we need to keep an extremely high bar and uh that just propagates all the way you know until revel is you know 200 500 people if we can maintain that and which is i think uh another kind of lesson from spacex is i think they have they've done a great job at this and we need to replicate that at revel um you want to still be at 500 people everyone looks around like wow this is an incredible company all these people are are awesome to work with that's you know maybe harder for us a little bit and that we don't have the the name brand of of spacex quite yet but that's essentially the biggest the biggest bottleneck in that we um i mean demand is totally outrun the current uh size that we're at uh which is i think a great problem to have yes um even with the same day deployments my prime prime focus right now is hiring and building out the team when you say keep a high bar every company wants to do that right what does that mean for for revel specifically like what is uh and how do you find those people in a in a distinctive way you know i've heard you know the the largest array of different ways people find a little bit of edge in in the market like have you found a few pockets where for whatever reason we're extremely good at taking Midwestern, you know, tinkerers and turning them into, you know, the world's best engineers or whatever that might be for you?
45:53Like, what is what is your playbook?
45:54Scott Morton:We're pretty open to where people are coming from. But I think you just have to have a really good, a really solid process for assessing talent. And I think generally, like you kind of know when you see it, our process is, I think, quite good at this point. And yeah, we have the best engineers can usually determine if they're an engineer sitting across the table is going to be a good fit on the team. And so we rely pretty heavily on that. Talking about this sort of mini VC role that you have in a way, you get to have an interesting front row seat into the amazing pieces of hardware and companies that people are building.
46:33What do you think the world looks like in five, ten years from now when some of these different customers that Revel is serving flourish? what do you see that maybe others haven't realized fully yet this is one of the best parts of being at revel i think is that you get to in one day you can go to a nuclear reactor company you can go to
46:54Scott Morton:this like the most cutting edge satellite manufacturer uh and then you can go to like a hypercar company it literally they're all it's pretty cool in la there's a lot of them there so i think as an engineer that is really great and also i think revel has a unique position that it's It's like a one-to-many platform. So if you work inside a company and you're a software engineer, you're going to work on just that company, only get exposed to that company's hardware they're building. And then at Revel, you get to be part of all of these missions. But I think what's really exciting, I think the small modular reactor space, I think, is really cool.
47:28Scott Morton:I think there's definitely going to be, what I'm seeing is they're making great progress. And I think the regulations are also kind of clearing the way for them. Obviously, I'm very excited about the future space economy with Starship doing extremely well. And then all the companies betting on having low cost access to space. Hypersonics are also really cool. I think that's, yeah. So we're now working with a couple of the best companies there. It's awesome. One of them was actually very hard to get into. It actually took a year for them to finally say, okay, we're going to try Revel out. As soon as we got into one place, it just spread throughout the company.
48:07Scott Morton:uh it was like on the order of a month it went from one to like 20 systems wow what was the hesitation like for is that is there something that you learned from that this is a critical part of their operation uh and um they tried one approach before and they were kind of trying to see if that was going to pan out and then they're like okay this let's let's give revel a shot and uh we're able to very quickly prove ourselves and then also deliver on the you know we say it's 5 to 10x, it's going to increase your cadence of test. And then the first one we did, it did exactly that. They had like, their engineers became like application engineers.
48:45Scott Morton:They had to write a lot of Python. And then there had a lot of safety issues with that. Where like, you know, if you have Python, a big difference between Revel code and Python is that the runtime safety. So Revel, if it compiles, it cannot crash. So you may have these 12-hour long tests. In Python, there's no guarantee of that. And so you may have this simplest mistake that's probably most common is like a string interpolation error. And that will just kill your runtime system in the middle of a test. And then you have your system left in an unsafe state, may have even broken hardware. And then you also need to go and redo your 12-hour test.
49:24Scott Morton:And then whoever was waiting for the results is also upset. And so that first deployment fully demonstrated all the capability. And then we had people at other sites asking about it and then it kind of just took off. Wow. You know, I feel like it's almost axiomatic that every great company has to have at least one near-death moment. Have you had yours yet? No, I mean, I really can't complain on the trajectory of Rebels so far. See, that's what it looks like from the outside. I'm like, it looks almost too good. 23 months in, i i think it is though going back to talent i think it all comes down to to that i mean we've been very fortunate and we've gotten just an incredible set of engineers and and product folks jess winzinger joined from palantir who is i think you know we at spacex we really knew how to execute uh on the engineering side and she just brought a lot of product and kind of customer facing experience.
50:22Scott Morton:And so it truly is just getting an incredible group of people together. And a lot of people that have just a lot of experience in the relevant places that we needed. What's been the hardest week of running the company? I think honestly, the last month has been a little more frustrating in that we have, we just need more engineers on the team. Like we have an extremely clear vision of the future. it's a very good position that demand is so high so we've set up an fte team recently so that's kind of the biggest bottleneck and we're really focused on you know how do we hire great ftes it's obviously not something that spacex had so it's something that i'm personally having to learn a lot about but that frustration obviously is just like it's a it's a great problem to have we talked a little bit about ai building software uh and and the ways in which you know you can leverage that.
51:12To what extent do you have to build the system to accommodate for agents as almost users? Like, is that something that is already happening at some of these companies? Is that something that you imagine will start to happen more or because of the need for precision control, is that sort of less likely?
51:30Scott Morton:I think something very exciting that we're seeing is I think a lot of companies are trying to add AI into their product and kind of push on their customers and like see what's basically just throwing spaghetti at the wall and seeing what sticks with AI. And we have people are actually already using AI with our product. And I actually think we found that our code is the best possible format to generate, you know, control software from an AI, because the code has, that's again, going back to the qualities of it, it's highly performant, highly accessible, and high and runtime safe. And so if you're going to generate code, those are the exact things that you'd want you wanted to maintain accessibility meaning you can still read it and totally understand it so whatever you generate is still very easy to easy to grok what's happening and then the runtime safety is also really if you're if you're going to generate code and you're kind of like maybe it's less critical at least you know that if it gets to the compiler stage it's not going to crash so those are two two asterisk language i think are just make it the best possible thing to use with ai a lot of customers are already doing that yeah It's not something we're necessarily supporting directly, but they are already heavily leveraging AI with the platform.
52:43When you think sort of like very long term about what Revel becomes, you know, let's say five, ten years from now. If I extrapolate it out, it feels like there's like all these really fascinating things that you can do, whether that's, you know, creating an industry standard around some of these coding language, this coding language you've developed or, you know, aggregating demand across different industrial companies to sort of help them procure in different ways. Like there's sort of feels like a dozen different interesting things. Like what's your sort of vision for what this might look like?
53:16Scott Morton:The mission of the company is twofold. you know i've sat in the seat of many of these engineers and i was a hardware engineer and then at spacex i wrote a lot of control software a lot of test software as well and obviously that scaled up to starship uh so i feel like i have deep empathy for the engineers that are day-to-day just trying to get through their testing uh write the code they need to write and so we really want this you know today i'd say the tools they use they really feel like a bottleneck on their processes we want to give them something that feels like an accelerant and it is truly an accelerant.
53:49Scott Morton:The other side of it is if we do that at scale, what does that mean for all the companies out there going after these incredibly ambitious missions? Many more of them will be successful. They'll get through their testing campaigns way faster. You can test 50 times in a week instead of five times in a week. You're going to ship your product sooner and you're going to ship a much better product. And so that's what I'm extremely excited about long-term is that we deliver that kind of twofold mission of like for the engineer, but then also what does that enable across all these great companies. I always like to wrap up with a thought experiment or a question or two.
54:22If you had unlimited resources and no operational constraints, what is an experiment that you would like to run?
54:29Scott Morton:I watched so much Star Trek growing up. Huge TNG fan, Jean-Luc Picard. And I just want to know if, you know, humans going to be out there, you know, maybe are we going to go to another galaxy someday? I think just, are we going to be propagating around our galaxy? Like, is that actually, you know, Is that going to happen? Yeah, I think. I think we are obviously running the experiment. That's what I was super excited about working at SpaceX for 10 years. But I just really want to I want the answer to that question. Is that like I thought Star Trek was just like I was watching as like a, you know, in a middle schooler.
55:05Scott Morton:And it just blew my mind. It was like, wow, you know, we could be out there exploring all these other solar systems. And I would love to know. If you could assign a book to everyone on Earth to read, do you have one you'd want everyone to have read once in their life? And you get the assurance that they're going to understand it also. I reread this book. It's Our Mathematical Universe. I don't know that book. Who wrote it? I'm trying to remember it to get back to you. Yeah, it's really interesting. I think it really helps me put things into perspective. It just kind of chronologues all the physics discoveries up to today.
55:51Scott Morton:And it presents this explanation of the universe that it's really just a mathematical model. And that's it. And I think, you know, whatever is going on at Revel or in my personal life, it's like, I listen to this and it's just like, I think it really gives you like, it's like the most zoomed out perspective you could possibly have on everything. Yes. and there's something that gives you peace in that in a sense yeah i think it yeah i think it's always like i think the hard part and running a company is always i think seeing the seeing the forest instead of just looking at the trees and that it's like i i listen to it you know i usually when i'm trying to fall asleep and it actually helps helps a lot just to like it's like literally the most zoomed out view of the forest you can imagine like from a universe the the perspective of the universe.
56:39I love that. Well, that's a great, great place to end. Scott, thank you so much. Thank you.
57:09See you next time as we continue to explore the future.
From the publisher
Scott Morton is the founder and CEO of Revel, a software platform for testing and controlling complex hardware systems. Before founding the company in 2024, Scott spent nearly a decade at SpaceX building control software for Falcon 9 and Starship. That experience helped him recognize a broader problem: while rockets, nuclear systems, supersonic aircraft, and other advanced machines have grown increasingly sophisticated, the software used to test and control them is often fragmented and decades old. Revel was created to close that gap. The company has raised $180 million, was reportedly valued at just over $1 billion, and counts Impulse Space and Radiant Nuclear among its customers. Its platform scales from small benchtop tests to industrial systems with hundreds of thousands of telemetry channels. Revel has also created its own programming language, RevelCode, designed to combine performance and accessibility with the runtime safety required for high-stakes physical systems.
In our conversation, we explore:
- How AI can accelerate high-consequence software teams without replacing rigorous testing and review
- Why hardware test and industrial-control software still relies on tools created in the 1980s and 1990s
- What Scott took from Elon Musk about betting on teams before you know the answers
- Why Revel created its own programming language
- The “runtime safe” philosophy: what it means and why it matters
- Revel’s one-to-many model and the hardware frontiers it’s touching
- The strategic case behind Revel’s $150 million Series B
- How Revel’s edge showed up in an industrial-control bake-off
- How Scott hopes to preserve Revel’s engineering culture as it scales toward 500 people
- Revel’s long-term mission – and what it means for the hardware renaissance
—
Timestamps
(00:00) Intro
(02:04) Why no one will vibe-code a nuclear reactor
(04:15) Revel’s engineering edge
(05:27) What Revel actually does
(06:34) Why industrial software has stagnated
(07:52) Why previous startups couldn’t crack it
(10:26) The limits of building control software in-house at SpaceX
(15:20) Lessons from nearly a decade at SpaceX
(20:22) Why Revel built RevelCode
(24:46) Will Revel open-source the language?
(25:25) Scott’s early projects and builder mentality
(32:28) Where his drive comes from
(33:50) What Scott took from Elon – and what he chose to leave behind
(36:02) Scott’s standards as CEO
(38:56) Scaling from small tests to industrial systems
(43:40) Deploying Revel and the hiring bottleneck
(45:23) How Revel finds and assesses talent
(46:21) Emerging frontiers in hardware
(49:36) Revel’s unusually smooth trajectory
(51:05) How AI fits into Revel’s platform
(52:42) Revel’s long-term vision
(54:18) Final meditations
—
Follow Scott Morton
LinkedIn: https://www.linkedin.com/in/scott-morton-68334a15
—
Resources and episode mentions: https://www.generalist.com/p/an-ex-spacex-engineer-on-elon-musk
—
Production and marketing by penname.co. For inquiries about sponsoring the podcast, email jordan@penname.co.




