"What about latency issues? How is your platform able to handle the load if more people join and use it simultaneously? As I understand, you are not registered with the MCA and do not have a CIN, which implies you are operating either as a partnership firm or an individual.
Given this setup, how do you plan to support users (24*7) and manage infrastructure during periods of high volatility, glitches, or other major technical issues.
Company registration in process as of Now MCA portal is stuck due to fire in servers
On latency & infrastructure:
Each user gets a dedicated IP address provisioned on our infrastructure, which they whitelist directly in their broker terminal . This means the kill switch fires from a fixed, trusted IP — no middleman routing, no shared congestion. It’s as close to direct as you can get without sitting inside the broker’s datacenter.
On scale:
Adding more users doesn’t slow down existing ones — each connection is isolated at the IP level.
One bad trade turns into three worse ones because you’re not thinking anymore — you’re just trying to get the money back. Feels like conviction but it is not.
The fix that actually worked: a hard stop on new positions for 30 minutes after closing a loss. No exceptions. Take time to think and then start again
This is very true. A profitable trade can be dangerous if it teaches the wrong lesson.
I’ve had trades where I broke the entry rule or widened the SL, still made money, and then subconsciously started treating that as “experience”. Later the same habit came back in worse conditions and cost much more.
That’s one reason I like tagging trades in EdgeLog. P&L alone makes the trade look fine, but when you mark it as “rule broken” or “poor entry”, the review becomes more honest. A green trade can still be a bad trade, and a red trade can still be a good one if the process was followed.
Outcome is noisy. Behaviour is what needs tracking.