Connections

Know what works now, what is coming, and what each connection is for.

Tradelevate separates private records, read-only imports, execution connectivity, and community delivery so one connection is never mistaken for another.

Connection scope
Status by role
Provider-free JournalAvailable now
Read-only recordsComing soon
Execution connectionsUnder evaluation
Community deliveryPlanned

Available now

Start with a private Journal. No provider required.

Private manual entry, file imports, and recorded-data review work without connecting a brokerage or execution provider.

Manual Journal

Record and correct a trade privately, then add the setup, context, and lesson that raw activity cannot capture.

File import

Bring supported trade files into a reviewable private record without granting provider access.

Recorded-data review

Use recorded-data TradeShield to study risk discipline after activity is in the Journal; it does not route or alter orders.

Read-only trading records

Schwab / thinkorswim — Coming soon.

Commercial review is in progress. The proposed connection would retrieve customer-authorized account, order, and transaction activity for private Journal review.

Schwab / thinkorswim

The proposed read-only integration will not place, change, or cancel orders. No customer connection is available while commercial review and verification remain incomplete.

Coming soon

Future execution connections

Execution access is a separate role.

Rithmic and Tradovate are under evaluation for future execution workflows.

Rithmic

Under evaluation as a separate future execution connection. Availability depends on provider approval, technical verification, and clear customer controls.

Under evaluation

Tradovate

Under evaluation as a separate future execution connection. Availability depends on provider approval, technical verification, and clear customer controls.

Under evaluation

Community delivery

A reviewed destination, never an automatic public feed.

Discord and Slack are planned delivery destinations. Every selected update would require explicit review; nothing is automatically public.

Discord

Planned as an optional destination for a selected update only after the customer explicitly reviews the content and destination.

Planned

Slack

Planned for communities that use Slack, with the same explicit review and destination-control boundary.

Planned

Illustrative status

Availability stays visible before a customer relies on a connection.

The connection-scope visual on this page is synthetic and illustrative. It shows product roles and intended availability labels, not a live customer account or a completed provider connection.

Trust and privacy

Review the product boundaries and how personal information is handled.

TrustPrivacy

Terms

Read the terms governing the use of Tradelevate.

Terms

Questions

Contact Tradelevate about product scope, security, or connection availability.

Contact