The first half of my second career (third maybe) in software was spent in satellite ground processing. My first true culminating project, so to speak, was when the portion of the US Maritime Domain Awareness meant for use by the Navy went to initial operational capability.
I checked out your site briefly. It's mildly amusing to note differences between that and a real system in use by military units. It'd be nice to be able to use a selector of some sort rather than typing in a location. The globe itself is most obvious, but a flat map works. If you're going to suggest arbitrary locations underneath the text entry box, you should probably suggest places you actually have imagery for. I don't care what looked at the hotel I'm in this morning and don't know coordinates for places off the top of my head, but I can find them on a map.
The real version of a system like this doesn't try to draw orbits and estimate what was overhead when. The imagery archives already have geolocation information you should be able to query directly instead of trying to project backwards like that. There are at least three downsides to the way you've done it. One, users typically don't care whether an image was collected from orbit. They just want to know what happened in location X at time Y. If you have aerial imagery or even ground imagery you can correlate with, augment, or entirely replace orbital imagery if it doesn't exist, that's just as useful. Two, satellites don't need to be overhead to collect on a location. The exact angles they can collect from are classified (and of course depend on atmospheric conditions and potentially other obstructions), but they don't have to be overhead. Three, not all satellites have fixed orbits. You can't always solve Kepler's equations to figure out where they've been from their current velocity. Some make changes to their own orbits.
Seeing things like this puts me in weird headspace. I think a lot of you get dazzled by how easy it's become to put together software. I want to reiterate the "not the bottleneck" phrase you probably keep hearing. Being able to do something like this relies on decades of past effort to put the sensor platforms in orbit in the place, create imagery from the data they collect, and archiving that imagery in a way that users can query. MDA itself was first announced by George Bush in his 2004 budget request. We went live with our first users in 2016. The effort involved was massive, but we had to invent new sensors, put them in orbit, test them in controlled, uncontested waters, figure out how to simulate data feeds that didn't yet exist in order to create software processing capabilities without being to run against real sensor feeds during the development, figure out how to chip, compress, and redact the massive files we produce so they can be disseminated over radio to tablets on ships in the middle of nowhere to field commanders that don't have top secret clearances with compartments for the collection method, or to partner nations that don't have US clearances at all.
The web frontend was such a small part of this that we never even retrained or hired JavaScript developers. The original non-browser frontend was a Java Swing desktop UI, so they just ported it to use the Google Web Toolkit, which transpiles Java to JavaScript, and that code was touched at a rate of maybe a few hundred lines a year, in contrast to every other part of the system involved in orchestrating the batch workload scheduling, order queueing, dissemination logic, everything that made it possible to process more data per hour than any other computing system on the planet, or at least they told us that in 2009. I'm sure that is no longer true thanks to LLM training. But man, we basically wrote our own Borg before Kubernetes existed (they of course migrated to Kubernetes eventually, which is why I'm in a hotel at KubeCon NA). We wrote our own filesystem because we couldn't get the IO throughput we needed from what the proprietary Unixes of the 90s offered. We wrote our own network protocols. We scrounged for replacement parts on eBay to service end of life SGI Altix boxes while the government squabbled over how to fund and who to award a contract to build a classified cloud, meanwhile canceling hardware refresh funding to already running operational systems. There are so many battle stories I really hope I can tell someday before I die when they're declassified. I'm sure the commercial providers you're querying have similar stories.
This is a nice effort, by the way. I don't want to come across like I'm downplaying it. I just want the next generation as they get awed at what they can do in days or even hours from a browser to understand you can only do that because of the supporting infrastructure and data that is out there. Bringing that data into existence took a lot of work. It was done by people. Without it, you're drawing ellipses on a screen. We had pocket computers that could do that with a few keystrokes 30 years ago.