RSA+
Serverside and RSA strategies
How the TradeLabs Reverse Split Arbitrage scanner streams alerts to the app, and how to build an RSA strategy that fans one signal out to every broker at once.
TradeLabs runs its own Reverse Split Arbitrage scanner and streams the resulting buy and sell alerts to the desktop app over a WebSocket. There is no Discord channel to watch, no Telegram group, and no AI keys to paste. You connect your brokers, subscribe an RSA strategy to the Serverside feed, and the app fans each alert out to every broker you checked.
An RSA strategy can take its signal two ways: the Serverside feed (the scanner, and the default), or a Discord channel that posts RSA calls. Both drive the same multi-broker fan-out. This page covers both.
RSA and the Serverside feed appear in the RSA+ build of the app. In the copy-trading build the RSA instrument and its brokers are hidden.
How the Serverside feed works
-
The feed streams alerts. The app connects to the TradeLabs alert bus over WebSocket, authenticated with your license. It heartbeats every 30 seconds and reconnects automatically with exponential backoff if the connection drops.
-
Alerts arrive already parsed. Each alert carries the ticker, side, quantity, and price. There is no chat message to read and no AI interpretation step.
-
Matching strategies pick it up. Every running strategy subscribed to the Serverside feed receives the alert.
-
Your brokers execute. The order fans out to every broker you checked on the strategy’s Brokers tab, all at once.
-
Sell alerts close positions. When you turn on Process sell signals, the feed’s close alerts exit the position. A 10-minute dedup window suppresses duplicates from re-broadcasts.
The Serverside feed is scoped to your TradeLabs account, which the desktop app already authenticates. There is nothing else to configure beyond connecting your brokers and turning the feed on.
The Serverside feed is a single switch
In the Signals hub, the Server-side feed is one on/off toggle. It needs no credentials, so there is nothing else to fill in.
The Server-side feed detail shows a single switch. When on, new alerts route into matching strategies in real time.
Under the hood the feed connects to the TradeLabs alert bus with your license, heartbeats every 30 seconds, and reconnects on its own if a heartbeat is missed. Where Discord and Telegram read messages from an external channel and use AI to extract the trade, Serverside needs neither.
Setting up an RSA strategy
The fastest start is the built-in template.
-
Open the Strategies page in the app.
-
Click Templates in the header (or Browse templates on an empty list). The Start from a template drawer opens.
-
Pick Reverse split arbitrage. It creates the strategy and opens its editor.
-
Check your brokers. On the Brokers tab, check every account you want the alerts to hit.
-
Set it to Running. Use the header toggle to turn the strategy on. Edits save automatically.
The template pins the source to Serverside, sizes at one share per broker, and pre-checks a broad set of RSA brokers (Fennel, Firstrade, Public, BBAE, DSPAC, Robinhood, Chase, Fidelity, SoFi, and WellsTrade). Uncheck the ones you have not connected, and change anything else afterward.
To build one by hand:
-
Create a new strategy. Click New strategy on the Strategies page.
-
Set the Instrument to RSA. On the General tab, pick RSA from the Instrument dropdown. This locks Direction to Both, Entry and Exit to Market, and Time in force to Day.
-
Leave the source on Serverside. In the Signal source section, the Source field shows two chips for RSA, Serverside and Discord. Leave it on Serverside.
-
Check your brokers on the Brokers tab.
-
Set the RSA controls. On the Protections tab, turn on Process sell signals for automatic exits, and optionally set Minimum profit.
-
Set it to Running with the header toggle.
Eligible brokers
RSA supports more brokers than any other instrument, because fanning out across many accounts is the whole strategy. The eligible brokers are:
Fennel, BBAE, Public, SoFi, DSPAC, Fidelity, WellsTrade, Robinhood (stocks), Chase, Firstrade, and Webull.
A broker only appears as a selectable card once you have added an account for it on the Brokers page. Brokers with no connected account are not eligible.
Maximum coverage: check every broker you have connected so one alert fires to all of them at once. Per-broker account limits are on RSA Broker Limits and Signup.
The RSA controls
Two settings drive RSA behavior. Both live on the Protections tab of the strategy editor.
Process sell signals
| State | Behavior |
|---|---|
| On | The feed’s close, STC, and sell-to-close alerts exit positions automatically. |
| Off | Only entries are processed. You close positions yourself. |
Turn this on for hands-off exits: when the feed sends a close alert, the strategy sells.
Minimum profit
A percent filter on sell alerts. When set, the strategy skips a close alert whose expected profit is below that percent. It applies to sell alerts only, not entries, so it never filters which opportunities you buy.
| Setting | Behavior |
|---|---|
| Off | Every sell alert is honored. |
| 50% | Skips any close alert projecting under 50% profit. |
Sizing
RSA sizing has one control on the Sizing tab: Per-broker size.
| Option | Behavior |
|---|---|
| Fixed · 1 share | Buys one share per broker per signal. |
| Follow signal | Uses whatever quantity the serverside feed pings (common for fractional-friendly brokers). |
For most RSA setups Fixed · 1 share is all you need.
What RSA locks
Picking RSA as the instrument locks several fields and hides whole tabs, because the strategy dictates them.
| Setting | Locked or hidden |
|---|---|
| Direction | Locked to Both |
| Entry and Exit | Locked to Market |
| Time in force | Locked to Day |
| Size | Fixed at 1 (unless you switch to Follow signal) |
| Risk & exits tab | Hidden (no stop loss, take profit, or trailing stop) |
| Filters tab | Hidden |
| AI tab | Hidden |
The Ticker field stays editable and defaults to ALL, since the feed chooses the ticker for you.
RSA does not use per-strategy stops or targets. The thesis is the reverse-split round-up, not price movement, so the editor does not surface those controls.
Multi-broker execution
RSA fans one alert out to every broker you checked, all at once.
One serverside alert fires to every broker you checked, at once.
RSA plays have limited share availability at each broker. Fanning out across many accounts increases your total position, means you are not dependent on a single broker, and means one broker rejecting the order does not sink the trade.
Retriggering
Running RSA strategies show a Retrigger button, a lightning-bolt pill on the strategy detail view and a compact icon on the strategy row. It opens a modal that first loads a read-only preview of the current serverside batch, which dispatches nothing. You filter by Buys, Sells, or Both, and by target broker, and the list shows exactly what will go out under the Will fire header.
Only the Fire N orders button sends anything, and it sends exactly the filtered rows you are looking at. If the market is closed, the app offers to schedule the strategy for U.S. market hours instead of firing into a wall of rejections.
The preview never dispatches. Firing sends the exact list on screen, matched by ticker, side, and price, so what you see is what fires.
Serverside vs Discord RSA
RSA is the one instrument where the Source field offers both Serverside and Discord. Telegram and TradingView are not offered, because they never drove these brokers.
Pick Serverside when you want the TradeLabs scanner to be the signal source and the simplest possible setup: connect brokers, turn on the feed. There is no per-source config. On the Protections tab, turn on Process sell signals for automatic exits and optionally Minimum profit.
Pick Discord when you follow a specific RSA caller whose posts you trust. Choose Discord in the Source field, then use the Channel field to search your channels or paste a channel ID. Turn on Inherit trade details from message so the app reads the ticker, direction, and timing from the message instead of the strategy defaults. When a play is posted, the app parses it and fires to your brokers.
Nothing stops you from running a Serverside RSA strategy and a Discord RSA strategy at the same time. Turn on Duplicate protection on each so the same trade does not fire twice.
If you use Discord signals, use a burner Discord account. Signal automation against your primary account carries a real risk of it being flagged or banned.
Other protections and notifications
The Protections tab also carries the general guardrails. Two worth knowing for RSA:
- Duplicate protection drops a signal that matches a recent trade on this strategy.
- Maximum trade value hard-caps the dollars per trade per broker.
On the Notifications tab, turn on Send to Discord to mirror the strategy’s events to a webhook. Leave the URL empty to inherit the global webhook from Settings, or paste a custom URL. Broker error alerts pings the webhook when a broker-side action fails.
Where to go next
- RSA+ Trading: how the reverse-split play works
- RSA Broker Limits and Signup: per-broker account limits and signup steps
- The App, Day to Day: the four broker health states in depth