If you want to route TradingView alerts into a MetaTrader 5 terminal, you can run an open-source connector that you deploy and maintain yourself, or you can pay a company to run the whole arrangement for you. Both are legitimate. The difference is not quality or price. It is who can see the code, who can change it, and who owns the updates, the hosting and the 3 a.m. incident.
This article sets out what each model actually gives you and what it asks of you, then gives you two question lists: one to put to any open-source project, one to put to any managed provider, including PineConnector. Where PineConnector's public documentation does not answer a question, the article says so rather than guessing.
What "open source" means, and what it does not
The Open Source Initiative is blunt about it: "Open source doesn't just mean access to the source code."[1] A project qualifies only if its licence meets a set of criteria, including that "the program must include source code, and must allow distribution in source code as well as compiled form" and that "the license must allow modifications and derived works".[1] In practice that gives you three real advantages over any closed product:
- You can read what the connector does. How it parses an alert, how it decides which account to trade, whether it checks the broker's response, where it writes your credentials. None of that is a promise; it is text you can inspect.
- You can change it. A broker with an unusual symbol suffix, a custom order type, an extra safety check before every order: you can add them, or pay someone to.
- Nobody can take it away. If the maintainer loses interest or the company behind it closes, you still have the code and the licence to keep using it.
What open source does not mean is "someone else runs it". A licence grants rights to the code. It says nothing about hosting, monitoring or support. Those are yours unless you buy them separately.
What you take on when you self-host an open-source connector
The connector is one piece. The rest of the system has to exist and stay up, and it is all yours to operate.
An always-on MetaTrader 5 terminal. MetaQuotes lists the ways an Expert Advisor stops running, and the first two are simply "turn off the trading platform" and "close the chart the Expert Advisor is running on".[2] Whatever receives your alerts must hand them to a terminal that is open, logged in and awake. That means a Windows machine or server that you keep running.
The webhook contract. TradingView will cancel a request "if a remote server takes longer than three seconds to process a request", warns that "webhooks may occasionally fail to reach the specified URL", and tells you not to "include sensitive information such as login credentials or passwords in the webhook body".[3] If your receiver returns a server error, TradingView resends: "the notification will be sent again after 5 seconds", and "the maximum number of webhook sends for one trigger can be 4".[4] Whether a resent alert becomes a second order depends on how the connector handles repeats. That consequence is our engineering inference, not something TradingView states, and it is the first thing to read for in the code.
The host itself. If the terminal lives on a Windows VPS, Windows will patch itself. Microsoft's own guidance notes that "automatic restarts after an update occur outside of the active hours" and that "devices that don't have locally signed-in users, or active RDP sessions, are restarted".[5] A headless trading server is exactly that kind of device. You configure active hours, you make the terminal relaunch, you notice when it did not.
Dependencies and platform changes. Language runtimes, libraries, the MetaTrader build, TradingView's alert format. Each can change. In a healthy project the maintainers ship a fix and you apply it. In a stale project, you are the maintainer.
Incident response. When an alert arrives and nothing happens, the person who reads the logs, restarts the process and decides whether to resend is you. There is no support desk to open a ticket with, unless the project offers paid support.
None of this is a criticism. For a trader who wants to understand and control every link in the chain, it is the point.
What you get, and give up, with a managed service
A managed service moves the hosting and operating jobs onto the vendor. With PineConnector Edge, the company's managed MT5 hosting, PineConnector runs the MetaTrader 5 terminal on its own infrastructure and describes the arrangement as "managed infrastructure, not managed execution".[6] You still bring the broker account, the strategy and every trading decision. Credentials "are encrypted in transit and at rest, and your instance is isolated to you rather than shared with other traders".[6]
What you give up is transparency and control at the connector level, and it is worth being specific about the current limits rather than waving at them:
- You cannot inspect the code. PineConnector's connector is proprietary. You are trusting documented behaviour and support answers, not source.
- The vendor sets the roadmap. PineConnector's Edge Guide states that the service "is currently in Early Access", that "EA settings currently use a fixed default configuration and cannot be edited", and that "trading account data, including account balance, and the Experts and Journal logs are not yet available on the Edge page".[7] Customising those settings is described as planned, not available.
- Only the vendor's component runs. "Edge does not support custom or other third-party EAs."[7] Edge is MetaTrader 5 only, hosted in New York today with London described as coming soon for the Plus and Pro plans.[6]
What you get in exchange is that the terminal, its operating system and its restarts stop being your problem, and there is one support desk for the whole path from webhook to terminal. The portal gives you "controls for manually restarting or terminating your Edge MT5 instance",[7] which is the extent of the operational control the guide documents today.
Side by side
| Question | Open-source, self-hosted | Managed (PineConnector Edge as the example) |
|---|---|---|
| Can I read the connector code? | Yes, by definition[1] | No |
| Can I change how it behaves? | Yes, licence permitting[1] | No; EA settings fixed in early access[7] |
| Who keeps the MT5 terminal running? | You[2] | PineConnector[6] |
| Who handles OS patches and restarts? | You[5] | PineConnector |
| Who adapts to TradingView or MT5 changes? | The project, or you if it is stale | PineConnector |
| Can I see terminal logs? | Yes, on your machine | Not yet available on Edge[7] |
| Can I run other EAs alongside? | Yes | No[7] |
| What happens if the vendor or project disappears? | You keep the code | You keep your broker account and strategy; you need a new connector |
| Cost shape | Your time, plus hosting | Core $59, Plus $129, Pro $199 per month, hosting included[6] |
Questions to ask any open-source connector
- Which licence, exactly? Read it. Some "source-available" projects publish code but forbid modification or commercial use, which fails the Open Source Definition.[1]
- When was the last meaningful commit, and who made it? A project that has not changed since the last TradingView or MetaTrader update may already be broken.
- How do I report a bug, and does anyone answer? Look at open issues and how long they stay open.
- What does it do when TradingView resends the same alert?[4] Search the code for how it identifies a repeat. If you cannot find it, assume it does not.
- Where do broker credentials live? Config file, environment variable, database, or inside the MT5 terminal only? Are they ever written to a log?
- Does it check the broker's response, or does it treat "sent" as "filled"?
- What happens on restart? Is there any persistence of in-flight instructions, or are they dropped?
- What do I need to host it, and how do I keep the terminal alive through a Windows restart?[5]
The same questions for a managed provider, including PineConnector
Being paid does not exempt a vendor from the list. Here is how PineConnector's public documentation answers each item, checked on 10 September 2026.
| Question | What PineConnector documents |
|---|---|
| What am I allowed to change? | Early access EA settings are fixed; customisation planned.[7] |
| What is the current scope? | Early Access; MT5 only; no third-party EAs; New York now, London coming soon for Plus and Pro.[6][7] |
| How do I report a problem? | Through PineConnector support. Ask what response times apply; none are published on the pages cited here. |
| What happens when TradingView resends an alert? | Not documented. Ask support before relying on it, exactly as you would with an open-source project. |
| Where do my broker credentials live? | Encrypted in transit and at rest; instance isolated to you.[6] Who inside the company can access them, and how they are removed when you leave, is not stated on these pages: ask. |
| Does it check the broker's response? | Not described in the Edge Guide. Ask, and test on a demo account, which the guide itself recommends for a first setup.[7] |
| What happens on restart? | The portal offers manual restart and terminate controls.[7] Handling of in-flight instructions is not documented: ask. |
| Can I see what the terminal did? | Not yet; Experts and Journal logs are not available on Edge.[7] |
Four of those eight rows end in "ask". That is the honest state of the public documentation, and the same standard applies to every vendor you evaluate.
Who should choose which
Choose open source and self-host if you want to read and modify the connector, you run MetaTrader 4 or other Expert Advisors alongside it, you need control over EA settings and terminal logs today, your broker or workflow is not supported by any managed product, or you value the learning and independence. Expect to own the hosting, the patching and the incidents, and budget your time for it. Our build-or-buy worksheet helps put a number on that time.
Choose a managed service if you only need PineConnector's connector on MetaTrader 5, you would rather not operate a server, and you accept the current early-access limits on settings and logs. Read what PineConnector Edge is and the Edge Guide for the exact scope before deciding.
A middle path exists. PineConnector's connector can also be run self-hosted on your own machine or VPS, which keeps the vendor's connector but leaves you the terminal, its settings and its logs. The setup guide covers both routes, and do you need a VPS covers where to run it.
Whatever you pick, run the nine pre-live tests on a demo account. Transparency lets you read the answers; a managed service asks you to trust them. Testing is how you verify either.
Frequently asked questions
Is open-source automation less safe than a paid product?
No. Openness is a property of the licence, not of quality. A well-maintained open project you can read may be easier to trust than a closed one you cannot. The risk in both cases is operational: who keeps it running and who fixes it.
Can I run an open-source connector on PineConnector Edge?
No. Edge runs only PineConnector's own component and "does not support custom or other third-party EAs".[7] Open-source connectors need your own Windows machine or VPS.
If I go managed, do I lose my strategy if the vendor disappears?
Your strategy and alerts stay on TradingView and your account stays at your broker. You would need a new connector and terminal, which is the same position a self-hoster is in if their server dies, minus the code.
Does PineConnector publish how it handles duplicate alerts?
Not on the pages reviewed for this article. Ask support and test it on a demo account before relying on it.
Next step: if you are leaning managed, check the Edge Guide for current scope. If you are leaning open source, start with the eight questions above against the project you have in mind.
Reviewed 10 September 2026. Facts and prices were checked against the linked sources on that date.
Sources
- Open Source Initiative – The Open Source Definition, accessed 10 September 2026.
- MetaQuotes – MetaTrader 5 Help: Algorithmic Trading (Expert Advisors), accessed 10 September 2026.
- TradingView – How to configure webhook alerts, accessed 10 September 2026.
- TradingView – Webhook resubmission, accessed 10 September 2026.
- Microsoft Learn – Manage device restarts after updates, accessed 10 September 2026.
- PineConnector – PineConnector Edge: Managed MT5 Hosting, accessed 10 September 2026.
- PineConnector Docs – Edge Guide (Early Access), accessed 10 September 2026.
PineConnector executes the instructions you send it. It does not select trades, manage money, or hold funds. Trading carries risk, and past performance of any strategy does not indicate future results.
