Source data workflow

A controlled layer around Dukascopy / JForex historical tick data.

TickArk works with historical data available through the Dukascopy/JForex ecosystem, then adds local repository state, integrity verification, targeted recovery, normalization and platform export.

Independent product

TickArk is not an official Dukascopy or JForex product, partner or endorsed service. References on this page describe the historical data source and technical workflow only.

SOURCE CONTEXT

JForex exposes historical ticks over time ranges.

Dukascopy's JForex documentation describes access to historical ticks through its history interface, including synchronous and asynchronous retrieval by shift or time interval.

TickArk uses the supported source ecosystem as the acquisition side of a wider data-engineering process. The application compares source availability with local coverage and keeps acquisition, verification and recovery state visible per instrument.

That distinction matters: source access provides the history, while TickArk manages the local operational lifecycle around it.

Official JForex historical data overview ↗Official JForex history ticks documentation ↗

TICKARK WORKFLOW

What happens after a source range is identified.

01 / Discover

Read source availability

Instrument rows show the historical period currently reported as available through the configured JForex workflow.

02 / Acquire

Download a chosen range

Select an exact interval or a period preset and build or update the local UTC repository.

03 / Verify

Compare local state

Inspect local coverage, gap duration, detected problems, repository size and current verification status.

04 / Recover

Retry only what needs attention

Run a full check, retry unverified hours or repair selected problems instead of restarting every acquisition.

05 / Normalize

Prepare consistent history

Convert source records into TickArk's controlled internal representation for downstream workflows.

06 / Export

Map to a supported platform

Prepare verified data for MetaTrader 5 today, with MetaTrader 4 listed only as a future target.

SOURCE & LOCAL STATE

Keep availability and coverage in the same view.

The repository shows the source-reported period next to local coverage. This helps distinguish history that has not been downloaded from a local interval that needs verification or repair.

TickArk repository comparing Dukascopy availability, local coverage, gaps and status — **Source-to-repository visibility**TickArk v0.16.2

CLARITY

Source-data questions.

Is TickArk affiliated with Dukascopy or JForex?

No. TickArk is an independent product. The names are used to identify the source ecosystem and compatible technical workflow.

Does TickArk modify data on Dukascopy or JForex servers?

No. Repository acquisition, verification, repair and normalization concern the local TickArk data workflow.

Does TickArk promise that every source period is available?

No. Source availability can vary by instrument and period. TickArk displays the source-reported range and local state so the user can make a scoped decision.

Can this history be prepared for MetaTrader 5?

Yes. MetaTrader 5 is the currently supported platform export target, using synchronized profiles and explicit custom symbol mapping.

Repository guideHistorical tick data managementCoverage, checks and recovery ↗TechnologyComplete TickArk pipelineSource through export ↗Supported platformMetaTrader 5 exportProfiles, mapping and package ↗

PRIVATE BETA

Start with data
you can trust.

Join the private beta interest list. Share the instruments and workflow that matter to you, and we'll contact you when a suitable opportunity becomes available.

Join the Private Beta ↗