Read time … min

AI-native runtime for Dukascopy Bank trading strategies

Author JForex SDK and FIX 4.4 strategies in Cursor, Claude Code or any AI IDE. Deploy from GitHub into a managed cloud runtime with first-class MCP control, logs and region selection.

By the TradingHost engineering team

Section 01 · At a glance

At a glance

Broker
Dukascopy Bank
Broker type
Swiss bank and forex/CFD broker
Asset class
Forex, indices CFDs, commodities CFDs, metals, share CFDs, bond CFDs, crypto CFDs
Supported products
60+ spot FX currency pairs, major and minor indices CFDs, metals (XAU/USD, XAG/USD), energies, soft commodities, share CFDs and crypto CFDs. Dukascopy operates a marketplace model with ECN-style execution against bank-tier liquidity.
Runtime model
Containerised strategy runtime
Deployment source
GitHub
Languages
Any language that runs in a container (JForex SDK is Java-native; FIX is language-agnostic)
Common integrations
JForex Java SDK (maven com.dukascopy.api), JForex Strategy API, FIX 4.4, NautilusTrader (via Java bridges), custom connectors
AI workflow integration
MCP control surface for Cursor, Claude Code, GitHub Copilot and CLI agents
TradingHost role
Runtime, deployment, logs, health checks, region selection, MCP control
Dukascopy role
Bank account, broker account, API access, market access, execution venue (ECN marketplace)
Regulators
Dukascopy Bank SA (FINMA bank licence, Switzerland, since 2010); Dukascopy Europe IBS AS (Latvian FCMC, MiFID II / EMIR, Latvia); Dukascopy Japan KK (FSA Japan).
Retail leverage caps
Switzerland (Dukascopy Bank SA, FINMA): FINMA leverage rules apply. EU (Dukascopy Europe, Latvian FCMC, ESMA-aligned): 30:1 on major FX, 20:1 on non-major FX and gold, 10:1 on non-gold commodities and non-major indices, 5:1 on stocks, 2:1 on crypto CFDs. Japan (Dukascopy Japan, FSA Japan): 25:1 leverage cap per Japanese FSA rules.
Affiliation
TradingHost is independent and is not affiliated with Dukascopy Bank SA, Dukascopy Europe IBS AS or Dukascopy Japan KK

Section 02 · What Dukascopy Bank offers

What Dukascopy Bank offers

Dukascopy Bank offers spot FX on 60+ pairs, indices and commodities CFDs, metals, share CFDs, bond CFDs and crypto CFDs against a Swiss-bank-licensed ECN marketplace through the JForex Java SDK and FIX 4.4. The JForex SDK is the canonical TradingHost-compatible surface; FIX 4.4 is the institutional-style alternative. Specific endpoints, JForex strategy classes and the full instrument list live in the Dukascopy Javadocs and developer wiki.

Markets and strategy patterns

  • JForex Java SDK strategies on 60+ FX currency pairs
  • Bank-licensed Swiss-entity strategies (FINMA)
  • ECN marketplace execution strategies
  • XAU/USD and XAG/USD precious-metals strategies
  • Crypto CFD strategies (BTC/USD, ETH/USD)
  • Tick-data backtests via the Dukascopy historical-data feed
  • FIX 4.4 institutional-style execution

API surface

Product surfaces
60+ spot FX currency pairs, major and minor indices CFDs, metals (XAU/USD, XAG/USD), energies, soft commodities, share CFDs, bond CFDs and crypto CFDs. Dukascopy is positioned as a bank-tier ECN marketplace; both bank and broker functions are under one Swiss licence. Demo and live JForex environments are separate.
Connection methods
JForex Java SDK (canonical surface) published at the Dukascopy maven repository under com.dukascopy.api. The SDK exposes the JForex Strategy API for implementing strategy classes that run inside a JForex container. FIX 4.4 is available as a separate institutional-style surface. A demo Java client and a historical-data Java client are available for development without a live account.
Authentication
JForex SDK uses Dukascopy account credentials (username, password and optional PIN) supplied at strategy startup; the strategy connects to either the demo or live JForex server. FIX 4.4 sessions require explicit FIX enablement on the live account, which carries a monthly subscription fee. Demo Java clients and the historical-data client are available without account approval for development.

For specifics, refer to Dukascopy

JForex Java SDK Javadocs and the Dukascopy developer wiki are the source of truth. Treat the FINMA register as the authoritative regulatory reference.

Section 03 · Build with AI

Build your Dukascopy strategy with AI

Pick an integration method, fork a TradingHost framework starter, and author your strategy in an AI IDE. The JForex Java SDK is the canonical TradingHost-compatible path; FIX 4.4 is available as a paid alternative. Dukascopy does not run on MetaTrader.

  • JForex Java SDK

    Canonical Dukascopy programmatic surface. Implement the JForex IStrategy interface, package as a JAR, and deploy to TradingHost.

    dukascopy.com (use JForex SDK)

  • FIX 4.4 (subscription)

    Institutional-style FIX 4.4 session, separate Quote and Trade sessions. Live FIX is a paid monthly subscription on Dukascopy.

    dukascopy.com developer wiki

  • NautilusTrader (via Java bridges)

    NautilusTrader is Python-first; Dukascopy integrations typically run JForex strategies alongside as a Java sidecar that publishes events to the Python core.

  • Custom Java connector

    Your own Java client built on top of the JForex SDK, or any FIX engine in any language against the FIX 4.4 surface.

Framework support for Dukascopy products

The JForex SDK and FIX 4.4 both span Dukascopy's full multi-asset surface. NautilusTrader requires a Java sidecar to bridge JForex events to its Python core; support is partial. MetaTrader is not offered by Dukascopy.

FrameworkFXIndicesCommoditiesCFDCrypto CFDs
JForex Java SDKSupportedSupportedSupportedSupportedSupported
FIX 4.4 (subscription)SupportedSupportedSupportedSupportedSupported
NautilusTrader (Java bridge)Partially supportedPartially supportedPartially supportedNot documented as supportedPartially supported
MetaTrader 4 / 5Not documented as supportedNot documented as supportedNot documented as supportedNot documented as supportedNot documented as supported

✓ confirmed support per JForex SDK Javadocs and Dukascopy developer wiki. "limited" indicates partial framework adapter coverage. "no" indicates Dukascopy does not offer the platform.

TradingHost does not force a framework. It runs your project.

Author with AI

The framework starters above pair naturally with AI IDEs. The TradingHost MCP control surface closes the loop: AI tools can inspect deployments, review logs and manage the runtime alongside you, never the trade execution path.

Section 04 · Run on TradingHost

Run your code on TradingHost

Dukascopy Bank provides the Swiss-bank-licensed broker account and JForex SDK access. TradingHost provides the production environment where your Dukascopy-connected Java strategy runs.

Instead of running strategy code on a laptop, desktop machine, generic VPS or manually configured server, you deploy from GitHub into a TradingHost-managed container runtime.

You

  • Your repo contains your code.
  • Your deployment defines how it runs.
  • Your strategy connects to Dukascopy via JForex SDK or FIX.

TradingHost

  • Keeps the runtime online.
  • Surfaces logs and health checks.
  • Region selection.
  • Controlled deployment surface.

Deployment flow

  1. STEP 01

    Connect GitHub

    Authorise TradingHost to access your GitHub account.

  2. STEP 02

    Link a repo or start from a framework

    Point TradingHost at your existing strategy repo, or fork a TradingHost JForex SDK starter (Maven, com.dukascopy.api).

  3. STEP 03

    Deploy into a TradingHost container

    Pick a region (EU is the natural fit for Dukascopy Bank SA Swiss-tier liquidity; US-East when paired with US data), supply the environment values your strategy needs (Dukascopy username, password and account selector, demo or live JForex server), and deploy. TradingHost builds your container from the repo (the JForex JAR plus its Maven dependencies) and runs your strategy on managed Kubernetes infrastructure.

  4. STEP 04

    Monitor logs and health

    Watch live logs, health and runtime state from the TradingHost dashboard. The same surface is reachable through MCP from any AI IDE, so Cursor, Claude Code or a CLI agent can read deployment state and manage the runtime alongside you.

  5. STEP 05

    Update and redeploy

    Push changes to your GitHub main branch and TradingHost redeploys automatically.

Deploy

Section 05 · Operational notes

Operational notes for Dukascopy Bank

Things that bite you when you actually run a Dukascopy strategy in a containerised cloud runtime. Every claim is paraphrased from the JForex Javadocs, the Dukascopy developer wiki or the FINMA register; the deployment-side guidance is from running these strategies on TradingHost.

  1. 01 · Java-first SDK

    JForex SDK ships at the Dukascopy Maven repository under com.dukascopy.api

    Dukascopy is the only major retail forex broker whose programmatic surface is Java-native rather than HTTP. The JForex SDK is published at Dukascopy's own Maven repository (not Maven Central) and is consumed by adding the Dukascopy repo to your build.gradle or pom.xml and pulling com.dukascopy.api. A strategy implements the IStrategy interface, packages as a JAR, and is uploaded to JForex (or run from a container that embeds the JForex client). TradingHost builds and runs the container that hosts the JForex client; the JForex client itself connects to Dukascopy servers.

    SourceDukascopy: use JForex SDKJForex Javadocs

  2. 02 · Demo vs live

    Demo Java client and historical-data client are free; live access requires account approval

    Dukascopy publishes a demo Java client and a historical-data client that can be used without a Dukascopy account to develop and backtest. Live trading requires opening a Dukascopy Bank or Dukascopy Europe account, completing KYC, and explicitly enabling the JForex API for that account in the user portal. The demo and live JForex servers are separate; credentials are not interchangeable.

    SourceDukascopy JForex API overview

  3. 03 · FIX subscription

    FIX 4.4 is a paid monthly subscription on live, separate from the JForex SDK

    Dukascopy offers a FIX 4.4 surface for institutional-style execution, with separate Quote and Trade sessions. Unlike JForex SDK (which is included with the account at no extra cost), live FIX access carries a monthly subscription fee. For most retail-leverage strategies the JForex SDK is the right path; FIX is for clients with existing FIX engines or who need the multi-asset behaviour of a single FIX session.

    SourceDukascopy developer wiki

  4. 04 · Bank licensing

    Dukascopy Bank SA holds a FINMA bank licence; client funds are bank-deposit protected

    Dukascopy Bank SA has been a FINMA-supervised Swiss bank since 2010. Client cash at Dukascopy Bank is held under Swiss banking rules rather than the segregated-client-account model used by non-bank brokers. This is a credibility differentiator from non-bank retail FX shops. Dukascopy Europe IBS AS (Latvia) and Dukascopy Japan KK operate as separate entities under their own regulators (Latvian FCMC and Japan FSA respectively) and do not automatically inherit Swiss bank protections.

    SourceFINMA authorised institutions register

  5. 05 · Marketplace execution

    Dukascopy operates a multi-bank ECN marketplace; expect partial fills on size

    Dukascopy aggregates liquidity from multiple bank counterparties into a single ECN marketplace and routes orders against the best available price. Strategies must handle partial fills explicitly, especially on size and on minor pairs. JForex IStrategy implementations receive onTick and onMessage callbacks that may emit multiple fills for a single submitOrder call.

    SourceJForex Strategy API reference

  6. 06 · Trade reporting

    FINMA, EMIR and MiFID II reporting is Dukascopy's responsibility

    Dukascopy Bank SA reports under Swiss FINMA rules. Dukascopy Europe IBS AS reports under Latvian FCMC, MiFID II and EMIR. Dukascopy Japan KK reports under Japan FSA rules. TradingHost does not perform regulatory trade reporting on your behalf. The strategy code you run on TradingHost is your own algorithmic activity; reporting attaches to the Dukascopy entity holding the account.

    SourceFINMA authorised institutions register

Section 06 · Built for

Built for

TradingHost Dukascopy runtimes are best suited to:

  • Developers building strategies in AI IDEs (Cursor, Claude Code)
  • Java-first JForex SDK developers
  • Bank-tier liquidity, ECN marketplace systematic traders
  • Tick-data backtest-validated strategy developers
  • Teams moving from MetaTrader and VPS hosting to containerised deployment

Connecting GitHub and creating your first strategy is free.

Section 08 · FAQ

FAQ

No. TradingHost is independent and is not affiliated with Dukascopy Bank SA, Dukascopy Europe IBS AS or Dukascopy Japan KK.

No. TradingHost is not a bank, not a broker and not a registered investment firm. TradingHost is a cloud runtime that runs your strategy code. The bank relationship, the account, the leverage, the execution and the regulatory protections all live with the Dukascopy entity that holds your account.

No. Your JForex strategy or FIX client connects to Dukascopy and sends instructions according to your own logic. TradingHost provides the runtime where that code runs.

No. The JForex Java SDK is published by Dukascopy at its own Maven repository. Live trading also requires JForex API enablement on a live Dukascopy account.

Yes. TradingHost runs any language that can run inside a container, including Java. The JForex Java SDK ships as a Maven dependency; your container builds the JForex client (with your IStrategy implementation) and runs it as the container entrypoint.

For Dukascopy specifically, the canonical surface is the JForex Java SDK. Python and other languages can reach Dukascopy via FIX 4.4 (any FIX engine works) or via a Java sidecar that publishes JForex events to a Python process. The pure-Python path through JForex SDK is not supported by Dukascopy.

Yes. Dukascopy publishes a demo Java client and a historical-data Java client that can be used without a Dukascopy account, which is useful for development and tick-data backtests. Live trading requires opening a Dukascopy account.

Yes. Live FIX 4.4 on Dukascopy is a paid monthly subscription, separate from the JForex SDK which is included with the account. For most retail-leverage strategies the JForex SDK is the right path. FIX is for clients who specifically need it.

Open a Dukascopy Bank SA or Dukascopy Europe IBS account, enable JForex API in the user portal. Fork a TradingHost JForex SDK starter that pulls com.dukascopy.api, or connect your own GitHub Java strategy repo. Linking a GitHub repo and creating a strategy is free; runtime plans are listed on the pricing page.

Yes. Leverage is set by the Dukascopy entity. Dukascopy Europe IBS AS (Latvian FCMC, ESMA-aligned) applies 30:1 majors and the standard ESMA cascade. Dukascopy Japan KK (Japan FSA) caps leverage at 25:1. Dukascopy Bank SA (FINMA) applies FINMA rules. The API surface is the same across entities.

In your GitHub-controlled secrets workflow. TradingHost reads the Dukascopy username, password and account selector at runtime through GitHub repository secrets, environment secrets or your own approved secret-management process.

Yes. TradingHost supports MCP-based control for AI IDEs including Cursor, Claude Code, GitHub Copilot and CLI-based AI agents. Java strategies and JForex IStrategy classes are first-class citizens in TradingHost's MCP control surface.

No. Regulatory reporting is the broker's responsibility. Dukascopy Bank SA reports under FINMA rules. Dukascopy Europe IBS AS reports under Latvian FCMC, MiFID II and EMIR. Dukascopy Japan KK reports under Japan FSA rules. TradingHost runs your code; the Dukascopy entity handles regulatory reporting.

No. TradingHost is focused on production runtime and deployment. Dukascopy ships a Java historical-data client and tick-data feed that you can use for backtests in your own research stack, or in AlgoBuilder.