Ploutos Help

Accounts and Connections

Read this before you connect anything so history lands in the right workspace and not the wrong one.

Read this page before you connect anything.

Most setup mistakes in Ploutos are not credential problems. They happen because the data was pointed at the wrong workspace.

The three layers that matter

  • a Ploutos account is your workspace
  • a connection is the saved provider setup inside that workspace
  • a provider account is the account reference discovered through that connection

If those three layers are clear in your head, the rest of setup is usually straightforward.

Brokers and platforms supported today

Ploutos currently supports Rithmic, Tradovate and NinjaTrader trade-history sync, plus Interactive Brokers Flex for historical import. If your broker is not listed yet, CSV import keeps the review workflow open while more providers are added.

What a Ploutos account is really for

Use a separate Ploutos account when you want a real wall between review contexts.

Good reasons:

  • eval versus funded
  • your own account versus a desk account
  • a fully different trading approach that you do not want mixed in the same journal

Weak reasons:

  • morning trades versus afternoon trades
  • longs versus shorts
  • one workspace per symbol when you are really running one book

Those are usually better handled with filters, tags, and strategy labels.

What a connection does

A connection lives under Manage Connections. It is the saved bridge between one workspace and one provider login.

That means it is responsible for:

  • validating the credentials
  • discovering available provider accounts
  • deciding which provider accounts stay enabled for sync
  • pushing future history into the selected Ploutos account

The important part is this: a connection is not global. If you build it in the wrong workspace, the sync can work and still feel wrong afterwards.

Supported connection types today:

  • Rithmic
  • Tradovate / NinjaTrader
  • Interactive Brokers Flex

For Rithmic, choose the system that matches where your trading account lives. For example, Lucid-funded accounts use LucidTrading, while Apex accounts use Apex. If your login works in R | Trader Pro but fails in Ploutos, check that the selected system and gateway match the details from your funding provider or broker. Use your Rithmic credentials, not the password for a separate funding-provider website.

NinjaTrader uses the same trade-history connection path as Tradovate. In the app, choose Tradovate / NinjaTrader when you want to connect either platform. This sync covers execution history; chart previews still depend on compatible market-data coverage.

For Tradovate simulation accounts, choose the Demo environment during sign-in. If an account is inactive, breached, or not visible in Tradovate, Ploutos may connect successfully but discover no provider accounts until the account is active again.

Interactive Brokers Flex is a historical report connection. You enter the Flex token and Flex Query ID from Interactive Brokers, and the query should return XML activity trades with account id, symbol, side, quantity, price, commission, realized P&L, and execution or trade id fields.

For the first setup, use an Interactive Brokers Activity Flex Query with the Trades section enabled. If a Trade Confirmation Flex Query keeps its period locked to Today, create an Activity Flex Query instead so Ploutos receives a real historical window.

The Activity Flex Query also needs realized P&L in the XML. If the Trades field picker does not show a P&L field, adjust the Profit and Loss setting in the query's general configuration, then return to the field list. If IBKR still does not expose a realized P&L field, include Proceeds, Cost or Cost Basis, and IB Commission; Ploutos can calculate the realized result from those fields.

If you are setting it up for the first time, use the Interactive Brokers Flex import guide. It walks through the token, query, field list, and the most common empty-report fixes.

Why provider accounts matter

One provider login can expose more than one account.

That shows up most clearly when one login gives you, for example, an eval and a funded account. In that case, Ploutos lets you refresh the discovered list and only keep the provider accounts you actually want to sync.

That is usually where people fix a confusing setup without having to rebuild everything from scratch.

For Interactive Brokers Flex, provider accounts are discovered from the account ids included in the Flex report. If the account list is empty, update the Flex Query in Interactive Brokers so the report includes account id data.

A simple example

Say you trade NQ in an eval and a funded account.

The clean setup is usually:

  • one Ploutos account for the eval
  • one Ploutos account for the funded account
  • a connection inside each workspace, with only the relevant provider account enabled

What usually goes wrong instead is one big workspace, one connection, and then confusion later about why the journal feels mixed.

Two questions people ask all the time

"I connected the broker. Why are the trades not where I expected?"

Usually one of these is true:

  • the connection was created in the wrong Ploutos account
  • the right provider account exists but is not enabled
  • you are looking at the demo workspace instead of your real one

"If I delete the connection, do I lose the journal?"

Not automatically.

Removing a connection stops future sync from that provider path. It does not mean Ploutos instantly wipes your journal history.

The order that causes the fewest mistakes

  1. Pick the right Ploutos account.
  2. Create the connection.
  3. Check the provider accounts inside it.

That order is boring, but it saves a lot of cleanup.

Next pages