ETNA: branded brokerage platforms, order APIs and back-office controls

ETNA’s products address the customer-facing terminal and the operational systems behind a brokerage or investment-adviser business. Individual modules can be deployed separately or combined into a branded service. The relevant purchase is therefore a defined software and integration package.[1]

The adviser product’s portfolio automation and custody integrations are relevant to managed-account businesses. Its onboarding tools collect documents, assess investor status and risk tolerance, and maintain agreements. These functions should be specified separately from the reporting and billing features still labelled as forthcoming; the product page does not justify treating every illustrated module as delivered.[4]

For a broker whose core business is FX, the most concrete current product specification is ETNA’s US-securities platform and its associated account infrastructure. The public trading page describes advanced and contingent orders, extended sessions and account-group permissions. Asset and venue availability should follow the selected connection and implementation scope.[2]

The published API reference uses an environment-specific base address. Authentication combines a company application key with the user’s credentials, returning a bearer token whose documented lifetime is 24 hours. The application key is managed through company settings and may distinguish web, mobile or custom applications. Implementations therefore need both application configuration and the correct user context.[6]

ETNA’s MCP bridge exposes five read tools, four trading tools and a diagnostic tool. It describes a read-only default and explicit user approval before a place, modify, reprice or cancel request reaches ETNA. The language model prepares the action; the bridge handles approved submission. This is materially different from permitting an assistant to trade solely because it can read positions.[10]

The MCP security description keeps ETNA credentials and application keys on the server, encrypted with AES-256-GCM. Browser consent issues short-lived scoped bridge tokens. It also describes redirect allowlists, token-family revocation and trading-call audit records. Those controls belong to the documented bridge design; they do not establish the configuration of every custom application built against ETNA’s APIs.[10]

Enterprise platform and integration purchases use an enquiry route. The directly published prices are for an individual paper-trading service, and should not be used to estimate a broker’s branded production licence. The page directs professionals and businesses to a customised offer.[11]

Custom development is another distinct commercial workstream. ETNA offers product engineering, architecture, legacy modernization, cloud-migration planning and dedicated development teams. A project involving an inherited brokerage system may therefore include implementation services beyond the standard product subscription; the public services page does not supply a universal project rate.[15]

The ETNA–RQD offering separates ETNA’s trading and order-management layer from RQD’s clearing operation. ETNA describes REST/webhook integration, while RQD provides event-driven clearing connectivity. Its advertised two-week ETNA go-live is a supplier proposition: the same page describes parallel clearing certification and phased onboarding. That timetable should be evaluated against the agreed integration and approvals.[13]

ETNA’s clearing-software workflow illustrates separate decisions by the broker and clearing firm: the investor supplies an account application, the broker approves it, and the clearing firm performs KYC and its own approval. Funding likewise passes through approvals before the clearing firm initiates the bank transfer. This identifies the software’s orchestration role without making ETNA the account’s clearing counterparty.[14]

Operational migration also involves account and security configuration. The back office supports automated start/end-of-day balance and position imports, security availability, corporate actions and customer or group-level commission settings. These are continuing administration functions as well as initial setup tasks; the broker’s own investor charges are separate from the fees paid to ETNA.[3]

The public EULA does not provide a complete enterprise renewal, deconversion or database-export schedule. Its update clause permits automatic updates without obliging ETNA to supply them, and breach can terminate the right to use the software immediately. A production agreement needs to resolve the operational handover and ongoing maintenance applicable to the purchased package.[16]

The official documentation directory separates broker administration/API material from end-user help. That distinction matters during onboarding: an investor’s terminal instructions do not grant administrative API access, while an integration team needs the environment and company settings described in the API reference.[20][6]

The public software licence names ETNA Software Corp and grants a limited, revocable right of use while retaining ETNA’s intellectual property. Sublicensing requires an additional agreement permitting it. A white-label relationship therefore needs the appropriate contractual rights for the broker’s intended distribution; the public EULA alone is not a blanket right to redistribute the platform. It selects Florida law.[16]

The compliance product describes configurable pre-trade quantity/price checks, duplicate-order detection and automatic rejection with logs, alongside supervisory alerts and risk-limit monitoring. These are supplier-described control functions. They support a broker’s operating procedures; a product’s compliance-oriented name is not financial authorisation for ETNA or a guarantee that a customer meets every applicable obligation.[18]

ETNA’s privacy notice concerns personal data. It allows retention for the relevant purposes and legal obligations, and describes deletion and machine-readable-copy rights subject to applicable legal and contractual conditions. Those rights should be distinguished from a negotiated export of a brokerage’s complete transaction history, configuration and audit records.[17]

ETNA Software Corp is the named software licensor. ETNA’s published history starts with custom financial-software development in 2002 and identifies 2013 as the launch of its trading and paper-trading SaaS products. Its current corporate contact address is in Boca Raton, Florida. This history helps explain the combination of packaged software and bespoke development services.[1][16]

The current business also markets dedicated development teams, technical advisory work and continuing product development. For procurement, that creates a choice between adopting a product’s standard workflow and commissioning additional engineering around it. The statement of work should identify which deliverables become part of the subscribed product and which remain a separately maintained integration.[15]

Operator

ETNA Software Corp

Service scope

Branded trading, order routing, account administration and operational controls.

Customer types

Broker-dealers; Investment advisers; Fintech firms; Trading educators

Delivery

SaaS; API

Pricing publication

Public and quoted pricing

Headquarters

Boca Raton, Florida, United States

Platforms

ETNA Trader; ETNA Digital Advisor

Pricing scope

Enterprise deployments by enquiry; separate published individual simulator plans.

Implementation

Modular software, integration and clearing-partner onboarding.

Support

Basic and Premium tiers have different published coverage and reaction times.

Permissions and regulatory scope

Software and workflow provision; brokerage and clearing roles remain with the relevant financial firms.

Provider metadata checked 21 Oct 2026Source 1Source 16Source 19Source 2Source 3Source 18Source 5Source 4Source 11Source 13Source 12Source 14Source 23

The omnibus product adds an internal sub-account layer to a consolidated external account. ETNA describes bulk execution, sub-account risk controls, account-level data and customised reporting, with international brokers using US broker relationships for US-market access. Its privacy proposition concerns how client details are represented within that structure; it should not be read as an exemption from the parties’ legal disclosure or onboarding duties.[21]

For market-data procurement, the product page distinguishes live quotations from a 15-minute delayed service and historical price/volume records. Depth displays and embedded branded interfaces are also offered. The commercial specification still needs to identify the markets, user population and permitted display or redistribution use; a product’s technical ability to show data does not by itself define exchange-data rights.[5]