Hi all — solo dev, in case some of you have hit this road block and can save me guessing….
I run My Running Dashboard (myrunningdashboard.com), an analytics dashboard for club runners — training load, relative fitness level, historical data context, race predictions over multiple distances - that kind of thing. Client ID 213283.
Grandfathered on the pre-June-1 Standard Tier (999 athletes / 3,000 daily reads), currently at ~250 athletes, growing by word of mouth, currently in free beta stage while I polish it.
I have submitted two applications this year asking for more daily reads within that existing allocation — not trying to move up to a new category, just more headroom on what I already had. May’s was maybe slightly speculative on numbers; August’s had real measured telemetry (peak-day reads, a documented traffic surge, an audit of every backfill-triggering code path). Both rejected, the first after many weeks wait, this latest one in just 4 days with the standard generic potential reasons list, no specifics. I can’t see anything obviously wrong with my application and there is no indication Strava are unhappy with it as the 999/3000 capacity remains in place.
Given the new tier language, I’m not actually sure what I applied into. Is a request like mine — more capacity on an existing pre-restructure grandfathered allocation — now evaluated as an Extended Access application by default, since that’s the only tier offering “greater user capacity”? Or is there a distinct process for legacy accounts that I’m missing?
Has anyone at similar scale (low hundreds of users, solo/indie, not a company) gotten a capacity increase through post-restructure? Trying to work out if another attempt is worth the effort or if I should just plan around the current allocation permanently.
A huge amount of effort has gone into MRD and this rejection without reason is quite disheartening.
Thanks — happy to give more detail if useful.
