How to Run the WeCore Trading Engine on Your Own Cloud Server

Some traders prefer the system that executes their trades to run on a server they own, not only on shared infrastructure. WeCore lets you run the trading engine on a cloud server in your own account with a cloud provider. This guide explains, at a conceptual level, how it works, what you need to decide and how to keep an eye on it.

Screen names may change, so the steps refer to areas of the app.

Why your own server at all

Before the steps, it helps to understand the common reasons:

• Control and ownership - the server is in your account with the provider. You can see it, you pay for it, and you can stop or delete it.
• Location - you can choose a region close to the exchange, which shortens the time between a signal and an order.
• Separation - the engine that runs your account runs in a separate environment.

General background, including security and costs, is in the guide to running strategies on your own server.

Your own server is not a must for everyone. If you are just starting, you will probably want to get to know the system first through connecting TradingView alerts and simulation mode.

Step 1: Connect your cloud provider account

In the trading server area, choose a cloud provider. DigitalOcean and Linode are supported today. If you do not have an account with the provider yet, open one directly on the provider's site.

The connection itself is done by authorizing on the provider's site: you are sent to their site, sign in there and approve the access. You do not give WeCore a password or an API token. WeCore keeps an encrypted authorization that you can revoke at any time.

Disconnecting the provider revokes only WeCore's authorization. Your servers stay in your account exactly as they were.

Step 2: Choose region and size

Two main decisions:

Region. The closer the server is to the exchange, the less time passes between the signal and the order. The popular equity index futures trade on CME Group, so a US region, preferably close to Chicago, is a sensible choice. Distant regions add delay to every order. Background on how execution affects results is in the guide to slippage and execution costs.

Size. The default is the smallest server that runs the engine. A larger server lets you run more strategies and accounts. The app shows which options fit, and your choice is checked again at creation time.

Billing. The server is created in your account and you pay the provider directly, according to its price list. WeCore does not charge for the server itself and does not own it. Check current prices on the provider's site.

Step 3: Accept the Trading Server terms

Before the server is created you have to explicitly accept the Trading Server terms. In short, they cover a few topics:

• Permission for WeCore to install and remove the software on the server.
• Responsibility for the provider account and its billing is yours.
• Trading risk disclosures.

Read them carefully before accepting, as with any agreement.

Step 4: Server creation and installation

After you accept, the server is created in your account with the provider, and the software is installed on it automatically. On the trading server screen you can follow the installation stages until the server is marked as ready. "Ready" means the engine is up and has made contact, not just that the installation finished.

A few things good to know:

• The installation is verified before it runs, and the server is configured to block inbound connections.
• If the installation fails, you can run it again or delete the server and create a new one.
• Usually there is one active server per provider.

Step 5: Connect a broker account to the server

A broker account that runs on your server connects from the server only, not from the website at the same time. That is deliberate: the account is never logged in from two places at once.

How many accounts and strategies you can run on the server depends on your subscription. As with any account, it is best to start in simulation mode and save risk rules before switching to real trading. There is a separate guide on risk rules.

If you later want to move an account from the server back to the website, the server stops trading it and logs out of the broker, and only then does the account return and connect on the website.

Step 6: Ongoing monitoring

Your own server needs a little more attention:

• Check the server status on the trading server screen from time to time, and make sure it shows as connected.
• Set up notifications so you know if something changes.
• Keep an eye on the invoice from your cloud provider, since the billing is yours.
• Remember that pausing the server, deleting it or disconnecting the provider stops the engine on that server.
• If you trade a prop firm account, check its official help center for its policy on automated trading and remote servers.

Checklist

• I have an account with DigitalOcean or Linode.
• I connected it by authorizing on the provider's site, without sharing a password or token.
• I chose a region close to the exchange and a size that fits my needs.
• I read and accepted the Trading Server terms.
• The server shows as ready and connected.
• The account runs in simulation with saved risk rules.

Key takeaways

• The engine can run on a server in your own cloud account, and you pay the provider directly.
• The provider connection is done by authorizing on its site, with no passwords or tokens.
• A region close to the exchange shortens execution time.
• An account running on the server connects from there only.
• Start in simulation, and monitor both the server and the billing.

If you are considering this step, you can start with WeCore without a server, get to know the system in simulation mode, and only then move the engine to a server in your own account.