Flowmate · Algo workflow and backtesting
Draw a strategy, then prove it.
A node-based canvas to compose a strategy, a backtest to run it against history before it touches an order, and deployment from the same screen.
Built to the SEBI algo framework rather than retrofitted to it — which is the difference between offering algos and being allowed to.
- Node-based canvas
- Backtested before deploy
In plain words
What Flowmate actually is.
Every broker is being asked for algo access, and most of the answers on the market are a scripting box with a disclaimer under it. The problem is not composing a strategy — it is proving what it does before it reaches the market, and being able to show a regulator how it got there.
Flowmate is built around that. A strategy is drawn on a canvas as nodes rather than typed as code, which makes it readable by whoever has to approve it; it is backtested against history before it is allowed near an order; and the framework it was built to is the one that governs it.
What you get
Four things it does, and what is behind each.
Every line below names something that can be shown in a walkthrough. If one of them cannot be, we would rather you found out in the hour than after the signature.
A canvas, not a script
Strategies composed as connected nodes, so the person approving one can read it without being able to write it.
- Node-based builder
- Readable by a reviewer
- Versioned per change
Proven against history
A backtest run over historical data before deployment, with the result attached to the strategy that produced it.
- Historical backtest
- Result kept with the strategy
- Run again on every change
Deployed from the same screen
From canvas to live on one surface — no export, no second system, and no gap between the thing tested and the thing running.
- One-screen deployment
- Tested build goes live
- Stop from the same place
Inside the framework
Built to the SEBI algo framework from the start, so approval and identification are part of the product rather than paperwork around it.
- To the SEBI framework
- Per-strategy identification
- Audit of every deployment
Common questions
The ones that come up on the first call.
If yours is not here, it is a better use of an hour than a slide deck — bring it to a walkthrough.
Can clients build their own strategies?
That is a decision for you and for the framework you operate under, not a switch we would flip by default. Bring it to the walkthrough — it changes both the configuration and the per-user count.
Can a strategy be deployed without a backtest?
Not by design. The backtest result is attached to the strategy version that produced it, and a strategy edited after its test is a new version needing a new one. That is the control the module exists to provide.
The next step
See Flowmate on your own books.
Tell us how this part of your firm runs today and what you would want it to stop doing. We will walk you through the same screens your team would work in.
Or call +91 76765 83344