Skip to content

Feature request

Tell us what it should do next

Every request is 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, and why.

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 get describe a workflow, and the fix often turns 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 every morning 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

Use the address on your instance if you have one; it saves us asking which instance you mean.

What you are trying to do, and what stops you today. Never include passwords, API keys or broker TPINs.

How often it comes up, and what it costs you today. This is what we weigh requests against each other with.

We read every one, and reply within one working day.

One thing we will not build, whoever asks

Anything that decides what to trade. triStack AlgoTrader is hosting infrastructure, not an investment adviser and not a signal provider. It will not ship signals, tips, calls, a strategy marketplace, copy trading from someone else's account, or a model that tells you what to buy, and no amount of demand will change that: forming a view on a security and putting it in front of you is a regulated activity we are not registered for and have no intention of entering. Ask for anything that helps you run your own code better and we are listening.

Everything else is fair game, including the unglamorous infrastructure requests. Read what the platform does today first if you want to check whether it already does it, and our compliance position if you want the full version of the paragraph above.

Something broken rather than missing? The bug report form takes a screenshot or a recording with it.

Before you send

What happens to a request

How it is read, what you get back, and why there is no votes board.

Get started

Get your own instance

Tell us what you trade and how you run it, and we will provision an instance for you: your own database, your own dedicated address to whitelist at your broker, and your own engine. You bring the algorithms.

Your infrastructure, your code, your broker account. · [email protected]