FundedNext hub

FundedNext EA permission and JPTC setup

Check permission for the exact FundedNext account before choosing software. The current policy restricts account size, platform, add-ons and strategy. JPTC product availability does not override those conditions. Official rules checked 16 October 2026.

Published by JPTC EA Team under the JPTC editorial policy.

Compare Prop Firms

Check account and platform eligibility first

FundedNext’s CFD policy of 8 September 2026 permits EAs on eligible MT4/MT5 accounts below $50,000 with the paid EA add-on. Accounts of $50,000 or more must be fully manual, including SL/TP and lot-adjustment tools. EAs are prohibited on cTrader and Match-Trader at every size. Check the actual programme and order as well; being below the size threshold is not approval for every offer or file.

Check the strategy, not only terminal support

Bots specifically designed to pass prop-firm Challenges are prohibited. FundedNext also requires customised settings and a distinct strategy, prohibits identical trades across its accounts and Telegram/WhatsApp application integrations. A per-strategy allocation ceiling does not waive the account-size restriction. An EA Hub rule profile or working connection is a technical feature, not FundedNext authorisation.

Use the actual product and phase rules

Record the model, purchase or reset date, phase, add-ons and applicable terms. Minimum trading days are eligibility conditions, not instructions to force otherwise unwanted orders. FundedNext’s Quick Strike parameter concerns profit from trades closed within 30 seconds, not a generic best-day profit formula. A Challenge progress hold and an account breach have different consequences. Check the current rule for the account and stage.

Validate the exact file in a permitted test environment

Record the EA version and hash, MT4 or MT5 binary, setfile, broker server and symbol. Verify order behaviour on an authorised demo or test environment before any permitted account use. Platform support does not establish identical fills across feeds or permission for a hosted strategy, copier or third-party access. Ask FundedNext about an unclear arrangement before connecting it.

Verify symbols, units and execution costs

Check the exact symbol string and suffix, contract size, tick or pip value, minimum lot, lot step, stop restrictions, spread, commission and server time. A symbol mismatch is one possible cause of missing orders, alongside settings, permissions, connectivity and deliberate entry filters. Do not diagnose every quiet session as a fault or place an unwanted trade to test an evaluation account.

Configure risk with room for execution uncertainty

Use the actual programme’s daily and maximum loss calculations, including floating positions and relevant costs. FundedNext’s daily calculation uses the initial-account-balance allowance and the day’s trading result; a generic highest-equity percentage or fixed daily equity floor is not interchangeable with it. Recheck resets and phase changes. Guards may attempt to stop orders or close positions, but gaps, slippage, disconnections and software errors can still cause a breach.

Keep a record that matches the account history

Save the exact file, setfile and test report with their dates and limitations. Log parameter changes, terminal restarts, manual actions and rejected orders. Reconcile records with actual fills and investigate unexplained differences. Documentation helps establish what ran; it does not guarantee approval, a Performance Reward or a future trading result. Do not conceal copying or change entries to disguise a prohibited arrangement.

Distinguish downloadable software and the hosted service

EA Hub software runs on the customer’s authorised MT4 or MT5 terminal and needs that terminal online. JPTC’s separately hosted Algo requires no customer installation or VPS, but its hosting does not establish FundedNext permission. The results page publishes monthly figures from that service’s broker statement. Those figures are neither an independent audit nor pass-rate evidence for another downloadable EA.

Read the actual licence and delivery conditions

Normal and Pro have separate checkout agreements. The current Normal agreement describes a 7-day refund from purchase before both licence-key issuance and binary download; delivery of either ends that stated refund condition. Pro additionally requires that no Pro-only setfile has been accessed. The condition is not simply whether the EA has traded. Read the selected product’s actual checkout and agreement, including separate bundle or hosted-service terms; this page creates no new policy.

Ready to run it on your own account?

You keep the account, the login and the withdrawal rights. We never hold funds and never trade on your behalf.

Compare Prop Firms

Common questions

Does FundedNext permit every EA?

No. The current CFD policy requires an eligible MT4/MT5 account below $50,000 and the paid EA add-on, with strategy and programme restrictions. Accounts from $50,000 must be manual; cTrader and Match-Trader prohibit EAs.

Does JPTC platform support prove permission?

No. A supported terminal, rule profile or connection does not authorise the strategy or account arrangement. Check the exact programme, file and current FundedNext rules before use.

Does a strong trading day automatically end a Challenge?

Do not substitute a generic best-day formula for the actual rule. FundedNext’s Quick Strike parameter assesses short-duration profit concentration. Its Challenge progress hold is distinct from account termination.

Can I reuse a setfile after a phase or account change?

Recheck permission, model, balance, units, loss calculations, server reset and execution conditions. A setfile only changes supported inputs; it cannot add a missing code-level control or guarantee an outcome.

Can a loss guard prevent every breach?

No. It depends on the correct configuration, current data, a running terminal and execution. Gaps, costs, slippage, connection failures and other trades can still cross a limit.

Is the refund based only on the first trade?

No. The actual Normal and Pro agreements use licence, download and delivery conditions, with an additional Pro-setfile condition. Read the chosen checkout agreement; the hosted Algo and bundle have separate terms.

What records should I keep?

File and setfile versions, test conditions and limitations, parameter changes, order logs, restarts, rejected orders and manual actions. They should match the account history; a complete record is not approval or a payout promise.

Why has an EA placed no trades?

Check permissions, connection, symbol, inputs, session and entry filters, plus Experts and Journal messages. A quiet session may be intentional. Verify behaviour in an authorised test environment rather than forcing a trade.