Quick Start Overview
The fast version of the full setup in four phases. Read this first, then go through the full step-by-step section below in order.
Broker, VPS & MT5
After creating the member account, independently choose a compatible broker, create the MT5 account, prepare a Windows Server 2019+ VPS with at least 4 GB RAM and 2 vCPU, and connect MT5 to the exact broker account/server.
Complete Both Forms
The Setup Wizard matches your confirmed payment. Submit License Activation, then continue to the required secure Done For You form with the matching MT5/VPS details. Wait for server confirmation; one form alone is not the complete submission.
Manual License Review
kazpa manually reviews the submitted records and generates one VistaX license for one account. No fixed review time is promised. The active license and assigned file appear in the authenticated dashboard when issuance is complete.
Install & Verify
The kazpa team installs the compiled VistaX build in MT5. Open XAUUSD M5, confirm the current official setfile, license, product, account, connection, and logs together.
Full Step-by-Step Setup — In Exact Order
This is the current general setup sequence. The authenticated member record controls the exact product, account, license, and assigned-file facts.
What VistaX is
- An Expert Advisor (EA) — automated trading software that runs inside MetaTrader 5
- Licensed by kazpa — a software company, not a broker or fund manager
- Designed only for XAUUSD (Gold) on the M5 (5-minute) timeframe
- Session-based entries; an existing sequence may remain managed beyond the entry window until flat
- High risk — losses and substantial drawdown are possible
- MT5 and the Windows host must remain connected for the software to perform its programmed actions
What kazpa is NOT
- Not a broker, financial institution, or bank
- Not a fund manager — kazpa does not touch your money
- Not a financial advisor — nothing here is financial advice
- No profit, recovery, loss-limit, or suitability guarantee
- A software licensing company — that is the full scope
Facts to acknowledge before setup
- A setup mismatch can change or prevent software behavior
- Capital placed in a trading account can be lost entirely
- Configuration inputs can materially change exposure and automated actions
- The software does not remove market, broker, execution, or operational risk
- This guide does not assess whether trading or live automated execution is suitable for a member
VistaX purpose, limits, supported chart, and risk acknowledgement
Compatibility facts to verify
- The broker provides MetaTrader 5, not only MT4
- The intended account exposes XAUUSD with specifications compatible with the assigned VistaX package
- The account environment is clearly identified as demo or live
- The exact MT5 account number and server name are available in the broker record
- kazpa does not recommend a broker, account type, leverage level, deposit, or trading decision
If using TradeSmart
If independently selected, open the broker profile through the kazpa TradeSmart registration link so referral attribution is retained. Existing TradeSmart users should use their current profile rather than create a duplicate.
Record the exact platform identity
- Broker name and official account environment
- MT5 account number
- Broker server name, character for character
- Account currency and demo/live status
- MT5 credentials stored privately in a password manager
Independent broker review
- Review regulation, custody, fees, leverage terms, withdrawal rules, and complaint process from authoritative sources
- Broker account, funding, and personal-finance decisions are outside kazpa software support
Broker profile → MT5 account → exact account number and server recorded
Current documented baseline
- Windows Server 2019 or later
- At least 4 GB RAM
- At least 2 vCPU
- Capacity for one supported MT5 terminal and the assigned VistaX package
Operational checks
- Provider credentials and the exact host address are available
- Windows starts normally and receives current security updates
- Disk space, memory, CPU, and network status can be inspected
- The provider documents restart, recovery, and support procedures
No availability promise
A VPS can separate MT5 from a member's personal device, but it does not guarantee uptime, latency, broker connectivity, platform availability, execution, or any financial outcome.
Windows Server 2019+ → 4 GB RAM → 2 vCPU → credentials stored privately
Windows computer
- Open the built-in Remote Desktop Connection app (
mstsc) or Windows App - Enter the exact host address supplied by the VPS provider
- Use the provider-issued Windows username and password
- Verify that the Windows desktop shown belongs to the intended VPS
Mac, iPhone, iPad, or Android
- Install Windows App, the current Microsoft client formerly named Microsoft Remote Desktop
- Add the VPS as a PC using its exact host address and provider-issued credentials
- Use a desktop-sized session for initial setup; mobile is best limited to viewing operational state
Disconnect is not shutdown
- Closing or disconnecting the remote-view window normally leaves the VPS running
- Do not select Shut down or Stop unless the provider's documented procedure specifically requires it
- Verify MT5 and connection state after any VPS restart or provider interruption
- Never share the VPS password in a support ticket, public post, or shared message
Windows App or Remote Desktop Connection → intended VPS desktop visible
Install inside the VPS
- Open the broker's official website inside the VPS
- Download the broker-supported MetaTrader 5 installer
- Run the installer and open MT5 after installation
- Record the installed build and confirm MT5 starts without an unresolved error
Connect the intended account
- Use File → Login to Trading Account
- Enter the exact MT5 account number and broker server from Step 2
- Use the matching MT5 password stored privately
- Wait for MT5 to display the account and connection state
Verify before submitting kazpa forms
- Account number and server match the broker record exactly
- Account currency and demo/live environment are correct
- XAUUSD is available under the broker's symbol naming
- Experts and Journal show no unresolved login or connection error
MT5 installed in VPS → exact broker account and server connected
Use the official member flow
- Sign in with the member account tied to your confirmed payment and open the Setup Wizard
- If the paid purchase is missing, contact Support to match it; do not create another member account or pay again
- Enter VistaX, the exact MT5 account number, Live/Demo account type, and broker name
- Review and personally accept the current acknowledgment
- Do not enter a password or MT5 server in this first form; those belong only in the protected Done For You form
- Wait for the server-confirmed receipt, then continue into the secure setup form
Identity and credential boundaries
- Do not put VPS, broker, MT5, or license passwords in public posts, notices, or ordinary support messages
- Use only the fields in the official form for the exact information it requests
- If the form requests an unexpected secret or the account facts are wrong, stop the form and contact Support
Manual review remains required
- Submitting the form does not create or approve a license immediately
- No fixed review or issuance time is promised
- The authenticated dashboard is the source for current form and license status
Exact activation details → signed-in form submitted → server receipt
Submit objective setup facts
- Continue in the Setup Wizard after License Activation is confirmed
- Match the same broker, account number, software, and Live/Demo environment, then add the exact MT5 server and current trading password, not an investor/read-only password
- Enter the VPS address, Windows username, and current password only in the secure form, or use its verified unchanged-VPS option if offered for an additional license
- Review the setup authorization and wait for confirmation that both records were received
- The member acknowledgment and authorization must be completed by the member, not by staff on their behalf
Keep secrets private
- Never post credentials in the one-way Network, a public page, or a shared message
- Support can verify setup records and errors but cannot provide financial, timing, sizing, or active-position advice
- If two records disagree, do not submit guessed replacements; contact Support to correct the record
Done For You record matches activation facts → submitted once
What manual review establishes
- The submitted member, broker, MT5 account, server, product, and setup records reconcile
- The license is generated for one released engine on one account
- The assigned VistaX configuration is associated with that authenticated record
- Review does not assess suitability or promise performance
Dashboard proof required before installation
- Product is VistaX
- License status is active
- MT5 account mapping matches the intended account
- Both setup records are server-confirmed and the private access details are current
- Opening the optional scheduling link is not proof of a booked call or completed installation
If status is still pending or mismatched
- Do not use another member's key, copied package, old file, or internal validation file
- Do not infer approval from an email or notice alone
- Contact Support with the non-secret record details needed to identify the mismatch
- No fixed manual-review time is promised
Dashboard → active VistaX license → exact account mapping and assigned file
Before team installation
- Complete License Activation and the protected Done For You form
- Use the included call-scheduling option after submission if a call is needed; booking is not a setup-completion gate
- Confirm the VPS opens and the correct broker MT5 terminal is installed
- Enter two-factor codes only into the verified provider flow; never send passwords or codes in ordinary messages
What authorized staff install
- The approved compiled VistaX build
- Only the configuration linked to the authenticated setup record
- The license on the exact paid MT5 account and server
- No source code is distributed to a member or placed in a member download area
What you verify with the team
- VistaX appears in the intended MT5 terminal
- The chart, timeframe, account, server, license message, and connection match
- The Experts and Journal logs show no unresolved setup error
- Support is contacted for every reinstall or update; files are never copied between members
MT5 data folder → MQL5 → Experts → VistaX visible in Navigator
Compatibility check before attaching
- Open the XAUUSD chart in MT5 inside the VPS
- Set the timeframe to M5 — 5 minutes
- Confirm the intended demo or live account number and exact server
- Locate the AutoTrading control and understand that enabling it authorizes automated order actions
- Setup verification can be performed while automated execution remains disabled; the enablement decision is independent
Team verification — step by step
- Confirm VistaX is attached to the XAUUSD M5 chart in the intended terminal
- Confirm the team-applied configuration matches the authenticated setup record
- Confirm the exact license and MT5 account mapping
- Review the Experts and Journal messages with the installer
- Do not enable automated execution solely to make a status icon change
How to verify the installation state
- Confirm the VistaX name appears on the XAUUSD M5 chart
- Confirm the assigned file name and license message in the Experts tab
- Read the status icon together with the Experts and Journal logs; no icon proves safety or expected performance
- If the license, file, symbol, timeframe, or connection does not match, stop setup and contact support
- Do not enable automated execution solely to make a status icon change
XAUUSD M5 → assigned file loaded → license and logs verified
Operational checklist
- Confirm whether VistaX Conditions loaded and record its source timestamp
- Read scheduled-event labels as metadata, not predictions or action instructions
- Check authenticated dashboard notices and, when included, the one-way Network for maintenance, file-version, or service information
- Confirm the license, assigned file, terminal connection, symbol, and timeframe
- If information is missing, stale, or contradictory, record the mismatch and contact Support; the mismatch does not determine a trading action
Read the current color key
- Blue: no selected calendar rule or release is listed; not a safety or profit rating
- Amber: a listed release, relevant report, or descriptive unusual-gold-movement flag
- Red: a configured calendar rule, such as Friday, month/quarter boundaries, or the rate-decision period
- Gray: incomplete coverage or current inputs; known calendar rules can still remain visible
- FOMC minutes are a separate selected release, not the rate decision
- Today's movement checks do not predict future days. No color directs activation, a pause, or a position action
Operational fault indicators
- Scheduled maintenance or a software/version mismatch
- An expired, inactive, or unverified license
- Missing or stale event-source data
- A broker, terminal, symbol, or timeframe mismatch
- An authenticated service-availability notice
Event-source timestamp and operational notices verified
Objective monitoring facts
- VPS reachability and MT5 connection state
- Exact demo or live account number and server
- Loaded symbol, timeframe, assigned file, and license state
- Experts and Journal errors with their timestamps
- Official maintenance or software-version notices
What monitoring cannot answer
- Whether a market condition is favorable or safe
- Whether an active position should be held, closed, modified, or increased
- Whether a drawdown will reverse or become larger
- Whether a past or current result will continue
- What loss limit, lot size, or funding amount is appropriate for a member
Software-state verification
- Confirm the account environment shown in MT5
- Confirm XAUUSD M5 and the assigned configuration
- Confirm the license and source timestamps are current
- Record any error before changing software state
- Contact support for setup or license errors—not for trading direction
VPS terminal remains running → mobile view used for monitoring only
VistaX Settings Reference
A compatibility and status reference for the assigned software files. It does not recommend exposure, timing, funding, or a live trading action.
What the Configuration Can Change
VistaX can create substantial or total loss. This section explains configuration effects without supplying a balance, lot-size, drawdown, timing, or position-management recommendation.
Configuration mechanics
- Starting size changes the account impact of each price movement
- Averaging logic can add positions and increase combined exposure
- Greater combined exposure uses more margin and can deepen loss
- Drawdown inputs can change automated exit behavior and realised loss
- No configuration guarantees a limit on loss
Compatibility controls
- Verify the assigned file name, version, account mapping, symbol, and timeframe
- Internal validation files are not member files
- Manual edits to protected sizing or basket inputs are unsupported
- Supported simultaneous VistaX and VistaONE use requires separate active licenses, broker accounts, and MT5 terminals
- Contact support when the assignment shown in the dashboard does not match
No financial direction
- kazpa does not recommend a deposit, lot size, profile, leverage level, or drawdown limit
- No balance is a safe minimum
- Prior gains are not risk-free capital
- Demo or historical results do not establish future suitability
- Funding, withdrawal, and tax decisions are outside software support
No active-position direction
- kazpa support can explain license, file, connection, and log state
- Support cannot tell a member to hold, close, modify, or add to a position
- Chart patterns, indicators, news labels, and elapsed time are not action signals in this guide
- An operational error does not determine the correct financial response
- Independent licensed advice may be appropriate for personal trading or financial decisions
How VistaX Uses Time Parameters
This is the published v10 configuration reference, not an instruction to enable or disable execution. Your exact installed build and assigned file control; other account-reported versions must be verified with the team.
◴ Operational time verification
Timezone or daylight-saving mismatches can change how software interprets its configured parameters. Verifying the clock and file version is an operational check only; it does not establish a favorable condition or direct activation.
An existing sequence may continue being managed after the entry window until flat. “Window ended” does not mean the account is flat. GMT is fixed; its local-time equivalent can change with daylight saving. VistaX Conditions calendar dates use New York time.
Operational Verification Resources
These resources help verify files, licensing, platform state, and support history. They do not analyze market conditions or direct a trading action.
Member Dashboard
Verify the assigned product, license status, account mapping, and current software version from the signed-in member record.
Open dashboardSoftware & Resources
Open the official VistaX setfile library and product guides. Compiled software remains team-installed.
Open resourcesMT5 Experts & Journal
Record license, connection, attachment, and platform messages with their timestamps. Logs describe software state, not whether to trade.
kazpa Support
Use support for installation, license, file-version, dashboard, and connectivity issues. Support does not manage positions or provide trading advice.
Open supportCredential handling
- Never post MT5, VPS, broker, or license credentials in public posts, notices, or shared messages
- Use read-only credentials only where a verified service specifically requires them
- Confirm the destination before entering any credential
- Contact Support if a page or message asks for unexpected account access
Authenticated notices
- The dashboard is the source for member-specific product, license, account, and installation facts
- The Network is one-way and may show operational notices when access is included; it is not required for setup
- Notices are not market forecasts or trade signals
- Contact Support so authorized staff can perform any update
- Contact Support when a notice conflicts with dashboard state
Common Operational Mismatches
These are factual setup and verification failures that support can diagnose. None determines whether a member should start, stop, hold, close, or modify a position.
Wrong server selected in MT5
The account number is entered against a different broker server. Login can fail or display an unexpected environment. Compare the exact server string with the broker record.
Environment mismatch
MT5 is connected to demo when the member record references live, or vice versa. Record the account number, server, currency, and environment before troubleshooting.
Wrong chart or timeframe
VistaX is attached to a symbol other than XAUUSD or a timeframe other than M5. That is an unsupported software configuration.
Execution state misunderstood
The member assumes a loaded EA is placing orders without checking AutoTrading, the chart icon, Experts logs, and account environment together. No single indicator tells the whole state.
Remote Desktop input offset
A scaled or windowed remote session can offset clicks. Verify the pointer and display scaling before changing platform controls.
VPS or MT5 interruption
When MT5 is closed or disconnected, the EA cannot perform its programmed actions. The logs should record the interruption and reconnection state.
Unverified executable or setfile
Never accept a compiled kazpa executable from another person or a public host. Use setfiles only from the authenticated Resources page or the official VPS folder, and contact Support when the installed state is unclear.
Version mismatch
An older set file paired with a newer executable—or the reverse—can be unsupported. Compare both versions with the member record.
Calendar treated as a signal
Scheduled-event labels and quiet periods do not predict direction, certify safety, or direct activation.
Protected inputs changed
Manual changes to sizing, sequence, time, or drawdown inputs can materially alter exposure and automated actions. Such edits are outside supported setup.
What This Guide Can and Cannot Verify
The final checklist is limited to objective setup, identity, license, file, platform, and support facts. It intentionally contains no market, timing, sizing, or active-position instructions.
✓ Objective checks
- Account number, broker server, currency, and demo/live environment match the member record
- Chart is XAUUSD on M5
- Team-installed build and configuration match the authenticated setup record
- License belongs to the displayed account and reports a current status
- VPS, MT5 connection, Experts log, and Journal log are available
- VPS clock and timezone are correct
- Protected inputs have not been manually altered
- Credentials are stored privately and never posted to a public page, notice, or shared message
- Maintenance or version notices came from an authenticated kazpa surface
- Any setup mismatch is recorded before support is contacted
✕ Not provided by this guide
- No instruction to enable or disable automated execution
- No recommended broker, leverage, account type, or funding amount
- No balance-to-lot mapping or recommended risk profile
- No recommended drawdown or loss limit
- No interpretation of price action, indicators, trends, or chart levels
- No calendar-based start, stop, skip, or run direction
- No claim that a condition, profile, or configuration is safe
- No direction to hold, close, modify, or add to a position
- No promise of recovery, profitability, or loss containment
- No substitute for independent licensed financial or trading advice