A few questions on dependencies: do you need to be using the paid Cypress dashboard? do you need to be using Github for your repo?
As for Github - no as well. We just have a Github app integration if you do to comment in on PRs. But we have teams using Gitlab/Gitlab CI as well. We print out our debugger links directly in your CI stdout or also add links into your JUnit report if that's enabled (ex for Jenkins). Though there's plenty of teams that just check our dashboard directly for test results as well! We just want to make it easy to access your test failure when they occur.
Typically our customers see the pain around debugability and currently waste dev & CI cycles rerunning tests and seeing their CI as largely ignored, or a productivity bottleneck to pushing code into main/production quickly. On top of that, they usually look for some tablestakes ability to load balance tests for parallelized runners, and some basic reporting to get a health check on their suite now and again.
Teams where their primary concern is around in-depth analytics and graphing reports, we have those on the roadmap, but can't say we're better than Cypress Dashboard yet :) But we think our focus on debugging overall gives teams a better chance of fixing errors, as opposed to reporting on them.
We have a free trial if you want to take it for a spin yourself! A lot of teams start off introducing us in an experimental PR to try out the product, and then merge into their main branch when they see the benefits. I'm also happy to chat in-depth on specifically where we might be able to help if you already have an existing Cypress set up, feel free to ping me at mike [at] deploysentinel.com
Saw your YC profile as well - I'll shoot you an email as I'd love to get a chance to chat with you more about what you thought about the messaging/product :)