Below are the most common questions that we get asked.

If you have a question that isn't listed here, please send it to feedback@tradologics.com.

What is an action?

An action is the basic unit we use to measure platform usage. It represents any operation you initiate with the cloud platform. This includes: every API call, every Tradehook data push, every Monitoring minute (during market hours).

Where are you getting market data from?

We're working with data from multiple sources, including AlgoSeek, IEX Cloud, Finnhub, as well as Forex and Crypto data from every supported exchange/broker.

Do you have Level-2 market data?

We currently support US Equities (Stocks and ETFs), FX, and Crypto at minute-level data. We will offer tick-level and tick-based data bars by early next year (tick bars, volume bars, dollar bars). Support for L2 data is on the roadmap for early next year.

Can I use the universal API from my servers?

Yes, you can! Although your algo code isn't visible to anyone (including us), we understand that you may feel more comfortable - at least at first - to run your algo from your own servers, and that's totally fine.

How do I access market data?

You can use our API for that - but you don't really have to 😉. We will push market data to you based on your specified intervals (1M, 45M, 3H, EOD, x minutes before/after the market opens, etc) - or whenever an event you've subscribed to occurs (earnings report, % price move, etc).

What about security and IP protection?

We have several layers of security, including putting all of our servers behind a firewall, using containerized environments for every strategy, encrypting everything from disks to database records, using password-less logins, forcing API token expiration, and obfuscating everything to make it nearly-impossible to tell which trade belongs to which trader and which trades are part of the same strategy.

Wouldn't you have the power to "reverse-engineer" my strategy?

Theoretically, for every trading platform, broker, and auditing service can use your trading data to reverse engineer your strategy. However, we've designed the platform in such a way that it will be extremely hard to do so unless it's done in real-time (see the question above). On top of that - we really wouldn't want to copy anyone's strategy, as it both unethical, and not good for business (if we did that, our customers would both leave us and sue us - and win).

Can you do both event-driven and vectorized backtest?

Our backtester is an event-driven. It was designed this way to allow you to move from backtesting to live trading with zero code changes. That being said - you can use the research instances to perform vectorized backtesting in order to "prototype" a strategy.

Can I backtest/trade using the same code even with rolling instruments like Futures?

Support for Futures is coming in Q3 of this year.

Will there be support for European markets?

International markets support will be added early next year.

Are there going to be additional fees on data feed?

No. Market data push is going to be billed just like any other "action".

Where are the servers going to be located (physically)?

Our servers are based in Equinix's New York datacenter. When we expand support for trading international markets, we'll also be placing servers in the relevant locations.

Which programming language does your editor support?

Python, Javascript, Java, Go, Ruby, PHP, C#, and Bash.

What about execution speed?

Trading using an intermediary platform such as Tradologics adds some latency to every order submission. In our case, there's an average added latency of 100ms-200ms. However, since our servers are located on Equinex, the overall execution speed should be faster compared to running on your local machine. That being said - if you're looking to trade sub-second strategies, than Tradologics is not the platform for you for now.

Can we plug in our own data source?

Yes. Since your strategy is running on its own isolated environment - you can install anything and do anything you want - including connecting to external data sources.