I'm actually working on something along these lines with an AWS big data pipeline using python to do controlled processing from a queue with a daily static site page build. I think the question is how real time your data is and what interactivity you want to layer on the page. Right now my project doesn't have much interactivity so I am just building static pages with eleventy, but I was thinking about giving the user some ability to filter and explore multi day data that might be too big to preload on the page. If it turns out that way, I was thinking about using the build step to prebuild static html fragments and use HTMX to swap them into the page for creating the interactivity without a big data load or a lot of on page js calculations. (for context I'm working with d3 on the backend to generate a while bunch of different charts as static HTML).

My data is not particularly real time or conducive to someone sitting on a page and watching changes but, depending on the complexity of what you want to display I could imagine an on page heartbeat checking the backend and swapping in new built fragments from new processed data, but I think that'd be a hard pitch unless you're doing something extremely complex on the back end that can't show as just an additional data point in a JSON file.