Updated October 6, 2026 · 15 min read

Cloudflare Workers vs VPS vs AWS for WebTrader Hosting (2026)

Cloudflare Workers vs a VPS vs AWS for hosting a broker’s MT5 web terminal on its own domain: setup, SSL, WebSockets, operations and a decision framework.

Key takeaways
  • All three options can serve a branded MT5 web terminal on your domain; the real difference is who patches, renews, monitors and scales what.
  • A VPS is one location your team owns end to end; AWS adds regions and managed services but also architecture work and cloud skills.
  • Cloudflare Workers run on Cloudflare’s network in 348 cities, with automatic certificates for custom domains and WebSocket support, and no servers to maintain.
  • None of the three replaces the MT5 trading server: trades are still executed on your MetaTrader 5 platform, so hosting choice does not change execution speed.
  • Choose with five questions: in-house operations capacity, client geography, launch deadline, existing cloud footprint and how much the terminal itself must change.
  • Whatever you pick, test WebSockets, login restrictions, certificates and legal links before you send the first client to the new address.

Cloudflare Workers vs a VPS vs AWS: the short answer

For most brokers, prop firms and introducing brokers, Cloudflare Workers are the simplest way to host a branded MT5 web terminal: there are no servers to patch, certificates are issued automatically for custom domains, WebSockets are supported and delivery runs on a global network. A VPS fits teams that already run their own Linux infrastructure around the clock, and AWS fits groups whose platform already lives there and who employ cloud engineers.

The rest of this guide explains what “WebTrader hosting” really involves, compares the three options on the criteria that matter for a trading terminal, and ends with a decision framework, a migration checklist and the common mistakes to avoid.

What does WebTrader hosting actually need to do?

Before comparing platforms it helps to be precise about the job. When a client opens trade.yourbrand.com, whatever sits behind that address has to do five things well:

  1. Answer on your domain with valid SSL. Browsers warn loudly about missing or expired certificates, and a warning on a login page is the fastest way to lose a new client’s trust.
  2. Serve the terminal with your brand. Company name, contact details, licence and privacy links, and the trading server name clients should see.
  3. Pass live traffic. Prices, charts and orders flow over WebSocket connections, so the layer in front of the terminal must keep long-lived connections open rather than treating every request as a short page load.
  4. Control who can log in. Many brokers want only certain account ranges to use a given branded address, for example one range per brand or per partner.
  5. Stay available when it matters. Traffic rises around news releases and market opens, which is exactly when clients notice slowness or errors.

What the hosting layer does not do is execute trades. Since MetaQuotes introduced the new WebTerminal in October 2022, the terminal works with a specific broker’s platform and runs on the broker’s access server, so orders still go to your MT5 platform. The hosting choice decides how the terminal is delivered and branded, not how fast the trading server fills orders. For the bigger picture of where the terminal fits, see our forex broker technology stack guide.

A few terms used throughout this comparison:

  • Upstream: the address of the actual MT5 web terminal that the hosting layer forwards traffic to. It stays the same whichever option you choose.
  • Reverse proxy: software such as Nginx on a server that receives requests on your domain and forwards them to the upstream, optionally rewriting content.
  • Edge: computing that runs in many locations close to users rather than in one central data centre.
  • Custom domain: your own hostname, such as trade.yourbrand.com, attached to a service so clients never see the provider’s address.
  • Environment variables: named settings stored outside the code, so values like a phone number change without touching the program itself.

Cloudflare Workers vs AWS vs VPS: side-by-side comparison

The table compares a typical setup for each option: a single VPS with a reverse proxy such as Nginx, an AWS design built from a load balancer, instances or containers and a content delivery network, and a Cloudflare Worker attached to a custom domain.

CriterionVPS + reverse proxyAWS (load balancer, compute, CDN)Cloudflare Workers
Initial setupProvision server, install proxy, configure certificatesSeveral services to design and connectDeploy a Worker, attach the custom domain
SSL certificatesYou install and renewManaged certificates availableIssued and renewed automatically for custom domains
WebSocketsProxy configuration needed (upgrade headers, timeouts)Supported with the right services and settingsSupported natively
LocationsOne per serverRegions you choose and runCloudflare’s network in 348 cities, 100+ countries
Operating system patchingYour teamYour team for instancesNone
Traffic spikesSize the server in advanceAuto-scaling if configuredElastic by design
DDoS protectionSeparate service neededExtra services availableBuilt into the network
Changing branding or rulesEdit files, reload the proxyRedeploy or reconfigureChange environment variables
Skills neededLinux, networking, monitoringCloud architecture and securityBasic DNS and Cloudflare dashboard
Typical time to first clientDays, depending on teamDays to weeks, depending on designTypically the same day

The pattern is consistent: the further right you go, the less infrastructure your team owns. That is not automatically better, because ownership also means control, but for a web terminal the control you gain from running servers rarely changes what the client sees. For a broader comparison including hosted vendor options, see our WebTrader hosting comparison.

How each option sits between the client and the MT5 server

It is easier to judge the options once you picture the request path. In every case the client’s browser connects to your branded address, something in the middle handles that connection, and the terminal talks to your MT5 platform.

  • VPS: browser → your server in one data centre → upstream terminal. Every client, wherever they are, travels to that one location first. If the server is down, the address is down.
  • AWS: browser → content delivery edge → load balancer in your chosen region → instances or containers → upstream terminal. You can add regions, but each one is another stack to run, secure and keep in sync.
  • Cloudflare Workers: browser → nearest Cloudflare location → Worker code → upstream terminal. Cloudflare says 95% of internet users are within 50 ms of its network, so the first hop is short for clients in most regions.

Two points are worth stressing. First, a closer first hop improves how quickly the page and its connections are established; it does not make the trading server execute faster, and nobody should promise that. Second, WebSockets matter more than raw page speed for a trading terminal. Cloudflare’s documentation describes WebSocket support in Workers, including proxying connections and a 32 MiB message limit, which is far above what normal price and order messages need. On a VPS the equivalent is correct proxy configuration: upgrade headers, sensible read timeouts and enough connection capacity for peak sessions. Our guide to WebTrader latency and uptime goes deeper on what clients actually feel.

When is a VPS the right choice for a web terminal?

A VPS with a reverse proxy is the most familiar option, and it is a sensible one if your team already runs servers next to your MT5 infrastructure and has round-the-clock operations. You get full control over the proxy, logs and network rules, and nothing about the setup is exotic.

The cost that is easy to underestimate is not the server, it is the work around it. Before choosing a VPS, make sure someone owns each of these tasks:

  • Operating system and proxy patching, including security updates that cannot wait for a quiet week.
  • Certificate renewal and monitoring that alerts you before, not after, a certificate expires.
  • Resilience: a second server, health checks and a failover plan, because a single VPS is a single point of failure.
  • DDoS and abuse protection, usually from a separate provider placed in front of the server.
  • Capacity planning for news spikes, since a VPS only has the resources you sized in advance.
  • Change control for branding and login rules, so edits to proxy files are reviewed and reversible.

If those tasks already exist in your operations runbook, a VPS adds little extra load. If they would be new, the VPS is cheap to rent and expensive to run.

When does AWS make sense for WebTrader hosting?

AWS suits groups that already run their CRM, client portal or back office there and want every public endpoint in one cloud account, under one set of security policies and one bill. It offers managed certificates, load balancing, auto-scaling and content delivery, so in principle it can do everything a web terminal needs.

The trade-off is architecture. A resilient, multi-region setup involves several services, network and security rules between them, logging, alarms and infrastructure-as-code to keep it reproducible. That is routine work for a cloud engineering team and a large project for a small broker. AWS is a reasonable answer when:

  • you already have engineers who design and run AWS workloads;
  • compliance or group policy requires all client-facing systems in one provider;
  • the terminal needs custom logic tied to other services in the same account.

If none of those apply, AWS is often more platform than the job needs. Note too that the options are not mutually exclusive: a broker can keep its back office on AWS and deliver the terminal through Cloudflare, since the Worker only needs to reach the upstream terminal address.

How do Cloudflare Workers serve an MT5 web terminal?

A Cloudflare Worker is a small piece of code that runs on Cloudflare’s network instead of on a server you manage. Attached to a custom domain such as trade.yourbrand.com, it receives the client’s request, applies your branding and rules, and passes traffic to the upstream terminal. Cloudflare’s documentation notes that Custom Domains create the DNS record and the certificate automatically; wildcard hostnames are not supported, so each address is added explicitly.

FXPTrader uses exactly this model. The Worker is deployed in the broker’s own Cloudflare account, and all settings are Cloudflare environment variables:

  • company name, address, email, telephone and website;
  • trading server name and upstream address;
  • licence URL, privacy URL and end-user text;
  • allowed login ranges, so only the account ranges you choose can sign in on that address.

Changing a phone number, a legal link or a login range is an edit to a variable rather than a redeploy or a server change. Running several brands means one Worker and one configuration per brand, each on its own domain; see multi-brand WebTrader. Login control is explained in login access control.

Context matters here too: MetaQuotes itself partnered with Cloudflare in 2020 to protect MT5 endpoints against DDoS attacks, so placing the terminal’s front door on Cloudflare follows a path the platform vendor has already taken. And to be clear about scope, FXPTrader is not an MT5 licence or a white label. You need your own MT5 access; the Worker delivers and brands the terminal on your domain. Our Cloudflare Workers for brokers guide covers the platform in more detail.

Who maintains what? Day-two operations compared

Launch day is a small part of the total effort. The table below shows who carries each recurring task once clients are using the terminal.

Recurring taskVPSAWSCloudflare Workers
Security patches for the OS and proxyYour teamYour team (instances) or provider (managed services)Not applicable
Certificate renewalYour team or an automated client you maintainManaged if configuredAutomatic
Capacity for traffic spikesResize in advanceScaling policies you tuneHandled by the network
Failover between locationsSecond server and health checksMulti-region designBuilt into the network
Updating contact details or legal linksEdit config, reloadRedeploy or update configurationEdit environment variable
Adding a new brandNew virtual host and certificateNew listener, rules, certificateNew Worker and custom domain
Monitoring and alertingYour toolingCloud monitoring you configureCloudflare dashboard plus your checks

Even with Workers you still own some things: the upstream terminal, your MT5 platform, DNS for your zone and the accuracy of your legal content. Our WebTrader operations and support guide lists the checks worth running every week.

A decision framework for choosing WebTrader hosting

Work through these five questions in order. The first “yes” that applies usually settles the choice.

  1. Do you lack an in-house team that runs servers around the clock? Avoid self-managed servers. Choose Cloudflare Workers.
  2. Are your clients spread across several regions? Prefer edge delivery so the first connection is short for everyone, not only clients near one data centre.
  3. Do you need to launch this week? A Worker on a custom domain is typically live the same day once your MT5 access and upstream are in place.
  4. Does group policy require everything in your existing AWS account, and do you have cloud engineers? AWS is a reasonable choice; budget engineering time for a resilient design.
  5. Do you already run servers next to MT5 with mature operations? A VPS proxy is acceptable, provided you add redundancy and DDoS protection.

Two edge cases sit outside the framework. If you need a completely different trading interface, that is a custom front end built on a separate API, a development project rather than a hosting decision. And if you do not yet have MT5 access, solve that first; read white label vs grey label vs own MT5 licence.

A quick scoring sheet helps when stakeholders disagree. Rate each option from one to three on operations effort, time to launch, global reach, control and fit with existing systems, weighting the criteria by what your business actually prioritises. Most small and mid-sized brokers find operations effort and time to launch outweigh control.

Different business models tend to land in different places. A prop firm launching evaluation accounts usually values speed and per-brand login rules, see WebTrader for prop firms. An introducing broker wants its own address without running any infrastructure. A larger multi-entity broker may keep AWS for internal systems while delivering each entity’s terminal at the edge.

Common mistakes when hosting a broker web terminal

  • Testing only page load, not trading. A terminal can load perfectly while WebSockets fail behind a misconfigured proxy. Always log in and place a demo order through the new address.
  • Forgetting login restrictions. Without account-range rules, any client of the trading server may be able to sign in on a partner’s branded address. See how to restrict MT5 WebTrader login ranges.
  • Leaving legal links empty. Licence, privacy and risk text should be visible from the terminal, not only on the main website.
  • Using the wrong DNS record. A stale record pointing at an old server can keep some clients on the previous setup for longer than expected.
  • Relying on one VPS. A single server is a single point of failure; plan for the day it reboots during a market open.
  • Promising faster execution. Moving the front door to the edge does not change how the MT5 server processes orders. Market it as reliability and convenience, not speed of fills.
  • Expecting expert advisors in the browser. Broker sources note that neither MT4 nor MT5 web terminals run expert advisors or custom indicators, whatever hosting you choose.

How to move from a VPS proxy to Cloudflare Workers

Brokers already running a terminal behind a VPS can switch without changing the address clients use. A typical sequence:

  1. Inventory the current setup. Note the upstream terminal address, trading server name, any login rules in the proxy and the legal links shown today.
  2. Make sure the zone is on Cloudflare. Your domain’s DNS must be managed in your Cloudflare account; see WebTrader subdomain DNS setup.
  3. Deploy the Worker on a test hostname, for example trade-test.yourbrand.com, and set the environment variables.
  4. Test end to end: certificate, branding, login with an allowed and a blocked account, live prices, a demo order, and mobile browsers.
  5. Move the production hostname to the Worker as a custom domain during a quiet period, removing the old DNS record that pointed at the VPS.
  6. Keep the VPS available briefly as a fallback, then decommission it and its certificates once traffic is confirmed on the new path.

For a launch from scratch rather than a migration, follow our branded WebTrader launch checklist.

Sources

Frequently asked questions

Is Cloudflare Workers better than a VPS for a web terminal?

For most brokers, yes. Workers remove server maintenance, issue certificates automatically for custom domains, support WebSockets and run on a global network. A VPS still makes sense if you already operate servers next to your MT5 infrastructure with round-the-clock operations.

Can a Cloudflare Worker host my MT5 trading server?

No. The Worker delivers and brands the web terminal on your domain and passes traffic to the upstream terminal. Trades are executed on your MT5 platform, which you run or access through your own MT5 arrangement.

Will Cloudflare make trade execution faster?

No, and you should not claim it does. Edge delivery shortens the first connection between the client and the network, which helps the terminal load and connect smoothly. Order execution happens on the MT5 server and is unaffected by where the terminal is delivered from.

Do WebSockets work through Cloudflare Workers?

Yes. Cloudflare documents WebSocket support in Workers, including proxying connections to an upstream, with a 32 MiB message limit. That comfortably covers the price and order messages a trading terminal uses.

Does Cloudflare protect against DDoS attacks?

DDoS protection is built into Cloudflare’s network. MetaQuotes also partnered with Cloudflare in 2020 to protect MT5 endpoints, so the approach is familiar in the MetaTrader ecosystem.

Is AWS overkill for a web terminal?

Often, unless your platform already runs on AWS and you have engineers who design and operate cloud workloads. A resilient multi-region setup involves several services and ongoing tuning, which is a lot of work for a single branded address.

How long does it take to go live on each option?

With Workers, a branded terminal is typically live the same day once MT5 access and the upstream are ready. A VPS usually takes days, depending on the team, and an AWS design can take days to weeks. Testing time is similar for all three.

Can I run several brands on one setup?

Yes. With FXPTrader each brand gets its own Worker and configuration on its own domain, with its own company details, legal links and login ranges. On a VPS or AWS the equivalent is a separate virtual host or listener and certificate per brand.

Do I need a wildcard certificate for multiple subdomains?

Not with Workers Custom Domains, which do not support wildcards anyway. Each hostname is added explicitly and receives its own certificate automatically, which also keeps each brand’s address clearly defined.

Does FXPTrader include an MT5 licence or white label?

No. FXPTrader delivers the MT5 web terminal on your domain through a Worker in your own Cloudflare account. You need your own MT5 access, whether through your own licence or another arrangement.

Can I keep my back office on AWS and use Cloudflare for the terminal?

Yes. The options are not exclusive. The Worker only needs to reach the upstream terminal address, so your CRM, client portal and other systems can stay wherever they run today.

Why does my web terminal say it is not supported by this MetaTrader 5 server?

Since the 2022 change, each broker’s web terminal works with that broker’s own platform. Forum reports of this message usually mean the terminal being used is not the one enabled for that server, so the broker needs its own web terminal set up through its MT5 arrangement.

See your brand on a live WebTrader

Send us your company name and domain. We will set up a personalised demo so you can see exactly how your terminal will look.