EAERA

EAERA PROP is sold as five named modules. The Prop Dashboard is what the trader opens: balance, P&L and risk levels, evaluation progress against profit targets and remaining days, an equity curve, trade history, payout requests with profit-split detail, and gamification through badges and leaderboards. The CRM handles onboarding with KYC/AML document upload and checks, centralised trader profiles, lead capture and scoring, and compliance monitoring that "automatically flag[s] rule violations like daily loss limits or drawdowns". The Backoffice covers deposits and withdrawals against integrated gateways, financial and compliance reporting, account automation and audit trails. The Affiliate module runs multi-tier commissions with sub-affiliate hierarchies, referral links and QR codes, and payouts via PayPal, Skrill, crypto or bank transfer.

The rule engine lives in the Admin module, and this is where a buyer should press hardest. EAERA states the firm authors its own rules — "Define evaluation rules like profit targets and drawdown limits, track trader progress with automated alerts, promote successful traders to funded accounts, and manage account resets with fee tracking" — and that detection is real-time, with traders alerted "of potential breaches before penalties" and admins notified "of rule breaches or fraud in real time". Firm-wide risk is covered: "Monitor firm-wide exposure, including open positions and margin levels, set risk alerts for thresholds like drawdowns", with a live dashboard showing active accounts, evaluation progress, P&L, payouts and daily loss.

What is absent is the specificity a prop operator needs. Across the whole site EAERA never names a drawdown model — the words static, trailing, end-of-day and relative do not appear — and never says whether drawdown is measured on equity or balance. It does not publish what the system does on a breach: auto-close, lock, disable trading or notify only. Consistency rules and news-event lockouts are not mentioned. Prohibited-strategy detection is described only as spotting "unusual trading patterns, multiple account usage, or potential fraud", with no named strategy class. Ask for a written rule matrix and a live demo of a breach before signing.

EAERA's prop product page states that it offers "Seamless integration with trading platforms like MT4/MT5, Ctrader, DX Trade, Match Trade and proprietary solutions", and the integrations page carries logos for MetaQuotes, Match-Trader, DXtrade, cTrader, Takeprofit Tech and Brokeree Solutions. EAERA also ships its own browser-based terminal, described on the Trading Platform page as "EAERA's CFD WebTrade: Integrated, modern web trading platform for retail trading & broker operations", offering real-time execution, charting and order management. Separately, EAERA sells an MT4/MT5 maintenance and administration service covering setup, updates and monitoring.

So the trader opens MetaTrader, one of the connected third-party terminals, or EAERA's own web terminal. What a futures-focused operator will notice is the absence of that side of the market: TradeLocker, Rithmic, Tradovate, NinjaTrader, Quantower and TradingView are named nowhere on the site. EAERA is an FX and CFD stack. Asset classes are described loosely — the competition product references "forex pairs, commodities" and the terminal is branded for CFDs — and no instrument list is published. A crypto spot exchange solution is advertised in the main navigation, but that page is currently a broken link.

Mobile is thinner than the navigation suggests. The Prop Dashboard page promises a responsive dashboard and "a dedicated app", but EAERA publishes no app store listing and the Mobile App page in its menu is a development service it sells to clients, not a shipped trader app. The site itself runs in English, Indonesian, Japanese and Spanish, and EAERA says the product supports multi-language interfaces and multi-currency transactions, but it never enumerates which languages the trader-facing product ships in. Treat the terminal, the mobile app and the language list as demo items.

This is the strongest-documented part of EAERA's site. The integrations page and the site-wide Integrations menu group named third parties into eight categories. Trading platforms: MetaQuotes, Match-Trader, DXtrade, cTrader, Takeprofit Tech and Brokeree Solutions. eKYC: Sumsub, the only provider named. Business intelligence: Power BI, Tableau, Looker Studio and MATLAB. News: Autochartist and Acuity. VoIP: Squaretalk and Voiso. Marketing: SendGrid, GetResponse and SendPulse.

The payments list is the longest: Confirmo, B2BinPay, Zotapay, Payment Asia, Stripe, PayPal, Skrill, Neteller, Nuvei, Decta, BridgerPay, Help2Pay, bitwallet, BitPay, Binance Pay, SticPay and Perfect Money, plus XValley Exchanger. A generic bank-transfer tile also appears, which is a method rather than a provider. These are presented as logos without accompanying text, so EAERA does not say which are certified, which are live in the prop product versus the FX product, or what each connection costs to enable.

The Brokeree Solutions tie is the best-evidenced: announced in August 2025, it puts copy trading leader and follower activity and trading volumes into EAERA's CRM dashboards across MT4 and MT5, with automated onboarding flows for copy trading roles. Two gaps matter for an operator. No liquidity provider or bridge is named anywhere — for a prop firm running a live book that is a conversation to have early. And the build-it-yourself path is undocumented: EAERA references "APIs for CRM systems, risk management tools, and compliance solutions" but publishes no developer documentation, so anything not on the logo wall is an unpriced custom project.

EAERA is consistently described as cloud software — the homepage calls EAERA CBS "our unified cloud software" and the About page describes accelerating "cloud-based deployments for financial clients" from 2020. White-labelling is offered on top of that, so the two deployment models evidenced are SaaS and white label. Nothing on the site offers or rules out self-hosting or an on-premise licence.

Beyond that, the hosting picture is undisclosed. EAERA names no cloud provider, no hosting region and no data-centre operator. The closest the site comes is an FAQ answer about "the data centers that house your technology infrastructure", which says they "adhere to industry-leading security standards, employing multi-layered encryption, regular audits, and strict access controls" — a statement with no verifiable content. There is no published latency figure, no co-location claim and no statement of proximity to any trading venue.

Three specific questions are unanswered and should go on the call agenda. Does each firm get a dedicated instance and database, or is this multi-tenant with logical separation? Can a firm run the trader-facing portal on its own domain? And in which jurisdiction will the firm's trader data physically sit — which matters given EAERA operates from Vietnam, Cyprus, Montenegro and Malaysia, and its privacy policy states that data "may be transferred internationally, including outside the EEA" under Standard Contractual Clauses. For a firm with EU or UK traders, get the data residency answer in writing.

Branding control is claimed but never specified. Three separate pages assert white-labelling — "Enable white-label customization to match firm branding" on the Admin module, "Allow custom branding for dashboards and materials" on the Affiliate module, and "White-label solutions to align with broker branding" on PAMM/MAM. None of them says what is actually configurable. Logo and colour changes, full CSS or theme control, custom email templates, a custom domain, and whether EAERA's own branding is removed from the trader journey are all unstated. An operator should ask to see a live client instance rather than a marketing screenshot.

The API surface is the weakest-documented area of the product. EAERA refers to "API for custom integrations and extensions" on the PAMM/MAM page and "APIs for CRM systems, risk management tools, and compliance solutions" on the prop page. That is the whole of it. REST is never stated, and neither is GraphQL, WebSocket or webhook support, so none of those can be recorded as present. No SDK is offered in any language. No sandbox or test environment is mentioned.

Critically, there is no developer documentation at all. No documentation URL is linked from any page, and the conventional hosts do not exist: docs.eaera.com, api.eaera.com and developer.eaera.com all fail to resolve, and /docs returns nothing (checked 2026-09-19). For a buyer planning to build their own trader front end or push data into a warehouse, this means the integration effort cannot be scoped before contract — you are dependent on EAERA's team to describe its own API to you. EAERA does sell bespoke development through its Mobile App and Web App service lines, which is the route it appears to expect firms to take, and which is billed separately.

EAERA publishes no pricing whatsoever. There is no pricing page — https://eaera.com/pricing/ returns a 404 — and no price, tier name, currency or percentage appears anywhere on the site. This was checked on 2026-09-19 across the homepage, both product lines and all their sub-pages, the solutions and services pages, the partners and partnership pages, both FAQ centres and the legal pages. So the prop firm white label cost here is entirely a custom quote, and the model, billing cycle and minimum term are all unknown.

Every call to action on the site routes to the same destination: a Request a demo form. The homepage form sets the expectation plainly — "Our team will introduce the solution, walk through demo examples, and deliver a commercial proposal." A demo is therefore available. The About page adds "Try demo version of EAERA products for free", but attaches no trial length, no scope and no terms, so it cannot be read as a defined free trial.

What the headline quote will not cover is predictable from the product's shape, and an operator should price these separately: the MetaTrader, cTrader, DXtrade or Match-Trader platform licence itself, which EAERA connects to rather than supplies; payment gateway fees across whichever of the seventeen-plus named PSPs you enable; per-verification KYC charges from Sumsub; the Brokeree copy trading licence; any BI tooling such as Power BI or Tableau; and custom development, since anything outside the named integration list has no published API to build against. EAERA's MT4/5 maintenance service and its mobile and web app development are separate service lines and should be assumed to be separately billed. One structural point in EAERA's favour, from the homepage: "We do not own or sell your data, nor do we rely on advertising-based revenue models. Our sole source of income is the software licensing fees you pay us."

EAERA states a notably short timeline. Both the prop and FX FAQs answer the implementation question identically: "On average, our software implementation process takes approximately 3-5 days, though it may vary depending on the project scope and customization requirements." That is fast against typical prop tech onboarding, it is the vendor's own unaudited figure, and it is explicitly scope-dependent. It also covers software implementation only — company formation, banking, PSP approvals, platform licensing and KYC provider contracts sit outside it and are usually what actually determines a launch date.

A seven-step setup sequence is published: define business requirements, choose the CRM platform, plan integrations, customise the CRM, data migration, training and testing, then go live and support. Read it carefully, because it is written as generic advice on selecting and deploying any CRM rather than as EAERA's own project plan — step two is "Choose the CRM Platform… Select a CRM tailored for FX brokers or a customizable generic CRM", which is a buyer's-guide step, not an onboarding step. Ask EAERA for its actual implementation plan with named owners and dates.

On migration, EAERA lists a data migration step — "Transfer existing client and lead data securely into the new CRM" and "Validate the accuracy and integrity of the migrated data" — so migration support exists. But it never says migration is included in the fee, and it names no incumbent platform it migrates firms off, so budget for it as a line item. Training appears as a step ("Train staff on how to use the CRM effectively") without a stated format, duration or whether it is live or recorded. No dedicated project manager is promised, and no implementation documentation is published.

Support hours are the one firm commitment EAERA makes. Both FAQ centres state: "We provide 24/7 technical support, ensuring prompt assistance with any issues, updates, or maintenance required post-deployment, ensuring uninterrupted operations." The FAQ centre offers two routes — an Email Us option and a Call Us option — so email and phone are the evidenced channels. Live chat is described as a feature EAERA builds for its clients' own affiliate support, not as a channel EAERA offers its customers, so it should not be assumed.

Everything else in this section is unpublished. There is no first-response target, no P1 definition, no escalation path, no named support languages, and no promise of a dedicated account manager. On uptime, the phrase "Uptime Guarantee" does appear — as a benefit card heading on the MT4/5 maintenance service page — but the text beneath it reads "Keep your platform operational around the clock with minimal disruptions", with no percentage attached. A heading without a number is not a commitment, so no uptime figure can be recorded for EAERA.

There is also no way to verify reliability independently. EAERA operates no status page: /status/ returns 404 and status.eaera.com does not resolve (checked 2026-09-19). There is no incident history, no post-mortem archive and no changelog. And because no SLA, MSA or customer terms document is published anywhere on the site, there is no evidence on whether service credits exist or what they would be worth. For an operator whose traders are live 24/5, this is the single largest documentation gap in EAERA's public surface: the uptime commitment, the credit regime and the escalation path all have to be negotiated from scratch and written into the contract.

Be explicit about what is and is not evidenced here, because the distinction matters. EAERA holds no certification that is publicly evidenced. The only ISO reference anywhere on eaera.com is one line in the About page timeline, under 2024: "Recognizing the need for strong governance, EAERA began developing its Integrated Management System (IMS), aligned with ISO 9001:2015 and ISO/IEC 27001:2022, ensuring quality and information security in financial environments." That states alignment and work begun — not certification. No certificate, certificate number, issuing body, auditor, scope statement or expiry date is published, and EAERA has no security or trust page (/security/ returns 404, checked 2026-09-19). SOC 2 is never mentioned. PCI DSS appears only as a standard EAERA says it builds client applications to, not as something EAERA itself holds. If a certification is a regulatory requirement for you, ask for the certificate PDF and verify it with the issuing body.

Access controls are stated more concretely. The FX broker page describes "advanced security features like role-based access, two-factor authentication (2FA), and comprehensive audit logs", and the prop page adds "role-based access controls, two-factor authentication, and encrypted connections". The Prop Dashboard offers traders 2FA, active-session monitoring and audit logs. So role-based access, MFA, audit logs and encryption in transit are supported. Encryption at rest is never stated, and neither is SSO.

On data protection, EAERA's privacy policy is a properly constructed GDPR document: it names two data controllers, sets out lawful bases including consent, contract, legal obligation and legitimate interest, grants the full set of data subject rights including erasure and portability, and commits to Standard Contractual Clauses for transfers outside the EEA. What it does not do is offer customers a data processing agreement — the DPAs it references are the ones EAERA holds with its own suppliers. Backup frequency, recovery point and time objectives, disaster recovery testing and penetration testing frequency are all unpublished; the privacy policy's "regular security audits" names no frequency and no auditor. There is no bug bounty programme.

EAERA names no client. There is no case study, no client logo wall and no testimonial anywhere on the site — not on the homepage, the prop or FX product lines, the Partners page or the About page (checked 2026-09-19). The Partners page, despite its name, lists technology categories rather than customers: "we partner with industry leaders in PSPs, trading platforms, VOIP systems, and KYC/AML providers". For an operator, this means no reference can be taken from public material, and no independent view of scale is available.

The only quantities EAERA publishes are three animated counters on its homepage, whose target values are 10, 3 and 100, labelled "years of CRM expertise", "offices worldwide" and "Fintech firms". These are self-reported marketing figures with no methodology, and one of them is internally inconsistent: the counter says three offices while the contact page lists four (Vietnam, Montenegro, Malaysia and Cyprus). None is recorded as a figure in this profile. The About page separately states "For more than 10 years, we've been bucking FX Industry trends", which is consistent with a 2015 founding but says nothing about how long the prop product specifically has been in market — EAERA's own timeline dates EAERA CBS V2, the version it says supports proprietary trading operations, to 2022.

Two externally verifiable markers do exist. EAERA CBS received an "Outstanding Technology Product in the Fintech Field" award at Vietnam's Sao Khue Awards on 13 April 2024, though EAERA's own write-up frames that product as a securities-company core system rather than the prop stack. And the August 2025 Brokeree Solutions integration was covered in trade press, which quoted Quan Ta as CEO of EAERA. Neither tells you how many prop firms are live on the platform. Ask directly for the number of prop firms currently in production, how many launched in the last twelve months, the largest account count on a single instance, and two referenceable clients running the same modules you intend to buy.

Nothing is disclosed. EAERA publishes no customer-facing contract of any kind: the only legal documents on the site are a Privacy Policy and a Cookie Policy, both written for website visitors rather than for software customers. Both /terms/ and /terms-of-service/ return 404 (checked 2026-09-19). There is no MSA, no order form template, no service schedule and no acceptable use policy. Consequently minimum term, notice period, auto-renewal, cancellation rights, liability cap, service credits and governing law are all unevidenced, and none can be recorded here.

The same applies to the exit questions an operator should care about most. Who owns the trader data — the firm or EAERA? In what formats can it be exported, and via what mechanism? How long after termination does the firm retain access? Is there any offboarding assistance? None of this is addressed in any published document. The only adjacent statement is a positioning line on the homepage: "We do not own or sell your data, nor do we rely on advertising-based revenue models. Our sole source of income is the software licensing fees you pay us." That is a commercial-model statement, not a contractual data ownership clause, and it should not be relied on as one.

One structural point deserves attention before contracting. EAERA's privacy policy names two controllers — "EAERA Ltd, registered in Cyprus" and "EAERA VN Co., Ltd, registered in Vietnam" — while the site footer carries a disclaimer that the site "serves as a common showcase for marketing services of different companies that work in the frames of their local legislations" and that "EAERA Ltd does not provide any financial or other services advertised on this website", directing buyers to "contact the sales team for more information about the servicing company". Establish in writing which legal entity will be your counterparty, in which jurisdiction, under which governing law, and whether that entity carries the liability for the services you are buying.