PETE Trade Gateway · How it works

The Telegram message is only the front door.

PETE is customer-directed trade execution and trade-management software for MT4. You decide the trade. PETE validates the instruction, connects it to your own MT4 terminal, routes it through your own broker account and reports the trade lifecycle back to you through Telegram.

Founding Beta · £9.99/month Back to Trade Gateway

PETE in 60 seconds

One customer instruction. A controlled execution chain underneath.

PETE Hosted Core

Windows Gateway

MT4

Your broker

Your broker account remains yours. PETE does not hold your trading funds or operate a pooled trading account. It is the engineered infrastructure between your instruction and your broker.

What happens after you press Send

Eight stages between your instruction and the full trade lifecycle.

You choose the trade

Send PETE a supported trade instruction through Telegram. You define the direction, entry, stop, targets and risk within the supported command format.

PETE validates it

PETE checks that the instruction makes structural sense before it can progress. Invalid trade geometry is rejected rather than silently reinterpreted.

Your setup is checked

PETE associates the instruction with the customer, subscription and paired installation while the local Gateway and MT4 route remain part of the execution chain.

PETE builds the basket

PETE applies the supplied risk and prepares the execution basket. Multi-target instructions can be represented as multiple broker orders linked to one PETE basket.

Gateway sends it to MT4

The PETE Windows Gateway Agent bridges the hosted service to the PETE client running inside your own MT4 terminal on a Windows PC or VPS.

Your broker executes

Orders pass through your own MT4 terminal to your own broker account. Broker fills, symbol rules, lot limits, margin and normal execution conditions still apply.

PETE tracks the basket

PETE tracks the execution state and basket lifecycle rather than simply sending an instruction and forgetting about it.

You get feedback

Telegram becomes the control and feedback surface, showing whether an instruction was accepted, executed, rejected or closed.

Why the Windows Gateway matters

A real bridge into your MT4 environment.

PETE deliberately uses a local Windows or VPS Gateway rather than pretending every MT4 broker account is a direct cloud API. The paired installation, broker binding and MT4 heartbeat form the local execution route between PETE's hosted control layer and your own terminal.

That architecture is part of what makes PETE more than a Telegram message copier.

Validation philosophy

Fail closed. Don't guess.

Invalid trade geometry is rejected rather than silently changed.
Expired-but-valid Agent sessions use the supported session-recovery path.
Each extracted customer package uses its own local state folder to avoid installation collisions.
Expired pairing credentials must be replaced rather than bypassed.
Broker writes should not be enabled until the preflight route is healthy.

Preflight

Prove the route before trading.

Founding Beta setup includes a preflight stage before the customer progresses to live broker writes. It checks the local route including MT4 heartbeat, broker/account binding, connectivity, trade permission and online authorization requirements.

Do not continue until

PRE-FLIGHT PASSED

Beta onboarding deliberately starts with a demo broker account so the complete route can be proven before live use.

What you control

The trading decision stays with you.

You decide the trade and market direction.
You choose the broker and MT4 account.
You supply the supported trade instruction and requested risk.
You control whether PETE is armed for broker writes.
Your broker account and trading funds remain with your broker.

Public Gateway V1 does not choose a market direction on the customer's behalf. PETE's role is the execution infrastructure around the instruction.

What needs to be running

PETE is infrastructure, so the route needs to be online.

A supported Windows PC or suitable VPS.

MT4 open and logged into the intended broker account.

The PETE MT4 client installed on one chart.

The PETE Gateway Agent running.

The required WebRequest permission enabled in MT4.

A healthy paired installation and valid subscription.

A VPS is optional, but useful if you want the Gateway and MT4 available without leaving a home PC running continuously.

PETE is

Customer-directed execution software.
An MT4 execution bridge.
A validation and authorization layer.
A risk-aware basket execution system.
A trade lifecycle and feedback system.
Software operating through your own broker account.

PETE is not

A signals subscription.
Investment advice.
A managed account.
A profit guarantee.
A pooled trading account.
An autonomous public strategy in Gateway V1.

Broker and symbol realities

Your broker still behaves like your broker.

PETE works through the customer's broker, so broker-specific rules still exist. Symbol names, contract sizes, lot steps, minimum lots, trading permissions, margin requirements and execution conditions can vary. That is one reason the Founding Beta is deliberately being tested across different brokers, PCs and VPS environments.

Founding Beta

Understand it before you use it.

The Founding Beta is deliberately small, initially targeting around 5–10 MT4 traders so each onboarding can be observed properly across different brokers, Windows environments and VPS setups.

£9.99 / month

The Founding Beta price is intended to remain locked while the subscription remains continuously active.

View Founding Beta

Important information

PETE Trade Gateway is execution and trade-management software for customer-directed instructions. It does not provide investment advice, trading signals or guaranteed outcomes. Trading leveraged products can result in losses. Customers remain responsible for their trading decisions, broker account and instructions submitted to PETE.