Connect broker data without hiding the integration method.
Aether distinguishes production direct APIs, installable bridges and guided file imports. Before setup, traders can see which data path is actually available.
One ledger, three transparent data paths.
Every connection aims for reliable execution records and explicit account mapping. Aether Ledger does not implement order execution.
Direct APIs
Implemented server-side read paths connect supported providers without exposing secrets to the browser.
Signed bridges
Local platform companions can send executions through an authenticated connector.
Guided imports
Other sources use explicit file profiles instead of being advertised as live integrations.
API, bridge and import are not the same.
Direct APIs run server-side. Bridges need a local companion. Import profiles process files. Aether labels the difference before setup.
Choose the right path for the platform
A clear workflow keeps capture, analysis and decisions inside the same system.
Find the source
Search for the broker or platform and inspect its current connection status.
Set up read-only access
Provide only the data access or companion configuration that the selected path requires.
Verify the result
Test the connection, map the remote account and inspect synchronization status.
Frequently asked questions
The most important capabilities and boundaries, answered clearly.
Does every listed broker have a direct live API?+
No. Direct APIs, bridges and file imports are labeled separately, and the setup dialog shows the available path.
Why does NinjaTrader need a bridge?+
A local NinjaScript companion reads executions inside the platform and sends them to the personal Aether connector with a signature.
Are broker passwords stored in the browser?+
No. Server-side credentials are not stored as clear text in the browser. Local bridges use a separate signing secret.
Turn your data into a better trading process.
Start your private Aether Ledger workspace for free during the open beta.
Try Aether Ledger