Signalator Notify is a monitoring and alerting product for Windows machines, trade terminal health, trade activity, and price conditions.
Signalator Notify FAQ
Clear answers for setup, monitoring, delivery, and deployment
This FAQ covers what Signalator Notify does, how the main modules differ, how setup works, how alerts are routed, and when hosted or self-hosted deployment makes sense.
On this page
- Product scope and plan differences
- Setup and source connection basics
- Windows Monitor, Trade Monitoring, Terminal Health, and Price Watch
- Alerts, privacy, and troubleshooting guidance
Notify FAQ
General
Start here if you want the shortest explanation of what Signalator Notify is, what it covers, and who it is built for.
Signalator Notify monitors Windows machine status, trade terminal health, trade activity, and price conditions. This can include a Windows VPS or local Windows machine, terminal health for platforms such as MT4, MT5, cTrader, NinjaTrader, and TradingView-connected workflows, plus trade monitoring and price watch rules.
Signalator Notify is for users who need operational visibility into Windows machines, trade terminals, trade activity, or price conditions.
Notify Windows is the simpler Windows machine monitoring product. Notify Pro adds broader monitoring such as trade terminal health, trade activity, and price conditions.
Signalator Notify supports Windows machines and trading workflows connected through platforms such as MT4, MT5, cTrader, NinjaTrader, and TradingView-connected paths.
No. Signalator Notify can also be used for Windows machine monitoring.
Yes. Signalator Notify can be used for Windows machine monitoring. Service-level monitoring depends on the exact setup and sender path used.
Notify FAQ
Plans and pricing
These answers explain how the Notify plan structure is positioned and when each level makes sense.
The current Notify structure includes Notify Windows, Notify Pro, Notify Advanced, and Enterprise. See the full plan comparison on the Notify pricing page.
Notify Windows is the standalone Windows machine monitoring plan. It is intended for monitoring the status of a Windows-based system without the broader trade monitoring modules. Typical examples include a Windows VPS, a CCTV or security workstation, or another always-on Windows machine that needs uptime monitoring.
Notify Pro is the hosted plan that adds broader monitoring beyond Windows-only coverage, including trade terminal health, trade activity, and price conditions. See the full breakdown on the Notify pricing page.
Notify Advanced is the stronger hosted tier for broader monitoring capacity, more profit rule monitoring, advanced profit rule monitoring, enhanced privacy options, additional supported sources compared with Pro such as NinjaTrader and TradingView, and access to extra delivery channels such as SMS. See the full breakdown on the Notify pricing page.
Consider Enterprise when you need self-hosted deployment, client-controlled infrastructure, or a more customized setup.
Yes. You can start with a smaller Notify plan and move to a broader one later.
Yes. Notify Windows supports up to 2 active monitored sources. Notify Pro supports up to 10. Notify Advanced is designed for higher limits. Enterprise depends on the capacity and design of the self-hosted deployment. See the full plan comparison on the Notify pricing page.
Notify FAQ
Setup and onboarding
This section explains how a new user usually gets from the first page visit to the first live monitored source.
Choose the right Notify plan, create the monitored source, apply the token or config, and wait for the first live heartbeat or event. Start here: Notify setup.
Create the source that matches what you want to monitor, then connect the correct sender or utility to that source. Use the normal onboarding flow here: Create a monitored source.
A source connection is the monitored object inside Notify that represents the sender side.
They identify the source connection and attach the sender side to the correct monitored object.
Use the Notify downloads page for setup files and apps, or go to Notify setup if you want the normal onboarding path first.
A simple Windows Monitor setup can be done quickly. Broader terminal and trade monitoring usually takes longer. The next step is here: Notify setup.
No. Notify can also run on a local Windows machine or another Windows host.
Notify FAQ
Windows Monitor
Windows Monitor is the machine-level monitoring layer. It is not the same thing as terminal health and it is not limited to VPS usage.
Windows Monitor is the module used to monitor the operational status of a Windows machine.
Windows Monitor checks whether the machine is still sending the expected heartbeat.
No. Windows Monitor is for the machine. Terminal Health is for the trade terminal.
Yes. Windows Monitor can run on a Windows VPS, local Windows PC, or another Windows machine.
Windows Monitor sends regular heartbeats on a short cadence.
If the machine stops sending heartbeats and crosses the offline threshold, Notify generates the offline event.
Yes. Notify can generate a recovery event when the heartbeat returns.
Windows Monitor is for operational monitoring. It collects the heartbeat signal and the limited source metadata needed to manage the monitored machine correctly.
Notify FAQ
Trade Monitoring
Trade Monitoring is the event layer. It answers what happened in trading activity, not whether the machine or terminal is alive.
Trade Monitoring is the part of Notify that monitors trade-related events.
Notify can detect trade events such as position opened, position closed, position partially closed, and pending order events.
Yes.
Yes.
No. Trade Monitoring and Terminal Health are separate capabilities.
Yes. That depends on the plan and deployment model.
Yes. Windows Monitor covers the machine, Terminal Health covers the terminal, and Trade Monitoring covers trade events.
No.
The practical trading-terminal focus is centered on MT4, MT5, and cTrader workflows.
Notify FAQ
Terminal Health
Terminal Health exists so users can monitor the operational state of the terminal itself without confusing it with either machine status or trade-event status.
Terminal Health is the part of Notify that monitors whether a trading terminal is operationally alive and still sending its expected heartbeat.
Trade Monitoring covers trade events. Terminal Health covers terminal operational status.
Windows Monitor is for the Windows machine. Terminal Health is for the trade terminal.
If the terminal heartbeat stops and crosses the threshold, Notify generates the terminal-health event.
Yes.
Yes.
Notify FAQ
Price Watch
Price Watch is the symbol and price-condition layer. It is there for target levels, crossings, and event-driven level alerts.
Price Watch is the module that generates alerts when a configured price condition is met.
You create a rule for a symbol and a target condition. Notify evaluates the price state against that rule and generates the hit event when the condition is met.
Yes.
Price Watch supports target and crossing-style conditions, including greater-than, lower-than, and crossing logic.
Yes.
Yes.
It is designed for event-driven delivery as soon as the configured condition is detected.
Notify FAQ
Alerts and channels
Notify is not only about detecting events. It is also about sending those events to the right place with the right amount of detail.
Notify supports dashboard alerts, Telegram paths, and mobile push.
Yes.
Yes.
Yes.
Yes.
Yes.
That depends on the configured routing and the available alternative channels.
Notify FAQ
Privacy and deployment
Privacy in Notify is strongly tied to visibility control, retention decisions, and deployment model rather than only to message transport language.
Hosted Notify handles privacy through visibility control, retention decisions, and plan-based deployment positioning.
Pro is the standard hosted tier. Advanced adds stronger hosted privacy positioning. Enterprise is the self-hosted path.
Yes.
Yes.
The client controls the server and database in Enterprise.
Yes, when the correct tier and deployment model are chosen.
Notify FAQ
Troubleshooting
This section helps users narrow problems down to the right operational layer instead of treating every issue as the same kind of outage.
That usually means the expected heartbeat or event flow has stopped long enough to cross the configured threshold.
First confirm the source is alive, then confirm the module is enabled, then confirm the event is being generated, and then confirm the delivery path is active.
Delays can come from heartbeat thresholds, evaluation cadence, channel behavior, or the path between detection and delivery.
This usually happens when Windows Monitor, Terminal Health, and Trade Monitoring are conceptually mixed.
Check the source object, token or config, sender status, first heartbeat or event arrival, and the enabled module.
If the Windows machine stopped reporting, it is a Windows Monitor issue. If the machine is fine but the terminal stopped reporting, it is a Terminal Health issue. If both are alive but trade events are missing, it is a Trade Monitoring issue.
Contact support when the source is correctly configured but still not attaching, or when the event or delivery path remains inconsistent after the core checks are complete. Contact us here: Contact.
Still need help?
Choose the next step that fits the question
Go to setup and downloads if you need to install or attach a source, move to pricing if you are choosing the right plan, or contact us when the question is commercial, custom, or deployment-specific.