Dukascopy/JForex Data
Historical source data enters a controlled acquisition workflow.
TICKARKPRIVATE BETA ↗Technology
A deterministic path from source data to platform-ready history.
Tickark treats historical ticks as an engineering pipeline: acquire deliberately, verify visibly, repair where possible, normalize consistently and export only after the repository is understood.
↓
Tickark Acquisition Engine
Range-aware retrieval builds and updates the local repository.
Integrity Verification
Coverage, timestamps and tick records are checked for detectable quality issues.
Automated Repair / Retry
Recoverable gaps and failed acquisition periods are retried systematically.
Normalization
Source records are prepared as consistent data for downstream processing.
Platform Export
Verified repository data is transformed for supported output workflows.
MetaTrader 5
Current platform export target.
MetaTrader 4
Future target; not currently available.
Know what exists locally.
Coverage, package counts, gaps, empty periods, problems and current process status remain visible inside the repository view.
Find issues before testing.
Verification is designed to surface incomplete or inconsistent periods before data is relied on in a backtest.
Retry with context.
Acquisition and repair workflows operate against known date ranges and repository state, supporting targeted recovery instead of blind redownloads.
Verification in practice
A quality process you can see.
The current interface exposes progress and verification results directly, keeping the operational state of the repository understandable while long historical ranges are processed.
PRIVATE BETA
Start with data
you can defend.
Tell us about your workflow and get updates as Tickark moves toward wider availability.
Join the Private Beta ↗