Skip to content
anvas
Join the waitlist
← Back to anvas
Use cases

Strategies that do not fit in a settings form

Every strategy here has the same thing in common: it needs to do more than one thing, and it needs to decide for itself when to change.

That is the line between a bot and a graph. A bot performs a behaviour you configured. A graph holds several behaviours and the conditions that move between them.

Every entry gets its own reasonA DCA bot's safety orders are one rule repeated at fixed deviations. There is nowhere to attach a different condition to the third entry than to the first.One strategy that ladders in a downtrend and grids in a rangeA DCA bot cannot become a grid bot. They are separate objects with separate budgets and no shared state, so the switch has to be a human being.Not every strategy ends in an orderAlert-to-order bridges have no middle, and chat-alert tools have no conditions. Doing both means a script on a server you now maintain.Your Pine script finds the signal. The graph decides what to do about it.A webhook bridge turns an alert into an order. Any logic in between has to go back into Pine, which cannot see your positions, your other bots or your account.Five bots with five stop-losses is not a risk limitBots are separate objects with separate settings. Each one's stop-loss knows only its own position, so nothing on the platform knows your total.Take a third, take another third, trail the restMost bots offer one take-profit and one stop. Where multiple targets exist they are fixed percentages that cannot react to what has already filled.Enter on the 5-minute, but only when the daily agreesA bot instance is configured on one timeframe. A second timeframe means a second bot, which cannot gate the first.

The pattern underneath

Read three of these and the shape repeats. A platform built around bot types can express any one behaviour well, and cannot express a change of behaviour at all, because the change would have to live between two objects that do not know about each other. That argument, platform by platform, is on the comparison pages.

So it lives in you. You are the regime switch, the exposure check and the kill switch — which works, right up until the condition is true at four in the morning.

Everything above is the same move: take the part of the strategy that is currently in your head, and put it somewhere it can run without you, and be looked at afterwards.

Where anvas is today

Private alpha, invite-only. The core engine — the builder, the node library and live execution against real venues — is step 01 and is what these pages describe. Backtesting is step 02 and is not shipped yet, which matters if you want to test one of these before running it. The roadmap has the order, without dates.

03 — Early access

Get in before the alpha closes

Tell us what you trade and how you automate it today. We open seats in small batches and start with the setups closest to what already works in the alpha.

We email once when your seat opens. Nothing else. See our privacy notice.