Help
Not-so-FAQ
Welcome to Speedrun Insights. Here's a bit of information about what this is, and a few requests from me if you'd like to use it.
What is this?
Speedrun Insights is a tool that lets you upload your speedrun data and get a deep analysis of your runs. LiveSplit is an amazing timer and data resource, and speedrun.com provides tremendous leaderboards, but this is meant to help with deep analysis of your runs. With comparisons to past runs, reset tracking, PB history, and IL statistics, I'm hopeful this will help you focus your practice and optimize your runs.
Why does it exist?
I wanted a personal project to work on a few software engineering concepts and hopefully learn some new things. Speedrunning was a natural fit — it's something I understand and care about, and the idea lined up with a lot of technical goals I had. As it started to come together I thought it might be useful for others, so I decided to make it available.
How do I use it?
Log in, upload one of your LiveSplit .lss files, and look at your data. Explorer is where you browse historical runs for a category (and drill into individual segments). Insights is for more detailed analysis. On Manage you can remove all runs for a category and start over.
Where is it going?
I'm not sure yet. If nobody uses this, or if I run out of interest, I may leave it like this and move on. If people like it and stay engaged, I may keep building.
The biggest gap right now is that any .lss you re-upload for the same game/category must have the same segment layout. If you delete, add, or rename segments, the current version of the site will reject that file. I'd like to add segment mapping to get around this, but there's an easy workaround in the meantime: delete the runs on Manage and re-upload.
Taking that a step further, I'd love more run management — editing segment names, layout, and historical run data entirely in the app.
Longer term, this could become a place to share analytics with other runners, or even aggregate data across a community. That's tricky, because everybody tracks runs and splits differently, but I think there are ways to do it. A first step would be allowing run analytics to be shared. For now, my policy is that all of your data is yours and is private.
Another feature I'd like to make more broadly available is AI integration — asking an LLM "tell me about this run" or "where am I losing time?" sounds really cool. I do have a prototype version of this feature already built, but since LLM use is expensive, I have to control access to it. If you would like to mess around with it, just let me know! I also do have an MCP server available even today which you could use to set up your own chat or integration, if you know how to do that. If you'd like access to that too, just ask.
Video demo
It's a work-in-progress...
This is very much an alpha, if even that. I don't claim it's feature-complete or without bugs. Given that half of my reason for making this was to experiment with some technical stuff, not every feature is necessarily useful to everyone.
It looks crappy
Hey... I think it looks pretty good, all things considered. I'm by no means a designer, and I think the LiveSplit-inspired color scheme works. The lack of images and branding also takes a bit away from the look, but managing images across an unknown and unbounded number of games just isn't feasible for one person. At a minimum, it would be great to include the same split images you use in LiveSplit — but that means storage and moderation I'm not equipped for at the moment. I'd love to do more here, so we'll see.
The analytics are wrong
I wouldn't be surprised. I only had my own .lss files as examples, and the sheer number of ways people save data and manage splits would be impossible to anticipate. If something is blatantly wrong, I'd love to know. If you're willing to share your .lss along with a clear description of what metric is wrong and what it should be, that would help a great deal.
It's slow and bad and doesn't work
Well, hopefully not. I'm currently running this on the cheapest infrastructure I can. I don't know what load I'll get, so I'm keeping server and database size intentionally small. If demand shows up, I may increase the resources — but that would add cost. For now, I'm keeping spend limited to what the project actually needs. Please let me know if specific things are problematic. I'd like to know what they are and see if I can address them.
How can I help?
Try it out. Upload your runs, use the features, tell your friends, and give me feedback.
Report issues / request features
Let me know about issues, especially the sorts of things described above. This is an alpha, so there are sure to be things that are wrong. And as one person, I'm sure there are useful analytics or features I didn't think of. If you'd like access to the MCP server or to the built-in AI chat,feel free to ask.
Join the Discord
To report issues, request features, or ask me anything else about this, please join my Discord server (the #speedrun-insights channel).
Share!
If you find this useful, tell people about it! I don't use social media, so I can't advertise this in that way myself. But if you think I'm on to something here, please let your speedrunning communities know about this.
Donate?
Well, thank you for offering. For now, please just throw me a sub or some bits on Twitch (@Antilles58) — that'll be plenty. If server costs start to increase, I may add a more formal donation option here to help cover that. If this becomes a useful tool, I would hate for cost to be a reason I'd have to keep it slow or shut it down.