Feature request
Tell us what it should do next
Every request is stored the moment you send it and read by a person. We do not run a public vote board, and we will not tell you a date we are not sure of: what you get back is a straight answer about whether it is something we intend to build.
What helps
Three things that make a request land
None of these are required, and a one-line request is still worth sending. These are simply what turns one into something we can act on.
The problem, before the solution
What you are trying to do and what stops you, rather than the feature you have already designed. The best requests we have had described a workflow; the fix turned out to be simpler than the feature that was asked for.
How often it bites
Every trading day, or once a quarter? A small annoyance you hit daily outranks a large one you hit rarely, and we cannot tell which is which from the request alone.
What you do instead today
The workaround tells us what the feature actually has to beat. It also occasionally tells us the platform can already do it, in which case we will say so and show you where.
The request
Send it
Already on the way
Adapters for Groww, Upstox, Dhan are in development, so a request for one of those is a vote on ordering rather than a new idea. The brokers page is the honest list of what is live today.
One thing we will not build, whoever asks: anything that decides what to trade. QuantGrid is a technology platform, not an investment adviser. It replicates orders you place yourself, and it is not registered with SEBI in any capacity.
Something broken rather than missing? The bug report form takes a screenshot or a recording with it.