Frequently asked questions.

FirmGated is an execution-routing and prop-rule defense platform. It receives alerts from tools such as TradingView or TrendSpider, checks them against the controls you configured, and routes eligible orders to a connected account. FirmGated is not a broker, does not hold customer funds, and does not choose trades for you.

No. Once your alert and webhook are configured, the alert travels from the signal provider to FirmGated's servers. Closing your browser or computer does not stop server-side routing. Your connection and strategy still need to be enabled and healthy.

Use this order: connect a paper or demo broker account, create a strategy, copy its webhook URL into your alert provider, route the strategy to the paper account, send a test signal, and inspect the signal and trade records. Move to live capital only after the complete paper flow behaves as expected.

Create a FirmGated strategy, copy its unique webhook URL, paste that URL into the TradingView alert webhook field, and put valid JSON in the alert message. Route the strategy to a paper account first and verify the received signal before enabling any live route.

Yes. Any service or program that can send an HTTP POST request with a JSON body can call a FirmGated strategy webhook. That includes TrendSpider and custom Python or JavaScript code. Keep the webhook URL private because it identifies the strategy endpoint.

A basic alert needs a ticker and action. Quantity is recommended; when omitted, the documented default is 1. An optional id or alertId helps you trace the event. Use the exact schema shown in the signal reference and test it on paper before relying on it.

A strategy is your playbook. It owns the webhook URL and the rules for its signals. Strategy to Broker (step 4 in the left menu) connects that strategy to a broker account. One strategy can connect to several accounts, each with its own settings.

Yes. One strategy can be routed to multiple accounts. Each account remains a separate destination with its own mode and route settings. Prop-firm permissions and account-ownership restrictions still apply, especially when using the trade copier.

Yes. Post JSON with action close_all or flatten_and_lock to your strategy's webhook URL, from a TradingView Pine alert or any Python or HTTP client. close_all cancels working orders and closes positions; flatten_and_lock also locks execution. The request runs in the background and the result arrives as an alert. Where a firm does not allow orders from FirmGated's servers, or the account is a funded live account, FirmGated sends an alert and does not place closing orders.

FirmGated tracks signal identity to reduce accidental duplicate execution. Include a stable id or alertId when your alert provider supports it. Do not intentionally reuse an identifier for a different trade, and verify the event trail whenever an alert appears more than once.

No. Broker APIs, exchange conditions, market liquidity, order type, network timing, and the broker's own controls affect execution. FirmGated records the routing trail, but it cannot guarantee acceptance, fill price, fill timing, or that an order will fill.

Use an exit message that matches the documented webhook schema. Existing FirmGated documentation supports a flat sentiment or an opposing action configured as an exit. Confirm the exact strategy behavior on a paper account first, because a plain opposite-side order can reverse rather than flatten if its quantity or route configuration is wrong.

Manual Approval holds an incoming trade for review instead of immediately routing it. Approve or reject the held trade from Alerts. It is useful during setup or whenever you want a human decision before an order reaches a broker.

Authorized Auto-Route permits eligible signals to route without manual approval each time. Authorization does not override safeguards, broker rejections, market conditions, or a prop firm's rules. Confirm that your own account agreement permits the intended automation before enabling it.

Open Trading Activity and the signal detail first. Check whether the trade is awaiting manual approval, a safeguard blocked it, the destination route is paused, the broker session needs attention, the symbol or quantity was rejected, or the broker returned an error. The recorded status is the authoritative starting point, do not resend blindly because that can create a second order.

Confirm the alert is enabled at the source, the webhook URL exactly matches the active strategy, the request uses POST with valid JSON, and the strategy has not been replaced or disabled. Check the alert provider's delivery log. Never publish the full webhook URL in screenshots or support messages.

Connect a paper or demo account, route a strategy to it, send representative entry and exit alerts, and verify the full trail from signal receipt through broker response. Test safeguards, duplicate handling, wrong symbols, rejected orders, reconnects, and session boundaries. Do not use live or funded capital until those results match your intent.

Safeguards evaluate eligible orders against controls you configure, such as loss, drawdown, position, timing, and approval limits. Depending on configuration, a control can warn, hold, block, or trigger an authorized protective action. Safeguards reduce operational risk; they do not eliminate trading risk.

New eligible signals can be blocked for the configured period once the limit condition is met. An open position is not necessarily closed merely because new entries are blocked; liquidation requires the relevant protective action to be configured and authorized. Review the exact safeguard state and account rules before relying on it.

Guardian is FirmGated's separate monitoring and rule-protection surface. It can watch supported account conditions, produce warnings, and, only where configured and authorized, apply protective controls. Availability and rule coverage vary by broker, firm, program, and account phase.

Possibly, but permission is firm-, program-, phase-, platform-, and sometimes account-specific. FirmGated displays evidence and warnings where available, but your signed agreement controls. Confirm automation, copier, signal, cloud/VPS, and account-ownership rules with the firm before enabling routing.

No. Firm rules and agreements can change without notice, and the same firm may apply different terms by program or purchase date. FirmGated's evidence is informational, not a definitive legal answer. Check the firm's current official rules and your signed agreement before trading.

Use the Firm Countries checker for the latest documented availability by firm. A firm's published country list can differ between evaluation and live funding, and it can change. FirmGated is unavailable in comprehensively sanctioned locations.

The copier mirrors eligible orders from a lead account to selected follower accounts owned by the same trader. Each follower remains subject to its broker connection, sizing, safeguards, and firm rules. Copying between accounts owned by different people is not an approved FirmGated use case.

Connection status changes as integrations pass testing. Use the Connections directory as the live source of truth; it distinguishes available routes from planned or limited ones. Do not assume a listed broker, platform, or prop firm is enabled for every account type.

Open Connect Brokers, choose the provider, select the correct environment or account mode, and complete the provider-specific connection flow. Start with paper or demo access. Never send credentials through chat or email; enter them only through FirmGated's designated secure connection flow.

Pause affected live routes, open the broker connection record, and follow its reconnect or credential-refresh flow. Verify account discovery and paper execution again before resuming automation. Repeated failures should be reported with timestamps and non-secret error text, never with passwords, tokens, or full webhook URLs.

FirmGated's documented vault design encrypts broker credentials with AES-256-GCM before database storage. Decryption is limited to the execution path that needs it, and plaintext broker credentials are not intended for logs or Redis storage. You should still use provider security controls and report suspected exposure immediately.

Treat a strategy webhook URL like a secret endpoint. Do not post it publicly, include it in screenshots, or paste it into community messages. If you believe it was exposed, stop the affected route and replace or rotate the strategy endpoint through the supported workflow.

Use a unique password, keep your email account secure, review security and audit events, and never share sessions or broker credentials. If access may be compromised, reset the password and contact support before resuming live automation.

Plans differ by live-route capacity, paper-route capacity, and asset access. Compare those limits against the number and type of accounts you actually intend to run. The current Plans page is the source of truth for pricing and included capacity.

No. This assistant explains FirmGated and points to documented operational information. It does not recommend trades, predict markets, select firms, interpret your agreement as legal advice, or decide how much risk you should take.

Use the Support page for current contact options. Include the approximate time, page, broker/provider, account mode, signal or trade identifier, and the visible error. Remove credentials, tokens, full account numbers, and webhook URLs before sending anything.