Live trading is a graduation, not a default.
The sandbox is the product; a real broker is the opt-in. A real order can only leave Akechi Trade through four gates, checked together so none can be skipped — and when one refuses, the refusal names the gate that stopped it. (CL-009)
- Deployment flagoff by default
- Versioned consentexact wording
- Step-up MFA15-minute lifetime
- Your confirmationevery single order
The gates, one by one
1 · Deployment flag
Live trading is off by default in every deployment — the default is written into the values files our infrastructure checks lint. The admin console can display the switch; it cannot flip it. Turning live trading on is a deploy, reviewed like one.
2 · Versioned consent
You consent to specific wording under the DPDP Act, and the consent stores the version you saw. If the wording changes by one clause, prior consent is invalid and you are asked again. Nothing is inferred from your continued use.
3 · A fresh second factor
Step-up MFA with a fifteen-minute lifetime. A session you opened this morning does not get to place a real order this afternoon — recent is the point.
4 · Your confirmation, on every order
The confirmation field defaults to absent, so an integration that forgets to ask is refused rather than trusted. There is no bulk mode, no standing instruction, no “confirm all”. One order, one deliberate yes.
Where this stands with SEBI, in plain words
SEBI's February 2025 framework regulates retail algorithmic trading — automated orders placed on your behalf. Akechi Trade places no automated live orders, ever: gate four means every real order carries your explicit, per-order confirmation, which is what keeps this product outside that perimeter. The refusal text in the product names the framework, so the reason is in front of you at the moment it matters, not buried here. (CL-009) We treat this line as load-bearing — it is listed on our homepage under “what we will not do”, and it is not negotiable for convenience features.
Zerodha Kite, mapped honestly
Kite is the adapter that exists today. The architecture is broker-agnostic — adapters declare capabilities, and the bridge maps orders loss-transparently — but we name integrations when they work, not when they are planned.
A bracket order becomes a GTT-OCO — and says so
Zerodha discontinued bracket orders, so a sandbox BO graduates to a GTT-OCO trigger. That is a different risk shape: a bracket's stop is a live order resting at the exchange; a GTT is a trigger sitting with the broker that becomes an order only when touched. The adapter attaches that note to the mapped order where you can see it, because the failure mode we refuse is believing you have a bracket when you do not. The adapter also declines to claim bracket support — a capability it does not have is not listed. (CL-032)
A timed-out order is never retried
If a live order times out, its state is unknown — the broker may or may not have it. Akechi Trade marks the attempt UNKNOWN and refuses further attempts until it has reconciled against the broker's own book. You cannot route around this by clicking again, and neither can our code. The duplicate order is the disaster this rule exists to make impossible. (CL-033)
Your broker password has nowhere to live
We integrate through the broker's own token flow. The session model has no field a password could occupy, a scanner refuses any payload that carries one, and the tokens we do hold are envelope-encrypted — the details are on the security page. (CL-031)
Until you choose to graduate, nothing here applies to you: the sandbox runs on virtual money, full stop. Start there — join early access.