Python & FastAPI core
Asynchronous request handling, supervised background loops for recording, alerting and pulling, and a clean boundary between the interface and everything else.
Technology
A small stack, chosen on purpose
Every dependency is a thing that can break on a server you cannot reach at midnight. The platform runs on a short list of well-understood parts, packaged into one file that needs nothing installed around it.
- One binary, no runtime to install
- One database file, portable
- No framework churn in the console
one binary, three roles
$ UltimateCoreX.exe$ UltimateCoreX.exe --agent --hub https://hub --token ***$ UltimateCoreX.exe --workerThe stack
Six parts, and the job each one has
Embedded SQL storage
Accounts, snapshots, servers and settings in one file with write-ahead logging. All access sits behind a single module so the engine can change without touching the rest.
Generated MQL programs
Reader, sender and receiver programs are produced from hardened templates, so a fix reaches every account by regenerating instead of hand-editing twenty files.
Dependency-free console
The operator console is plain HTML, CSS and JavaScript. Nothing to build, nothing to upgrade, no framework release breaking your dashboard six months from now.
Single-file packaging
Hub and agent ship as the same executable — the mode is a command-line switch. Copy one file to a server and you are done.
Standard-library networking
Outbound calls use what the language already ships. Fewer moving parts, fewer supply-chain surprises, and nothing to reinstall when a server is rebuilt.
Platform architecture
Outbound-only by design, resilient by default
Nothing in the system requires an inbound port. Agents post outward, the hub pulls outward, and native calls are isolated so a hung terminal can never freeze your console.
Source
Terminal
MT4 or MT5, already running your strategy.
MQL4 · MQL5
Publisher
Generated reader writes state, reads control.
Outbound
Agent
One per VPS. Reads files, never terminals.
Yours
Core Hub
Validates, stores, analyzes, alerts.
Live
Console
Your browser, reading from the hub.
No inbound ports
Works behind NAT and restrictive firewalls without a single rule change.
Isolated native calls
Terminal access runs in a separate process with enforced timeouts.
Atomic control writes
A robot can never read a half-written freeze instruction.
Portable storage
One database file. Copy it, move it, back it up — it is yours.
At a glance
Technical facts
- Application corePython 3.11+ with FastAPI, served by Uvicorn
- StorageEmbedded SQL database, write-ahead logging, single portable file
- Trading integrationMetaTrader 5 programmatic access plus a generated file bridge for MetaTrader 4
- Generated programsMQL4 reader, MQL5 sender and receiver from hardened templates
- TransportHTTPS, outbound only; optional secure tunnel when no inbound port exists
- PackagingSingle-file Windows executable, ~38 MB, hub and agent in one binary
- Operating systemWindows 10, Windows 11, Windows Server 2012 R2 and newer
- Scale target50+ accounts per hub across many servers
Engineering principles
Four rules we hold ourselves to
01
One definition per number
A metric is implemented once and reused. When two code paths computed profit differently, that was treated as a defect and fixed — not documented as a quirk.
02
Nothing important fails quietly
A failed freeze, a rejected token, a dropped connection: each one surfaces loudly. Silent failure in trading software is worse than no software.
03
Never overwrite good data with empty data
Writers refuse to replace a populated record with a blank one, because a fast path should never destroy what a slow path just built.
04
Backwards compatibility is not optional
Older agents keep working against a newer hub and fall back automatically. You upgrade servers when you are ready, not when we ship.
Console responsiveness
50 accounts reporting · 24 hours
200ms150ms100ms50ms0
00:0006:0012:0018:0024:00
10s
Telemetry interval
Per account, continuously
50+
Accounts per hub
Across many servers
<100ms
Console refresh
In-place value updates
20k
Snapshots retained
Per account, then pruned
Performance
Fast on the hardware you already own
The console refreshes constantly but moves rarely. Values update in place, heavy analysis stays off the request path, and growth is bounded automatically.
- Interface updates values without rebuilding the layout — no flicker, no lost tab state
- Analysis runs in worker threads so one large account never stalls another page
- Bounded concurrency on native calls: a slow sync cannot consume every thread
- Write-ahead logging keeps five background writers from losing a single snapshot
Security
The safest credential is the one we never ask for
Most aggregation tools want your investor password or a server login. ULTIMATE CORE X is designed so that request never has to happen.
No broker passwords
There is no field for one anywhere in the product. Accounts connect through software you install.
Token-protected access
Anything reaching the hub from outside the machine must present a bearer token, compared in constant time.
Narrow control surface
Even with control enabled the platform can only freeze new entries. It cannot open, resize or move a position.
Your data, your file
One portable database on the machine you chose. Nothing is transmitted to us — there is no route for it.
- Broker credentialsNever requested or stored
- Remote accessOutbound connections only — no inbound port
- Control surfaceFreeze new entries only, never order entry
- Data locationA single portable file on your machine
- TransportHTTPS with bearer token for anything remote
- Output handlingEvery external value escaped before render
Ready to Take Your Tradingto the Next Level?
Join thousands of traders who trust ULTIMATE CORE X to power their trading success.
- 14-Day Free Trial
- No Credit Card Required
- Cancel Anytime