TITANS OPS

TITANS LIVE OPERATIONS

Admin Control Plane · Approval, Deployment, Runtime Monitoring

Admin API authentication is required for client and deployment actions.

Force-Close Controls

Send controlled close instructions through the TITANS backend. No MT5 process kill path is used here.

Admin user + reason are required for audit logging.

Receiver VM ID

Total Registered

0

Trusted Live

0

Pending

0

Trusted PnL

$0

Only VERIFIED + LIVE SYNC broker telemetry is shown for Equity/PnL. Session-not-ready MT5 payloads are flagged as waiting and do not overwrite trusted broker metrics.

#	Name	Phone	Shantahl	MT5 Login	Broker Server	Equity	PnL	Broker Live	Main EA	Proof	Sync	Expires In	Status	Deployment	Trade Control	Action

Deployment Queue

Client	Request Time	Deployment State	VM ID	Node

Execution Node Power Control

Weekday provider schedule runs on Asia/Manila time. Weekend auto-start stays locked unless an explicit Hetzner-side override start is requested from this control plane.

Shutdown remains safety-gated. No blind hard power-off path is used here.

Operator reason

Time	Event	Source	Result	Reason	Failure

Infrastructure Monitoring

Client	VM ID	Node	Deploy State	Runtime State	Updated	Action

Force-Close Operations

Recent controlled close requests, receiver progress, and final outcomes.

Request	Scope	Target	Options	State	Result	Updated

Sender Credentials Panel

Store sender MT5 credentials securely, keep the UI masked, and show clearly when the sender deployment target is not fully configured.

Waiting for sender credential status...

Clear stored MT5 login Clear stored MT5 password Clear stored investor password

Autonomous EA Package (Sender VM)

Use the direct sender .ex5 workflow for one-file sender replacement. The legacy package path remains available below for the older .ex5 + .bin sender bundle.

Direct Sender EA Deployment

Upload one compiled .ex5, deploy it to sender staging, then activate it on the sender VM profile that already owns the XAUUSD M5 chart.

Stable target file: Autonomous_Main.ex5 on sender VM 150

Selected .ex5

No file selected.

Status: idle

Uploaded sender .ex5 files

Activation uses the existing portable MT5 launcher and saved TITANS profile. This avoids leaving duplicate sender EA instances behind.

Time	Event	Status	Operator	Message

Legacy Sender Package Workflow

Use this only if you still need the older .ex5 + .bin sender package path.

Choose both files at once (.ex5 + .bin)

You can use the single picker above, or the separate pickers below.

If your browser file dialog hides .bin, switch filter to All files (*.*).

Receiver EA Upload & Clone Panel

Upload the compiled receiver package, optionally include the telemetry reporter, then deploy to all receiver VMs or only a selected subset.

Deployment is only marked successful after per-VM verification.

Uploaded receiver packages

Waiting for receiver package status...

VM	Client	Status	Version	Updated	Failure

Sender Live View Data Panel

Mirror the practical sender dashboard data without pretending real-time when the heartbeat is stale or missing.

Waiting for sender live data...

Field	Value	Field	Value

Receiver Fleet Status Panel

See receiver VM availability, latest deployed version, heartbeat freshness, and which machines need retry or manual intervention.

Waiting for fleet telemetry...

VM	Client	Runtime	Latest Status	Version	Last Heartbeat	Failures	Last Update

Deployment History / Audit Panel

Operator-triggered credential changes, sender deployments, receiver rollouts, retries, and other audited control-plane actions.

Time	Event	Actor	Target	Result	Failure

Errors / Alerts / Action Required Panel

Critical truth over false green lights. If telemetry is stale, credentials are incomplete, or a deployment only partially succeeded, it is surfaced here.