Commodities trading automation

The exchanges and instruments we build for

Commodities trade on their own venues, each with its own contracts, hours and quirks. We build across the ones that matter, through your broker's API:

• Energy, on NYMEX. Crude oil and natural gas, with the session behaviour and rollovers those contracts are known for.
• Metals, on COMEX. Gold, silver and copper, spanning the full contract calendar.
• Grains, on CBOT. Corn and wheat, with their delivery months and seasonal patterns.
• India, on MCX. The same engineering for Indian commodity futures, for traders and desks working the local market.

• Gold
• Silver
• Copper
• Crude Oil
• Natural Gas
• Corn
• Wheat

Trend and swing strategies, run as software

Whatever your approach, we automate the rules you have already defined. Two families come up again and again in commodities:

• Trend-following. Riding a sustained move in oil, gold or the grains, with your entries, your exits and your position sizing enforced in code.
• Swing trading around patterns. Trading structures like rising and falling wedges, where your rules define what counts as the pattern, the entry and the invalidation.

The pattern and the parameters are yours. We build the detection and the execution around them, and we test the whole thing honestly before it ever goes near a live account. For a worked example of the engineering behind pattern detection, read our case study on backtesting a linear-regression support strategy.

Why commodities are their own engineering problem

A commodity system carries problems that equity systems never see, and they are where most of the real work goes:

• Contract rollover. Futures expire, so the code has to roll from one contract to the next on the right date, and build clean continuous series for research without inventing prices that never traded.
• Leverage and margin. Futures are leveraged, so margin and position limits have to be checked in code before an order goes out, not discovered after.
• Sessions and time zones. Each venue keeps its own hours, with breaks and settlement times that naive code gets wrong.
• Many venues at once. A book spread across energy, metals and grains means several contracts, several calendars, and one system that has to keep them all straight.

Rollover is the part that most often breaks a naive commodity system. We go into it in our guide to automating futures contract continuity, and our futures trading automation page covers the broader picture.

You bring the strategy. We build the system.

We are engineers, not advisers. We do not supply commodity strategies, we do not give trading calls, and we make no claim about what any strategy will earn. Commodity futures are leveraged, and leverage works against you as easily as for you, so the risk and every decision stay with you. What we do is turn the logic you already have into software that runs it correctly, and stops the moment you tell it to. Most of this work lives inside our custom trading software and broker API integration.