Engineering Principles

Zero Telemetry

JYXOS products do not collect trading data, account credentials, position information, equity curves, broker names, or any sensitive data from the operator's machine. The software runs entirely locally.

The only outbound network traffic is license validation against the JYXOS Worker (a single HTTPS request containing the Machine ID, Order ID, and software version) and the notifications that the operator explicitly configures (Telegram bot messages and email alerts). Both are opt-in and operator-controlled.

There is no analytics SDK embedded in the binary. No usage tracking, no crash reporting phone-home, no feature flags fetched from a remote server. The operator can verify this by monitoring outbound traffic with any network inspector.

This is not a marketing claim. It is a verifiable architectural decision. The binary makes exactly one type of outbound request that the operator did not explicitly configure: license validation. Everything else stays on the machine.

Zero Downtime Architecture

The monitoring system is designed so that no single failure, and no combination of two simultaneous failures, can prevent recovery. Five independent layers ensure that the monitoring stack comes back online after any disruption, including terminal crashes, process hangs, system reboots, power failures, and VPS provider restarts.

The main engine detects crashes and restarts terminals. A redundant monitor inside the same process detects if the main loop hangs. An independent supervisor process detects if the entire engine goes down. Windows Task Scheduler relaunches everything after a reboot. Auto-logon configuration ensures the user session exists for the scheduler to fire.

The measured recovery time from a terminal crash to a fully operational terminal with all Expert Advisors running is consistently under 30 seconds. This includes failure detection, process restart, broker reconnection, and chart reinitialization.

Institutional-Grade Security

Every license key is signed with HMAC-SHA256. The signature covers the tier, machine constraints, expiry date, and product identifier. Modifying any field in the license file invalidates the signature and blocks activation immediately. There is no grace period for tampered keys.

Machine fingerprinting uses a composite hash derived from four hardware identifiers. Single-machine licenses are cryptographically bound to specific hardware. Multi-machine licenses enforce activation counts via server-side tracking in Cloudflare D1.

The JYXOS and Sentinel MT trademarks are registered with INPI Argentina under Classes 9 and 42. The source code is registered with the Direccion Nacional del Derecho de Autor (DNDA). The SHA-256 hash of every release binary is published and independently verifiable.

Every release undergoes a comprehensive audit before shipping. The audit covers code correctness, configuration validation, license enforcement, notification delivery, and recovery behavior under failure conditions.

Single-Binary Deployment

Every JYXOS product ships as a single standalone Windows executable. No runtime dependencies, no framework installations, no PATH configuration, no admin privileges for normal operation. Download, place in a folder, run.

First-time configuration is handled by a built-in wizard that guides the operator through terminal setup, notification credentials, and monitoring preferences. The wizard writes a single config.yaml file that the operator can inspect, back up, and edit manually at any time.

The target installation time is under ten minutes from download to a fully operational monitoring system with Telegram alerts configured. This includes downloading the binary, running the wizard, placing the Guardian Heartbeat EA on the terminal charts, and verifying that the first health check completes.

There is no installer, no Windows registry modification, no system service installation. Uninstalling is deleting the folder. This simplicity is a deliberate architectural constraint, not a shortcut.