You pay nothing to start. We offer a generous trial period where the first 38 days are completely free from the date you register your Machine ID. Here is your roadmap to live trading:

1. Register: Create your account at NinjaConnects.com.
2. Machine ID: Navigate to your User Profile Page. Edit your profile, enter your NinjaTrader Machine ID, and complete your details.
3. Installation: Download the software and follow the Setup Instructions carefully.
4. Connectivity: Create a tunnel (ngrok or Cloudflare) to your NinjaTrader computer and test the connection to ensure signals can reach you.
5. Trade: You are now ready to trade!
6. Subscribe: To continue using NinjaConnects after your trial, simply purchase a subscription at the Subscription Page.

To route signals over the WAN, the Receiving Computer must be visible to the internet. This is achieved in two ways:

• Option A: Use a Tunnel (Cloudflare or ngrok) to expose the local port.
• Option B: Ensure the computer is listening on Port 35426. (Tip: You can remember this port using the numeric keypad acronym FKHAN).

Configuration Rules:

• The Sending Computer must use a TargetSecret that matches the Receiving Computer's SourceSecret.
• Upon generating an alert (from a local NinjaTrader execution) or receiving one (from TradingView), the Sender forwards the JSON payload to the Receiver.
• The Receiver will accept the order only if the Secrets match. It will drop the signal if:
  1. The Secrets do not match.
  2. It is configured strictly as an "Observer" node (unless adoption criteria are met).

LAN forwarding is simpler than WAN:

• Ensure Computer A (Sender) can Ping Computer B (Receiver) via its local IP address.
• Configure the Target Secret on Computer A to match the Source Secret on Computer B.
• No tunnels are required for LAN communication; just direct IP routing on port 35426.

Technically: No. The FSK Distributed Trading Protocol is designed to scale indefinitely. Your trading "Sysplex" can span the globe with computers geographically dispersed to match your design requirements.

Licensing: A standard Single User License allows you to implement the protocol on up to 4 Computers simultaneously. To expand your grid beyond 4 nodes, you simply create a new account to obtain an additional license.

The Politeness Delay is a configurable wait-time feature that serves two critical objectives within the FSK Ecosystem:

1. Synchronization & Safety (Anti-Race Condition):

• When using an "Observer" (Backup) computer, the delay prevents it from fighting the Primary computer for control. The Observer waits (e.g., 3 seconds) to see if the Primary acts. If the Primary fails (crash/disconnect), the Observer steps in only after the delay expires.

2. Stealth & Market Normalization (Iceberg Slicing):

• When distributing a large "Whale Order" across many nodes, executing them all at the exact same millisecond can create an artificial price spike.
• By adding a random Politeness Delay to different nodes, you can deliberately stagger the orders. This disperses the execution over time, mimicking "normal market activity" and hiding your institutional intent from high-frequency algorithms.

Lifeboat settings are configured on the Receiver (the computer placing the trades):

• Enable: Check the "Use Lifeboat" box.
• Configuration: Specify your Max Profit and Max Loss amounts.
• Disable: Setting Max Profit or Loss to 0 (Zero) effectively disables the Lifeboat logic for that parameter.

Important Notes:

• Broker-Side Safety: Lifeboat Orders (Stops/Targets) are sent directly to the Exchange/Broker. They reside there, protecting you even if your internet fails.
• Daily Limits vs. Lifeboat: If "Use Lifeboat" is unchecked, NinjaConnects will still respect the Account Daily Max Loss/Profit limits. If a limit is hit, the system will flatten the account and cease trading for the day.
• Unlimited Mode: If "Use Lifeboat" is OFF and Daily Limits are set to 0, there are no safety caps. The strategy alone controls the outcome.

Yes. By default, "Trade All Day" is enabled. To restrict operations:

1. Uncheck the Trade All Day flag.
2. Define your Start and End times using your local time zone.

Behavior: When the start time arrives, NinjaConnects begins honoring trade orders. When the end time expires, the system will automatically Flatten the account it is running on to prevent overnight exposure.

Yes. NinjaConnects is not limited to automated strategies. It can detect manual trades placed on the chart and export them as the exact same JSON alerts used by the protocol. This means a manual trader can act as the "Signal Source" for a fleet of automated followers, creating a hybrid Man-Machine ecosystem.

• Registration/Login: Visit https://ninjaconnects.com.
• Subscription Payment: Use this direct link for all plans: Subscription Page.

Yes. You can pay for a year (or more) in advance during the limited-time discount period.

• Your subscription expiry date will be extended accordingly.
• This protects you from future price increases. Once the limited-time offer expires, new renewals will be at the standard displayed price, but your pre-paid period remains valid.

No. We believe in fair partnerships. While we are a for-profit company, our history of price increases is less than 5% per year, strictly to cover inflation and the costs of development, testing, and support. We do not hold customer data or infrastructure "hostage" with sudden hikes.

No. Your subscription includes protection against price increases for the paid period and guarantees access to all recent upgrades, enhancements, and feature releases. We believe in service first.

General Questions: Please post on the community forum at support.ninjaconnects.com. We answer promptly and point to relevant documentation.

Bugs & Technical Issues:

1. Do not post raw logs on the public forum.
2. Copy the Client Log (from Output 1) and Server Log (from Output 2).
3. Save them as client_log.txt and server_log.txt.
4. Email them to [email protected].
5. In the email, describe the issue in detail, including steps to reproduce it in a market simulation.

We will research the issue and post the resolution (excluding your private logs) to the community.