You can set up different scripts in your package.json, one that logs to cypress dashboard and one that doesn't. You could run the one that doesn't on every commit, and output results somewhere else i.e. we have our gitlab integration set up with MS Teams so it spits out a message into a Teams channel. Then you can save the dashboard costs for Release Candidate runs when you've got a stable RC, or live-only smoke tests etc. Think about who you need to have visibility on the dashboard, and if others can gain visibility elsewhere. Also think about scheduled runs and how often you actually need results captured in the dashboard.